OpenWrt on raspberry pi disconnects from the router and drops all clients connected to it over WIFI

i have Raspberry Pi connected over ethernet cable to my router(WAN) and i have external antena Netgear a6210 coneccted to Pi to broadcast wireless (LAN). everything works normally for period of time (sometimes minutes, sometimes hours). then my Raspberry Pi drops all clients that are connected to it and its imposibble to reconnect to it untill restart is done.

anybody had any similar issues ??

Sun Oct  9 22:31:44 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-DISCONNECTED bssid=2c:b2:1a:e9:4e:32 reason=3
Sun Oct  9 22:31:44 2022 daemon.notice netifd: Network device 'wlan1' link is down
Sun Oct  9 22:31:45 2022 daemon.notice wpa_supplicant[847]: wlan1: Trying to associate with 2c:b2:1a:e9:4e:32 (SSID='F2202' freq=2422 MHz)
Sun Oct  9 22:31:46 2022 daemon.notice netifd: Network device 'wlan1' link is up
Sun Oct  9 22:31:46 2022 daemon.notice wpa_supplicant[847]: wlan1: Associated with 2c:b2:1a:e9:4e:32
Sun Oct  9 22:31:46 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-CONNECTED - Connection to 2c:b2:1a:e9:4e:32 completed [id=0 id_str=]
Sun Oct  9 22:31:46 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Oct  9 22:35:45 2022 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on wlan1 which has no address
Sun Oct  9 22:36:45 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-DISCONNECTED bssid=2c:b2:1a:e9:4e:32 reason=3
Sun Oct  9 22:36:45 2022 daemon.notice netifd: Network device 'wlan1' link is down
Sun Oct  9 22:36:46 2022 daemon.notice wpa_supplicant[847]: wlan1: Trying to associate with 2c:b2:1a:e9:4e:32 (SSID='F2202' freq=2422 MHz)
Sun Oct  9 22:36:47 2022 daemon.notice netifd: Network device 'wlan1' link is up
Sun Oct  9 22:36:47 2022 daemon.notice wpa_supplicant[847]: wlan1: Associated with 2c:b2:1a:e9:4e:32
Sun Oct  9 22:36:47 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-CONNECTED - Connection to 2c:b2:1a:e9:4e:32 completed [id=0 id_str=]
Sun Oct  9 22:36:47 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Oct  9 22:41:47 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-DISCONNECTED bssid=2c:b2:1a:e9:4e:32 reason=3
Sun Oct  9 22:41:47 2022 daemon.notice netifd: Network device 'wlan1' link is down
Sun Oct  9 22:41:48 2022 daemon.notice wpa_supplicant[847]: wlan1: Trying to associate with 2c:b2:1a:e9:4e:32 (SSID='F2202' freq=2422 MHz)
Sun Oct  9 22:41:49 2022 daemon.notice netifd: Network device 'wlan1' link is up
Sun Oct  9 22:41:49 2022 daemon.notice wpa_supplicant[847]: wlan1: Associated with 2c:b2:1a:e9:4e:32
Sun Oct  9 22:41:49 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-CONNECTED - Connection to 2c:b2:1a:e9:4e:32 completed [id=0 id_str=]
Sun Oct  9 22:41:49 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Oct  9 22:46:48 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-DISCONNECTED bssid=2c:b2:1a:e9:4e:32 reason=3
Sun Oct  9 22:46:48 2022 daemon.notice netifd: Network device 'wlan1' link is down
Sun Oct  9 22:46:49 2022 daemon.notice wpa_supplicant[847]: wlan1: Trying to associate with 2c:b2:1a:e9:4e:32 (SSID='F2202' freq=2422 MHz)
Sun Oct  9 22:46:50 2022 daemon.notice netifd: Network device 'wlan1' link is up
Sun Oct  9 22:46:50 2022 daemon.notice wpa_supplicant[847]: wlan1: Associated with 2c:b2:1a:e9:4e:32
Sun Oct  9 22:46:50 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-CONNECTED - Connection to 2c:b2:1a:e9:4e:32 completed [id=0 id_str=]
Sun Oct  9 22:46:50 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Oct  9 22:47:02 2022 daemon.info hostapd: wlan0: STA 64:a2:f9:a6:f1:bb IEEE 802.11: authenticated
Sun Oct  9 22:47:02 2022 daemon.notice hostapd: wlan0: STA-OPMODE-N_SS-CHANGED 64:a2:f9:a6:f1:bb 2
Sun Oct  9 22:47:02 2022 daemon.info hostapd: wlan0: STA 64:a2:f9:a6:f1:bb IEEE 802.11: associated (aid 3)
Sun Oct  9 22:47:02 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 64:a2:f9:a6:f1:bb
Sun Oct  9 22:47:02 2022 daemon.info hostapd: wlan0: STA 64:a2:f9:a6:f1:bb WPA: pairwise key handshake completed (RSN)
Sun Oct  9 22:47:02 2022 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED 64:a2:f9:a6:f1:bb
Sun Oct  9 22:47:02 2022 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.183 64:a2:f9:a6:f1:bb
Sun Oct  9 22:47:02 2022 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.183 64:a2:f9:a6:f1:bb OnePlus-6
Sun Oct  9 22:51:51 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-DISCONNECTED bssid=2c:b2:1a:e9:4e:32 reason=3
Sun Oct  9 22:51:51 2022 daemon.notice netifd: Network device 'wlan1' link is down
Sun Oct  9 22:51:52 2022 daemon.notice wpa_supplicant[847]: wlan1: Trying to associate with 2c:b2:1a:e9:4e:32 (SSID='F2202' freq=2422 MHz)
Sun Oct  9 22:51:53 2022 daemon.notice netifd: Network device 'wlan1' link is up
Sun Oct  9 22:51:53 2022 daemon.notice wpa_supplicant[847]: wlan1: Associated with 2c:b2:1a:e9:4e:32
Sun Oct  9 22:51:53 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-CONNECTED - Connection to 2c:b2:1a:e9:4e:32 completed [id=0 id_str=]
Sun Oct  9 22:51:53 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Oct  9 22:56:53 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-DISCONNECTED bssid=2c:b2:1a:e9:4e:32 reason=3
Sun Oct  9 22:56:53 2022 daemon.notice netifd: Network device 'wlan1' link is down
Sun Oct  9 22:56:54 2022 daemon.notice wpa_supplicant[847]: wlan1: Trying to associate with 2c:b2:1a:e9:4e:32 (SSID='F2202' freq=2422 MHz)
Sun Oct  9 22:56:54 2022 daemon.notice netifd: Network device 'wlan1' link is up
Sun Oct  9 22:56:54 2022 daemon.notice wpa_supplicant[847]: wlan1: Associated with 2c:b2:1a:e9:4e:32
Sun Oct  9 22:56:54 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-CONNECTED - Connection to 2c:b2:1a:e9:4e:32 completed [id=0 id_str=]
Sun Oct  9 22:56:54 2022 daemon.notice wpa_supplicant[847]: wlan1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Oct  9 22:59:32 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 64:a2:f9:a6:f1:bb
Sun Oct  9 23:00:05 2022 daemon.info hostapd: wlan0: STA 64:a2:f9:a6:f1:bb IEEE 802.11: authenticated
Sun Oct  9 23:00:05 2022 daemon.notice hostapd: wlan0: STA-OPMODE-N_SS-CHANGED 64:a2:f9:a6:f1:bb 2
Sun Oct  9 23:00:05 2022 daemon.info hostapd: wlan0: STA 64:a2:f9:a6:f1:bb IEEE 802.11: associated (aid 3)
Sun Oct  9 23:00:05 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 64:a2:f9:a6:f1:bb
Sun Oct  9 23:00:05 2022 daemon.info hostapd: wlan0: STA 64:a2:f9:a6:f1:bb WPA: pairwise key handshake completed (RSN)
Sun Oct  9 23:00:05 2022 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED 64:a2:f9:a6:f1:bb
Sun Oct  9 23:00:05 2022 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.183 64:a2:f9:a6:f1:bb
Sun Oct  9 23:00:05 2022 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.183 64:a2:f9:a6:f1:bb OnePlus-6

Just taking a guess here -- it could be a power issue. In some cases, the USB ports on a Pi cannot provide enough power (this could be the USB-A ports themselves and/or the main supply that doesn't have enough power).

A way to test this theory is to use a powered USB-3 hub that has a high quality power supply.

That said, even with the best of these types of USB wifi adapters, you're almost always better off with a proper AP as compared to these devices. The range and performance (especially with multiple clients) on these devices is generally worse than even a pretty old AP or wifi router used as a dumb AP.

1 Like

Hm, never occurred to me it could be power problem. Netgear dongle has its own stand with cable going into it, I'll try and lose that, so i can just plug it in directly.

As for coverage, it's perfectly fine because i need to cover small part of the apartment.

I currently live in China, that's why i need to have something running openwrt, and Pi is easier to get to rather than some router supporting Openwrt.

Removing a passive cable is unlikely to solve anything (unless the cable is really cheap and poorly made). What you need to do is plug it into a USB hub that provides power -- this hub would sit between the Pi and the adapter and it would provide power to the adapter so that the Pi doesn't have to.

Ah ok. I'll try that. Thanks

I have quite a few Raspberry Pis and pretty much every problem I have ever had has been power supply problems especially with Pi3s. Pretty much all power supplies I can find with a Pi3 USB-Micro-B connector are only 5.0V/2.5A which just doesn't seem enough. What I am doing now for Pi3s is using Pi4 power supplies that supply 5.1V/3.0A and use USB-C to USB-Micro-B converter. Have not had any problems since then.

1 Like

Im running Pi 4B with original cable... Im still waiting for the USB hub to arrive so i can test is it power related problem. Thanks for your info.

So just to be clear here. Usb hub should have its own power supply cable that plugs in electrical outlet, NOT into raspberry itself. And he should have 1 male usb 3.0 or USB-C that connects to raspberry pi which will be data transfer.

And i will plug my wireless dongle into one of the female ports on the hub?

You need a usb 3 hub (data, not just charging) with a usb A connection and its own power supply.