Re: Re: Remotely exploitable crash in dhcpcd
Roy Marples
Sat Jun 24 21:35:05 2017
Hi Jason
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.
If for some unfortunate reason you're not willing to do that, perhaps
you could at least make this an option?
If neither, then maybe the better behavior would be for dhcpcd to
reassign the IP address when one interface goes down to the
still-existing interface. This would achieve ± the same as above, but
would be slightly less error prone.
It already does this .....
The current behavior also rarely actually works, with it being quite
unreliable which interface winds up getting the IP. The whole current
mechanism is just broken.
It's odd as it works really well for me.
I actually had a hard time getting it to crash - I had to ensure that
the wired interface started down and stayed down until the wifi reached
the BOUND state and then start the wired interface by hand.
Roy
Archive administrator: postmaster@marples.name