NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WAN IPv6 Prefix Delegation doesn't work
I bought recently a new FVS328Gv2 as replacment for an older D-Link DIR-825. The FVS318Gv2 is connected to an AVM Fritz!Box 6490 which is the internet access router of my provider. The Fritz!Box 6490...
Hi DaneA, dear community,
here some more update acc. to IPv6 prefix delegation on WAN side. The last problem I was struggeling around was, that I used a VLAN configuration on my FVS318Gv2 which was not compatible with IPv6 prefix delegation. I had some more disscusions with the help of NETGEAR support and figured out that delegated IPv6 prefixes are alway attached to VLAN1 the default VLAN.
I got the following advise from the support:
So if you are using prefix delegation, you accept that the subnet associated with the particoular hosts is always the same (and it should not be if you are using different VLANs). In our case, RADVD (Router Advertisement Daemon) is making the choice for us and it picks automatically VLAN 1 when he try to assign an IPv6 address to the clients. This done according to the standards that define RADVD.
So folks that all for this topic.
Which you you a pleasant new year.
Regards
Andreas
Hi DaneA, dear community,
here a short update of this topic which I could clarify with the help of NETGEAR support.
The solution was quite simple. I needed to reboot my Frtitzbox 6490. The problem was that either my ISP or the Fritzbox vendor deliver IPv6 prefix delegations with a lifetime flag set to 0 (which means infinite). Due to the fact that I get a prefix of length 62 from my ISP there are only 4 possible IPv6 subnets available. And these seam to be already assigned to my older DIR-825. After I changed the DIR-825 to the FVS318Gv2 I did no reboot of the Fritzbox because I thought that DHCPv6 prefix delegations would have a limited lifetime.
So it is a good advice to do a reboot of an internet access router when you change the IPv6 infrastructure (firewall, router) behind it. Especially when you get a IPv6 prefix of a large length.
Regards
Andreas
PS.: I'm actually clarify other IPv6 routing problems which came up after prefix delegation is working. I'll keep you informed.
Hi DaneA, dear community,
here some more update acc. to IPv6 prefix delegation on WAN side. The last problem I was struggeling around was, that I used a VLAN configuration on my FVS318Gv2 which was not compatible with IPv6 prefix delegation. I had some more disscusions with the help of NETGEAR support and figured out that delegated IPv6 prefixes are alway attached to VLAN1 the default VLAN.
I got the following advise from the support:
So if you are using prefix delegation, you accept that the subnet associated with the particoular hosts is always the same (and it should not be if you are using different VLANs). In our case, RADVD (Router Advertisement Daemon) is making the choice for us and it picks automatically VLAN 1 when he try to assign an IPv6 address to the clients. This done according to the standards that define RADVD.
So folks that all for this topic.
Which you you a pleasant new year.
Regards
Andreas
Thank you for the update. :) The information you have shared would really help a lot of community members.
Cheers,
DaneA
NETGEAR Community Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
