-
Notifications
You must be signed in to change notification settings - Fork 121
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
10.2.0 - IPv6 default route being deleted #465
Comments
That log shows that dhcpcd just noted that the route was deleted, dhcpcd didn't delete it itself. |
What is the lifetime of the default route? Is it hitting zero at these times maybe? |
With dhcpcd 10.1.0, no lifetime is set :
With dhcpcd 10.2.0, a lifetime is set :
What seems to happen is that the lifetime is not reset to the value advertised by the router (4500 seconds) when a RA is received. Lifetime decreases until it gets negative and the route is deleted.
Typical RA from my ISP :
It is processed by dhcpcd :
But the default route's lifetime is not updated :
|
I'm seeing neither the "change" route log message, so it looks like it's not doing any route update after the initial push out to the kernel, and then the kernel is dutifully deleting the route after the expiry time. in 10.1.0 a lifetime is not set, so the kernel assumes "infinite" @jlsnt can you add an exit hook for ROUTERADVERT that logs the environment? If a router advertisement comes in it should be getting processed. I will try to replicate, but that info would help. |
Sure, which data are you interested in ? "ip route" 's output is already available above. |
@jlsnt ip route shows the aftermath. I'm curious what dhcpcd is seeing from the incoming RA. I add a file in /usr/libexec/dhcpcd-hooks that does something like
dhcpcd will push a lot of the info from the RA into the exit hook environment. the log should then contain a bunch of entries from the RA.
I wonder if the oversized MTU is causing it to think the route isn't the same? |
Here it is. Captured at dhcpcd's (10.2.0) startup.
|
I notice even in 10.1.0 it's not actually setting the mtu of 1540
But at least that gives me some more info, we do see it sending a lifetime.
I wonder if the MTU value is somehow short-circuiting the logic that tries to update the route. |
MTU was a red herring, it was just warning us that it was ignoring the "1540" and setting it to 1500. I'm still looking into why it might be skipping the route update. |
Sorry for the quick comment without detailed logs but I am having the same issue.
This is the RA with 1800sec lifetime every 30 minutes, dhcpcd gives me the "pid 0 deleted default route via" message.
dhcpcd.conf
|
Hello,
I upgraded from 10.1.0 to 10.2.0.
Since then, I noticed the IPv6 default route being deleted for no apparent (or understandable, to me at least) reason.
Mind the "pid 0 deleted default route via fe80::ba0:bab" log messages.
Falling back to 10.1.0 solves the issue.
I'm running Debian 12.
Please let me know if you need any kind of test/config change.
Configuration below :
Relevant logs (debug enabled) :
The text was updated successfully, but these errors were encountered: