Well-known · Cross-platform

161 SNMP

TCP Assigned
UDP Yes
SCTP
DCCP

What it is

Simple Network Management Protocol polling of device metrics.

When / why

Monitoring of network gear/servers. Use SNMPv3; never expose v1/v2c to untrusted networks.

Protocol status detail

TransportStatusMeaning
TCP Assigned Assigned by IANA, but not standardized, specified, or widely used on this port.
UDP Yes Assigned by IANA and standardized, specified, or widely used on this port.
SCTP Not applicable for this transport.
DCCP Not applicable for this transport.

Port range

Well-known (0–1023). System port for a core service. On Unix-like systems, binding it requires superuser privileges.

Browse all ports →

Firewall rules for port 161

Copy-ready inbound rules for the active transports. Replace every <source> placeholder with the specific host, subnet, or CIDR that should reach this port.

⚠ High exposure risk — this service should never be reachable from untrusted networks. Scope the rule to a management subnet or VPN.

ufw

sudo ufw allow proto udp from <source> to any port 161

Allow UDP 161 (SNMP). Replace <source> with the network/host that should reach it.

firewalld

sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<source>" port port="161" protocol="udp" accept'

Allow UDP 161 (SNMP) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

nft add rule inet filter input ip saddr <source> udp dport 161 accept

Allow UDP 161 (SNMP). Assumes table 'inet filter' with an 'input' chain.

iptables

sudo iptables -A INPUT -p udp -s <source> --dport 161 -j ACCEPT

Allow UDP 161 (SNMP). Persist with iptables-save/netfilter-persistent.

Azure NSG

az network nsg rule create -g <resource-group> --nsg-name <nsg> -n Allow-snmp-161 --priority 1000 --access Allow --direction Inbound --protocol UDP --source-address-prefixes <source> --destination-port-ranges 161

Inbound rule for 161 (SNMP). Set <source> to a CIDR; lower priority number = higher precedence.

AWS Security Group

aws ec2 authorize-security-group-ingress --group-id <sg-id> --ip-permissions IpProtocol=udp,FromPort=161,ToPort=161,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound UDP 161 (SNMP). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

gcloud compute firewall-rules create allow-snmp-161 --direction=INGRESS --action=ALLOW --rules=udp:161 --source-ranges=<source-cidr> --network=<network>

Ingress rule for 161 (SNMP). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow SNMP 161/UDP" dir=in action=allow protocol=UDP localport=161 remoteip=<source>

Inbound UDP 161 (SNMP). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow SNMP 161/UDP" -Direction Inbound -Action Allow -Protocol UDP -LocalPort 161 -RemoteAddress <source>

Inbound UDP 161 (SNMP). Replace <source> with a host or subnet.

Rules are generated only for transports marked active for this port. They default to an inbound allow with an explicit source placeholder — never any. Review direction, scope, and rule precedence before applying in production.