Track interface seems not to work
-
Hi,
after spending several days of bringing ipv6 online via pfSense, I gave up for now and trying to get help.
I have a Fritzbox with IPv6 support by my cable isp which I have to use, I am using the ipv6 tunnel functionality to get a working tunnel to Sixxs.
I got a /48 prefix by Sixxs now and are trying to get IPv6 working on my second subnet which is routed via a pfSense server behind the fritzbox.IPv6 is working great on the fritzbox subnet and on the pfsense WAN interface (ping & dns to the internet e.g. ipv6.google.com).
I configured the interfaces as following:
em1 (wan): dhcpv6 client, delegation size /62 (according to the fritzbox help thats the right size for routers behind)
em0 (lan): track interface, prefix ID 0on the pfSense box itself I have ipv6 connectivity but no client on my subnet gets an official ipv6 adress (2001:xxx), also the LAN interface itself does not get one.
Beside some fancy log messages in the routing log I get no further info if anything is missing:
Apr 25 16:30:45 radvd[37505]: RDNSS address fd00::2665:11ff:fefa:8158 received on em1 from fe80::2665:11ff:fefa:8158 is not advertised by us Apr 25 16:30:45 radvd[37505]: our AdvLinkMTU on em1 doesn't agree with fe80::2665:11ff:fefa:8158 Apr 25 16:39:52 radvd[37505]: our AdvCurHopLimit on em1 doesn't agree with fe80::2665:11ff:fefa:8158 Apr 25 16:39:52 radvd[37505]: our AdvOtherConfigFlag on em1 doesn't agree with fe80::2665:11ff:fefa:8158 Apr 25 16:39:52 radvd[37505]: our AdvValidLifetime on em1 for 2001:4dd0:fbe3:: doesn't agree with fe80::2665:11ff:fefa:8158 Apr 25 16:39:52 radvd[37505]: our AdvPreferredLifetime on em1 for 2001:4dd0:fbe3:: doesn't agree with fe80::2665:11ff:fefa:8158 Apr 25 16:39:52 radvd[37505]: RDNSS address fd00::2665:11ff:fefa:8158 received on em1 from fe80::2665:11ff:fefa:8158 is not advertised by us Apr 25 16:39:52 radvd[37505]: our AdvLinkMTU on em1 doesn't agree with fe80::2665:11ff:fefa:8158
Actually I have no idea what I can do to supply a subnet to my clients on LAN behind pfSense.
I am using the following daily build:
2.1-BETA1 (amd64)
built on Tue Apr 23 20:41:18 EDT 2013
FreeBSD 8.3-RELEASE-p7Can anybody tell me what to investigate further or where to start?
Thanks,
Dan -
I am a bit further now, LAN interface has now also an official IP (some reboots fixed it).
What is left is that my local clients don't get an IP, isn't a DHCP6 needed? I ask cause I cannot enable it (no static IP on any interface).Anyone has an idea?
Dan
-
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.
-
Make sure "radvd" is running in status -> services; there's some problem that causes it to not get started automatically in some cases.
-
Runs fine, but clients do not get any ipv6 related setting.
Even track interface seems not to work anymore since my LAN interface also has no ipv6 anymore, without changing anything on pfSense!
Seems the whole ipv6 support is extremely buggy on Fritzbox or pfSense side.Even better as I just recognize: As long as mein LAN interface has a IPv6 adress, pfSense will hardcrash from time to time. I already sent 3 crash reports. The funny thing: if the interface does not get a IPv6 adress, there will be no crash.
Hopefully some dev is able to trace that down with the debug logs uploaded…
Dan