Unbound integration into 2.1 is a ongoing project.

Hello databeestje: When I performed the resync the first time, my shell session got "terminated" (got kicked back to local prompt) and I had to login again so I thought the router had rebooted.  I resynched it just a moment ago and rebooted it again after my session got terminated and it looks like everything's working.  I can access ipv6.google.com and a test site so all appears well now. Thank you for your assistance. FIRESTORM_v1 Note to newbies:  If you're planning on implementing IPv6, it's best to use a v6/v4 dual-homed network.  Running IPV6-only will leave you with very little to do on the Internet.  (example:  www.v6.facebook.com only works halfway.  Facebook's fault. :P )

Without the rtadvd the router will not announce itself. I have made a number of changes that could have caused it. Investigating.

Are you referring to the dhcpv6 server here? For the server part you can already choose. For the wan slaac is not supported currently since it does not work for a router.

Ah, thanks jimp! I was using the userid from the other method instead of my username. Works now.

OK. So I solved this by deleting my tunnel and assignment with the tunnel broker. I then created a new tunnel and routed assignments, and replaced those in my non-working configuration and they worked. I have to surmise it was something at the other end (tunnelbroker). ipv6 gateway came right up, once I changed the ipv6 assignment for LAN/DHCP and refreshed, it all worked.

I've managed to fix his installation and committed a few patches to the repo. The biggest issue is that the bogonsv6 table might be lagging on your installation, although we update that table very frequently at files.pfsense.org it might still be out of date. If you do run into issues with the dhcp6 client not aquiring a address and the dhcp6 requests ending up in the firewall logs as [fe80::something]:547 or [fe80::something]:546 it is probably hitting the bogons filter. After disabling the bogons on the WAN interface it succesfully acquired a DHCP-PD prefix for the LAN.

you gitsynced but did not perform a config upgrade. Please reboot and it should upgrade your configuration and thus your rrd files.

their reasoning is that the amount of directly connected users is not trivial. So this should be a fairly harmless afair. Also, if the DHCP6 client is activated on the WAN interface pfSense will pick a DHCP6 address but there will be no prefix delegated when requested from the DHCP6 server. In the near future you can request a prefix delegation from the DHCP6 server and that should provide you with a routed subnet for the LAN. From my understanding from talking to Comcast they want to have generic devices from Netgear and D-link that work with DHCP-PD. They are not going the route that Ziggo in .nl is with the UBEE modems/routers/wifi gateways.

i already thought of that over the weekend. thanks again ticket: http://redmine.pfsense.org/issues/1996

I've still for a couple Alix boxes sitting around here, maybe I'll try IPv6 on one of those again soon in a test environment.  I'm done on my primary box at home though until it goes gold.  My main computer bought it during the same power outage this past weekend and it was hell trying to get the thing working without a working internet connection for research… EDIT:  Also, file.pfsense.org/jimp/ipv6 is a bad link, I think you meant "http://files.pfsense.org/jimp/ipv6/"

we only have the rrd graphs at this point which have v4 and v6 counters for pass and block in both directions

@jimp: 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.

@asterix: Would be a good idea to include this info in pfSense IPv6 install doc It is already there, and was there before you posted this :-) http://doc.pfsense.org/index.php?title=Using_IPv6_on_2.0&diff=4171&oldid=4168

You can use the pfSense 2.0 image and then overlay the ipv6 tree via gitsync

When there is no status file we show gathering data. When we 1st write out the status file it is online until apinger marks it down after 10 timeouts.

There already is a open ticket in redmine for importing a newer upnpd binary that supports some bare ipv6 and the ipv6firewallcontrol function from the igd 2.0 specification.

@iFloris: The above code works fine for me. I had to add "; to the end of line 2337.```    $ipfrules .= "table <bogonsv6>persist file "/etc/bogonsv6"\n</bogonsv6> I'm sorry, ";" was eaten by copy-paste.

@Michael: because of this: http://forum.pfsense.org/index.php/topic,40953.msg215068.html#msg215068 Thanks for the catch, I've fixed that line and everything seems fine so far.

Thanks for the info.  I just realized that after I got console connectivity into the device.  Boooo.  I managed to install the 2.0 official release but it was just not usable at all.  I'll probably wait to get myself one of the ALIX setups instead. LoboTiger