Missing PPPoE option for IPv6
-
My ISP uses PPPoEv6 to assign IP addresses on their network. I currently have the WAN interface set for PPPoE in the IPv4 but am unable to select it for IPv6 (currently have IPv6 set to none). I already show that the pppoe0 interface has an IPV6 address assigned to it. Without a option to select this in the IPv6 field in the WAN I am unable to use Track Interface in the LAN IPv6. I can already ping6 google.com on the pfSense computer and get replies but am unable to get IPv6 to the LAN. Hopefully in the next release you could possibly fix this. Thanks for the hard work.
-
Uhm… Use DHCP6. Tick Use IPv4 connectivity as parent interface. Without any ISP details, providing further advise is pretty much impossible.
-
I am using a small local ISP with the name of S&T Telephone. Currently running pfSense 2.2.2-RELEASE version. I tried setting as DHCP and it gives me a fe80:: address as the gateway. If a ifconfig is run the following is displayed under ppoe0 (X is to hide ip address):
pppoe0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1492
inet6 fe80::X:X:X:X%pppoe0 prefixlen 64 scopeid 0x8
inet6 2607:9600:X:X:X:X:X:X prefixlen 64 autoconf
inet X.X.X.X –> X.X.X.X netmask 0xffffffff
nd6 options=23 <performnud,accept_rtadv,auto_linklocal>The only thing that looks wrong is there is a fe80:: address assigned as well as a 2607:: address. This may be a problem at the ISP level possibly. But convincing them of that might be a problem. I have seen their service work fine with Linksys routers at other locations.</performnud,accept_rtadv,auto_linklocal></up,pointopoint,running,noarp,simplex,multicast> -
@nfr:
The only thing that looks wrong is there is a fe80:: address assigned as well as a 2607:: address. This may be a problem at the ISP level possibly.
There is nothing wrong with that. Also note that the IPv6 display for PPPoE has never worked properly – neither in the GUI dashboard, nor in the console menu.
-
…
Also note that the IPv6 display for PPPoE has never worked properly -- neither in the GUI dashboard, nor in the console menu.+1, that is, the WAN IPv6 prefix + MACderivative parallel to the WAN IPv4 entry.
Luckily I know my steady /48 on beforehand, so I can issue the different subnets for the SLAAC, Static or DHCPv6 LAN's ;)