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

    Comcast 6to4 how-to?

    Scheduled Pinned Locked Moved
    IPv6
    4
    32
    14.4k
    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

      yep, no binary changes required

      1 Reply Last reply Reply Quote 0
      • M
        mrhanman
        last edited by

        OK, I just did a gitsync and nothing seems to have changed.  I then installed the latest snapshot, which was a few hours newer and did another gitsync.  I still have no ipv4 gateway on my PC, and no default ipv6 route on pfSense.

        Just to be clear, to do a gitsync, you SSH into the box, hit 12 for pfSense Developer Shell, type 'playback gitsync git://github.com/bsdperimeter/pfsense.git', and hit enter a couple times, right?  I also rebooted a few times, just for fun - both the PC and pfSense.  Did I miss something?

        EDIT: Also, there is only the ipv6 gateway listed under Status -> Gateways.  The ipv4 gateway is missing.

        EDIT: I tried adding an ipv4 LAN gateway in the GUI, and a strange thing happened.  The original ipv4 LAN gateway reappeared, but I couldn't set it as default, and I couldn't get the new LAN gateway to work.  I just delelted all the ipv6 settings on the interfaces, and everything is back to normal - minus ipv6 support, of course.  Now, I'm going to try to add the settings back.  Maybe it'll work this time around.

        EDIT: I'm about to reset to defaults.  Nothing else has worked.

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

          wow, yeah, that sounds horrific, i'm really not sure what has gone wrong but it appears it's thoroughly confused.

          The VM I setup for testing has a WAN_DHCP gateway for IPv4 and a WAN_6to4 gateway for ipv6.

          Both of those gateways are automatically added by the system during setup. I did start with a clean install of 2.1 which may be the difference.

          I had no time to setup a test vm behind it to verify I actually got a v4 gateway on the LAN, but i do see a "routers" line in /var/dhcpd/etc/dhcpd.conf do you have such a line in your dhcpd.conf?

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

            All is working now for me.  Both v4 and v6 gateways and routes came up fine at boot.  Thanks again!

            Using this snapshot: built on Tue Apr 17 06:39:44 EDT 2012

            One question.  I'm using IPv6 Prefix ID "none".  Is that the correct configuration or is it better to assign a prefix ID?

            ![Screen Shot 2012-04-17 at 10.44.11 AM.png](/public/imported_attachments/1/Screen Shot 2012-04-17 at 10.44.11 AM.png)
            ![Screen Shot 2012-04-17 at 10.44.11 AM.png_thumb](/public/imported_attachments/1/Screen Shot 2012-04-17 at 10.44.11 AM.png_thumb)

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

              assign something other then "none" and it will get assigned to the LAN interface.

              A 6to4 wan has 65535 choices. 0000 to ffff.

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

                Strange, after changing the Prefix ID to 1 (chosen arbitrarily) from none,  pfSense could no longer ping the IPv6 gateway (WAN_6TO4)  – even after reboot.  However, everything else worked  (ex.  ping6 ipv6.google.com from both pfsense and machines on LAN).

                Changing back to none (and reboot) and the WAN_6TO4 gateway is pingable from pfsense again.

                1 Reply Last reply Reply Quote 0
                • M
                  mrhanman
                  last edited by

                  I still haven't gotten around to starting over.  :-[  Would a "Reset to factory defaults" be just as good, or will that leave something behind?

                  EDIT:  Went ahead and did it and - woohoo! - 6to4 is now working as it should.  Must have been all the various versions I've gone through over the last year that messed it up.  I still get that error on line 42 at startup, though.

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

                    I think there might be a corrupt PHP file in /usr/local/pkg from a defunct package.

                    1 Reply Last reply Reply Quote 0
                    • M
                      mrhanman
                      last edited by

                      Is there anyway I can check for what's causing it and remove it?  If I'm not mistaken, it did this on the first boot, before I had added any packages.

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

                        ls -l /usr/local/pkg see if there is a file there that you don't recognize.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post