dhcpcd-discuss

Hi Tim

On 06/04/2020 17:20, Tim Tassonis wrote:
> Hi all
>
>
> After initial success on my ethernet interface, I now tried dhcpcd on my wifi 
> interface, sadly unsuccessfully.
>
> I'm runninng network-manager 1.14.4 with wpasupplicant 2.9 and had/have no 
> problems whatsoever with 8.1.7, but with 9.0.0, I get
>
>
> Apr  6 18:08:32 henderson dhcpcd[2983]: wlp2s0: new hardware address: 
> 72:2e:1f:16:5e:cf
> Apr  6 18:08:44 henderson dhcpcd[2983]: wlp2s0: new hardware address: 
> 0c:8b:fd:97:ce:3f
> Apr  6 18:08:47 henderson NetworkManager[3204]: <info> [1586189327.9625] dhcp4 
> (wlp2s0): dhcpcd started with pid 3592
> Apr  6 18:08:47 henderson dhcpcd[3601]: wlp2s0: connected to Access Point `babasis'
> Apr  6 18:08:47 henderson dhcpcd[3601]: DUID 
> 00:01:00:01:26:1e:0f:ac:f0:1f:af:5d:ec:ba
> Apr  6 18:08:47 henderson dhcpcd[3601]: wlp2s0: IAID fd:97:ce:3f
> Apr  6 18:08:48 henderson dhcpcd[3601]: wlp2s0: rebinding lease of 192.168.123.138
> Apr  6 18:08:48 henderson dhcpcd[3601]: wlp2s0: leased 192.168.123.138 for 43200 
> seconds
> Apr  6 18:08:48 henderson dhcpcd[3601]: wlp2s0: adding route to 192.168.123.0/24
> Apr  6 18:09:33 henderson dhcpcd[3601]: received SIGTERM, stopping
> Apr  6 18:09:33 henderson dhcpcd[3601]: wlp2s0: removing interface
> Apr  6 18:09:33 henderson dhcpcd[2983]: wlp2s0: new hardware address: 
> ba:71:48:96:41:e6

Seems like you have too many dhcpcd's managing wlp2s0 :/

> Apr  6 18:09:34 henderson dhcpcd[3601]: dhcpcd exited
> Apr  6 18:09:34 henderson dhcpcd[3601]: main: write: Broken pipe
>
>
> This is on linux, if you need further details on my setup, I will gladly provide 
> that.

Output of this command please
ps axu | grep dhcpcd

Can you also try my git master please? It's possible that two recent commits 
might have resolved this.

Roy