bitlvl
EN

Port 33434 traceroute · UDP

The base UDP port of traceroute: Unix traceroute sends probes to 33434 and increments per hop (33434–33534), expecting ICMP "port unreachable" from the destination because nothing listens there.

Port33434
TransportUDP
Servicetraceroute — Base port for UDP traceroute
CategoryInfrastructure
Rangeregistered (1024–49151)
EncryptedNot applicable
ExposureDesigned to face the internet

What runs on port 33434

The base UDP port of traceroute: Unix traceroute sends probes to 33434 and increments per hop (33434–33534), expecting ICMP "port unreachable" from the destination because nothing listens there. A firewall that blocks this range inbound makes traceroute end in asterisks at your host, even though the host is up. Windows tracert uses ICMP echo instead; mtr and traceroute -I/-T use ICMP or TCP.

Software that uses it: traceroute · mtr · tcptraceroute · network diagnostics in monitoring tools

Should port 33434 be open?

Designed to face the internet. This port exists to be reachable from anywhere, so the usual question is not whether to open it but how the service behind it is configured and patched.

Check port 33434

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

# from another machine: is it reachable?
nc -zuv host 33434
sudo nmap -sU -p 33434 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 33434

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

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

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

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=33434 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 33434" 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 33434 TCP or UDP?

UDP. traceroute is datagram-based; TCP 33434 is not used by it.

Is port 33434 encrypted?

Not applicable. The protocol carries no application data worth encrypting, or encryption is handled at another layer.

How do I check whether port 33434 is open?

On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 33434 and which process. From another machine, nc -zv host 33434 -u or nmap -p 33434 -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 traceroute 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.