-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 gateway monitoring not working when WAN is a link local. #2164
Comments
|
Funny, this. 4590b17 I refactored this, but now it looks like it was a silly piece of code in the first place. Can you spot an issue with the refactor besides moving it out of the if block for when gateways are set? |
|
Before this, the line was a clean copy from 2014... 727453c |
|
This is today. And I also found this... |
|
Was the original intention just to delete the files to clean up, or was it to do with some strange gateway issue? Cannot see where you've moved it to as I'm now on my tablet and it won't play nicely with github. :) |
|
I've moved it out of the if loop below. I think the system tries to delete stale gateways and put them back only when working. At some point it grew to do IPv6 as well. Organically grown, outlived its prime time... |
|
Try this.... I need to take this further though, not backwards. |
If we don't have default gateways and no connectivity, we cannot rely on the idea that "WAN" will save us. It could be an OPT interface instead... PR: #2164
|
May still walk all over you, now simply when you less expect it. |
|
I have a better solution for this logic ready, it should hit master in the next two days. |
Inspired by: pfsense/pfsense@d35dfaaec (cherry picked from commit 4f955e4)
One of my testers has an issue whereby he cannot get v6 gateway monitoring to work. On investigation I find that the *_defaultgw6 file is empty. This file is echoed out by rtsold and it took me a while to find the cause and it's in system.inc lines 460 to 463.
What is the purpose of this apart from deleting the files at this point?
The text was updated successfully, but these errors were encountered: