Here's the bug for the IPv6 addressing being lost:  http://redmine.pfsense.org/issues/2919

I would definitely consider this a Show Stopper bug.  The ability to acquire and maintain addressing is a basic function, without that nothing else matters.  I was surprised to see the change to RC status, with issues like this remaining.

That was exactly what I thought. When I read about the RC status I went back looking for this hoping that I missed the update. Considering that the main feature of 2.1 is IPV6 support, this is pretty major, together with the broken 6RD support.

Any updates on this one?

I have a somewhat similar setup for my home network, except I use an Alix box and an Engenius WAP with 2 SSID's: one bridged to lan and the second (bound to a separate Vlan) with just internet access, isolated from LAN.

In your case, just connect the AP to the available port on your pfSense box and set the firewall rules accordingly. Personally I would let pfSense manage the DHCP stuff just to keep things simple.

Having similar issue, but at this point I'm not sure if it's a pfSense problem or my lack of knowledge with IPV6. My ISP (Rogers) just enabled IPV6 through DHCP and like in your case I can get a ipv6 on the wan and lan (bridged with WLAN) by using the track option, but none of the clients seem to get an IP and route for ipv6.

I have the same issue with 6RD tunnel on Rogers.

If you want to save yourself time and headaches, forget about wifi cards to use directly in pfSense. Get an external AP and connect it to a new interface or VLAN on your pfsense box and manage the access rules on the FW.

I did the same at home and it works great:
http://forum.pfsense.org/index.php/topic,59799.0.html

Would it make sense to use to use this feature on a Alix box with 256MB of ram?

I tried the WiFi option in pfSense as well and I had to give up at the end (I posted about it in the wireless section). I came to the conclusion that the hardware that works well with FreeBSD 8.3 in AP mode is very limited and hard to find at best. I could spend hours trying to find the right ath based card on ebay or just spend $90 for a proper AP and be done with it.

I understand, but that was not the case up to 10 days ago. If I had IPV6 disabled, the ipv6 traffic blocked by the FW would not be logged.

I just noticed this commit:
https://github.com/pfsense/pfsense/commit/ac135e422b704e6e778b3cd9614da93c2349a851

Is that related to this?

I update my Alix box to the Mar 11 08:59:46 build. I disabled IPV6 in the advanced settings, but after a while I noticed that traffic gets logged in the FW log on one of the interfaces. This did not happen with the previous build I was using (Mar 1).

The other unusual thing is that the logs show the IPV6 traffic going in through one of the LAN bridge member interfaces instead of the bridge itself. I have net.link.bridge.pfil_member set to 0 and net.link.bridge.pfil_bridge set to 1. The IPV4 traffic gets logged on the bridge interface as it should.

I got an EnGenius EAP300

http://www.engeniustech.com/business-networking/indoor-access-points-client-bridges/16139-eap300

and I'm very happy with it. It has enough power for a 3 floor 2000 sqf townhouse plus all the features I needed, including VLAN and multi SSID support.
Not bad for $89.

Update: it worked perfectly! Second SSID on separate VLAN, no problem at all.

Thank you for the info. I'll give it a try when I get the AP setup.

I use an Alix 2D13 box for my home with the WiFi AP connected to OPT1 and bridged to LAN. The other day the AP died. I noticed that the one I'm going to buy has VLAN support with the option to associate up to 4 SSID to separate VLANS.

Since the AP will be connected directly to OPT1, I was wondering if I would still be able to setup a separate VLAN on OPT1 for a second SSID without going through a managed switch. Basically I would like to have a trusted SSID to bridge to LAN and a guest SSID with just internet access.

Great! I'll try the next snapshot.