I'm having the same issue.  I originally had IPv6 set up to track the 6rd connection on the WAN interface, but later switched to a static LAN IP with the DHCPv6/RA server, but even with that, I still only ever get IPv4 addresses in DNS (except for static mappings).  Google hasn't been much help, and I can't find anything helpful in the pfSense documentation, beyond settings for the IPv4 mappings.  Any suggestions?

I'm ignoring it…

found it: services.inc

Looking at the 0.0ms RTT and Monitor "none" on HENETv6_TUNNELv6 GW… Are you absolutely sure you did NOT tick the "Disable Gateway Monitoring" instead of "Default Gateway"?

There's really no point in dropping MTU to 1280 on LAN.

split to its own thread since it had no relation at all to where it was originally posted.

@jpp: However, I noticed that pfSense assigns the client mac address as the local part of the IP6 address. No, your clients are doing that themselves. They should be using privacy addressing, so the v6 IP with the MAC in it is assigned, but not actually used for Internet traffic. Check on privacy addressing with your client OS(es) of choice. It's on by default in every recent mainstream OS (Windows, Linux, OS X, iOS, BSDs, etc.).

Also there is a bug when prefix length is not 32 for 6rd. Check this section of the forum for a  fix.

To add: MTU values must be in alignment. Test if you need 1492 with the PPPoE (not the 1500). So in pfSense Interfaces WAN & LAN set MTU 1492. Assure with rebooting in line with the MoDem. Expectation: if MoDem in bridge > if MoDem/PPPoE(IPv4) on WAN-iface > if WAN-DHCP6 > then a fe80…. on WAN-iface and a 2001:44b8:etc/64 on LAN-iface.

The ISP is useless. Get a tunnel from HE and ditch the ISP's IPv6 clusterfuck.

It would add some latency - yes.

Good for you. So a lack of register  ;)

Suggestions ? Post explicit configuration (data, pictures) like: Interfaces: WAN, : LAN and Services: Router advertisements.

First of all thanks! it is working now for future reference the changes i have made: System: Advanced: Networking: Allow IPv6 Firewall:   Wan Allow DHCP6 UDP from port 547 to 546 (would be nice to make it more specific/secure..)   LAN  Allow IPV6 from LAN to any hardware lineup: Fiber NTU > HP 1810 switch to split up Vlan's to TV's (vlan4) and pfSense (Vlan6 PPPoE) then the pfSense is running on VMware esxi using 2 vswitches (one connected to the HP1810)

@hda: Why is it reporting, where to look and adjust ? Found a factor for the sendmsg: When created a IPv6-static LAN with a switch plugged-in, and set Services: Router advertisements: (Router Only), but no hosts active/connected. Solution: change to Services: Router advertisements: (Disabled).

Retry with 2.2 release, still have to run it manually?

I don't have much expectations from dhcpv6/radvd I don't think they are important for me. I can even disable them and configure each VM with static IPv6. All I want to do is to implement the following: "routable doesn't mean reachable" Just need the pfsense box to be a ipv6 firewall/gateway for VMs on LAN Thanks!!

@balubeto: @hda: @balubeto: … Enable IPv4 NAT encapsulation of IPv6 packets ... WHY do you need IPv6 ? IPv6 is meant as a public addressing system that you manage with inbound/outbound allowances. Because I have some programs that also use the IPv6 protocol. Can you mention an example, a typical program that wants to go public while there is no public IPv6, but that will refuse to take the IPv4 instead ? What brand-type of MoDem-Router/Switch do you have ? Is your Internet Service Provider able to offer you IPv6 ?