dhcpcd-discuss

On Tue, Jun 30, 2020 at 01:55:38PM +0100, Roy Marples wrote:
> That's not a bug, that's a feature :)
> Because you restricted dhcpcd to lagg0 via the commandline, all subsequent
> commands need to be limited the same way
>
> dhcpcd lagg0	# Start dhcpcd on lagg0
> dhcpcd -n	# If dhcpcd is not started on all interfaces, start it or rebind
>
> What you need to do is:
> dhcpcd -n lagg0
>
> Notice that `dhcpcd -x` will likewise fail, but `dhcpcd -x lagg0` will work.
>
> This is why it's generally better to limit the interfaces in dhcpcd.conf to
> save any potential issues on the command line.
> This behaviour is documented in dhcpcd(8) under the "Multiple interfaces" section.
>
> Does this fix your issue?
>
> Roy

Ah, so it's my missunderstanding of -n parameter. Thank you very much
for your time and awesome software! :o) Everything works as expected.

Regards,
meka

Attachment: signature.asc
Description: PGP signature