06 Sep 2024 11:19 AM
I have tried setting up SNMP traps on port 162.
I can see the traps are hitting the Activegate instance as these are displaying in TCP dump.
The extension for SNMP traps is repeatedly displaying an error in the logs:
Failed to start listen on port::162 err: listen udp :162: bind: permission denied
Do we need to open up port 162 on the activegate instance?
Can this be done in custom.properties?
Or is there a permissions issue using ports under 1024?
If anyone has a workaround for this please let me know
Solved! Go to Solution.
06 Sep 2024 11:42 AM
To listen on port 162, you have to have root permission. There are some ways to escaping that, and I believe the standard way ActiveGate is installed doesn't require additional configuration.
Additionally, there might be another program already listening on port 162. Run the following command to find out if that is the case:
06 Sep 2024 12:04 PM - edited 06 Sep 2024 12:04 PM
Hi Antonio,
Thank you for the reply - I have tried a netstat and nothing else appears to be using this port.
It looks like we have a specific user running activegate - is it possible to give this user permissions for port 162 - or would I need to pick a new port > 1024 to allow SNMP traps to be handled?
06 Sep 2024 12:25 PM
You have several options here: