dhcpcd-discuss

Re: Re: Remotely exploitable crash in dhcpcd

Jason A. Donenfeld

Sun Jun 25 16:48:31 2017

Hi Roy,

Both interfaces now get both address, which is great.

However, I've found two small bugs in this initial stab at the implementation:

- eth0 is metric 200
- wlan0 is metric 300
- set eth0 up --> eth0 gets 10.10.10.100
- set wlan0 up --> wlan0 gets 10.10.10.100
- unplug eth0 --> ARP sent wlan0 so smooth transition
- plug eth0 --> ARP sent on wlan0 instead of on eth0, so transition is
not smooth, until gateway does its own ARP

and

- eth0 is metric 200
- wlan0 is metric 300
- set eth0 up --> eth0 gets 10.10.10.100
- set wlan0 up --> wlan0 gets 10.10.10.100
- unplug wlan0 --> ARP sent on eth0 even though it isn't needed, I think
- plug wlan0 --> ARP sent on wlan0, which is incorrect, so pings of
eth0 get interrupted temporarily

Jason

Follow-Ups:
Re: Re: Remotely exploitable crash in dhcpcdRoy Marples
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
Re: Re: Remotely exploitable crash in dhcpcdRoy Marples
Re: Re: Remotely exploitable crash in dhcpcdJason A. Donenfeld
Archive administrator: postmaster@marples.name