I dugged up a 4k, updated it, copied over a .kodi dir, cleaned a bit. Everything is fine except I’m loosing the connection to the Wifi every (2nd) time after reboot. I’d need to go to MyOSMC/Network to connect. Works but it is annoying. Any idea what went wrong? Here’s the log. Thanks
These are the parts in the log
Sep 10 10:05:24 aemilia wpa_supplicant[432]: wlan0: Trying to associate with 48:dd:0c:64:98:a5 (SSID='@thob' freq=2412 MHz) Sep 10 10:05:24 aemilia connmand[337]: ipconfig state 2 ipconfig method 1 Sep 10 10:05:24 aemilia kernel: Connectting with 48:dd:0c:64:98:a5 channel (1) ssid "@thob", len (5) Sep 10 10:05:24 aemilia wpa_supplicant[432]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=48:dd:0c:64:98:a5 status_code=30 Sep 10 10:05:24 aemilia kernel: connect failed event=0 e->status 1 e->reason 0
Sep 10 10:07:27 aemilia wpa_supplicant[432]: wlan0: Trying to associate with 48:dd:0c:64:98:a6 (SSID='@thob' freq=5180 MHz) Sep 10 10:07:27 aemilia kernel: Connectting with 48:dd:0c:64:98:a6 channel (36) ssid "@thob", len (5) Sep 10 10:07:28 aemilia wpa_supplicant[432]: wlan0: Associated with 48:dd:0c:64:98:a6 Sep 10 10:07:28 aemilia kernel: wl_iw_event: Link UP with BSSID=48:DD:0C:64:98:A6 Sep 10 10:07:28 aemilia kernel: wl_bss_connect_done succeeded with 48:dd:0c:64:98:a6 Sep 10 10:07:28 aemilia wpa_supplicant[432]: wlan0: WPA: Key negotiation completed with 48:dd:0c:64:98:a6 [PTK=CCMP GTK=CCMP] Sep 10 10:07:28 aemilia wpa_supplicant[432]: wlan0: CTRL-EVENT-CONNECTED - Connection to 48:dd:0c:64:98:a6 completed [id=0 id_str=]
So looks like for whatever reason the connection to the 2.4Ghz network is rejected. Generally the advice is to have different SSID for 2.4 and 5Ghz which might solve your problem.
Thanks, I can see it. I got another 4k+ which has no problem at all with the 2. Is there a way to tell the OSMC to just connect to the one or the other network?
I’m using an eero mesh network, there’s no way to have different SSIDs, I think.
Not to my knowledge without separate SSID.
Yeah seems to be a strange system, just quickly googled and found this thread
As it only happens after reboot how bad is the issue? Normally other than an upgrade with Kernel change there should be no need for a reboot.
right, it was just during set up. It shouldn’t bother the user (it’s not me) too much. Thanks for the pointer too.