Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Cannot tracert IPv4 sites from IPv6 WAN with Hurricane Tunnel or Track Interface

    Scheduled Pinned Locked Moved IPv6
    14 Posts 4 Posters 2.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      fadzwa2000yahoo.com
      last edited by

      I was able to set up IPv6 WAN using Track Interface and also tried Hurricane Electric Tunnel.  I was able to navigate IPv6 sites without any problems.  However I could not tracert IPv4 sites with either set up though and could not connect to IPv4 sites.  I am missing something, can someone please assist.

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        What did your traceroute look like?

        1 Reply Last reply Reply Quote 0
        • F
          fadzwa2000yahoo.com
          last edited by

          It just Request timed out to all IP4v sites.

          1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator
            last edited by

            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?

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by

              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.

              1 Reply Last reply Reply Quote 0
              • D
                doktornotor Banned
                last edited by

                Sounds like you did something completely broken, like directing IPv4 out via the bogus _TUNNELV4 gateway.

                1 Reply Last reply Reply Quote 0
                • F
                  fadzwa2000yahoo.com
                  last edited by

                  Yes I have that active, it was just there when I added the IPv6 tunnel. Do I need to disable it?

                  1 Reply Last reply Reply Quote 0
                  • F
                    fadzwa2000yahoo.com
                    last edited by

                    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

                    1 Reply Last reply Reply Quote 0
                    • F
                      fadzwa2000yahoo.com
                      last edited by

                      Tracert for IPv4 is actually failing at the LAN gateway.  For IPv6 it works fine. Just an update.

                      1 Reply Last reply Reply Quote 0
                      • D
                        doktornotor Banned
                        last edited by

                        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.

                        1 Reply Last reply Reply Quote 0
                        • johnpozJ
                          johnpoz LAYER 8 Global Moderator
                          last edited by

                          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.

                          traceroute.png
                          traceroute.png_thumb

                          An intelligent man is sometimes forced to be drunk to spend time with his fools
                          If you get confused: Listen to the Music Play
                          Please don't Chat/PM me for help, unless mod related
                          SG-4860 24.11 | Lab VMs 2.8, 24.11

                          1 Reply Last reply Reply Quote 0
                          • F
                            fadzwa2000yahoo.com
                            last edited by

                            This is the firewall settings for my LAN net.

                            Capture.JPG
                            Capture.JPG_thumb

                            1 Reply Last reply Reply Quote 0
                            • D
                              doktornotor Banned
                              last edited by

                              Ping uses ICMP, as written above. Not TCP. Not UDP.

                              1 Reply Last reply Reply Quote 0
                              • johnpozJ
                                johnpoz LAYER 8 Global Moderator
                                last edited by

                                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..

                                An intelligent man is sometimes forced to be drunk to spend time with his fools
                                If you get confused: Listen to the Music Play
                                Please don't Chat/PM me for help, unless mod related
                                SG-4860 24.11 | Lab VMs 2.8, 24.11

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post
                                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.