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

    ULA routing broke after 2.7.2 update

    Scheduled Pinned Locked Moved
    IPv6
    6
    39
    3.4k
    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.
    • Bob.DigB
      Bob.Dig LAYER 8 @gwabber
      last edited by Bob.Dig

      @gwabber Maybe this patch has a problem and someone else can verify this:
      Today I tried to add IPv6 to another interface via Track Interface, no matter what I did, the interface didn't got an IPv6-address. I then disabled the auto-patching, rebooted and there was the IPv6-address. I then re-enabled auto-patching and everything still works as expected after another reboot.

      G 1 Reply Last reply Reply Quote 0
      • G
        gwabber @Bob.Dig
        last edited by

        @Bob-Dig I looked into my firewall and I replicated your issue, so you are not the only one! I guess it is a bigger issue.

        Bob.DigB 1 Reply Last reply Reply Quote 1
        • Bob.DigB
          Bob.Dig LAYER 8 @gwabber
          last edited by

          @gwabber Thanks. So I let @marcosm know, if he isn't already aware of it.

          the otherT 1 Reply Last reply Reply Quote 0
          • the otherT
            the other @Bob.Dig
            last edited by

            @Bob-Dig Hey there, same here: had v6 on 3 out of 9 (v)Interfaces running. Read your post and tried adding another one.
            Set everything under Interfaces exactly as the others (track Interface > WAN), picked a Subnet prefix ID, picked a fitting ULA prefix etc...

            first: interface does not get an GUA IPv6, so yeah, same here
            second: other interface's GUA v6 was gone, took around 5 minutes til they were back...
            third: in that time no DNS via unbound, ping with IP to 8.8.8.8 okay, ping to google.com...not okay. Came back eventually.

            So after 15 minutes an 2-3 try outs: everything working except that "new" v6 interface, which does not get GUA or ULA. Unbound has to be started manually again.
            Even disabling and enabling the interface again did not get a v6...

            the other

            pure amateur home user, no business or professional background
            please excuse poor english skills and typpoz :)

            1 Reply Last reply Reply Quote 1
            • M
              marcosm Netgate
              last edited by

              The original issue/patch does not affect what address is added to the interface. If the interface that is set to track does not get an IPv6 address, that is a separate issue that would need its own redmine report (with exact steps to reproduce). If you reproduce the issue, does Status > Interfaces show the IPv6 address?

              G Bob.DigB 2 Replies Last reply Reply Quote 0
              • G
                gwabber @marcosm
                last edited by

                @marcosm thanks for your reply!

                Just checked it. The statuspage also doesn't show the IP address.

                1 Reply Last reply Reply Quote 0
                • Bob.DigB
                  Bob.Dig LAYER 8 @marcosm
                  last edited by Bob.Dig

                  @marcosm said in ULA routing broke after 2.7.2 update:

                  The original issue/patch does not affect what address is added to the interface. If the interface that is set to track does not get an IPv6 address, that is a separate issue that would need its own redmine report (with exact steps to reproduce). If you reproduce the issue, does Status > Interfaces show the IPv6 address?

                  This patch is the reason that one can not set another interface to Track Interface. Or to be more precise, that interface will not get GUA-IPv6. Disabling this patch will fix this. So I don't think that there should be another redmine?

                  I have uninstalled the patch and removed any ULAs (and VIPs) I had, so I am not able to do much more testing on this.

                  G 1 Reply Last reply Reply Quote 1
                  • G
                    gwabber @Bob.Dig
                    last edited by

                    @Bob-Dig @marcosm It is indeed typical the problems started with the fix. I have not enough experience with pfsense or BSD to know why this occurs.

                    1 Reply Last reply Reply Quote 0
                    • M
                      marcosm Netgate
                      last edited by marcosm

                      Disabling "Auto Apply" for the patch and rebooting is not a good test since that option does not affect reboots and it may have worked after the reboot because of something unrelated. A more proper test could be to reapply interface settings before and after the patch to see if there's any difference with the IPv6 addresses.

                      G 1 Reply Last reply Reply Quote 0
                      • G
                        gwabber @marcosm
                        last edited by

                        @marcosm indeed... without the reboot, my interface still doesnt get an IPv6 address on " track"

                        1 Reply Last reply Reply Quote 1
                        • Bob.DigB Bob.Dig referenced this topic on
                        • the otherT the other referenced this topic on
                        • S Sevi referenced this topic on
                        • S Sevi referenced this topic on
                        • Bob.DigB Bob.Dig referenced this topic on
                        • w0wW w0w referenced this topic on
                        • First post
                          Last post