Bridge link-local IPv6 address assignment on startup
-
comitted.
-
The patch seems to have been lost. Today I upgraded to 2.0-RC1-IPv6 (i386)
built on Fri Aug 26 18:54:18 EDT 2011 and git sync'd for IPv6. On reboot sawSep 1 08:25:46 pfsense php: : The command '/sbin/ifconfig bridge0 inet6 427d:dcff:fe45a8:cc' returned exit code '1', the output was 'ifconfig: 427d:dcff:fe45a8:cc: bad value'
-
That's not current code, not sure what you are syncing against because the current version string is 2.1-DEVELOPMENT
-
That's not current code, not sure what you are syncing against
I was running a snapshot 2.0 build from around 21 Jun 2011 and wanted to upgrade to something rather more current.
There doesn't seem to be a single "current" guide to getting something I can use for some basic IPv6 testing, firstly with a Hurricane Electric tunnel then (maybe) with my ISP. What should I do? Is a recent 2.0 snapshot build enough?
-
To try to answer my own question, I'll start again with the Jun snapshot I was running, upgrade to 26th Aug snapshot build then follow http://doc.pfsense.org/index.php/Using_IPv6_on_2.0 (dated 5th Aug) and take a bit more notice of what I'm doing and report back.
-
I restored my 2.0 snapshot build of 21 Jul. I cleared out the files from pfsense/pfSenseGITREPO/pfSenseGITREPO to get enough free space for the install. (I have a 1GB hard drive which was about 91% full. After clearing this directory utilisation fell to about 60%. The installs would quietly fail with the low disk free space. The failure was reported on the next boot as the bootloader getting a premature EOF on reading the kernel.)
After installation of the 26 Aug snapshot and its reboot, I connected to the console and followed http://doc.pfsense.org/index.php/Using_IPv6_on_2.0 and things worked better. Looks like I messed up the gitsync somehow.
-
With the latest available snapshot (30 sep or so), my bridge doesn't get assigned a link-local address (causing routing issues, since i have a link-local address as gateway, and I cannot set it because it's not in the 'bridge net'). Is this intended behavior or should I file a bug?
-
I just posted a new set of images a few days ago, give it a try with up-to-date code.
-
jimp – so can we point our update url to http://files.pfsense.org/jimp/ipv6/
And have it grab updates as you post them? Mine currently says no updates available - etc.
Are these that you posted using the new freebsd 9?
2.1-DEVELOPMENT (i386)
built on Sun Sep 11 21:36:53 EDT 2011
FreeBSD 8.1-RELEASE-p4Unable to check for updates.
Would be really nice if we could get an update of details for us wanting to use IPv6 and maintain using the lastest stuff for 2.1 line, where to grab updates/snaps - where to point for gitsync, etc.
An announcement of the all the required settings would be great!!
-
jimp – so can we point our update url to http://files.pfsense.org/jimp/ipv6/
And have it grab updates as you post them? Mine currently says no updates available - etc.
No - those are just individual files that can be downloaded and used for new installs/updates.
Are these that you posted using the new freebsd 9?
No, not yet.
–-
2.1-DEVELOPMENT (i386)
built on Sun Sep 11 21:36:53 EDT 2011
FreeBSD 8.1-RELEASE-p4Unable to check for updates.
Would be really nice if we could get an update of details for us wanting to use IPv6 and maintain using the lastest stuff for 2.1 line, where to grab updates/snaps - where to point for gitsync, etc.
An announcement of the all the required settings would be great!!
The gitsync process is still the recommended way - just do a manual firmware update instead of an auto update. You aren't quite on 2.0-RELEASE there, but it should be close enough. You could upload a 2.0 firmware and it'll kick in, or if you just want to update the code, run gitsync on its own as described on the doc wiki.
-
I just posted a new set of images a few days ago, give it a try with up-to-date code.
Same problem with the latest snapshot, (2.1-DEVELOPMENT (amd64) built on Fri Oct 21 12:51:15 EDT 2011). The bridge iface only gets assigned the global IPv6 IP and not a (generated) link-local IP. Since my gateway is a link-local address (due to HSRP), I don't have IPv6 connectivity.
