bitlvl
EN

Port 161 SNMP · UDP

SNMP: how monitoring systems read counters from switches, routers, printers and servers (get/walk), and how some write to them (set).

Port161
TransportUDP
ServiceSNMP — Network monitoring
CategoryMonitoring and logging
Rangewell-known (0–1023, needs root to bind on Unix)
EncryptedNo, plaintext
ExposurePrivate network or VPN only

What runs on port 161

SNMP: how monitoring systems read counters from switches, routers, printers and servers (get/walk), and how some write to them (set). Versions 1 and 2c authenticate with a plaintext "community string", usually still "public"; only SNMPv3 has real authentication and encryption. Reachable from the internet it hands out interface tables, routing tables and device models to anyone.

Software that uses it: Net-SNMP (snmpd, snmpwalk) · LibreNMS · Zabbix · Prometheus snmp_exporter · PRTG

Should port 161 be open?

Private network or VPN only. Nothing good comes from this port being reachable from the internet. Keep it on an internal network, reach it over a VPN or an SSH tunnel, and firewall it from everything that does not need it.

Check port 161

# on the host: is anything listening, and which process?
ss -lunp 'sport = :161'
sudo lsof -i :161

# from another machine: is it reachable?
nc -zuv host 161
sudo nmap -sU -p 161 host

A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.

Allow or block port 161

# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 161 proto udp
sudo ufw deny 161/udp

# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 udp dport 161 accept
nft add rule inet filter input udp dport 161 drop

# iptables (legacy)
iptables -A INPUT -p udp --dport 161 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p udp --dport 161 -j DROP

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=161 protocol=udp accept'

Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 161" with no source is just "open".

Related ports

Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.

Questions

Is port 161 TCP or UDP?

UDP. SNMP is datagram-based; TCP 161 is not used by it.

Is port 161 encrypted?

No, plaintext. Anything sent over it can be read by whoever is on the path, so it belongs on a trusted network or inside a VPN or SSH tunnel.

How do I check whether port 161 is open?

On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 161 and which process. From another machine, nc -zv host 161 -u or nmap -p 161 -sU host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).

Can SNMP run on a different port?

Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.