Arch Linux

Comix

Member

Registered: 2020-08-17

Posts: 13

[SOLVED]wlo1: dhcp_envoption 213: Operation not supported

i found that in my log file,and there is another error

dhcpcd[484]: no valid interfaces found

but my network is working normally, so should i solve this problem?
if the anwser is yes, how can i fix it?

Last edited by Comix (2021-02-06 16:48:43)

rsmarples

Member

Registered: 2009-05-12

Posts: 287

Re: [SOLVED]wlo1: dhcp_envoption 213: Operation not supported

DHCP 213 option is defned here:
https://roy.marples.name/cgit/dhcpcd.gi … .conf#n312

For a domain name option to return operation not supported, it's using a reserved encoding option as defined in RFC1035 4.1.4
https://roy.marples.name/cgit/dhcpcd.gi … mon.c#n333
https://tools.ietf.org/html/rfc1035#page-30

The only RFC I can find which updates this is an expired one here:
https://tools.ietf.org/html/draft-ietf- … ression-05

So my guess is that have a non RFC compliant DHCP option.
You can verify this with wireshark capturing the network traffic and filtering for bootp.
restart dhcpcd during this and it should easily get picked up. I'm actually curious as to what is looks like so if you could email it to me at roy@marples.name I'd appreciate it!

As to the know valid interfaces found ..... well if dhcpcd starts too early and your interfaces get added much later it's possible you could see that message I guess.
To be sure I would add this at the top of /etc/dhcpcd.conf
debug
logfile /var/log/dhcpcd.log

and pastebin the logfile somewhere  so we can see why it's saying that.

Comix

Member

Registered: 2020-08-17

Posts: 13

Re: [SOLVED]wlo1: dhcp_envoption 213: Operation not supported

this is dhcpcd.log

Feb 06 13:43:39 [444]: dhcpcd-9.4.0 starting
Feb 06 13:43:39 [444]: chrooting as dhcpcd to /var/lib/dhcpcd
Feb 06 13:43:39 [444]: sandbox: seccomp
Feb 06 13:43:39 [449]: spawned master process on PID 449
Feb 06 13:43:39 [450]: udev: starting
Feb 06 13:43:39 [450]: dev: loaded udev
Feb 06 13:43:39 [449]: spawned privileged actioneer on PID 450
Feb 06 13:43:39 [449]: spawned network proxy on PID 451
Feb 06 13:43:39 [449]: spawned controller proxy on PID 452
Feb 06 13:43:39 [449]: DUID 00:04:4c:4c:45:44:00:4c:4a:10:80:34:b8:c0:4f:51:34:32
Feb 06 13:43:39 [449]: lo: ignoring due to interface type and no config
Feb 06 13:43:39 [449]: no valid interfaces found
Feb 06 13:43:39 [450]: wlo1: libudev: add
Feb 06 13:43:39 [449]: wlo1: interface added
Feb 06 13:43:39 [449]: wlo1: executing: /usr/lib/dhcpcd/dhcpcd-run-hooks PREINIT
Feb 06 13:43:39 [450]: wlo1: libudev: move
Feb 06 13:43:39 [449]: wlo1: executing: /usr/lib/dhcpcd/dhcpcd-run-hooks NOCARRIER
Feb 06 13:43:40 [449]: wlo1: waiting for carrier
Feb 06 13:43:40 [449]: wlo1: carrier acquired
Feb 06 13:43:40 [449]: wlo1: executing: /usr/lib/dhcpcd/dhcpcd-run-hooks CARRIER
Feb 06 13:43:40 [449]: wlo1: IAID 41:cf:ff:58
Feb 06 13:43:40 [449]: wlo1: adding address fe80::ab35:91e0:4e09:84df
Feb 06 13:43:40 [449]: wlo1: pltime infinity, vltime infinity
Feb 06 13:43:40 [449]: wlo1: delaying IPv6 router solicitation for 0.5 seconds
Feb 06 13:43:40 [449]: wlo1: delaying IPv4 for 0.3 seconds
Feb 06 13:43:40 [449]: wlo1: carrier lost
Feb 06 13:43:40 [449]: wlo1: executing: /usr/lib/dhcpcd/dhcpcd-run-hooks NOCARRIER
Feb 06 13:43:40 [449]: wlo1: deleting address fe80::ab35:91e0:4e09:84df
Feb 06 13:43:40 [449]: wlo1: old hardware address: 90:78:41:cf:ff:58
Feb 06 13:43:40 [449]: wlo1: new hardware address: 0a:94:01:61:6f:2d
Feb 06 13:43:40 [449]: wlo1: interface updated
Feb 06 13:43:40 [449]: wlo1: waiting for carrier
Feb 06 13:43:40 [450]: virbr0: libudev: add
Feb 06 13:43:40 [449]: virbr0: ignoring due to interface type and no config
Feb 06 13:43:44 [449]: wlo1: old hardware address: 0a:94:01:61:6f:2d
Feb 06 13:43:44 [449]: wlo1: new hardware address: 90:78:41:cf:ff:58
Feb 06 13:43:45 [449]: wlo1: carrier acquired
Feb 06 13:43:45 [449]: wlo1: connected to Access Point: HUAWEI-040RH6
Feb 06 13:43:45 [449]: wlo1: executing: /usr/lib/dhcpcd/dhcpcd-run-hooks CARRIER
Feb 06 13:43:45 [449]: wlo1: IAID 41:cf:ff:58
Feb 06 13:43:45 [449]: wlo1: adding address fe80::d8e2:4b2a:12b1:120d
Feb 06 13:43:45 [449]: wlo1: pltime infinity, vltime infinity
Feb 06 13:43:45 [449]: wlo1: delaying IPv6 router solicitation for 0.2 seconds
Feb 06 13:43:45 [449]: wlo1: delaying IPv4 for 1.1 seconds
Feb 06 13:43:45 [449]: wlo1: soliciting an IPv6 router
Feb 06 13:43:45 [449]: wlo1: delaying Router Solicitation for LL address
Feb 06 13:43:46 [449]: wlo1: reading lease: /var/lib/dhcpcd/wlo1-HUAWEI-040RH6.lease
Feb 06 13:43:46 [449]: wlo1: rebinding lease of 192.168.3.68
Feb 06 13:43:46 [449]: wlo1: sending REQUEST (xid 0xcada7a04), next in 4.5 seconds
Feb 06 13:43:46 [449]: wlo1: acknowledged 192.168.3.68 from 192.168.3.1
Feb 06 13:43:46 [449]: wlo1: leased 192.168.3.68 for 86400 seconds
Feb 06 13:43:46 [449]: wlo1: renew in 43200 seconds, rebind in 75600 seconds
Feb 06 13:43:46 [449]: wlo1: writing lease: /var/lib/dhcpcd/wlo1-HUAWEI-040RH6.lease
Feb 06 13:43:46 [449]: wlo1: adding IP address 192.168.3.68/24 broadcast 192.168.3.255
Feb 06 13:43:46 [449]: wlo1: adding route to 192.168.3.0/24
Feb 06 13:43:46 [449]: wlo1: adding default route via 192.168.3.1
Feb 06 13:43:46 [449]: wlo1: dhcp_envoption 213: Operation not supported
Feb 06 13:43:46 [449]: wlo1: dhcp_envoption 213: Operation not supported
Feb 06 13:43:46 [449]: wlo1: executing: /usr/lib/dhcpcd/dhcpcd-run-hooks REBOOT
Feb 06 13:43:47 [449]: wlo1: sending Router Solicitation
Feb 06 13:43:51 [449]: wlo1: sending Router Solicitation
Feb 06 13:43:55 [449]: wlo1: sending Router Solicitation
Feb 06 13:43:59 [449]: wlo1: sending Router Solicitation
Feb 06 13:43:59 [449]: wlo1: no IPv6 Routers available

rsmarples

Member

Registered: 2009-05-12

Posts: 287

Re: [SOLVED]wlo1: dhcp_envoption 213: Operation not supported

I was emailed the wireshark dump and I can confrm that the value given for option 213 is invalid because it does not follow domain name encoding as specified in RFC5986 section 3.2 which goes to 3.1 which in turn goes to RFC1035.

Basically the first otect of the value must be the length of the label, but here it's just an ascii character.

ie the vendor uses a plain string which is not RFC compliant, hence the warning.

To work around this, you can force your own option in dhcpcd.conf like so:
define 213    string            access_domain

rsmarples

Member

Registered: 2009-05-12

Posts: 287

Re: [SOLVED]wlo1: dhcp_envoption 213: Operation not supported

From the dhcpcd log, my analysis was also correct! We can see that udev announced the interface after dhcpcd has started.
There's currentlly no option to silence that diagnostic and not sure I would want to loose it by default.

Comix

Member

Registered: 2020-08-17

Posts: 13

Re: [SOLVED]wlo1: dhcp_envoption 213: Operation not supported

Thank you!
The first problem has been solved, but if i upgrade dhcpcd in the future, should i delete "define 213    string       access_domain"?
The second problem does not seem to be solved currently, but it's harmless, am i right?

rsmarples

Member

Registered: 2009-05-12

Posts: 287

Re: [SOLVED]wlo1: dhcp_envoption 213: Operation not supported

No, you keep your custom define as the current dhcpcd default will not change - dhcpcd sticks to being RFC compliant.
Now, if your DHCP server becomes RFC compliant, then you can remove the override

Correct the second problem is not solved and it's currently harmless.
I think dhcpcd should warn still because the expectation is to get a working network address, but it cannot do so without an interface.

Comix

Member

Registered: 2020-08-17

Posts: 13

Re: [SOLVED]wlo1: dhcp_envoption 213: Operation not supported

OK, thank you for your patient help!