NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
(May be applicable to other Netgear devices as well)
Current firmware: V2.0.0.76
In Advanced LAN Setup, there is currently the option to use RIP1 or RIP2 protocols:
However, these protocols only support IPv4. In order to support routing IPv6, there is also a need to support RIPng (RFC 2080), otherwise, static routing is necessary. Unfortunately, static routes in an environment with dynamically allocated IPv6 prefix delegation is not a good idea - it would be much better to use RIPng and not have to manage (potentially changing) static routes.
Given that there are already multiple RIP protocols supported, the addition of RIPng seems like it should be a relatively simple change.
1 Comment
I also have a problem with my Orbi RBR50 :
On the IPv6 page : I can see my public IPv6 Adress under "Router's IPv6 Address On WAN" when the "Internet Connection Type" is set to "DHCP". But my "Router's IPv6 Address On LAN" is "Not Available", and when i'm connecting to the network from a computer, I see that the "Link-local IPv6 Address" and the "IPv6 Default Gateway" are correctly set to local adresses but the "IPv6 Address" and the "Temporary IPv6 Address" are set to strange IPv6 adresses : their prefix is "fd4b:bc9:1b74:1:" and it's not my public IPv6 adress and my IPv6 is not working.
I think that IPv6 should work because the routeur sees my public IPv6 adress with all allocated adresses (/64) but I probably made a mistake somewhere while configuring...