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

    ULA routing stops when trackinterface is down

    IPv6
    4
    32
    1.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.
    • G
      gwabber @NightlyShark
      last edited by

      @NightlyShark the addresses themselves unfortunately... thanks for your help so far!

      Other weird thing; I just disabled the default WAN ipv6 gateway just for shits and giggles. Now the ULA's were still reachable....

      NightlySharkN 1 Reply Last reply Reply Quote 0
      • NightlySharkN
        NightlyShark @gwabber
        last edited by NightlyShark

        @gwabber 😓 🚿😲 It's one of those "did you turn it on and off" things, then...

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

          @NightlyShark I really don't know anymore 😆. Only difference with pulling the plug on my modem was that the GUA's stayed active, only mu IPv6 internet was down. When I pulled the plug on my modem, the GUA's dissapeared. My girlfriend is using Netflix right nog, so I can't pull the plug on my modem. Tomorrow I will try that!

          The show continues...

          the otherT 1 Reply Last reply Reply Quote 1
          • the otherT
            the other
            last edited by the other

            hey..pantpant...there...jk ;)

            Just went in the cellar, pulled the plug (LAN cable between fritzbox (internetrouter) and pfsense's WAN.
            Then run back upstairs. Rebootet pfsense. Rebooted pc.
            Waited.
            Tried ip a on pc > shows no GUA (of course) but its ULA (static mapping in pfsense).
            Logged into pfsense (IPv4), tried ifonfig > no GUA, but all ULAs still there. ok
            Then went to Status > Interfaces: same, no GUA (I get dynmaic prefixes from my ISP here as well, a nice /56) but ULAs as set under RA settings. ok.

            then tried to ping my v6 devices (some of them, same and different vlans). reached all of them with their ULA.ok.

            then tried to reach them with firefox, entering my https://ULAs. Reached all of them.ok.

            So: after pulling the switch, rebooting, confirming that no GUAs are given out to anything in pfsense and pfsense itself...routing ULAs still works as if I never even pulled that LAN cable (and DID NOT RUN THOSE STAIRS, dammit). ;)

            Then went downstairs again, just put LAN cable between fritzbox and pfsense back in, crawled upstairs again...tadaa: no reboot, still getting my GUA now for all interfaces with active v6 and all devices get their GUA as well (as another ip a showed).

            I tried all that with their ULA, not DNS name...

            At least I got my pe today. 😁

            the other

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

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

              Maybe the problem is related to that patch? Now who has that patch and who doesn't.

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

                @Bob-Dig hey there,
                indeed, after the 2.72 "bug" that broke ULA routing I downloaded the patch (assuming that's the one you meant) and applied it.
                It worked and I just looked: must have reverted it sometime ago, it is not "active" in my system/patches view...
                But if I remember correctly: wasn't the problem to that patch, that even with v6 online and working one could not route ULAs only? Aliases and VIPs were somehow not working (which did prior to 2.7.2). But it's Monday and late and I might recall that incorrectly. :)

                the other

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

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

                  @the-other Hi, the problem with that patch is that you can not get IPv6 working on another interface after it is applied. Now has @gwabber this patch too? If yes, it is not related to that patch.

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

                    @Bob-Dig yes, I recall that there was a problem with the patch now...I read that and tried as well with no positive result...couldn't apply v6 to another interface as well (one that was pure v4 before). Maybe that's why I reverted it.
                    And funfact: the user @gwabber started that post back then as well (about the 2.7.2 ULA problem)...just read that one. :)

                    Here: 2.7.2 broke ULA routing thread

                    the other

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

                    1 Reply Last reply Reply Quote 0
                    • the otherT
                      the other @gwabber
                      last edited by

                      @gwabber yes, when I pulled the plug (before rebooting) GUAs stayed active (shown with ifconfig and Status/Interfaces) as well...same when I just deactivted v6 on my Fritzbox...but also: in all scenarios ULA routing worked.
                      So: do you have said patch applied on your system?

                      the other

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

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

                        @the-other thanks for trying the options! I have the said patch active on my system.

                        Weird that when you pull the plug, your GUA's stay active. Mine disappear completely. What could be diffrent in the default config...

                        Tomorrow is my day off, I'm gonna try the different scenario's!

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

                          @gwabber allright. Girlfriend went to bed. I went behind my pc.

                          I set, for testpurposes, the gateway on "Disable Gateway Monitoring Action". I pulled the plug. My GUA's were gone again.

                          I visited one of my servers with the ULA. I could reach it... same for my pi and stuff. One weird thing. My pings to those servers became slower and timed out once in a while.... What that's about... I don't know.

                          So it works, like most of it, but not what it's supposed to be I think...

                          EDIT
                          never mind... it was a fluke. It broke down again. I don't get it anymore

                          EDIT2:
                          With the fake gateways it works! I still have the feeling that it should be easier then creating a fake gateway per LAN, but it works for now :)

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post