-
Notifications
You must be signed in to change notification settings - Fork 247
Add section about using authbind #213
Comments
Using https://blogs.oracle.com/sduloutr/entry/binding_a_server_to_privileged |
I did read the technical explanation and it does not sound credible; if this was a java issue binding to lower ports how does it bind to 514 then? ok after some tinkering I discovered that the OVA which ships with 2.1.0+62db7e0, codename Smuttynose uses authbind to make it work on 514 so that's how they get it going. Hence I only had to add UDP 162 to the authbind-by-port config and that allowed me to run the snmp plug-in as native 162 listener. Remember to use "!" when specifying a UDP port for authbind-by-port: touch '/etc/authbind/byport/!162' Remember to surround the path with '' because of the ! used in front of the numeric port for UDP. If you do NOT use ! then the port will be TCP and snmp plug-in won't work since snmp is UDP to begin with. Hope that help others to get their plug-in going for native snmp.
|
@bubba198 Please don't hijack this issue. Privileged ports are not a "Java issue" but simply restriction of the network stack of the operating system. You can read up on privileged ports at https://www.w3.org/Daemon/User/Installation/PrivilegedPorts.html |
as we do not have any information in our documentation for authbind or how to run inputs on unpriviliges ports we should have at least a small comment in the FAQ. The final goal would be to have a page in the configuration area that explains how to use this all and how to configure the different options that can be found in: #213
As we do not have any information in our documentation for `authbind` or how to run inputs on unprivileged ports we should have at least a small comment in the FAQ. The final goal would be to have a page in the configuration area that explains how to use this all and how to configure the different options that can be found in: #213
Another good explanation: https://www.reddit.com/r/graylog/comments/5qcjw0/using_authbind_to_run_graylog/ |
Or just add a port forward:
This seems a lot more straightforward than having to install and configure authbind. |
@miztroh Yes, just as the FAQ already mentions: |
@joschi Bingo. |
As we do not have any information in our documentation for `authbind` or how to run inputs on unprivileged ports we should have at least a small comment in the FAQ. The final goal would be to have a page in the configuration area that explains how to use this all and how to configure the different options that can be found in: Graylog2#213
People regularly struggle with the concept of privileged ports and how to allow Graylog to bind to these (e. g. port 514 for syslog).
The text was updated successfully, but these errors were encountered: