I have a network WIFI interface that will be always in monitor mode, but I suspect the DHCP client is trying to set it up and I do see the following errors on my logs (journalctl) constanstly:
<code>Jul 28 20:05:38 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: Invalid HW-addr family 0x0323
Jul 28 20:05:38 raspberypi1 NetworkManager[1087]: <info> [1722211538.3540] device (wlp1s0u1u3): supplicant interface state: inactive -> interface_disabled
Jul 28 20:05:38 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:38 raspberypi1 NetworkManager[1087]: <info> [1722211538.3623] device (wlp1s0u1u3): supplicant interface state: interface_disabled -> inactive
Jul 28 20:05:39 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:43 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:48 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:55 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:06:05 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:06:19 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:06:39 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:07:08 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:07:51 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
</code>
<code>Jul 28 20:05:38 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: Invalid HW-addr family 0x0323
Jul 28 20:05:38 raspberypi1 NetworkManager[1087]: <info> [1722211538.3540] device (wlp1s0u1u3): supplicant interface state: inactive -> interface_disabled
Jul 28 20:05:38 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:38 raspberypi1 NetworkManager[1087]: <info> [1722211538.3623] device (wlp1s0u1u3): supplicant interface state: interface_disabled -> inactive
Jul 28 20:05:39 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:43 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:48 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:55 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:06:05 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:06:19 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:06:39 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:07:08 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:07:51 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
</code>
Jul 28 20:05:38 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: Invalid HW-addr family 0x0323
Jul 28 20:05:38 raspberypi1 NetworkManager[1087]: <info> [1722211538.3540] device (wlp1s0u1u3): supplicant interface state: inactive -> interface_disabled
Jul 28 20:05:38 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:38 raspberypi1 NetworkManager[1087]: <info> [1722211538.3623] device (wlp1s0u1u3): supplicant interface state: interface_disabled -> inactive
Jul 28 20:05:39 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:43 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:48 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:05:55 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:06:05 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:06:19 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:06:39 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:07:08 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
Jul 28 20:07:51 raspberypi1 wpa_supplicant[1163]: wlp1s0u1u3: CTRL-EVENT-SCAN-FAILED ret=-95
There is a way to tell the DHCP client to ignore this interface completely?
Not sure what to try to disable this error, I don’t see any options for /etc/wpa_supplicant/wpa_supplicant.conf
(man wpa_supplicant.conf).
Thanks,
Jose