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

    [SOLVED] Tunnel Online but Not Routing to outside IPv6 Sites

    Scheduled Pinned Locked Moved IPv6
    17 Posts 6 Posters 7.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.
    • D
      databeestje
      last edited by

      as far as I can tell it did setup default routes for most if not all of the users.

      There is a checkbox to designate that gateway being the default. The not so intuitive part is that both a v6 and a v4 can be toggled default.

      I should really add a tag in the listing ;-)

      1 Reply Last reply Reply Quote 0
      • F
        focalguy
        last edited by

        Both my v4 and my v6 gateways are set as default. There is no "default" route for V6 in my routing table though.

        v4v6defaultgw.PNG
        v4v6defaultgw.PNG_thumb
        v6Routes.PNG
        v6Routes.PNG_thumb

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

          It might be fixed when you git sync up to newer code. I think Jim also started on new images, not sure what happened to those.

          1 Reply Last reply Reply Quote 0
          • K
            kionez
            last edited by

            AFAIK there's a problem in /etc/inc/system.inc at the line 420:

            mwexec("/sbin/route change -inet6 default " . escapeshellarg($gatewayipv6) ."{$ifscope}");
            
            

            if I do this on pfsense's console:

            
            # route change -inet6 default 2001:470:XXXX:XXX::1
            route: writing to routing socket: No such process
            change net default: gateway 2001:470:XXXX:XXX::1: not in table
            
            

            but if I manually add a fake default route and then change it, it works fine..

            
            # route add -inet6 default ::1
            add net default: gateway ::1
            # route change -inet6 default 2001:470:XXXX:XXX::1
            change net default: gateway 2001:470:XXXX:XXX::1
            
            

            so, maybe it could be added to init script a fake default route for inet6 .

            Another solution: check if there's a default inet6 route before changing it and using "add" instead of "change" if there's no default GW

            [sorry for my poor english :) ]

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

              the route binary we use in pfSense will add a route if it doesn't exist with Change. Maybe you have a older binary snapshot.

              1 Reply Last reply Reply Quote 0
              • K
                kionez
                last edited by

                I updated an old 1.2.3 installation to 2.0-RC3 with full-upgrade package, then updated to 2.1-DEVELOPMENT via "playback gitsync" to master version:

                
                # md5 /sbin/route
                MD5 (/sbin/route) = b8e47fdd0d5f1f3d249dd1b9ae69bd38
                
                

                Maybe i have to do a fresh install of 2.0?

                k.

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

                  a 2.0 snapshot should work fine, then gitsync 2.1-DEVELOPMENT

                  1 Reply Last reply Reply Quote 0
                  • F
                    focalguy
                    last edited by

                    @databeestje:

                    It might be fixed when you git sync up to newer code. I think Jim also started on new images, not sure what happened to those.

                    Nice! I have a "default" now after updating the snap and gitsyncing. My box still doesn't seem to gitsync automatically after updating the snap but that's another issue. Thank for all your work on this!

                    1 Reply Last reply Reply Quote 0
                    • K
                      kionez
                      last edited by

                      @databeestje:

                      a 2.0 snapshot should work fine, then gitsync 2.1-DEVELOPMENT

                      I just installed a clean 2.0 snapshot ( pfSense-memstick-2.0-RC3-i386-20110621-1650.img ) then updated via gitsync to 2.1-DEVELOPMENT and the /sbin/route binary still don't work as expected (and has the same md5sum of old installation). When it tries to "route change", it fails.

                      Where I'm wrong? I've installed from a wrong source?

                      thanks in advance.
                      k.

                      1 Reply Last reply Reply Quote 0
                      • K
                        kionez
                        last edited by

                        @kionez:

                        Where I'm wrong? I've installed from a wrong source?

                        I've just missed a step!

                        Updated to "2.1-DEVELOPMENT (i386) built on Mon Sep 5 04:07:51 EDT 2011" via Auto Update, then gitsync and now /sbin/route seems working fine.

                        If i remove the default route for inet6, then "change" it ,route gives "No such process" error, but then the new default is set!

                        thanks

                        k.

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