WiFi issues on the zeroes

urostor · 20 June 2024 06:54

To get things straight:

I am using the zero 3 overlay already (but there seems to be no difference in WiFi behaviour between them).
Yes, Ethernet was disabled in dietpi-config before removing the adapter (my previous post was chronological)
yes, WiFi does work after disabling in dietpi-config and then re-enabling it again. There are no issues with loading the kernel module again. It does not work after booting when the ethernet adapter in enabled with a cable connected. Just trying to reconnect fails, WiFi must be disabled and enabled again. I could send here the console output of reconnection attempts but it disappears in dietpi-config…
I doubted that it’s a routing issue because the WiFi is DOWN when it does not work. If I understand correctly, if it was a routing issue, it would be UP and connected but no data could be sent or received. Unless it is turned DOWN automatically when no proper connection can be made due to routing. Your explanation makes sense.
I don’t need two connections, I was just using Ethernet because WiFi wouldn’t connect (but there are indeed situations in which it’s useful to have two).

Now the question is: if it is indeed a routing issue, why does it not manifest when WiFi is disabled and re-enabled some time after booting, if ethernet is connected too? Because in this case I can happily use ethernet and WiFi simultaneously. You say that it removes the broken gateway, which makes sense. But would it still happen this way if Ethernet was enabled but there was no adapter? This seems to be the case for me. Plus it can cause the board not to boot at all because of the infinite timeout problem.

bjmurrey · 20 June 2024 14:45

so I did a few more tests and variations on my zeroes of various flavors.

all of them default to eth0 out route if it is configured and enabled, making wifi useless, whether onboard or usb etc.

what I did to get wifi working on Opi Zero2w w/ usb hub-nic hat:

disable wifi onboard. reboot
disable eth0 onboard reboot
enable wifi onboard, reboot
config wifi ssid (delete any existing and set up 1 only), apply settings. reboot.
enable eth0 reboot
config eth0 reboot
now both interfaces are up and accessible with NO MODS TO ANYTHING ELSE

On the PiZero2W i discovered more interesting behavior. It uses OTG adapter for any keyboard connections, etc. If you use a usb hub, to get access to more than one port, AND that hub has a built-in NIC, YOU WILL HAVE PROBLEMS all the time no matter what you do because the hub nic becomes eth0, the default route, etc, and then you remove it. Everything fails, no ssh access, etc… hook it all back up… retry, cuss, smash keyboard, cuss Dietpi… and it’s just doing what you told it to do.

So I tried something different. DO NOT USE A USB HUB WITH A NIC ON IT!!
Use something like this instead - KVM switch with usb hub built in - no NIC

This kvm requires hdmi+one usb a connection to work. So connect it to the pi via the OTG cable. On the body of the KVM plug in keyboard and you have a 2nd open USB a port - use this for adding a USB wifi adapter and for configuration, verifying everything works and then you can be CERTAIN when you disconnect the kvm, plug whatever adapter back into the OTG cable alone, or just use onboard wifi only without eth0, it will work as expected and intended.

this works because there is no NIC onboard the zero, none on the “usb hub” we are using, and so the INVISIBLE PHANTOM ETH0 route and interface never gets created.

Does this make sense? Does this help you at all? I’m certain your dietpi is FINE and you Hardware is probably FINE. the problem is the order of operations that dietpi requires and what you are expecting it to do are not the same.

dietpi is opaque in its networking the eth0 , changing it from onboard or none to eth0 on from usb hub, etc. it’s just done and you’re looking for wifi stuff… lol

again, reboot between each step. start with disabling everything. then enable wifi onboard (or plug in usb wifi to the kvm hub port), reboot, config , reboot, test . if working now you can set your 2nd adapter, wlan1 or eth0 or whatever and it will work.

@MichaIng - what do you think about displayaing the current route info in the config screen of dietpi when you pull up dietpi-config / networking ? Or add it to the MOTD banner (it’s kind of already there - if you’re routes are jacked it will always show eth0 or docker0 never wlan0 if you’ve not followed order of operations and steps above). But if you dont know what youre NOT seeing there that ought to be there, it’s something even I missed over and over. It may be helpful to have the existing MOTD banner, but add all phy interfaces to list even if not configed or configed wrong, as well as print default route and interface. This would give at a glance, the info necessary to know without testing anything that you will or will not be online.

bjmurrey · 20 June 2024 17:23

here’s another option for keeping wlan and eth apart config -wise…

.192 subnets. Lol One gateway / default route.

/192 subnet mask will give you 4 networks and 62 useable ips per network for machine addressable ips.

router
192.168.1.1
255.255.255.192

pi1
wlan0 192.168.1.66/192
eth0 192.168.1.132/192

pi2
wlan0 192.168.1.67 /192
eth0 192.168.1.133 /192

desktop Ubuntu /mac / iphone whatever
wlan0 192.168.1.68 /192
eth0 192.168.1.134 / 192

Having the /192 subnet mask gives you 4 networks in the reserved (private) ranges avail on ONE home router: 192.168.1.x
Net 1: 0-63
Net 2: 64-127
Net 3: 128-191
Net 4: 192-256

each net needs a gateway and broadcast so you’re wasting first and last ip of each net above. 62 left.

Example:
Net 1: Network 192.168.1.0, Brdcst: 192.168.1.63, ip range .1-.62 /192

Our router is on Net 1 @ 192.168.1.1 - this is our default route for each network no matter what machine we are configuring inside the lan or what subnet it’s on. All traffic hits this and then gets forwarded to the appropriate network and therefore interface, respectively.

Keep the Net 1 range for equipment that all your networks (net2 net3 etc aka wlan0, eth0, etc) need to access. This way it’s on the same network and port as the LAN port of router. anything not found gets forwarded to WAN by router. Use this network for your family, guests, etc so they arent on your network and cant access anything without any firewalling required!

Use net 2 range for wlan0 on all machines
Use net 3 range for eth0 on all machines
use net 4 range for wlan1/eth1 on all machines… for example…

whatever you do, be consistent and document your code with comments so future you remembers what’s going on.

Thoughts? seems like it’s way simpler and plays nice with things like HostAPd WIFIHotspot etc since no two nics in one machine are on same network ever.

bjmurrey · 20 June 2024 17:32

#3 demonstrates #4 is wrong.

it’s a routing issue.
again, any time you touch eth0 in dietpi, whether it’s onboard or usb connected, even after you disable it before rebooting…

pay attention now, I keep repeating this … and NOTHING has changed for you or dietpi… or the answer…

THE DEFAULT ROUTE IS OUT ETH0
to prove this just type route at the prompt.

Feel free to try my separate subnet suggestion below that keeps all eth0 and wlan0 on separate subnets but route all through one default gateway so that BOTH can be on at same time, but not on same network, so you are getting around the thing I keep telling you is the problem that you keep ignoring for some reason…?

THERE IS A DEFAULT ROUTE THROUGH ETH0 if it has EVER AT ANY TIME been enabled, unless you delete that route and add the new one through WLAN0 after removing NIC, rebooting etc.

Hear me please, I really want to help, and this is the issue. If you keep denying it, you’ll go mad trying to find the unicorn that doesn’t exist.

EDIT: TL;DR - NO MATTER WHAT your config looks like, or what you think you have accomplished mucking with settings on your nics, you’re wasting your time. Routing ONLY works ONE WAY FOR ALL INTERNET DEVICES USING IP. Ok? If you have a default route set, no matter what else you have or think you have it’s sending through that one “hole” no matter what. If you dont chhange the hole your throwing everything out to, NOTHING ELSE MATTERS.

STEP1 for you. Delete the default route through eth0. set new route through wlan0. Have a nice day. You’re done.

urostor · 20 June 2024 17:44

I don’t like being patronised, please stop writing to me like I was a child.

bjmurrey · 20 June 2024 17:50

my guy, I’m trying to encourage you to take the easy “route”’ and just type route at the prompt and rest easy that this isn’t a dietpi problem, it’s not a config problem, it’s the way the system works, and this is how you accomplish what you want to do … which you came here and asked for help with, and do not want to even type one word at the prompt lol but will keep rebooting forever and ever typing in the same ip addresses…

take a break. then take my suggesetion. and you’re done.

Offense is taken, not given. Your choice.

Joulinar · 20 June 2024 18:47

@bjmurrey pls can you put the routing issue to one side? If I understood @urostor correctly, the wifi connection is not even established properly. This is far from having anything to do with routing if the interface doesn’t even connect correctly

@urostor pls can you reboot your system having both adapter enabled and share following afterwards

journalctl -u ifup*

bjmurrey · 20 June 2024 20:43

sure no problem. have at it. I dont think you understood correctly tho (he stated it was new install, default drivers, and default config, but didn’t add that he was adding a USB hub w/ NIC til later. So yeah, have fun troubleshooting phantoms his wifi isn’t established because he keeps adding and removing an etehernet adapter on a usb hub to config wifi. no more - no less. 2 solutions. STOP DOING THAT or just fix the route. I “accidentally” make this happen all the time when I’m not paying attention to what I plug in - like this guy is doing - and get exactly the same resutls. But wth do I know.

It’s a nothing machine. Start fresh. It’s default card, default drivers, throw away the usb hub+nic problem (not a problem) solved. He was unloading default drivers on a new install to “fix”’ his problem… that he created… enjoy you labor.
OUT!

not complicated.

urostor · 20 June 2024 20:48

Either way, this is not what should ever happen so let’s try to fix it. You shouldn’t not be able to boot just because you connected and disconnected an ethernet adapter, don’t you think?

To be honest, I would love to apply your solution but it’s buried somewhere in these walls of text, so if you could briefly tell me exactly what to fix in what file and what this would do, it would be actually helpful.

bjmurrey · 20 June 2024 20:51

the solution has been given . and a dozen other options, none of which you have tried or are willing to. SMH

bjmurrey · 20 June 2024 20:52

reload your dietpi install fresh. DO NOT load unload defaul modules … there is NO REASON on a fresh install to do that. It takes 30 mins to reinstall everything.

Dont use the nic+hub. You wont have ANY problems.

urostor · 20 June 2024 20:53

This is not a fix. It will not prevent these problems from happening again.

bjmurrey · 20 June 2024 20:54

the fix is you not using software you dont underrstand and blaming it for your errors.

you caused it. you said it’s not important. there iss nothing wrong with dietpi operation. it’s configs are opaque, but they do exactly what they are supposed to do … it can’t do otherwise.

Denial is not a solution to you b eing the issue.

bjmurrey · 20 June 2024 20:56

in 21 years of professional tech experience from user support to international network backbones, I have never in my life encountered and 1D10T error this bad before.

urostor · 20 June 2024 20:58

This is my last reply to you. If you keep behaving like this, I will ignore anything you write and just talk to the developers.

Connecting and disconnecting an ethernet adapter is not an error, it’s what one can reasonably expect a user to do, especially on a server-like system. So please focus and try to find a way of it not happening in the future. Nobody here is interested in how much “professional tech experience” you have.

urostor · 20 June 2024 22:00

Here is the data dump.

Rebooting the board often causes it to stall at udisks2.service (but maybe it’s the network, which is just after this, just does not get shown). I do a REISUB SysRq restart then, but obviously this is not ideal.

With only wifi enabled:

Jun 20 21:45:00 opiz2w systemd[1]: Starting ifupdown-pre.service - Helper to synchronize boot up for ifupdown...
Jun 20 21:45:03 opiz2w systemd[1]: Finished ifupdown-pre.service - Helper to synchronize boot up for ifupdown.
Jun 20 21:45:04 opiz2w systemd[1]: Starting ifup@wlan0.service - ifup for wlan0...
Jun 20 21:45:04 opiz2w wpa_supplicant[575]: Successfully initialized wpa_supplicant
Jun 20 21:45:04 opiz2w wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB
Jun 20 21:45:04 opiz2w dhclient[619]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 21:45:04 opiz2w ifup[619]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 21:45:04 opiz2w ifup[619]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 21:45:04 opiz2w ifup[619]: All rights reserved.
Jun 20 21:45:04 opiz2w ifup[619]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 21:45:04 opiz2w dhclient[619]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 21:45:04 opiz2w dhclient[619]: All rights reserved.
Jun 20 21:45:04 opiz2w dhclient[619]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 21:45:04 opiz2w dhclient[619]: 
Jun 20 21:45:04 opiz2w systemd[1]: Finished ifupdown-wait-online.service - Wait for network to be configured by ifupdown.
Jun 20 21:45:04 opiz2w dhclient[619]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 21:45:04 opiz2w dhclient[619]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 21:45:04 opiz2w ifup[619]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 21:45:04 opiz2w ifup[619]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 21:45:04 opiz2w ifup[619]: Sending on   Socket/fallback
Jun 20 21:45:04 opiz2w dhclient[619]: Sending on   Socket/fallback
Jun 20 21:45:04 opiz2w ifup[619]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jun 20 21:45:04 opiz2w dhclient[619]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jun 20 21:45:07 opiz2w wpa_supplicant[614]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 21:45:07 opiz2w wpa_supplicant[614]: wlan0: Associated with 18:9e:2c:a9:df:20
Jun 20 21:45:07 opiz2w wpa_supplicant[614]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 21:45:09 opiz2w dhclient[619]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jun 20 21:45:09 opiz2w ifup[619]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jun 20 21:45:17 opiz2w dhclient[619]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jun 20 21:45:17 opiz2w ifup[619]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jun 20 21:45:19 opiz2w wpa_supplicant[614]: wlan0: Authentication with 18:9e:2c:a9:df:20 timed out.
Jun 20 21:45:19 opiz2w wpa_supplicant[614]: wlan0: CTRL-EVENT-DISCONNECTED bssid=18:9e:2c:a9:df:20 reason=3 locally_generated=1
Jun 20 21:45:19 opiz2w wpa_supplicant[614]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jun 20 21:45:19 opiz2w wpa_supplicant[614]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="szypki" auth_failures=1 duration=10 reason=WRONG_KEY
Jun 20 21:45:19 opiz2w wpa_supplicant[614]: BSSID 18:9e:2c:a9:df:20 ignore list count incremented to 2, ignoring for 10 seconds
Jun 20 21:45:19 opiz2w wpa_supplicant[614]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 20 21:45:19 opiz2w wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 20 21:45:19 opiz2w wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB
Jun 20 21:45:29 opiz2w dhclient[619]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jun 20 21:45:29 opiz2w ifup[619]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jun 20 21:45:30 opiz2w wpa_supplicant[614]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="szypki"
Jun 20 21:45:30 opiz2w wpa_supplicant[614]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 21:45:30 opiz2w wpa_supplicant[614]: wlan0: Associated with 18:9e:2c:a9:df:20
Jun 20 21:45:30 opiz2w wpa_supplicant[614]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 21:45:30 opiz2w wpa_supplicant[614]: wlan0: WPA: Key negotiation completed with 18:9e:2c:a9:df:20 [PTK=CCMP GTK=CCMP]
Jun 20 21:45:30 opiz2w wpa_supplicant[614]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:9e:2c:a9:df:20 completed [id=0 id_str=]
Jun 20 21:45:47 opiz2w dhclient[619]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jun 20 21:45:47 opiz2w ifup[619]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jun 20 21:45:47 opiz2w dhclient[619]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 21:45:47 opiz2w dhclient[619]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 21:45:47 opiz2w ifup[619]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 21:45:47 opiz2w ifup[619]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 21:45:47 opiz2w dhclient[619]: DHCPACK of 192.168.3.36 from 192.168.3.1
Jun 20 21:45:47 opiz2w ifup[619]: DHCPACK of 192.168.3.36 from 192.168.3.1
Jun 20 21:45:47 opiz2w dhclient[619]: bound to 192.168.3.36 -- renewal in 36193 seconds.
Jun 20 21:45:47 opiz2w ifup[619]: bound to 192.168.3.36 -- renewal in 36193 seconds.
Jun 20 21:45:47 opiz2w systemd[1]: Finished ifup@wlan0.service - ifup for wlan0.

With 2 adapters enabled but USB ethernet not present (WiFi does not work):

Jun 20 22:15:21 opiz2w systemd[1]: Starting ifupdown-pre.service - Helper to synchronize boot up for ifupdown...
Jun 20 22:15:24 opiz2w systemd[1]: Finished ifupdown-pre.service - Helper to synchronize boot up for ifupdown.
Jun 20 22:15:25 opiz2w systemd[1]: Starting ifup@wlan0.service - ifup for wlan0...
Jun 20 22:15:25 opiz2w wpa_supplicant[576]: Successfully initialized wpa_supplicant
Jun 20 22:15:25 opiz2w wpa_supplicant[617]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB
Jun 20 22:15:25 opiz2w dhclient[622]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:15:25 opiz2w ifup[622]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:15:25 opiz2w ifup[622]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:15:25 opiz2w ifup[622]: All rights reserved.
Jun 20 22:15:25 opiz2w ifup[622]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:15:25 opiz2w dhclient[622]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:15:25 opiz2w dhclient[622]: All rights reserved.
Jun 20 22:15:25 opiz2w dhclient[622]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:15:25 opiz2w dhclient[622]: 
Jun 20 22:15:25 opiz2w dhclient[622]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:15:25 opiz2w ifup[622]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:15:25 opiz2w ifup[622]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:15:25 opiz2w ifup[622]: Sending on   Socket/fallback
Jun 20 22:15:25 opiz2w ifup[622]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Jun 20 22:15:25 opiz2w dhclient[622]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:15:25 opiz2w dhclient[622]: Sending on   Socket/fallback
Jun 20 22:15:25 opiz2w dhclient[622]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Jun 20 22:15:26 opiz2w systemd[1]: Finished ifupdown-wait-online.service - Wait for network to be configured by ifupdown.
Jun 20 22:15:28 opiz2w wpa_supplicant[617]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:15:28 opiz2w wpa_supplicant[617]: wlan0: Associated with 18:9e:2c:a9:df:20
Jun 20 22:15:28 opiz2w wpa_supplicant[617]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 22:15:31 opiz2w dhclient[622]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jun 20 22:15:31 opiz2w ifup[622]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jun 20 22:15:38 opiz2w wpa_supplicant[617]: wlan0: Authentication with 18:9e:2c:a9:df:20 timed out.
Jun 20 22:15:38 opiz2w wpa_supplicant[617]: wlan0: CTRL-EVENT-DISCONNECTED bssid=18:9e:2c:a9:df:20 reason=3 locally_generated=1
Jun 20 22:15:38 opiz2w wpa_supplicant[617]: BSSID 18:9e:2c:a9:df:20 ignore list count incremented to 2, ignoring for 10 seconds
Jun 20 22:15:38 opiz2w wpa_supplicant[617]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 20 22:15:38 opiz2w wpa_supplicant[617]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 20 22:15:38 opiz2w wpa_supplicant[617]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB
Jun 20 22:15:41 opiz2w wpa_supplicant[617]: wlan0: Trying to associate with 18:9e:2c:a9:df:1c (SSID='szypki' freq=2437 MHz)
Jun 20 22:15:41 opiz2w wpa_supplicant[617]: wlan0: Associated with 18:9e:2c:a9:df:1c
Jun 20 22:15:41 opiz2w wpa_supplicant[617]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 22:15:41 opiz2w wpa_supplicant[617]: wlan0: WPA: Key negotiation completed with 18:9e:2c:a9:df:1c [PTK=CCMP GTK=CCMP]
Jun 20 22:15:41 opiz2w wpa_supplicant[617]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:9e:2c:a9:df:1c completed [id=0 id_str=]
Jun 20 22:15:42 opiz2w wpa_supplicant[617]: wlan0: WNM: Preferred List Available
Jun 20 22:15:42 opiz2w dhclient[622]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jun 20 22:15:42 opiz2w ifup[622]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jun 20 22:15:42 opiz2w wpa_supplicant[617]: wlan0: WNM: Preferred List Available
Jun 20 22:15:42 opiz2w dhclient[622]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 22:15:42 opiz2w dhclient[622]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:15:42 opiz2w ifup[622]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 22:15:42 opiz2w ifup[622]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:15:42 opiz2w dhclient[622]: DHCPACK of 192.168.3.36 from 192.168.3.1
Jun 20 22:15:42 opiz2w ifup[622]: DHCPACK of 192.168.3.36 from 192.168.3.1
Jun 20 22:15:42 opiz2w dhclient[622]: bound to 192.168.3.36 -- renewal in 35591 seconds.
Jun 20 22:15:42 opiz2w ifup[622]: bound to 192.168.3.36 -- renewal in 35591 seconds.
Jun 20 22:15:42 opiz2w systemd[1]: Finished ifup@wlan0.service - ifup for wlan0.
Jun 20 22:15:48 opiz2w wpa_supplicant[617]: wlan0: WNM: Preferred List Available
Jun 20 22:15:48 opiz2w wpa_supplicant[617]: wlan0: WNM: Preferred List Available
Jun 20 22:15:53 opiz2w wpa_supplicant[617]: wlan0: WNM: Preferred List Available
Jun 20 22:15:53 opiz2w wpa_supplicant[617]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:15:53 opiz2w wpa_supplicant[617]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=18:9e:2c:a9:df:20 status_code=1
Jun 20 22:15:53 opiz2w wpa_supplicant[617]: BSSID 18:9e:2c:a9:df:20 ignore list count incremented to 3, ignoring for 60 seconds
Jun 20 22:15:58 opiz2w wpa_supplicant[617]: wlan0: Trying to associate with 18:9e:2c:a9:df:1c (SSID='szypki' freq=2437 MHz)
Jun 20 22:15:58 opiz2w wpa_supplicant[617]: wlan0: Association request to the driver failed
Jun 20 22:16:04 opiz2w wpa_supplicant[617]: wlan0: Trying to associate with 18:9e:2c:a9:df:1c (SSID='szypki' freq=2437 MHz)
Jun 20 22:16:04 opiz2w wpa_supplicant[617]: wlan0: Association request to the driver failed
Jun 20 22:16:04 opiz2w wpa_supplicant[617]: BSSID 18:9e:2c:a9:df:1c ignore list count incremented to 2, ignoring for 10 seconds
Jun 20 22:16:10 opiz2w wpa_supplicant[617]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:16:10 opiz2w wpa_supplicant[617]: wlan0: Association request to the driver failed
Jun 20 22:16:13 opiz2w wpa_supplicant[617]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=1
Jun 20 22:16:18 opiz2w wpa_supplicant[617]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:16:18 opiz2w wpa_supplicant[617]: wlan0: Association request to the driver failed
Jun 20 22:16:18 opiz2w wpa_supplicant[617]: BSSID 18:9e:2c:a9:df:20 ignore list count incremented to 2, ignoring for 10 seconds
Jun 20 22:16:31 opiz2w wpa_supplicant[617]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:16:31 opiz2w wpa_supplicant[617]: wlan0: Association request to the driver failed
Jun 20 22:16:31 opiz2w wpa_supplicant[617]: BSSID 18:9e:2c:a9:df:20 ignore list count incremented to 3, ignoring for 60 seconds

With 2 adapters enabled but USB ethernet present, but no cable (WiFi works now, weirdly):

Jun 20 22:08:25 opiz2w systemd[1]: Starting ifupdown-pre.service - Helper to synchronize boot up for ifupdown...
Jun 20 22:08:28 opiz2w systemd[1]: Finished ifupdown-pre.service - Helper to synchronize boot up for ifupdown.
Jun 20 22:08:29 opiz2w systemd[1]: Starting ifup@eth0.service - ifup for eth0...
Jun 20 22:08:29 opiz2w systemd[1]: Starting ifup@wlan0.service - ifup for wlan0...
Jun 20 22:08:29 opiz2w dhclient[599]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:08:29 opiz2w ifup[599]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:08:29 opiz2w ifup[599]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:08:29 opiz2w ifup[599]: All rights reserved.
Jun 20 22:08:29 opiz2w ifup[599]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:08:29 opiz2w dhclient[599]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:08:29 opiz2w dhclient[599]: All rights reserved.
Jun 20 22:08:29 opiz2w dhclient[599]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:08:29 opiz2w dhclient[599]: 
Jun 20 22:08:29 opiz2w dhclient[599]: Listening on LPF/eth0/00:e0:4c:78:04:08
Jun 20 22:08:29 opiz2w ifup[599]: Listening on LPF/eth0/00:e0:4c:78:04:08
Jun 20 22:08:29 opiz2w ifup[599]: Sending on   LPF/eth0/00:e0:4c:78:04:08
Jun 20 22:08:29 opiz2w ifup[599]: Sending on   Socket/fallback
Jun 20 22:08:29 opiz2w ifup[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jun 20 22:08:29 opiz2w dhclient[599]: Sending on   LPF/eth0/00:e0:4c:78:04:08
Jun 20 22:08:29 opiz2w dhclient[599]: Sending on   Socket/fallback
Jun 20 22:08:29 opiz2w dhclient[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jun 20 22:08:29 opiz2w wpa_supplicant[598]: Successfully initialized wpa_supplicant
Jun 20 22:08:29 opiz2w wpa_supplicant[640]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB
Jun 20 22:08:29 opiz2w dhclient[645]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:08:29 opiz2w ifup[645]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:08:29 opiz2w ifup[645]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:08:29 opiz2w ifup[645]: All rights reserved.
Jun 20 22:08:29 opiz2w ifup[645]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:08:29 opiz2w dhclient[645]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:08:29 opiz2w dhclient[645]: All rights reserved.
Jun 20 22:08:29 opiz2w dhclient[645]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:08:29 opiz2w dhclient[645]: 
Jun 20 22:08:29 opiz2w dhclient[645]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:08:29 opiz2w ifup[645]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:08:29 opiz2w ifup[645]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:08:29 opiz2w ifup[645]: Sending on   Socket/fallback
Jun 20 22:08:29 opiz2w ifup[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jun 20 22:08:29 opiz2w dhclient[645]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:08:29 opiz2w dhclient[645]: Sending on   Socket/fallback
Jun 20 22:08:29 opiz2w dhclient[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jun 20 22:08:30 opiz2w systemd[1]: Finished ifupdown-wait-online.service - Wait for network to be configured by ifupdown.
Jun 20 22:08:32 opiz2w wpa_supplicant[640]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:08:32 opiz2w wpa_supplicant[640]: wlan0: Associated with 18:9e:2c:a9:df:20
Jun 20 22:08:32 opiz2w wpa_supplicant[640]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 22:08:34 opiz2w dhclient[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Jun 20 22:08:34 opiz2w ifup[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Jun 20 22:08:34 opiz2w dhclient[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jun 20 22:08:34 opiz2w ifup[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jun 20 22:08:34 opiz2w wpa_supplicant[640]: wlan0: WPA: Key negotiation completed with 18:9e:2c:a9:df:20 [PTK=CCMP GTK=CCMP]
Jun 20 22:08:34 opiz2w wpa_supplicant[640]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:9e:2c:a9:df:20 completed [id=0 id_str=]
Jun 20 22:08:41 opiz2w dhclient[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Jun 20 22:08:41 opiz2w ifup[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Jun 20 22:08:44 opiz2w dhclient[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jun 20 22:08:44 opiz2w ifup[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jun 20 22:08:53 opiz2w dhclient[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
Jun 20 22:08:53 opiz2w ifup[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
Jun 20 22:08:57 opiz2w dhclient[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Jun 20 22:08:57 opiz2w ifup[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Jun 20 22:08:57 opiz2w dhclient[645]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 22:08:57 opiz2w ifup[645]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 22:08:57 opiz2w ifup[645]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:08:57 opiz2w dhclient[645]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:09:01 opiz2w dhclient[645]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:09:01 opiz2w ifup[645]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:09:07 opiz2w dhclient[645]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:09:07 opiz2w ifup[645]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:09:11 opiz2w dhclient[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Jun 20 22:09:11 opiz2w ifup[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Jun 20 22:09:18 opiz2w dhclient[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 20 22:09:18 opiz2w ifup[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 20 22:09:18 opiz2w dhclient[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Jun 20 22:09:18 opiz2w ifup[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Jun 20 22:09:21 opiz2w dhclient[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 20 22:09:21 opiz2w ifup[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 20 22:09:24 opiz2w dhclient[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jun 20 22:09:24 opiz2w ifup[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jun 20 22:09:28 opiz2w dhclient[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
Jun 20 22:09:28 opiz2w ifup[599]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
Jun 20 22:09:30 opiz2w dhclient[599]: No DHCPOFFERS received.
Jun 20 22:09:30 opiz2w dhclient[599]: No working leases in persistent database - sleeping.
Jun 20 22:09:30 opiz2w ifup[599]: No DHCPOFFERS received.
Jun 20 22:09:30 opiz2w ifup[599]: No working leases in persistent database - sleeping.
Jun 20 22:09:30 opiz2w systemd[1]: Finished ifup@eth0.service - ifup for eth0.
Jun 20 22:09:31 opiz2w dhclient[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Jun 20 22:09:31 opiz2w ifup[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Jun 20 22:09:47 opiz2w dhclient[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Jun 20 22:09:47 opiz2w ifup[645]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Jun 20 22:09:47 opiz2w dhclient[645]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 22:09:47 opiz2w ifup[645]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 22:09:47 opiz2w ifup[645]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:09:47 opiz2w dhclient[645]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:09:54 opiz2w dhclient[645]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:09:54 opiz2w ifup[645]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:09:54 opiz2w dhclient[645]: DHCPACK of 192.168.3.36 from 192.168.3.1
Jun 20 22:09:54 opiz2w ifup[645]: DHCPACK of 192.168.3.36 from 192.168.3.1
Jun 20 22:09:54 opiz2w dhclient[645]: bound to 192.168.3.36 -- renewal in 38157 seconds.
Jun 20 22:09:54 opiz2w ifup[645]: bound to 192.168.3.36 -- renewal in 38157 seconds.
Jun 20 22:09:54 opiz2w systemd[1]: Finished ifup@wlan0.service - ifup for wlan0.

With 2 adapters enabled but USB ethernet present, cable connected (WiFi works now but it took 2 tries to boot, stopped at udisks2.service):

Jun 20 22:18:14 opiz2w systemd[1]: Starting ifupdown-pre.service - Helper to synchronize boot up for ifupdown...
Jun 20 22:19:27 opiz2w systemd[1]: Finished ifupdown-pre.service - Helper to synchronize boot up for ifupdown.
Jun 20 22:19:28 opiz2w systemd[1]: Starting ifup@eth0.service - ifup for eth0...
Jun 20 22:19:28 opiz2w systemd[1]: Starting ifup@wlan0.service - ifup for wlan0...
Jun 20 22:19:28 opiz2w systemd[1]: Finished ifupdown-wait-online.service - Wait for network to be configured by ifupdown.
Jun 20 22:19:28 opiz2w dhclient[593]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:19:28 opiz2w ifup[593]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:19:28 opiz2w ifup[593]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:19:28 opiz2w ifup[593]: All rights reserved.
Jun 20 22:19:28 opiz2w ifup[593]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:19:28 opiz2w dhclient[593]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:19:28 opiz2w dhclient[593]: All rights reserved.
Jun 20 22:19:28 opiz2w dhclient[593]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:19:28 opiz2w dhclient[593]: 
Jun 20 22:19:28 opiz2w dhclient[593]: Listening on LPF/eth0/00:e0:4c:78:04:08
Jun 20 22:19:28 opiz2w ifup[593]: Listening on LPF/eth0/00:e0:4c:78:04:08
Jun 20 22:19:28 opiz2w ifup[593]: Sending on   LPF/eth0/00:e0:4c:78:04:08
Jun 20 22:19:28 opiz2w ifup[593]: Sending on   Socket/fallback
Jun 20 22:19:28 opiz2w ifup[593]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jun 20 22:19:28 opiz2w dhclient[593]: Sending on   LPF/eth0/00:e0:4c:78:04:08
Jun 20 22:19:28 opiz2w dhclient[593]: Sending on   Socket/fallback
Jun 20 22:19:28 opiz2w dhclient[593]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jun 20 22:19:28 opiz2w dhclient[593]: DHCPOFFER of 192.168.3.40 from 192.168.3.1
Jun 20 22:19:28 opiz2w ifup[593]: DHCPOFFER of 192.168.3.40 from 192.168.3.1
Jun 20 22:19:28 opiz2w ifup[593]: DHCPREQUEST for 192.168.3.40 on eth0 to 255.255.255.255 port 67
Jun 20 22:19:28 opiz2w dhclient[593]: DHCPREQUEST for 192.168.3.40 on eth0 to 255.255.255.255 port 67
Jun 20 22:19:28 opiz2w dhclient[593]: DHCPACK of 192.168.3.40 from 192.168.3.1
Jun 20 22:19:28 opiz2w ifup[593]: DHCPACK of 192.168.3.40 from 192.168.3.1
Jun 20 22:19:28 opiz2w wpa_supplicant[594]: Successfully initialized wpa_supplicant
Jun 20 22:19:28 opiz2w dhclient[593]: bound to 192.168.3.40 -- renewal in 32675 seconds.
Jun 20 22:19:28 opiz2w ifup[593]: bound to 192.168.3.40 -- renewal in 32675 seconds.
Jun 20 22:19:28 opiz2w systemd[1]: Finished ifup@eth0.service - ifup for eth0.
Jun 20 22:19:29 opiz2w wpa_supplicant[672]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB
Jun 20 22:19:29 opiz2w dhclient[677]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:19:29 opiz2w ifup[677]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:19:29 opiz2w ifup[677]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:19:29 opiz2w ifup[677]: All rights reserved.
Jun 20 22:19:29 opiz2w ifup[677]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:19:29 opiz2w dhclient[677]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:19:29 opiz2w dhclient[677]: All rights reserved.
Jun 20 22:19:29 opiz2w dhclient[677]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:19:29 opiz2w dhclient[677]: 
Jun 20 22:19:29 opiz2w dhclient[677]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:19:29 opiz2w ifup[677]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:19:29 opiz2w ifup[677]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:19:29 opiz2w ifup[677]: Sending on   Socket/fallback
Jun 20 22:19:29 opiz2w ifup[677]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:19:29 opiz2w dhclient[677]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:19:29 opiz2w dhclient[677]: Sending on   Socket/fallback
Jun 20 22:19:29 opiz2w dhclient[677]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:19:32 opiz2w wpa_supplicant[672]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:19:32 opiz2w wpa_supplicant[672]: wlan0: Associated with 18:9e:2c:a9:df:20
Jun 20 22:19:32 opiz2w wpa_supplicant[672]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 22:19:33 opiz2w dhclient[677]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jun 20 22:19:33 opiz2w ifup[677]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jun 20 22:19:41 opiz2w dhclient[677]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Jun 20 22:19:41 opiz2w ifup[677]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Jun 20 22:19:44 opiz2w wpa_supplicant[672]: wlan0: Authentication with 18:9e:2c:a9:df:20 timed out.
Jun 20 22:19:44 opiz2w wpa_supplicant[672]: wlan0: CTRL-EVENT-DISCONNECTED bssid=18:9e:2c:a9:df:20 reason=3 locally_generated=1
Jun 20 22:19:44 opiz2w wpa_supplicant[672]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jun 20 22:19:44 opiz2w wpa_supplicant[672]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="szypki" auth_failures=1 duration=10 reason=WRONG_KEY
Jun 20 22:19:44 opiz2w wpa_supplicant[672]: BSSID 18:9e:2c:a9:df:20 ignore list count incremented to 2, ignoring for 10 seconds
Jun 20 22:19:44 opiz2w wpa_supplicant[672]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 20 22:19:44 opiz2w wpa_supplicant[672]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 20 22:19:44 opiz2w wpa_supplicant[672]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB
Jun 20 22:19:54 opiz2w wpa_supplicant[672]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="szypki"
Jun 20 22:19:54 opiz2w wpa_supplicant[672]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:19:54 opiz2w wpa_supplicant[672]: wlan0: Associated with 18:9e:2c:a9:df:20
Jun 20 22:19:54 opiz2w wpa_supplicant[672]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 22:19:55 opiz2w wpa_supplicant[672]: wlan0: WPA: Key negotiation completed with 18:9e:2c:a9:df:20 [PTK=CCMP GTK=CCMP]
Jun 20 22:19:55 opiz2w wpa_supplicant[672]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:9e:2c:a9:df:20 completed [id=0 id_str=]
Jun 20 22:19:55 opiz2w dhclient[677]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
Jun 20 22:19:55 opiz2w ifup[677]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
Jun 20 22:19:56 opiz2w dhclient[677]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 22:19:56 opiz2w dhclient[677]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:19:56 opiz2w ifup[677]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 22:19:56 opiz2w ifup[677]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:19:56 opiz2w dhclient[677]: DHCPACK of 192.168.3.36 from 192.168.3.1
Jun 20 22:19:56 opiz2w ifup[677]: DHCPACK of 192.168.3.36 from 192.168.3.1
Jun 20 22:19:56 opiz2w dhclient[677]: bound to 192.168.3.36 -- renewal in 37628 seconds.
Jun 20 22:19:56 opiz2w ifup[677]: bound to 192.168.3.36 -- renewal in 37628 seconds.
Jun 20 22:19:56 opiz2w systemd[1]: Finished ifup@wlan0.service - ifup for wlan0.

urostor · 20 June 2024 22:00

Bonus: boot when the settings were reverted to the original ones (only WiFi enabled, no ethernet adapter, but WiFi did not connect):

Jun 20 22:35:38 opiz2w systemd[1]: Starting ifupdown-pre.service - Helper to synchronize boot up for ifupdown...
Jun 20 22:35:41 opiz2w systemd[1]: Finished ifupdown-pre.service - Helper to synchronize boot up for ifupdown.
Jun 20 22:35:42 opiz2w systemd[1]: Starting ifup@wlan0.service - ifup for wlan0...
Jun 20 22:35:42 opiz2w wpa_supplicant[570]: Successfully initialized wpa_supplicant
Jun 20 22:35:42 opiz2w wpa_supplicant[612]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=DE
Jun 20 22:35:42 opiz2w dhclient[617]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:35:42 opiz2w ifup[617]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:35:42 opiz2w ifup[617]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:35:42 opiz2w ifup[617]: All rights reserved.
Jun 20 22:35:42 opiz2w ifup[617]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:35:42 opiz2w dhclient[617]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:35:42 opiz2w dhclient[617]: All rights reserved.
Jun 20 22:35:42 opiz2w dhclient[617]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:35:42 opiz2w dhclient[617]: 
Jun 20 22:35:42 opiz2w dhclient[617]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:35:42 opiz2w ifup[617]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:35:42 opiz2w ifup[617]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:35:42 opiz2w ifup[617]: Sending on   Socket/fallback
Jun 20 22:35:42 opiz2w ifup[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 20 22:35:42 opiz2w dhclient[617]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:35:42 opiz2w dhclient[617]: Sending on   Socket/fallback
Jun 20 22:35:42 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 20 22:35:43 opiz2w systemd[1]: Finished ifupdown-wait-online.service - Wait for network to be configured by ifupdown.
Jun 20 22:35:45 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 20 22:35:45 opiz2w ifup[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 20 22:35:45 opiz2w wpa_supplicant[612]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:35:45 opiz2w wpa_supplicant[612]: wlan0: Associated with 18:9e:2c:a9:df:20
Jun 20 22:35:45 opiz2w wpa_supplicant[612]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 22:35:47 opiz2w wpa_supplicant[612]: wlan0: WPA: Key negotiation completed with 18:9e:2c:a9:df:20 [PTK=CCMP GTK=CCMP]
Jun 20 22:35:47 opiz2w wpa_supplicant[612]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:9e:2c:a9:df:20 completed [id=0 id_str=]
Jun 20 22:35:48 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:35:48 opiz2w ifup[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:35:52 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:35:52 opiz2w ifup[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:35:56 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jun 20 22:35:56 opiz2w ifup[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jun 20 22:36:04 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Jun 20 22:36:04 opiz2w ifup[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Jun 20 22:36:18 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
Jun 20 22:36:18 opiz2w ifup[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
Jun 20 22:36:39 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:36:39 opiz2w ifup[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:36:43 opiz2w dhclient[617]: No DHCPOFFERS received.
Jun 20 22:36:43 opiz2w ifup[617]: No DHCPOFFERS received.
Jun 20 22:36:43 opiz2w ifup[617]: No working leases in persistent database - sleeping.
Jun 20 22:36:43 opiz2w dhclient[617]: No working leases in persistent database - sleeping.
Jun 20 22:36:43 opiz2w systemd[1]: Finished ifup@wlan0.service - ifup for wlan0.
Jun 20 22:41:23 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jun 20 22:41:31 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Jun 20 22:41:31 opiz2w dhclient[617]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 22:41:31 opiz2w dhclient[617]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:41:38 opiz2w dhclient[617]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:41:46 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jun 20 22:41:51 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jun 20 22:41:56 opiz2w dhclient[617]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jun 20 22:42:05 opiz2w wpa_supplicant[612]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 20 22:42:05 opiz2w wpa_supplicant[612]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 20 22:42:05 opiz2w wpa_supplicant[612]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Jun 20 22:42:05 opiz2w wpa_supplicant[612]: p2p-dev-wlan0: CTRL-EVENT-TERMINATING
Jun 20 22:42:05 opiz2w wpa_supplicant[612]: wlan0: CTRL-EVENT-DISCONNECTED bssid=18:9e:2c:a9:df:20 reason=3 locally_generated=1
Jun 20 22:42:05 opiz2w wpa_supplicant[612]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 20 22:42:05 opiz2w wpa_supplicant[612]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 20 22:42:05 opiz2w wpa_supplicant[612]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Jun 20 22:42:05 opiz2w wpa_supplicant[612]: wlan0: CTRL-EVENT-TERMINATING

and this happens when the WiFi is disabled and re-enabled, so that it can finally connect:

Jun 20 22:43:41 opiz2w systemd[1]: Stopping ifup@wlan0.service - ifup for wlan0...
Jun 20 22:43:41 opiz2w dhclient[3492]: Removed stale PID file
Jun 20 22:43:41 opiz2w ifdown[3492]: Removed stale PID file
Jun 20 22:43:41 opiz2w ifdown[3492]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:43:41 opiz2w ifdown[3492]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:43:41 opiz2w ifdown[3492]: All rights reserved.
Jun 20 22:43:41 opiz2w ifdown[3492]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:43:41 opiz2w dhclient[3492]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:43:41 opiz2w dhclient[3492]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:43:41 opiz2w dhclient[3492]: All rights reserved.
Jun 20 22:43:41 opiz2w dhclient[3492]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:43:41 opiz2w dhclient[3492]: 
Jun 20 22:43:41 opiz2w dhclient[3492]: Failed to get interface index: No such device
Jun 20 22:43:41 opiz2w ifdown[3492]: Failed to get interface index: No such device
Jun 20 22:43:41 opiz2w ifdown[3492]: If you think you have received this message due to a bug rather
Jun 20 22:43:41 opiz2w ifdown[3492]: than a configuration issue please read the section on submitting
Jun 20 22:43:41 opiz2w ifdown[3492]: bugs on either our web page at www.isc.org or in the README file
Jun 20 22:43:41 opiz2w ifdown[3492]: before submitting a bug.  These pages explain the proper
Jun 20 22:43:41 opiz2w ifdown[3492]: process and the information we find helpful for debugging.
Jun 20 22:43:41 opiz2w ifdown[3492]: exiting.
Jun 20 22:43:41 opiz2w dhclient[3492]: 
Jun 20 22:43:41 opiz2w dhclient[3492]: If you think you have received this message due to a bug rather
Jun 20 22:43:41 opiz2w dhclient[3492]: than a configuration issue please read the section on submitting
Jun 20 22:43:41 opiz2w dhclient[3492]: bugs on either our web page at www.isc.org or in the README file
Jun 20 22:43:41 opiz2w dhclient[3492]: before submitting a bug.  These pages explain the proper
Jun 20 22:43:41 opiz2w dhclient[3492]: process and the information we find helpful for debugging.
Jun 20 22:43:41 opiz2w dhclient[3492]: 
Jun 20 22:43:41 opiz2w dhclient[3492]: exiting.
Jun 20 22:43:41 opiz2w ifdown[3497]: Cannot find device "wlan0"
Jun 20 22:43:41 opiz2w ifdown[3522]: nl80211 not found.
Jun 20 22:43:41 opiz2w systemd[1]: ifup@wlan0.service: Deactivated successfully.
Jun 20 22:43:41 opiz2w systemd[1]: Stopped ifup@wlan0.service - ifup for wlan0.
Jun 20 22:43:52 opiz2w systemd[1]: Starting ifup@wlan0.service - ifup for wlan0...
Jun 20 22:43:52 opiz2w wpa_supplicant[3816]: Successfully initialized wpa_supplicant
Jun 20 22:43:53 opiz2w wpa_supplicant[3819]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=DE
Jun 20 22:43:53 opiz2w dhclient[3824]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:43:53 opiz2w ifup[3824]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:43:53 opiz2w ifup[3824]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:43:53 opiz2w ifup[3824]: All rights reserved.
Jun 20 22:43:53 opiz2w ifup[3824]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:43:53 opiz2w dhclient[3824]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:43:53 opiz2w dhclient[3824]: All rights reserved.
Jun 20 22:43:53 opiz2w dhclient[3824]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:43:53 opiz2w dhclient[3824]: 
Jun 20 22:43:53 opiz2w dhclient[3824]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:43:53 opiz2w ifup[3824]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:43:53 opiz2w ifup[3824]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:43:53 opiz2w ifup[3824]: Sending on   Socket/fallback
Jun 20 22:43:53 opiz2w ifup[3824]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jun 20 22:43:53 opiz2w dhclient[3824]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:43:53 opiz2w dhclient[3824]: Sending on   Socket/fallback
Jun 20 22:43:53 opiz2w dhclient[3824]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jun 20 22:43:56 opiz2w wpa_supplicant[3819]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:43:56 opiz2w wpa_supplicant[3819]: wlan0: Associated with 18:9e:2c:a9:df:20
Jun 20 22:43:56 opiz2w wpa_supplicant[3819]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 22:44:00 opiz2w dhclient[3824]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jun 20 22:44:00 opiz2w ifup[3824]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jun 20 22:44:00 opiz2w wpa_supplicant[3819]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 20 22:44:00 opiz2w ifup[3804]: Got signal Terminated, terminating...
Jun 20 22:44:00 opiz2w ifup[3804]: ifup: failed to bring up wlan0
Jun 20 22:44:00 opiz2w systemd[1]: ifup@wlan0.service: Main process exited, code=exited, status=1/FAILURE
Jun 20 22:44:00 opiz2w wpa_supplicant[3819]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 20 22:44:00 opiz2w wpa_supplicant[3819]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Jun 20 22:44:00 opiz2w wpa_supplicant[3819]: p2p-dev-wlan0: CTRL-EVENT-TERMINATING
Jun 20 22:44:00 opiz2w wpa_supplicant[3819]: wlan0: CTRL-EVENT-DISCONNECTED bssid=18:9e:2c:a9:df:20 reason=3 locally_generated=1
Jun 20 22:44:00 opiz2w wpa_supplicant[3819]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jun 20 22:44:00 opiz2w wpa_supplicant[3819]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="szypki" auth_failures=1 duration=10 reason=WRONG_KEY
Jun 20 22:44:00 opiz2w wpa_supplicant[3819]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 20 22:44:00 opiz2w wpa_supplicant[3819]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 20 22:44:00 opiz2w wpa_supplicant[3819]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Jun 20 22:44:00 opiz2w wpa_supplicant[3819]: wlan0: CTRL-EVENT-TERMINATING
Jun 20 22:44:00 opiz2w systemd[1]: ifup@wlan0.service: Failed with result 'exit-code'.
Jun 20 22:44:00 opiz2w systemd[1]: Stopped ifup@wlan0.service - ifup for wlan0.
Jun 20 22:44:00 opiz2w systemd[1]: Starting ifup@wlan0.service - ifup for wlan0...
Jun 20 22:44:00 opiz2w wpa_supplicant[3912]: Successfully initialized wpa_supplicant
Jun 20 22:44:00 opiz2w dhclient[3920]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:44:00 opiz2w ifup[3920]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 20 22:44:00 opiz2w ifup[3920]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:44:00 opiz2w ifup[3920]: All rights reserved.
Jun 20 22:44:00 opiz2w ifup[3920]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:44:00 opiz2w dhclient[3920]: Copyright 2004-2022 Internet Systems Consortium.
Jun 20 22:44:00 opiz2w dhclient[3920]: All rights reserved.
Jun 20 22:44:00 opiz2w dhclient[3920]: For info, please visit https://www.isc.org/software/dhcp/
Jun 20 22:44:00 opiz2w dhclient[3920]: 
Jun 20 22:44:00 opiz2w dhclient[3920]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:44:00 opiz2w ifup[3920]: Listening on LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:44:00 opiz2w ifup[3920]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:44:00 opiz2w ifup[3920]: Sending on   Socket/fallback
Jun 20 22:44:00 opiz2w ifup[3920]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:44:00 opiz2w dhclient[3920]: Sending on   LPF/wlan0/40:b9:91:4a:ac:92
Jun 20 22:44:00 opiz2w dhclient[3920]: Sending on   Socket/fallback
Jun 20 22:44:00 opiz2w dhclient[3920]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:44:03 opiz2w wpa_supplicant[3915]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:44:03 opiz2w wpa_supplicant[3915]: wlan0: Associated with 18:9e:2c:a9:df:20
Jun 20 22:44:03 opiz2w wpa_supplicant[3915]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 22:44:03 opiz2w wpa_supplicant[3915]: wlan0: WPA: Key negotiation completed with 18:9e:2c:a9:df:20 [PTK=CCMP GTK=CCMP]
Jun 20 22:44:03 opiz2w wpa_supplicant[3915]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:9e:2c:a9:df:20 completed [id=0 id_str=]
Jun 20 22:44:04 opiz2w dhclient[3920]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:44:04 opiz2w ifup[3920]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 20 22:44:04 opiz2w dhclient[3920]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 22:44:04 opiz2w dhclient[3920]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:44:04 opiz2w ifup[3920]: DHCPOFFER of 192.168.3.36 from 192.168.3.1
Jun 20 22:44:04 opiz2w ifup[3920]: DHCPREQUEST for 192.168.3.36 on wlan0 to 255.255.255.255 port 67
Jun 20 22:44:04 opiz2w dhclient[3920]: DHCPACK of 192.168.3.36 from 192.168.3.1
Jun 20 22:44:04 opiz2w ifup[3920]: DHCPACK of 192.168.3.36 from 192.168.3.1
Jun 20 22:44:04 opiz2w dhclient[3920]: bound to 192.168.3.36 -- renewal in 36642 seconds.
Jun 20 22:44:04 opiz2w ifup[3920]: bound to 192.168.3.36 -- renewal in 36642 seconds.
Jun 20 22:44:04 opiz2w systemd[1]: Finished ifup@wlan0.service - ifup for wlan0.

@bjmurrey is probably on to something because on the next reboot (same settings), the board was connected and had an IP but no data could be sent.

Also, I tried this method on rpi zero 2w and it did not get WiFi to connect. However when I made a fresh image, without connecting ethernet, it could connect.

But this is not ideal - nobody would ever think that using WiFi will be impossible once an ethernet adapter is detected…

Joulinar · 21 June 2024 06:46

This is not correct, at least not in general. On a RPi3B+ I can enable both and they will get connected without issue.

Well, wlan0 is connecting to your WiFi.

urostor:

Jun 20 22:35:45 opiz2w wpa_supplicant[612]: wlan0: Trying to associate with 18:9e:2c:a9:df:20 (SSID='szypki' freq=5540 MHz)
Jun 20 22:35:45 opiz2w wpa_supplicant[612]: wlan0: Associated with 18:9e:2c:a9:df:20
Jun 20 22:35:45 opiz2w wpa_supplicant[612]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 22:35:47 opiz2w wpa_supplicant[612]: wlan0: WPA: Key negotiation completed with 18:9e:2c:a9:df:20 [PTK=CCMP GTK=CCMP]
Jun 20 22:35:47 opiz2w wpa_supplicant[612]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:9e:2c:a9:df:20 completed [id=0 id_str=]

but due to whatever reason it has issues to receive an IP address via DHCP.

urostor:

Jun 20 22:36:43 opiz2w dhclient[617]: No DHCPOFFERS received.
Jun 20 22:36:43 opiz2w ifup[617]: No DHCPOFFERS received.
Jun 20 22:36:43 opiz2w ifup[617]: No working leases in persistent database - sleeping.

For testing, you could assign a STATIC IP address. This way we could exclude DHCP.

MichaIng · 24 June 2024 20:33

Hmm, for sure, it does not have anything to do with the Ethernet interface enabled (but adapter detached). As said and seen: having the Ethernet interface “enabled” (allow-hotplug eth0) has zero effect if the adapter is not attached. The config is simply ignored. Similarly, an attached Ethernet adapter has no effect if the Ethernet interface is not also enabled (or only an indirect one: voltage, udev detection loop, or something else caused by hardware or driver issues).

This error can happen when the used WiFi channel is not supported by the network adapter or country code. It can appear and disappear randomly, if your router changes the WiFi channel based on other WiFi networks around. But I also find this in combination with WMM (WiFi Multimedia prioritisation) or with WiFi roaming enabled. In case of Orange Pi Zero 2W, it can be however because by some other driver or bootloader quirk. Likely here since reboots make a difference.

I just triggered a new build of kernel and bootloader, in case there have been some enhancements.

In addition to testing with a static IP, could you also check whether this is returning the correct country code, as well as the frequency range and channel you are using?

iw reg get

I remember a case where faulty firmware limited the frequency ranges, so that the channel used by the router/AP could only be partly used by the adapter. Switching to another channel was a workaround.

urostor · 24 June 2024 21:17

Thank you very much! Let us know when the build completes.

I’m the meantime I resolved the issue with Raspberry Pi Zero 2 W WiFi. It worked on a fresh install but was unstable. I manually installed the latest firmware deb (placeholder name here, from June 2023) and got rid of the undervoltage I set. It also appears to be a bit power supply related (I get an sdio failure). So this can be only about Orange Pi Zero 2 W now.

WiFi issues on the zeroes

desktop Ubuntu /mac / iphone whatever wlan0 192.168.1.68 /192 eth0 192.168.1.134 / 192

desktop Ubuntu /mac / iphone whatever
wlan0 192.168.1.68 /192
eth0 192.168.1.134 / 192