Can't traceroute



  • Just upgraded to 2.1.3, and traceroute is broken.

    From behind pfsense, I get asteriks from the next hop beyond pf.

    From an ssh prompt in pfsense, I get this:

    traceroute to wstd.lithium.com (208.74.204.62), 64 hops max, 52 byte packets
    traceroute: sendto: Operation not permitted
    1 traceroute: wrote wstd.lithium.com 52 chars, ret=-1
    *traceroute: sendto: Operation not permitted
    traceroute: wrote wstd.lithium.com 52 chars, ret=-1
    *traceroute: sendto: Operation not permitted
    traceroute: wrote wstd.lithium.com 52 chars, ret=-1
    ^C

    I have made zero changes to rules or any configs.  Any idea what it could be?  I created a rule to explicitly allow all icmp from all hosts, still wouldn't work.  (Have since deleted said rule because it made me paranoid).  Not sure what else to try.

    Thanks.


  • Rebel Alliance Global Moderator

    And what rules do you have?  Traceroute works fine for me. Both from behind and from pfsense.



  • Also what does your routing table look like?

    "operation not permitted" generally would mean it's getting blocked, but you'd have to try to block egress traffic from the firewall itself, would require floating block rules.



  • @johnpoz:

    And what rules do you have?  Traceroute works fine for me. Both from behind and from pfsense.

    Actually I think this may have started when I configured a VPN using the wizard, although the VPN is not in use.




  • @cmb:

    Also what does your routing table look like?

    "operation not permitted" generally would mean it's getting blocked, but you'd have to try to block egress traffic from the firewall itself, would require floating block rules.

    No special routes configured at all, everything should be bone stock.  LAN interface routed through WAN interface, WAN interface is bridged to my ISP's network via a cable modem.