Re: Re: Remotely exploitable crash in dhcpcd
Jason A. DonenfeldSat Jun 24 22:20:15 2017
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
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.
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.
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 has supported this for quite some time now, but dhcpcd-7 has changed
> a lot of internals.
Ah, makes sense.
Archive administrator: email@example.com