dhcpcd-discuss

Re: Re: Remotely exploitable crash in dhcpcd

Roy Marples

Sun Jun 25 10:46:25 2017

Hi Jason

On 24/06/17 22:35, Roy Marples wrote:
On 24/06/2017 22:20, Jason A. Donenfeld wrote:
On Sat, Jun 24, 2017 at 09:30:20AM +0100, Roy Marples wrote:
What dhcpcd is supposed to do is to use the lease on the interface with
the lowest metric when there are multiple active leases with the same IP
address.

This behavior is really not good in practice and does not work well for
me. What I'd prefer to see is that the IP address is assigned to *both*
interfaces, so that when the one with the lower metric goes down (i.e. I
unplug the ethernet cable so it falls back to wifi), the connection
keeps working and simply falls back to the next one. This would really
solve many of my problems.

I'm happy to entertain the idea.
Why don't you post a task at https://dev.marples.name and I'll see if I can do something over the weekend for it.

As it turned out my evening and morning plans went completely to pot thanks to an issue outside of my control so I had some unexpected time to look into this.

I created a task here:
https://dev.marples.name/T126

And an initial patch here:
https://dev.marples.name/D122

I've only tested this on Linux-4.4.
I'll test on the BSD's over the course of the week as they need to work to before this is committed.

Please review and test.

Roy

Follow-Ups:
Re: Re: Remotely exploitable crash in dhcpcdJason A. Donenfeld
References:
Remotely exploitable crash in dhcpcdJason A. Donenfeld
Re: Remotely exploitable crash in dhcpcdJason A. Donenfeld
Re: Re: Remotely exploitable crash in dhcpcdRoy Marples
Re: Re: Remotely exploitable crash in dhcpcdJason A. Donenfeld
Re: Re: Remotely exploitable crash in dhcpcdRoy Marples
Archive administrator: postmaster@marples.name