Port reference › Network infrastructure
Port 161 · SNMP
Network device monitoring
UDP Network infrastructure Exposure risk: High
What is port 161 used for?
SNMP agent port for querying switch, router and server status. Network management systems poll devices through it.
Well-known port (0-1023): opening it on Linux needs root (or CAP_NET_BIND_SERVICE).
Security notes
v1/v2c community strings are effectively plaintext passwords. Change the default public/private, prefer SNMPv3 (auth + encryption), and allow only NMS server IPs.
Allow port 161 through the firewall
This port is risky to expose, so the commands below allow only the IPs you specify.
# Replace 203.0.113.10/32 with the IP or network you want to allow
sudo ufw allow from 203.0.113.10/32 to any port 161 proto udp
sudo ufw status # Replace 203.0.113.10/32 with the IP or network you want to allow
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="203.0.113.10/32" port port="161" protocol="udp" accept'
sudo firewall-cmd --reload # Replace 203.0.113.10/32 with the IP or network you want to allow
sudo iptables -A INPUT -p udp -s 203.0.113.10/32 --dport 161 -j ACCEPT # Replace 203.0.113.10/32 with the IP or network you want to allow
New-NetFirewallRule -DisplayName "Allow UDP 161" -Direction Inbound -Protocol UDP -LocalPort 161 -RemoteAddress 203.0.113.10/32 -Action Allow # Replace sg-0123456789abcdef0 with your security group ID
aws ec2 authorize-security-group-ingress --group-id sg-0123456789abcdef0 --protocol udp --port 161 --cidr 203.0.113.10/32 Check whether port 161 is open
sudo ss -ulpn | grep ':161 ' netstat -ano | findstr :161 nc -zuv SERVER 161
# UDP can look "open" even with no reply, so do not trust this alone.
# Testing with a real client for the service is more reliable. sudo lsof -i :161 Ports used together
- 162 SNMP trap · Device alert receiver