Show Posts
151
24.1 Legacy Series / Re: Dual WAN Dual IP Stack: gateway down, dpinger cannot bind to detached IPv6 addr
« on: February 12, 2024, 10:06:01 pm »
Nothing wrong with following up on your own post with additional information.
Unlikely that this is actually the issue you linked to. They're specifically discussing multiple SLAAC addresses on a single interface and RAs with a 0 router lifetime, neither of which is the case here.
I tried two SLAAC interfaces as well as one SLAAC and one DHCPv6 interface and don't see a detached SLAAC address in either case (didn't try a PPPoE parent though). Can you share details about your WAN / WAN2 configurations (SLAAC / DHCPv6)? And what does the Netgear advertise, DHCPv6 or SLAAC or both?
If nothing else works, you could not specify a monitor IP. dpinger will then ping the link-local gateway address, which doesn't require binding to a global source address.
And by the way,
- you don't need gateway groups when using default gateway switching and
- be aware that for IPv6 failover to actually work, you'll need to configure IPv6 outbound NAT for WAN2.
Cheers
Maurice
Unlikely that this is actually the issue you linked to. They're specifically discussing multiple SLAAC addresses on a single interface and RAs with a 0 router lifetime, neither of which is the case here.
I tried two SLAAC interfaces as well as one SLAAC and one DHCPv6 interface and don't see a detached SLAAC address in either case (didn't try a PPPoE parent though). Can you share details about your WAN / WAN2 configurations (SLAAC / DHCPv6)? And what does the Netgear advertise, DHCPv6 or SLAAC or both?
If nothing else works, you could not specify a monitor IP. dpinger will then ping the link-local gateway address, which doesn't require binding to a global source address.
And by the way,
- you don't need gateway groups when using default gateway switching and
- be aware that for IPv6 failover to actually work, you'll need to configure IPv6 outbound NAT for WAN2.
Cheers
Maurice
