IPv6 over PPPoE Dual Stack not working, please help

STI2011

Hello,

I am just testing IPv6 over PPPoE with German provider QSC, but without success…

I have configured the PPPoE interface to use DHCPv6 over v4 and the LAN interface track the PPPoE interface.
The LAN interface seems to be well configured showing the providers scope assigned to me.
But the PPPoE interface is showing LL addresses:

IPv6 Link Local fe80::6a05:caff:fe00:7293%pppoe2
IPv6 address fe80::6a05:caff:fe01:f101%em2
Subnet mask IPv6 64
Gateway IPv6 fe80::225:9eff:fe35:f03e

If you look with ifconfig you see that there is an good address, but not as first??

pppoe2: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1492
inet6 fe80::6a05:caff:fe00:7293%pppoe2 prefixlen 64 scopeid 0xa
inet6 2001:1a80:xxx:xx:xxxx:xxxx:xxxx:xxxx prefixlen 64 autoconf
inet x.x.x.x --> x.x.x.x netmask 0xffffffff
nd6 options=3 <performnud,accept_rtadv>Also there is no default IPv6 route.

Whats going wrong there?

I am using 2.1

Regards

Nico</performnud,accept_rtadv></up,pointopoint,running,noarp,simplex,multicast>

Daboom

have you checked to ensure the Default ipv6 route is pointing to the right interface. I am having the same issues now but I can fix it temporary with a couple cli commands. netstat -rn should show you in terminal/ssh mode.

STI2011

Thanks for you answer :)

After some hours of tests I have managed it to get it work :) :)

First I have done a clean install of V2.1 and have restored my config. After a couple of reboots suddenly the default route was set and i was able to ping IPv6 hosts from pfSense.

Lan interface was set to "Track Interface" but all my win7 clients wasn't able to get IPV6 addresses. The problem here was the /48 prefix delegated from my provider.

It seems that win7 clients are not able to handle it. After setting lan to fixed ip and configuring my own DHCPv6/RA service and set them to a /64 prefix all windows 7 clients got all IPv6 data correctly.

Important for me was to reboot pfSense after every IPv6 configuration change at least two times.

Now it is working fine 8)

razzfazz

… until the next time your provider assigns a new prefix to you (assuming it's not static).

STI2011

Is's Static :)

razzfazz

Nevertheless, the proper way to set this up should be to set the "DHCPv6 prefix delegation size" on your WAN interface to whatever your provider actually gives you (apparently /48 in your case) and then set your LAN interface to "track interface" with "IPv6 prefix ID" set to a one of the possible sub-prefixes (0-ffff for a /48). Does that not work for you?