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

    Native IPv6 over DHCPv6 and RA not working in combination with PPPoE IPv4

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    30 Posts 7 Posters 9.8k 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.
    • P
      phil.davis
      last edited by

      I was nearly going to tell you you are mad, then I tried it on the new snapshot, didn't work!!! After a bit of hair pulling I discovered that I had used the version from Github Main when testing (I had test configs that I had saved that had the setting set, so it did work). Compared Main to the 2.1 branch. The version committed to 2.1 branch had an different error - the code applying the setting was in the wrong IPv6 type case statement. So that never worked in 2.1, but it worked in Main.
      This (should) fix it:
      https://github.com/pfsense/pfsense/pull/723
      I tested with the version I submitted to the 2.1 branch this time :)

      As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
      If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

      1 Reply Last reply Reply Quote 0
      • dotOneD
        dotOne
        last edited by

        I don't care to be called mad  ;)  I applied the patch by hand and yes now the checkbox is working.
        Let's wait for the next snapshot. I'm fairly convinced that the parent interface is chosen instead of the pppoe interface.

        we'll know in a few hours.

        1 Reply Last reply Reply Quote 0
        • E
          eri--
          last edited by

          There is an option to click for cases like the XS4All ISP.
          Click that and you will have correct connectivity restored as previously.

          The option is with the description "Request a IPv6 prefix/information through the IPv4 connectivity link"

          1 Reply Last reply Reply Quote 0
          • dotOneD
            dotOne
            last edited by

            I'll check the next build.
            Results by tomorrow morning.

            1 Reply Last reply Reply Quote 0
            • D
              Dark-Sider
              last edited by

              @ermal:

              The option is with the description "Request a IPv6 prefix/information through the IPv4 connectivity link"

              Probably I need the same option for my M-Net FTTB connection. I'm running 2.1-RC0 (amd64)
              built on Mon Jul 22 15:44:15 EDT 2013 FreeBSD 8.3-RELEASE-p8 but I can't find that option. Is this not yet in or do I use a wrong release?

              bye
              Darky

              1 Reply Last reply Reply Quote 0
              • P
                phil.davis
                last edited by

                Ermal committed the new option 7 hours ago (as I type) and a build started about 3/4 hours ago. It looks like it is finishing just now. It should have a timestamp around 23 July 2013 10:00. Try that.

                As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                1 Reply Last reply Reply Quote 0
                • D
                  Dark-Sider
                  last edited by

                  Thanks for your quick explanation I'll try the new snapshot, as soon as it gets pushed to the update server :-)

                  1 Reply Last reply Reply Quote 0
                  • P
                    putty_thing
                    last edited by

                    @ermal:

                    The option is with the description "Request a IPv6 prefix/information through the IPv4 connectivity link"

                    Just signed up to say that this worked for me.

                    IPv6 (native) from my ISP was working on 2.1 beta and broke when I went to the RC, came back straight away with whatever this setting does :)

                    1 Reply Last reply Reply Quote 0
                    • D
                      Dark-Sider
                      last edited by

                      Unfortunately the amd64 build didn't get updated, it still has a last modified date of July 22nd

                      Therefore I manually checked out the interface.inc and interface.php files and replaced them on the box. The interface.php had a whitspace_error but this was easily fixed. The option did then appear on my box and I checked it. I still didn't receive an ipv6 prefix. Maybe I did forget sth. to patch, so I will way until the snapshot-build gets officially updated.

                      bye
                      Darky

                      1 Reply Last reply Reply Quote 0
                      • dotOneD
                        dotOne
                        last edited by

                        Just tested the latest snapshot. (built on Wed Jul 24 15:12:27 EDT 2013 ).
                        I can confirm that both options work as expected.

                        X Request a IPv6 prefix/information through the IPv4 connectivity link
                        X Only request a IPv6 prefix, do not request a IPv6 address

                        both options checked. IPv6 is working again without changing the config/interfaces.inc manually.

                        The only thing that is left is that after a reboot the dhcp6c daemon is not started automatically.
                        I think there is another thread about it.

                        I will do some testing but in the meanwhile I'll make a shellscript that checks if the daemon is running. If not it will (re)start it.

                        1 Reply Last reply Reply Quote 0
                        • E
                          eri--
                          last edited by

                          @avink,

                          the issue you have is not related to this.
                          Can you please open another thread with more details.

                          1 Reply Last reply Reply Quote 0
                          • dotOneD
                            dotOne
                            last edited by

                            I will.

                            But I want do do some checking before I do so.
                            Need to do a FW reboot to check but there are too many people relying on an active connection now.
                            Need to schedule this for this afternoon (CET)

                            1 Reply Last reply Reply Quote 0
                            • Y
                              YaNightmare
                              last edited by

                              I was away for a little while, what a nice surprise seeing that this is solved and multiple people even took time to test/register to confirm this.

                              Great job all and thanks a lot, i will update my firewall tonight to see if this is fixed.

                              PS, also have the dhcp6c not starting problem so i will update in a new thread as well. (and offc. test).

                              1 Reply Last reply Reply Quote 0
                              • Y
                                YaNightmare
                                last edited by

                                Just installed the latest build, like the rest i can confirm that everything is solved !

                                PS, DHCP6C still isnt started, but thats not really a problem for me at the moment, would still require some investigation.

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