| Port | 179 |
|---|---|
| Transport | TCP |
| Service | BGP — Border Gateway Protocol |
| Category | Infrastructure |
| Range | well-known (0–1023, needs root to bind on Unix) |
| Encrypted | No, plaintext |
| Exposure | Internet-facing only with authentication and care |
Port 179 BGP · TCP
BGP: the routing protocol between autonomous systems, and also between routers inside large networks and in Kubernetes CNIs like Calico and in MetalLB.
What runs on port 179
BGP: the routing protocol between autonomous systems, and also between routers inside large networks and in Kubernetes CNIs like Calico and in MetalLB. Sessions are TCP on 179 between explicitly configured peers; anything else connecting should be dropped. TCP-MD5 or TCP-AO authentication and the GTSM TTL hack protect the session itself.
Software that uses it: FRRouting · BIRD · GoBGP · Cisco/Juniper/Arista · Calico · MetalLB
Should port 179 be open?
Internet-facing only with authentication and care. It can be exposed when the service behind it is authenticated, rate-limited and kept up to date; most deployments are better off behind a VPN, an allow-list or a reverse proxy.
- A session stuck in Active or Connect usually means 179 is filtered one way or the peer address is wrong.
- Filter prefixes in both directions; a missing export filter is how route leaks happen.
Check port 179
# on the host: is anything listening, and which process? ss -ltnp 'sport = :179' sudo lsof -i :179 # from another machine: is it reachable? nc -zv host 179 nmap -p 179 host curl -v telnet://host:179 # raw TCP connect test, Ctrl-C to leave
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 179
# ufw (Ubuntu/Debian) sudo ufw allow from 10.0.0.0/8 to any port 179 proto tcp sudo ufw deny 179/tcp # nftables nft add rule inet filter input ip saddr 10.0.0.0/8 tcp dport 179 accept nft add rule inet filter input tcp dport 179 drop # iptables (legacy) iptables -A INPUT -p tcp --dport 179 -s 10.0.0.0/8 -j ACCEPT iptables -A INPUT -p tcp --dport 179 -j DROP # firewalld sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=179 protocol=tcp accept'
Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 179" 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 179 TCP or UDP?
TCP. BGP is a connection-oriented protocol; there is no UDP service on 179 by default (a scanner reporting UDP 179 open is usually seeing a filtered port).
Is port 179 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 179 is open?
On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 179 and which process. From another machine, nc -zv host 179 or nmap -p 179 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).
Can BGP 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.