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

    ipv6 broken: radvd: can't join ipv6-allrouters on <interface>

    Scheduled Pinned Locked Moved 2.5 Development Snapshots (Retired)
    144 Posts 15 Posters 60.5k 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.
    • w0wW
      w0w
      last edited by

      @jimp, any news? Did Netgate choose the FreeBSD version already? 12.1 is released a few days ago.

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        We are aware of the release (The FreeBSD Release Engineer is a Netgate employee :-)

        12.1 is the current plan but there may be some parts picked back from stable. We'll see how things shake out.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 1
        • w0wW
          w0w
          last edited by

          @jimp Hmm, missed that reddit post, thanks a lot for the information!

          ? 1 Reply Last reply Reply Quote 0
          • ?
            A Former User @w0w
            last edited by

            @w0w said in ipv6 broken: radvd: can't join ipv6-allrouters on <interface>:

            @jimp Hmm, missed that reddit post, thanks a lot for the information!

            Any clue why #9577 is not showing up on the issue list anymore?

            It might be better to split the redmine issue into two since there is spamming log issue and a FreeBSD 12.0 issue?

            • In net/radvd of Ports, remove logging of "IPv6 forwarding" in interface.c since "check_ip6_iface_forwarding" routine is stubbed out in "radvd/device-bsd44.c". This is unrelated to the FreeBSD 12 version

            • Upgrade network interfaces including netinet6/in6_mcast.c to code in RELENG/12.1. The mcast changes in 12.1 are extensive enough to both ipv4 and ipv6 to prohibit back-porting (I tried). This second issue resolves the "can't join ipv6-routers" logging and permits RADVD to function beyond 24 hours.

            1 Reply Last reply Reply Quote 0
            • S
              strangegopher
              last edited by

              so to fix this we need to update to 12.1 and that has 25% perf hit. ooof 😦

              w0wW 1 Reply Last reply Reply Quote 0
              • w0wW
                w0w @strangegopher
                last edited by

                @strangegopher
                Not so bad, I think. May be it affects only maximum throughput, who knows, no further information at the moment. Also as @jimp mentioned, they can apply some fixes by picking up some parts from stable.

                @rschell
                I've never checked was it listed before or not, but i don't see any changes made about that. May be it's because target version is missing?

                1 Reply Last reply Reply Quote 0
                • havastamasH
                  havastamas
                  last edited by

                  Any news about the problem/patch? I have this bug too, but too lazy/dont have time to go back to 2.4.4...

                  1 Reply Last reply Reply Quote 0
                  • w0wW
                    w0w
                    last edited by

                    @havastamas
                    Waiting for the new builds based on 12.1 version of FreeBSD. I don't know if there any target date available.
                    Currently you can use workaround published by @kiokoman. I use it with cron package. Just running command every hour.
                    f0939bfb-bc3d-41b2-84cd-8685ca3d6ab1-изображение.png

                    killall radvd && sleep 5 && /usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog
                    
                    havastamasH 2 Replies Last reply Reply Quote 0
                    • havastamasH
                      havastamas @w0w
                      last edited by

                      @w0w This workaround is much better than reboot the firewall every 6 hours, to get ipv6 working. Thank you!

                      1 Reply Last reply Reply Quote 0
                      • havastamasH
                        havastamas @w0w
                        last edited by

                        @w0w btw what is the experience with this patch? My ISP disconnets every user after 7 days of uptime, then gives new ipv4/v6 adress (dual stack).

                        Do you think this workaround will work after 7 days of uptime?

                        ? w0wW 2 Replies Last reply Reply Quote 0
                        • ?
                          A Former User @havastamas
                          last edited by

                          @havastamas With my build, applying fixes to to get 6RD working, removing spam messaging in RADVD and upgrading to 12.1 code base, my firewall has been up and passing ipv6 tests for over 12 days now.

                          So I think a solution has been found, its now a matter of priorities. Switching to 12.1 is non-trivial and who knows what other issues that creates. I'm not a networking expert and my application is relatively simple, so all it has done is highlighted that no fatal flaws are out there with starting to move that direction.

                          1 Reply Last reply Reply Quote 0
                          • w0wW
                            w0w @havastamas
                            last edited by

                            @havastamas
                            If you are talking about workaround... I see no reason why the workaround would not work, but it’s easier to check yourself whether it works or not.

                            1 Reply Last reply Reply Quote 0
                            • S
                              strangegopher
                              last edited by

                              any updates on this?

                              1 Reply Last reply Reply Quote 0
                              • w0wW
                                w0w
                                last edited by

                                https://redmine.pfsense.org/issues/9577 is updated, but nothing new so far, waiting for the new build based on 12.1

                                1 Reply Last reply Reply Quote 0
                                • w0wW
                                  w0w
                                  last edited by

                                  @jimp when do we expect snapshots based on FreeBSD 12.1? Is it coming early 2020?
                                  Happy holidays! 😉

                                  S 1 Reply Last reply Reply Quote 1
                                  • S
                                    strangegopher @w0w
                                    last edited by

                                    @w0w said in ipv6 broken: radvd: can't join ipv6-allrouters on <interface>:

                                    @jimp when do we expect snapshots based on FreeBSD 12.1? Is it coming early 2020?
                                    Happy holidays! 😉

                                    im sure upgrading to 12.1 will break other things and require more testing. But I hope this issue will be fixed.

                                    ? 1 Reply Last reply Reply Quote 0
                                    • ?
                                      A Former User @strangegopher
                                      last edited by

                                      @strangegopher said in ipv6 broken: radvd: can't join ipv6-allrouters on <interface>:

                                      im sure upgrading to 12.1 will break other things and require more testing. But I hope this issue will be fixed.

                                      I’m reasonably current with 12.1 and haven’t noticed any new issues and a few other issues have been fixed. Most of the 2.50 pfsense commits to 12.0 apply to 12.1 without conflicts.

                                      S w0wW 2 Replies Last reply Reply Quote 1
                                      • S
                                        strangegopher @A Former User
                                        last edited by

                                        @rschell thats great news! thanks for all the work. Happy holidays!

                                        1 Reply Last reply Reply Quote 0
                                        • w0wW
                                          w0w @A Former User
                                          last edited by

                                          @rschell
                                          Ronald, any chances to get already compiled radvd with patch provided on https://redmine.pfsense.org/issues/9577? Just for testing.

                                          ? 2 Replies Last reply Reply Quote 0
                                          • ?
                                            A Former User @w0w
                                            last edited by

                                            @w0w I can give it a try. I’ll have to update my 2.5 version first, it’s been a while.

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