IPv6 WAN interface not getting prefix, only single IPv6 address

[Guest]

If your V4 is PPPoE, set the WAN v6 to DHCP and tick the box 'Use IPv4 Connectivity as parent interface.

The dhcp6c client needs to talk over the PPPoE connection.

Set LAN IPv6 to track the WAN interface and you should get it working.

[earlish]

When I set the 'Use IPv4 Connectivity as parent interface' I just get a local link address on the WAN interface;

/root: ifconfig
igb0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4c
	inet6 fe80::208:a2ff:fe0b:d44c%igb0 prefixlen 64 scopeid 0x1 
	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
igb1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4d
	inet 10.0.10.1 netmask 0xffffff00 broadcast 10.0.10.255 
	inet6 fe80::1:1%igb1 prefixlen 64 scopeid 0x2 
	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active</full-duplex></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast></full-duplex></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast>

System>Routing log shows;

Jun 21 08:35:28 	radvd 	32913 	version 1.9.1 started
Jun 21 08:35:28 	radvd 	32913 	no auto-selected prefix on interface igb1, disabling advertisements 

dhcp6c;

Jun 21 08:30:42 	dhcp6c 	16741 	Sending Solicit
Jun 21 08:30:42 	dhcp6c 	16741 	set client ID (len 14)
Jun 21 08:30:42 	dhcp6c 	16741 	set elapsed time (len 2)
Jun 21 08:30:42 	dhcp6c 	16741 	set option request (len 4)
Jun 21 08:30:42 	dhcp6c 	16741 	set IA_PD prefix
Jun 21 08:30:42 	dhcp6c 	16741 	set IA_PD
Jun 21 08:30:42 	dhcp6c 	16741 	send solicit to ff02::1:2%igb0
Jun 21 08:30:42 	dhcp6c 	16741 	reset a timer on igb0, state=SOLICIT, timeo=228, retrans=129432
Jun 21 08:32:51 	dhcp6c 	16741 	Sending Solicit
Jun 21 08:32:51 	dhcp6c 	16741 	set client ID (len 14)
Jun 21 08:32:51 	dhcp6c 	16741 	set elapsed time (len 2)
Jun 21 08:32:51 	dhcp6c 	16741 	set option request (len 4)
Jun 21 08:32:51 	dhcp6c 	16741 	set IA_PD prefix
Jun 21 08:32:51 	dhcp6c 	16741 	set IA_PD
Jun 21 08:32:51 	dhcp6c 	16741 	send solicit to ff02::1:2%igb0
Jun 21 08:32:51 	dhcp6c 	16741 	reset a timer on igb0, state=SOLICIT, timeo=229, retrans=128028 

[Guest]

Something is definitely wrong, if you have selected use parent interface then the line in your logs that says this:

Jun 21 08:32:51 dhcp6c 16741 send solicit to ff02::1:2%igb0

Should be showing something like this:

Jun 21 06:43:01 dhcp6c 43299 send solicit to ff02::1:2%pppoe0

Note the pppoe0

In either case, dhcp6c is sending solicits but is getting no response from the ISP.

The settings should be like those I have shown in the attached image.

[earlish]

I factory defaulted the pfSense and I put the same config as yours, but still no IPv6.

ifconfig;

root: ifconfig
igb0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4c
	inet6 fe80::208:a2ff:fe0b:d44c%igb0 prefixlen 64 scopeid 0x1 
	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
igb1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4d
	inet 10.0.10.1 netmask 0xffffff00 broadcast 10.0.10.255 
	inet6 fe80::1:1%igb1 prefixlen 64 scopeid 0x2 
	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
igb2: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4e
	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
	status: no carrier
igb3: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4f
	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
	status: no carrier
pflog0: flags=100 <promisc>metric 0 mtu 33160
pfsync0: flags=0<> metric 0 mtu 1500
	syncpeer: 224.0.0.240 maxupd: 128 defer: on
	syncok: 1
enc0: flags=0<> metric 0 mtu 1536
	nd6 options=21 <performnud,auto_linklocal>lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
	options=600003 <rxcsum,txcsum,rxcsum_ipv6,txcsum_ipv6>inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 
	nd6 options=21 <performnud,auto_linklocal>pppoe0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1454
	inet 115.163.163.254 --> 59.146.160.74 netmask 0xffffffff 
	inet6 fe80::208:a2ff:fe0b:d44c%pppoe0 prefixlen 64 scopeid 0x9 
	nd6 options=21<performnud,auto_linklocal></performnud,auto_linklocal></up,pointopoint,running,noarp,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,rxcsum_ipv6,txcsum_ipv6></up,loopback,running,multicast></performnud,auto_linklocal></promisc></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></broadcast,oactive,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></broadcast,oactive,simplex,multicast></full-duplex></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast></full-duplex></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast>

dhcp6c logs;

Jun 21 18:52:27 	dhcp6c 	72748 	failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Jun 21 18:52:27 	dhcp6c 	72748 	failed initialize control message authentication
Jun 21 18:52:27 	dhcp6c 	72748 	skip opening control port
Jun 21 18:52:28 	dhcp6c 	72900 	Sending Solicit
Jun 21 18:52:28 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
Jun 21 18:52:29 	dhcp6c 	72900 	Sending Solicit
Jun 21 18:52:29 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
Jun 21 18:52:31 	dhcp6c 	72900 	Sending Solicit
Jun 21 18:52:31 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
Jun 21 18:52:35 	dhcp6c 	72900 	Sending Solicit
Jun 21 18:52:35 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
Jun 21 18:52:44 	dhcp6c 	72900 	Sending Solicit
Jun 21 18:52:44 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
Jun 21 18:53:01 	dhcp6c 	72900 	Sending Solicit
Jun 21 18:53:01 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
Jun 21 18:53:37 	dhcp6c 	72900 	Sending Solicit
Jun 21 18:53:37 	dhcp6c 	72900 	advertise contains NoPrefixAvail status 

Does this mean dhcp6c is getting a response, but there is no prefix?

[Guest]

Indeed it does, they are not offering a prefix.

[earlish]

Thanks for that,

So I'm wondering what does my ISP expect I can do with 1 IPv6 address (/128 ?) is that some kind of joke?

How can the crap consumer grade routers work in this case? Some kind of IPv6 pass-through/bridge?

Sorry I'm not so familiar with IPv6, but I thought it was supposed to get rid of all this NAT nonsense.

[awebster]

The sad truth is that many ISPs don't have a clue either and are hopelessly stuck in IPv4 mentality. 
Exercise your opinion with your wallet.

[Guest]

Best thing to do in the first instance is to email your ISP 2nd tier support and ask them what exactly they supply IPv6 wise.

[earlish]

Well it looks like I will be exercising my wallet, after I cancel this ISP after just one week and I have to pay the cancellation penalty. Their IPv4 is absolutely completely useless and going to IPv6 probably won't solve the problem as a lot of stuff is still in the IPv4 domain.

I just wanted to confirm that there is nothing silly I am doing with pfsense that would prevent me from getting IPv6 to work properly before I complained again to the ISP.

Cheers.

[earlish]

So it turns out if I use a v6 username (i.e. user@v6-isp.jp instead of user@isp.jp) for the PPPoE I can get a /56 prefix assigned. But by doing this I do not get an IPv4 address.

I did manage to get both IPv4 and IPv6 to work by adding another PPPoE tunnel on another interface. (OPT1 in my case)

So now my question is; do I need to use 2 interfaces (WAN and OPT1) to use 2 PPPoE tunnels, or can I use 2 PPPoE tunnels on 1 interface?
I couldn't find any information about this but I'm sure there is a better way than what I'm doing. Or is using 2 PPPoE tunnels just not the usual thing to do, as I did come across this thread https://arstechnica.com/civis/viewtopic.php?f=10&t=1378151

[gaijinboy]

@earlish Hi,

Do you still use pfsense?
I'm facing the same problem as you using AsashiNET provider.
Only the WAN gets the prefix, LAN It is not getting anything.
Please let me know if you found a solution because my provider doesn't support PPPoE for IPv6.

Thanks in advance.