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

    IPv6 testing

    Scheduled Pinned Locked Moved IPv6
    357 Posts 48 Posters 293.7k 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.
    • C
      Cino
      last edited by

      That is good news to hear!!

      I went ahead and deleted the /root/pfsense folder so it would point me back to the main code, git://github.com/bsdperimeter/pfsense.git
      . then gitsync

      After the system reboot I noticed 2 new errors:

      Warning: Unexpected character in input: "" (ASCII=92) state=1 in /etc/inc/pkg-utils.inc on line 556

      Parse error: syntax error, unexpected '"' in etec/inc/pkg-utils.inc on line 556

      1 Reply Last reply Reply Quote 0
      • T
        tebeve
        last edited by

        @singerie:

        what should we put in the repository url ?

        currently it's git://github.com/smos/pfsense-ipv6.git

        oops, sorry, didn't see this when I posted HERE asking the same thing.

        looks like the answer is yes tho, it should be:
        git://github.com/bsdperimeter/pfsense.git
        now

        1 Reply Last reply Reply Quote 0
        • I
          iFloris
          last edited by

          @Cino:

          After the system reboot I noticed 2 new errors:

          Warning: Unexpected character in input: "" (ASCII=92) state=1 in /etc/inc/pkg-utils.inc on line 556

          Parse error: syntax error, unexpected '"' in etec/inc/pkg-utils.inc on line 556

          That's due to a missing " in line 556, you can fix that by adding a " before the \n" so that it looks like this:```
          pkg_debug(gettext("ERROR! Unable to fetch package configuration file. Aborting installation.") . "\n");

          one layer of information
          removed

          1 Reply Last reply Reply Quote 0
          • C
            Cino
            last edited by

            @iFloris:

            @Cino:

            After the system reboot I noticed 2 new errors:

            Warning: Unexpected character in input: "" (ASCII=92) state=1 in /etc/inc/pkg-utils.inc on line 556

            Parse error: syntax error, unexpected '"' in etec/inc/pkg-utils.inc on line 556

            That's due to a missing " in line 556, you can fix that by adding a " before the \n" so that it looks like this:```
            pkg_debug(gettext("ERROR! Unable to fetch package configuration file. Aborting installation.") . "\n");

            Thanks iFloris! I didn't have a chance to look at the file before I posted but wanted to let the devs now so it can be fix in the code.

            1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator
              last edited by

              Ok just to be clear, maybe the last commit fixed error on line 550?  But 556 is still broke.

              I just changed over the new branch, and change git sync url, etc.

              Did an update too
              2.1-DEVELOPMENT (i386)
              built on Thu Jul 14 01:23:35 EDT 2011

              Even ran a manual gitsync, and still was getting error had to manually go in and add the " on this line
              pkg_debug(gettext("ERROR! Unable to fetch package configuration file. Aborting installation.") . "\n");

              in /etc/inc/pkg-utils.inc

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.7.2, 24.11

              1 Reply Last reply Reply Quote 0
              • C
                cmb
                last edited by

                @johnpoz:

                Ok just to be clear, maybe the last commit fixed error on line 550?  But 556 is still broke.

                I just changed over the new branch, and change git sync url, etc.

                Did an update too
                2.1-DEVELOPMENT (i386)
                built on Thu Jul 14 01:23:35 EDT 2011

                Even ran a manual gitsync, and still was getting error had to manually go in and add the " on this line
                pkg_debug(gettext("ERROR! Unable to fetch package configuration file. Aborting installation.") . "\n");

                in /etc/inc/pkg-utils.inc

                Jim fixed that one today.

                1 Reply Last reply Reply Quote 0
                • C
                  Cino
                  last edited by

                  My HE tunnel wont up after a gitsync/reboot today.

                  Looking at the changes, I believe this change: https://github.com/bsdperimeter/pfsense/commit/87f0f42c3230ad7ad15b14a8a9d63c58f8b2e379 is the cause. When i hand-type the code back in that was removed and reboot; my interface comes up.

                  1 Reply Last reply Reply Quote 0
                  • johnpozJ
                    johnpoz LAYER 8 Global Moderator
                    last edited by

                    I just did a gitsync, and got the latest commits - the one your talking about, and rebooted and my HE tunnel came up no problems.

                    Now it was odd before the reboot after the gitsync I was seeing a crash error on the UI that would not seem to go away.  Odd, it had no details in it, close it, send it and it would just pop back up.

                    But everything seems to be working currently

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 24.11 | Lab VMs 2.7.2, 24.11

                    1 Reply Last reply Reply Quote 0
                    • C
                      Cino
                      last edited by

                      @johnpoz:

                      I just did a gitsync, and got the latest commits - the one your talking about, and rebooted and my HE tunnel came up no problems.

                      Now it was odd before the reboot after the gitsync I was seeing a crash error on the UI that would not seem to go away.  Odd, it had no details in it, close it, send it and it would just pop back up.

                      But everything seems to be working currently

                      Is your subnet mask 64bits or 128bits for your tunnel? Mines 64-bit

                      I was able to get it to work after clicking save/apply under the interface configuration page. IPv6 code has had a similar issue a couple of months ago to where we had to manually add a route or click save/apply..

                      see post http://forum.pfsense.org/index.php/topic,32721.msg179781/topicseen.html#msg179781

                      1 Reply Last reply Reply Quote 0
                      • J
                        JoelC707
                        last edited by

                        I'm having to do the same save/apply business. To make matters worse my DSL was in and out all day yesterday and it was leaving the tunnel down every time the DSL came back up. Talk about annoying having to go in and do that every few minutes lol. I finally gave up on it and surfed from bed with my phone lol. Grrrr, seems to be doing it again. In any case my tunnel is a /64. IIRC the direction say to do /128 or /120 but my tunnel wouldn't come up with that config. Since HE's site  says /64 for the tunnel I figured it should be /64 on my end as well (same logic as different subnets on a LAN, they won't always talk to each other).

                        1 Reply Last reply Reply Quote 0
                        • johnpozJ
                          johnpoz LAYER 8 Global Moderator
                          last edited by

                          Mine is /128 There was some issues with that a while back.  You can bring it up /64 and then just change it to /128

                          An intelligent man is sometimes forced to be drunk to spend time with his fools
                          If you get confused: Listen to the Music Play
                          Please don't Chat/PM me for help, unless mod related
                          SG-4860 24.11 | Lab VMs 2.7.2, 24.11

                          1 Reply Last reply Reply Quote 0
                          • C
                            Cino
                            last edited by

                            When I first setup the tunnel we had to use 128 but it has resolve so we can use the 64 subnet that HE assigned to us for the tunnel. After my update yesterday, my tunnel wont come up with a 64 subnet but will come up with 128 subnet… I'm wondering if the code that was removed was a workaround to get the tunnel to come up using 64bit subnet... idk tho...

                            1 Reply Last reply Reply Quote 0
                            • J
                              JoelC707
                              last edited by

                              Currently running the 05:55:15 snapshot from 7/15 and whenever my DSL hiccups the v6 WAN still won't come back up by itself, it stays in "gathering data" according to the gateways widget. Obviously I'd love to get the DSL fixed and this probably wouldn't be a problem but alas it's not my house. It affects my grandfather just as much as it does me so you think he would be annoyed by it too. Two days ago when this started he said he would call Bellsouth and see if they can fix it but I have no idea if he did or if anyone ever came out to look at it (normally does this when we get a heavy rain so me things something is attenuating on the line somewhere which granted may not be an easy fix).

                              Anyway, both my WANv6 and GIF configs are still using a /64. They are the same v6 address space though (7, LAN is 8) so if I change it to a /128 should I change the gif tunnel settings or the WANv6 settings or both? Any chance this will even fix the problem? Note that we do have a static V4 IP from Bellsouth so the IP isn't changing causing this issue.

                              1 Reply Last reply Reply Quote 0
                              • D
                                databeestje
                                last edited by

                                I am using 128 for the gif interface config and 126 on the interfaces page. That comes up reliably after failure for me and reboots.

                                1 Reply Last reply Reply Quote 0
                                • J
                                  JoelC707
                                  last edited by

                                  Just changed mine to match, lets see what happens. IIRC after a reboot it was up, it was only when the DSL would hiccup and go offline. DSL/WAN would come back up but it's like it wouldn't reestablish the tunnel. It's gone down several times today but not in the last couple of hours. We'll see.

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    JoelC707
                                    last edited by

                                    Looks like we're good. DSL just went out, watched the gateways on the dashboard and both came up at the same time just as they are supposed to.

                                    1 Reply Last reply Reply Quote 0
                                    • A
                                      alexis.olivier
                                      last edited by

                                      Hello everybody,

                                      I just pointed out a little bug and have a feature to request for the DHCPv6 Server.

                                      The bug :
                                      On the DHCPv6 page, when you have a non-common bitmask, showed range is incorrect. My exemple :

                                      Address                XXXX:XXXX:XXXX:XXXX::1
                                      Subnet mask 65 bits
                                      Available range XXXX:XXXX:XXXX:XXXX:0:0:0:1 - XXXX:XXXX:XXXX:XXXX:ffff:ffff:ffff:ffff

                                      The available range should be :
                                      Available range XXXX:XXXX:XXXX:XXXX:0:0:0:1 - XXXX:XXXX:XXXX:XXXX:7fff:ffff:ffff:ffff

                                      and when specifying XXXX:XXXX:XXXX:XXXX:0:0:0:1 - XXXX:XXXX:XXXX:XXXX:ffff:ffff:ffff:ffff to the dhcp server, the server starts but doesn't deliver addresses on the network.

                                      The feature :
                                      You should add a checkbox allowing to disable the "Autonomous address-configuration", setting the rtadvd option "pinfoflags" to 0 (or "") for the interface.
                                      In my case, i need to disable this to keep the router advertisement but not to have autoconfigurated addresses or subnets delivered (because i have several different subnets linked to the same interface).

                                      Thanks to everyone for your excellent work on the IPv6 part !

                                      –- EDIT ---

                                      An old bug reappeared :

                                      In line 736, you should change :

                                      $dhcpdv6conf .= "            deny unknown clients;\n";
                                      

                                      by

                                      $dhcpdv6conf .= "            deny unknown-clients;\n";
                                      
                                      1 Reply Last reply Reply Quote 0
                                      • C
                                        cmb
                                        last edited by

                                        I added tickets on the two issues you mentioned.
                                        http://redmine.pfsense.org/issues/1725
                                        http://redmine.pfsense.org/issues/1726

                                        The last one, deny unknown-clients is correct in mainline, maybe you're still syncing from Seth's old branch? You don't have the latest code somehow.

                                        1 Reply Last reply Reply Quote 0
                                        • A
                                          alexis.olivier
                                          last edited by

                                          Thanks to you for adding tickets.

                                          In effect, i hadn't changed the repo URL.
                                          But I changed it now and ran a fresh gitsync from "https://github.com/bsdperimeter/pfsense.git", and the "deny unknow clients" bug is still there.
                                          Am i doing something wrong ? Is this the good URL ?

                                          Thanks for your answers !

                                          1 Reply Last reply Reply Quote 0
                                          • C
                                            cmb
                                            last edited by

                                            run 'rm -rf /root/pfsense*' and sync again from that URL. That's correct URL, but that's not where you're getting code from.

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