dhcpcd-discuss

Greetings Roy,

> Nothing indicates that it wasn't from your log?
I see this lines:
Sep 18 10:13:33 [2357]: sending commands to master dhcpcd process
Sep 18 10:13:33 [2357]: send OK
Sep 18 10:13:33 [1674]: control command: dhcpcd -t 0 -m 6 veth

twice in the log, only the second time veth gets ip

> My bad, I read that as capital M. Your command is fine.
>
> You could achieve the same in dhcpcd.conf like so:
>
> interface veth
> 	metric 6
>
> interface enp0s20f0u7
> 	metric 8
indeed but that will break the distro's startup dep tree.
e.g. other net depended services won't start.

> Ah. You might want to consider using udev to rename it.
> If dhcpcd is listening to udev then it ensures that udev can rename the device
> correctly and only then start it.
>
> Any other method involves a race between dhcpcd and something else which might
> be the real problem here.
not sure I understand what udev net renaming has to do with it?

> As libvirt is creating the interface, I think we can solve this by removing
> net.veth and letting udev handle the rename.

can you explain how?