PfSense not replying to UDP traceroute on WAN
-
That did the trick! Thanks!
-
One weird thing I'm seeing is with Windows tracert which uses ICMP, pfSense sends a TTL expired reply when the request TTL is < 6, so I get a weird result where my pfSense firewall shows up 5 times. I don't want to reject ICMP packets, and I don't see a way to configure the TTL threshold. Anyone know of a remedy?
-
I would need to see a packet capture of that.
-
Here you go. I've anonymized the pcap so 1.1.1.1 is the host running the traceroute, and 2.2.2.2 is my pfSense firewall. Looks like I was wrong and it stops sending a TTL expired, and starts replying, when the TTL is greater than 4.
Edit: Oops, there's a 1:1 NAT and the replies are probably the routers in between and the host the packets are being NATted to.
Edit: Packet capture on the LAN interface confirms this theory.
-
OK you're kind of all over the place. You state that pfSense responds in the negative with a TTL > 4. What, exactly am I looking for?
What interface was that pcap taken on?
Anonymizing MAC addresses? Really? I can't help you.
-
"One weird thing I'm seeing is with Windows tracert which uses ICMP, pfSense sends a TTL expired reply when the request TTL is < 6"
From where to where?
I trace through pfsense to internet all the time, never seen such a thing..
-
What was the resolution? I am having the same problem as in topic. Tracing PFSense from outside PFSense seems that it is not recognizing traces at all. Ping works fine. It can't be true that PFSense does not work with Traceroute in UDP mode... can it?
Ax.
-
Ah screenshot is missing - prob got lost when they updated the forum... You juts need to set a reject rule on your wan for the udp ports. When get back from lunch can post up a screenshot.
-
Got it... I think. I created Rejected rule for UDP between ports 33434 and 33634. It actually resolves the issue.
-
yup... that is all you need to do.
edit: for the next guy that finds this thread... I will post up screenshot of the rule
