stf interface IPv6 IP never leaves tentative state
I'm running 2.3 built on Fri Jan 08 15:32:00.
I use Charter's 6RD service which works great but I have to give the gateway monitor an address to ping. With 2.3 my gateway monitor doesn't come up when I specify the same address I use in 2.2.6.
I can see dpinger is running in "ps -aux" with an ipv4 address that makes sense & I can see the ipv4 gateway in /var/log/gateways.log but there isn't any ipv6 stuff in there at all.
I suspect it's related to issue #5711. If you tell me how to run "setup_gateways_monitor()" to manually see if I can get the ipv6 monitor working I'd be happy to try.
#1 Updated by Chris Buechler over 4 years ago
- Category set to Gateway Monitoring
- Assignee set to Chris Buechler
- Target version set to 2.3
- Affected Architecture added
- Affected Architecture deleted (
on a version that new it's not related to #5711. this is already something I was planning on going back to check for 6rd, to me for review.
#3 Updated by Will Wainwright over 4 years ago
This is what I get:
[2.3-BETA][email@example.com]/root: ifconfig wan_stf
wan_stf: flags=4001<UP,LINK2> metric 0 mtu 1280
inet6 2602:100:470e:4f67:: prefixlen 32 tentative
v4net 18.104.22.168/32 -> tv4br 22.214.171.124
#4 Updated by Chris Buechler over 4 years ago
Thanks, I thought maybe my test setup was just being weird in never leaving "tentative" state, guessing yours is working, but the v6 IP on the stf interface never leaves tentative? That's probably the issue, which is actually in 6rd not gateway monitoring.
#6 Updated by Chris Buechler over 4 years ago
This is broken in 10-STABLE, now has open bug here:
#9 Updated by Chris Buechler over 4 years ago
- Status changed from Confirmed to Feedback
Thanks for the confirmation, Will.
This fixes other circumstances I was seeing as well. Following up on that FreeBSD PR to see if that can be committed.
This is fixed, but leaving to feedback because we want it to be fixed in FreeBSD and to revert the change from our tree.