TTR Networks

Common network ports and protocol numbers

The ports, protocol numbers and addresses that turn up in firewall rules, packet captures and router configs. Port numbers are the IANA assignments unless marked (convention), meaning a widely used default rather than an official assignment. "Both" means the service is assigned for TCP and UDP.

Routing and network control

PortTransportServiceNotes
179TCPBGPFirewall it to your configured neighbours only.
646BothLDP (MPLS label distribution)UDP for discovery, TCP for sessions.
520UDPRIPRIPng uses UDP 521.
3784UDPBFD, single-hop3785 for BFD echo, 4784 for multihop BFD.
1985UDPHSRPCisco's gateway redundancy protocol. VRRP isn't a port: it's IP protocol 112.
323TCPRPKI to router (RTR)Validators commonly listen on 3323 (Routinator) or 8282 (StayRTR) (convention).

Management and monitoring

PortTransportServiceNotes
22TCPSSHAlso SCP and SFTP.
23TCPTelnetUnencrypted; disable it.
830TCPNETCONF over SSH
161UDPSNMPPolling the device.
162UDPSNMP trapsSent by the device to the collector.
514UDPSyslog6514 for syslog over TLS.
123UDPNTP
49TCPTACACS+
1812, 1813UDPRADIUSAuthentication, accounting.
2055UDPNetFlow (convention)Collectors also often use 9995 or 9996.
4739BothIPFIXThe standardised successor to NetFlow v9.
6343UDPsFlow
69UDPTFTPStill used to boot and provision devices.

Addressing and naming

PortTransportServiceNotes
53BothDNSUDP for most queries, TCP for large answers and zone transfers.
853TCPDNS over TLSDNS over HTTPS uses 443.
67, 68UDPDHCPServer 67, client 68.
547, 546UDPDHCPv6Server and relay 547, client 546.
43TCPWHOISAlso how IRR databases are queried. RDAP, its successor, runs over HTTPS.

Web, VPN and tunnels

PortTransportServiceNotes
80TCPHTTP
443TCP, UDPHTTPSUDP 443 is HTTP/3 (QUIC).
8080TCPAlternative HTTP (convention)
500UDPIKE (IPsec key exchange)
4500UDPIPsec NAT traversalESP wrapped in UDP when there's NAT on the path.
51820UDPWireGuard (convention)The default listen port; any port works.
1194UDPOpenVPNCan also run over TCP.
1701UDPL2TP
4789UDPVXLAN
6081UDPGeneve

IP protocol numbers

Some protocols don't use ports at all: they ride directly on IP, identified by the protocol number in the IPv4 header (the Next Header field in IPv6). A firewall rule for these matches the protocol, not a port.

NumberProtocolNotes
1ICMPPing, traceroute replies, "fragmentation needed".
2IGMPIPv4 multicast group membership.
4IP in IPIPv4 encapsulated in IPv4.
6TCP
17UDP
41IPv6 in IPv46in4 tunnels.
47GRE
50ESPIPsec encryption.
51AHIPsec authentication only.
58ICMPv6Includes neighbour discovery; don't block it wholesale.
88EIGRP
89OSPFOSPFv2 and OSPFv3.
103PIMMulticast routing.
112VRRP
132SCTP

IS-IS uses none of these: it runs directly over the link layer, not over IP.

Multicast addresses you'll see in captures

IPv4IPv6Who listens
224.0.0.1ff02::1All hosts / all nodes on the link
224.0.0.2ff02::2All routers on the link
224.0.0.5ff02::5All OSPF routers
224.0.0.6ff02::6OSPF designated routers
224.0.0.9ff02::9RIP routers
224.0.0.18ff02::12VRRP
—ff02::1:2DHCPv6 servers and relays
—ff02::1:ffXX:XXXXSolicited-node address (neighbour discovery)

EtherTypes

ValueCarries
0x0800IPv4
0x0806ARP
0x86DDIPv6
0x8100802.1Q VLAN tag
0x88A8802.1ad (QinQ) outer tag
0x8847MPLS
0x88CCLLDP

To see which of these a host is actually using, ss -tulpn on Linux lists listening sockets, and tcpdump -ni eth0 port 179 (or any port) shows the traffic itself — see Linux Network Connectivity and Packets That Never Come Back. For writing firewall rules around these, see Zone-based firewall on VyOS.