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

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

2.5 Development Snapshots (Retired)
15
144
49.5k
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.
  • K
    kiokoman LAYER 8
    last edited by kiokoman Sep 21, 2019, 3:49 PM Sep 21, 2019, 2:20 PM

    my guess at that time was some kind of buffer overrun like it's opening sockets until there are so many that is unable to go on and it stop working and depending on the hardware it could happen after 4 / 8 / 24 hours

    setsockopt(4,IPPROTO_IPV6,IPV6_LEAVE_GROUP,0x7fffffffd3e0,20) ERR#49 'Can't assign requested address'
    setsockopt(4,IPPROTO_IPV6,IPV6_JOIN_GROUP,0x7fffffffd3e0,20) = 0 (0x0)
    

    it is joining but not leaving everytime

    this is from ip6 man page for freebsd:

    IPV6_LEAVE_GROUP struct ipv6_mreq *
    Drop membership from the associated multicast group. Memberships are automatically dropped when the socket is closed or when the process exits.

    this is what made me think that restart radvd would temporary solve the problem
    but i don't understand a damn about c/c++ or coding
    but again that could be completely unrelated

    ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
    Please do not use chat/PM to ask for help
    we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
    Don't forget to Upvote with the 👍 button for any post you find to be helpful.

    1 Reply Last reply Reply Quote 0
    • W
      w0w
      last edited by w0w Sep 22, 2019, 5:33 AM Sep 22, 2019, 5:32 AM

      I've just grabbed radvd 2.17 binary from earlier version of 2.5 and testing it on latest (2.5.0-DEVELOPMENT (amd64) built on Thu Sep 19 17:07:24 EDT 2019). At least no SPAM "IPv6 forwarding on interface seems to be disabled, but continuing anyway". Will wait another 48 hours.

      ? 1 Reply Last reply Sep 22, 2019, 8:18 AM Reply Quote 0
      • ?
        A Former User @w0w
        last edited by Sep 22, 2019, 8:18 AM

        A couple of thoughts:

        • The call to “setup_allrouters_membership” is being called several hundred times an hour. Should it be more selective when it asks to join a group rather than repeated leaving and joining? Think that is just asking for trouble we are seeing.

        • There are a number of upstream commits that have been applied to stable/12 since releng/12 in in6_mcast.c that suggest there are issues lurking there.

        W 1 Reply Last reply Nov 2, 2019, 6:09 AM Reply Quote 0
        • K
          kiokoman LAYER 8
          last edited by Sep 22, 2019, 9:40 AM

          yes, indeed..
          i'm sure it will be ok sooner or later, it's a development snapshot after all, we have our workaround in the meantime. they are aware of the problem and i'm using it at home so it's not a priority for me at the moment

          ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
          Please do not use chat/PM to ask for help
          we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
          Don't forget to Upvote with the 👍 button for any post you find to be helpful.

          I 1 Reply Last reply Sep 22, 2019, 10:13 AM Reply Quote 0
          • I
            Irata @kiokoman
            last edited by Sep 22, 2019, 10:13 AM

            @kiokoman the problem is within open source or kernel code, so who are "they" who will fix it?

            1 Reply Last reply Reply Quote 0
            • W
              w0w
              last edited by Sep 22, 2019, 10:24 AM

              If radvd 2.17_5 works well, then the issue is isolated to radvd or radvd patches, I think. Let me test it and we will know it soon, am I right/wrong.
              The fact that there is no spam inspires me with hope.

              1 Reply Last reply Reply Quote 0
              • K
                kiokoman LAYER 8
                last edited by Sep 22, 2019, 10:34 AM

                sorry but if you check this
                https://redmine.pfsense.org/issues/9577
                you will see that we had 2.17 until 2019-07-22 with the same problem, it was updated to 2.18 at the end of july

                @irata i don't think that netgate will release a product with a broken service, they will find a way, or they ask upstream or with a patch they made

                ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
                Please do not use chat/PM to ask for help
                we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
                Don't forget to Upvote with the 👍 button for any post you find to be helpful.

                W I 2 Replies Last reply Sep 22, 2019, 11:02 AM Reply Quote 0
                • W
                  w0w @kiokoman
                  last edited by w0w Sep 22, 2019, 11:10 AM Sep 22, 2019, 11:02 AM

                  @kiokoman
                  One thing that looks quite different for me is that radvd can't join routers right after start, not hours later as we have it now.

                  EDITED:
                  Oh yes, epic fail.
                  1 Reply Last reply Reply Quote 0
                  • I
                    Irata @kiokoman
                    last edited by Sep 22, 2019, 11:45 AM

                    @kiokoman I agree, 2.5 will be left in beta until someone fixes it.

                    1 Reply Last reply Reply Quote 0
                    • K
                      kiokoman LAYER 8
                      last edited by Oct 17, 2019, 9:09 AM

                      @rschell good work about that update on redmine
                      personally i had decided to wait for 2.5 to advance before trying to do anything as any patch that we come out today it will probably be lost resulting in a waste of time as it is a kernel problem and not a pfsense's fault

                      ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
                      Please do not use chat/PM to ask for help
                      we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
                      Don't forget to Upvote with the 👍 button for any post you find to be helpful.

                      1 Reply Last reply Reply Quote 0
                      • Y
                        yon 0
                        last edited by Oct 18, 2019, 5:22 PM

                        Ipv6 problem also caused problems with FRR

                        ipv6 frr

                        1 Reply Last reply Reply Quote 0
                        • W
                          w0w @A Former User
                          last edited by Nov 2, 2019, 6:09 AM

                          @rschell
                          I see you have some progress on 12.1 builds, but you did not report back on redmine, is it working?

                          ? 1 Reply Last reply Nov 2, 2019, 4:04 PM Reply Quote 0
                          • ?
                            A Former User @w0w
                            last edited by Nov 2, 2019, 4:04 PM

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

                            @rschell
                            I see you have some progress on 12.1 builds, but you did not report back on redmine, is it working?

                            I have updated #9577, but for some reason the issue doesn't showup on the 2.5 issue list anymore. My version is running well and RADVD continues to work past 24 hours. The version is built on releng/12.1-RC2 with cherry-picked commits from 2.5 back to mid-February.

                            Once the pfSense is rebased on releng/12.1 or stable/12 and the message logging in RADVD is removed, these problems should be resolved.

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

                            Ipv6 problem also caused problems with FRR

                            ipv6 frr

                            I haven't used FRR, so I can't speak to whether this will resolve those issues.

                            Y 1 Reply Last reply Nov 3, 2019, 8:21 AM Reply Quote 0
                            • Y
                              yon 0 @A Former User
                              last edited by Nov 3, 2019, 8:21 AM

                              @rschell

                              frr use with openvpn ipv6 has issue, add two ipv6 Neighbor openvpn will happen.

                              1 Reply Last reply Reply Quote 0
                              • W
                                w0w
                                last edited by Nov 6, 2019, 3:35 PM

                                @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 Nov 6, 2019, 3:40 PM

                                  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
                                  • W
                                    w0w
                                    last edited by Nov 6, 2019, 3:44 PM

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

                                    ? 1 Reply Last reply Nov 7, 2019, 4:47 AM Reply Quote 0
                                    • ?
                                      A Former User @w0w
                                      last edited by Nov 7, 2019, 4:47 AM

                                      @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 Nov 7, 2019, 5:01 AM

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

                                        W 1 Reply Last reply Nov 7, 2019, 5:35 AM Reply Quote 0
                                        • W
                                          w0w @strangegopher
                                          last edited by Nov 7, 2019, 5:35 AM

                                          @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
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.