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

    Upgrade from 2.2.2 > 2.2.3 breaks HE.net tunnel; easy resolution

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    1 Posts 1 Posters 495 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.
    • paulskavP
      paulskav
      last edited by

      After upgrading, IPv6 stopped routing through the firewall (example from a Windows machine):

      IPv6 is through an HE.net tunnel.

      Ping…
      C:\Windows\system32>ping ipv6.google.com

      Pinging ipv6.l.google.com [2607:f8b0:4009:807::100e] with 32 bytes of data:
      Destination net unreachable.
      Destination net unreachable.
      Destination net unreachable.
      Destination net unreachable.

      Tracert…
      C:\Windows\system32>tracert ipv6.google.com

      Tracing route to ipv6.l.google.com [2607:f8b0:4009:807::100e]
      over a maximum of 30 hops:

      1    <1 ms    <1 ms    <1 ms  <redacted.lan.if>[2001:xxxx:xxxx:xxx::1]
        2  Destination net unreachable.

      Trace complete.

      The fix was to disable the HE.net IPv6 gateway (In System > Routing > edit "HEV6_TUNNELV6 (default)"). Select "Disable this gateway" & apply. Then, un-select "Disable this gateway" & apply.

      I noticed this in the previous upgrade to 2.2.2 but wasn't sure at the time which fiddle did the trick. This time, the above is all I did and it worked right away. No issue with RA or anything that I can tell (I rebooted the Windows PC as a quick check before applying the above fix).</redacted.lan.if>

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