dhcpcd-discuss

 Why would it confuses dhcpcd at renewal?
Since the kernel manages routing, and the kernel has the final word,
I think dhcpcd should use whatever routing the kernel tells it. dhcpcd
should give the kernel routing top priority, falling back to some other
routing table only if there is some predetermined necessities. Isn't it a bug
if that is not the case?
And doesn't exit-hook runs at renewal too? If it does, dhcpcd can keep
up setting whatever the dhcp server tells it to, and the exit-hook would
change that afterwards. hopefully, the transition time will not be noticeable.
Or, even better, isn't there a way to tell dhcpcd to ignore some of the 
settings the dhcp serever asks for?     On Thursday, December 12, 2019, 12:46:31 PM GMT, Roy Marples <roy@xxxxxxxxxxxx> wrote:  
 
 On 08/12/2019 10:46, Ron Varburg wrote:
> Hello,
> Obviously, I am not Roy.
> Have you tried to set appropriate ip route commands at exit-hook?
> I don't know if that is supposed to work. Just throwing a thought which 
> looks to me at the right direction.
> Do let us know your findings. I do hope it is right of me to ask you to 
> further post to the list about this subject.

While this would of course work, it might confuse dhcpcd when it 
re-examines the routing table at renewal. This though is speculation.

Out of curisosity, have you tried it Andrey - and if so, what were the 
results?

Roy