Cannot tracert IPv4 sites from IPv6 WAN with Hurricane Tunnel or Track Interface
-
And did you allow ipv4 at your interface rules?
I have been running he tunnel for years, and played with native from isp - went back to tunnel for stability and easy of getting and using a /48 Never an issue with ipv4 anything having ipv6 enabled.
Are you trying from pfsense or a client behind pfsense? Your saying as soon as you disable ipv6 the ipv4 starts working?
-
Timed out where?
IPv6 has no relation to IPv4 in that regard. What you've described thus far, I don't see anywhere you could have impacted your v4 traffic.
-
Sounds like you did something completely broken, like directing IPv4 out via the bogus _TUNNELV4 gateway.
-
Yes I have that active, it was just there when I added the IPv6 tunnel. Do I need to disable it?
-
I can navigate both IPv4 and IPv6 sites. I can also ping from the diagnostics in pfsense but I fail from a client behind pfsense on the pc
-
Tracert for IPv4 is actually failing at the LAN gateway. For IPv6 it works fine. Just an update.
-
Kindly post the System - Routing - Gateways screeshot.
@fadwa20@invalid.com:
Tracert for IPv4 is actually failing at the LAN gateway.
What LAN gateway? There should be no gateway set for LAN on pfSense.
-
And your lan rules.. If you don't allow icmp tracert will normally die
So for example.. I can traceroute just fine, if I change my lan rule to only allow tcp/udp vs any which would include icmp.. Then the trace dies.. But since my ipv6 rules is not limited then that works.
-
This is the firewall settings for my LAN net.
-
Ping uses ICMP, as written above. Not TCP. Not UDP.
-
That is not the default setting.. So clearly at some point you said, I only want tcp/udp outbound – so that would break ping/traceroute, etc..
