WIKIABOUT

FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14215 questions

16871 answers

27752 comments

54381 members

Most popular tags

rut955 rut240 rut950 rutx11 rms vpn to wifi openvpn not sms trb140 firmware connection - ipsec on rutx12 rutx09 modbus

When RUTX looses wireless connection to AP(Wireless WAN), all wireless APs of the same radio die.

+1 vote
258 views 3 comments
by
I am having problem with RUTX10 and RUTX11. For each wireless device (2G and 5G) I have 2 APs and one for internet access from other router client configured. This works perfectly until RUTX have connection to the AP. When RUTX loses connection as client (gets out of the range of router with internet access - wireless WAN) other APs die. Radio device serving band that loses connection keeps restarting what prevents connecting to router which is not allowed in our application of the router. I am running latest (RUTX_R_00.07.02.5) Firmware on all routers. Channel that wirelesses device is using doesn't change anything. Changing/disabling Fallback setting doesn't change anything. This behaviour is observed in all of our RUTX routers. When connection to AP is re-established problem diapers. Is there a way to configure a router in that way that losing connection as client won't affect other APs of the same radio device? I am attaching troubleshoot files.
by
Same with my RUT950 running RUT9_R_00.07.02.3 but also had this problem with earlier versions and even v6.
I had several topics here on this forum and sent several support dumps in to investigate but never got resolved.

Edit: Now I'm pure relying on SIM with 4G, but that was intended only for fail-over. Now it's a bit expensive.

1 Answer

0 votes
by
Hello,

Could you provide wireless interface settings of the router, which provides internet access?

An image of your network topology would be useful.

Does this happen only on 5GHz interface, or 2.4GHz as well?

What is the environment, distance between access points?

Could you expand on what do you mean by “other APs die“?

Is the router providing the internet running on the latest firmware?
by

Hello,

Could you provide wireless interface settings of the router, which provides internet access?

Our application of the router won't always let as to access setting of AP that provides internet access. Aside from that I don't believe that configuration of router that is used could be able to restart radio device on RUTX routers.

An image of your network topology would be useful.

I hope that is that this is what you meant by network topology, it looks more-like this:

In this topology internet access must be given to ROBOT'S PC and CLIENTS with full access.

Does this happen only on 5GHz interface, or 2.4GHz as well?

It happens on both interfaces starting with one first to loose connection to router with internet, so with 5G.

What is the environment, distance between access points?

Distance will vary very often our application which is a mobile robot that will work inside all kind of indoor environments. But same fact of loosing access to router with internet is not a problem, handling that event on the RUTX side is.

Could you expand on what do you mean by “other APs die“?

It think that logs will explain it well. In following logs you will see me connecting to the router as guest via 5G band (CLIENT with limited access) with my smartphone (behaviour is the same for all kind of devices), steering robot with "virtuall joystick" which is running on the ROBOT'S PC, out of the range of the router with internet access and then network device to that handles this connection is being restarted because it lost signal of the router with internet access (in this situation we can not let this connection between client device and robot to be stopped).

[email protected]:~# logread -f
Tue Aug 23 13:42:41 2022 daemon.info hostapd: wlan1-2: STA b6:51:73:24:f6:37 IEEE 802.11: authenticated
Tue Aug 23 13:42:41 2022 daemon.info hostapd: wlan1-2: STA b6:51:73:24:f6:37 IEEE 802.11: associated (aid 1)
Tue Aug 23 13:42:41 2022 daemon.notice hostapd: wlan1-2: AP-STA-CONNECTED b6:51:73:24:f6:37
Tue Aug 23 13:42:41 2022 kern.notice WiFi client connected: B6:51:73:24:F6:37
Tue Aug 23 13:42:41 2022 daemon.info hostapd: wlan1-2: STA b6:51:73:24:f6:37 RADIUS: starting accounting session FA53CB66DC28CAE5
Tue Aug 23 13:42:41 2022 daemon.info hostapd: wlan1-2: STA b6:51:73:24:f6:37 WPA: pairwise key handshake completed (RSN)
Tue Aug 23 13:42:45 2022 daemon.info dnsmasq-dhcp[9688]: DHCPDISCOVER(wlan1-2) b6:51:73:24:f6:37
Tue Aug 23 13:42:45 2022 daemon.info dnsmasq-dhcp[9688]: DHCPOFFER(wlan1-2) 192.168.11.207 b6:51:73:24:f6:37
Tue Aug 23 13:42:45 2022 daemon.info dnsmasq-dhcp[9688]: DHCPDISCOVER(wlan1-2) b6:51:73:24:f6:37
Tue Aug 23 13:42:45 2022 daemon.info dnsmasq-dhcp[9688]: DHCPOFFER(wlan1-2) 192.168.11.207 b6:51:73:24:f6:37
Tue Aug 23 13:42:45 2022 daemon.info dnsmasq-dhcp[9688]: DHCPDISCOVER(wlan1-2) b6:51:73:24:f6:37
Tue Aug 23 13:42:45 2022 daemon.info dnsmasq-dhcp[9688]: DHCPOFFER(wlan1-2) 192.168.11.207 b6:51:73:24:f6:37
Tue Aug 23 13:42:45 2022 daemon.info dnsmasq-dhcp[9688]: DHCPREQUEST(wlan1-2) 192.168.11.207 b6:51:73:24:f6:37
Tue Aug 23 13:42:45 2022 daemon.info dnsmasq-dhcp[9688]: DHCPACK(wlan1-2) 192.168.11.207 b6:51:73:24:f6:37 Jakub-s-Galaxy-S21-FE-5G
Tue Aug 23 13:42:45 2022 kern.info Leased 192.168.11.207 IP address for client b6:51:73:24:f6:37 - Jakub-s-Galaxy-S21-FE-5G in WiFi
Tue Aug 23 13:45:15 2022 daemon.notice wpa_supplicant[1769]: wlan1: CTRL-EVENT-BEACON-LOSS
Tue Aug 23 13:45:15 2022 daemon.notice netifd: Network device 'wlan1' link is down IN HERE IT "DIES" AND FROM THIS POINT, UNTIL CONNECTION WITH ROUTER IS REESTABLISHED ALL APs ASSOCIATED THIS NETWORK DEVICE DON'T WORK (RADIO DEVICE KEEPS RESTARTING UNTIL IT CONNECTS BACK TO THE ROUTER WITH INTERNET ACCESS)  
Tue Aug 23 13:45:15 2022 daemon.notice netifd: Interface 'WWAN_5G' has link connectivity loss
Tue Aug 23 13:45:15 2022 daemon.notice netifd: WWAN_5G (6127): udhcpc: received SIGTERM
Tue Aug 23 13:45:15 2022 daemon.notice netifd: Interface 'WWAN_5G' is now down
Tue Aug 23 13:45:15 2022 daemon.notice netifd: Interface 'WWAN_5G' is disabled
Tue Aug 23 13:45:15 2022 daemon.notice netifd: Interface 'WWAN_5G' is enabled
Tue Aug 23 13:45:15 2022 daemon.info dnsmasq[9688]: reading /tmp/resolv.conf.d/resolv.conf.auto
Tue Aug 23 13:45:15 2022 daemon.info dnsmasq[9688]: using only locally-known addresses for domain test
Tue Aug 23 13:45:15 2022 daemon.info dnsmasq[9688]: using only locally-known addresses for domain onion
Tue Aug 23 13:45:15 2022 daemon.info dnsmasq[9688]: using only locally-known addresses for domain localhost
Tue Aug 23 13:45:15 2022 daemon.info dnsmasq[9688]: using only locally-known addresses for domain local
Tue Aug 23 13:45:15 2022 daemon.info dnsmasq[9688]: using only locally-known addresses for domain invalid
Tue Aug 23 13:45:15 2022 daemon.info dnsmasq[9688]: using only locally-known addresses for domain bind
Tue Aug 23 13:45:15 2022 daemon.info dnsmasq[9688]: using only locally-known addresses for domain lan
Tue Aug 23 13:45:15 2022 daemon.info dnsmasq[9688]: using nameserver 192.168.1.1#53
Tue Aug 23 13:45:15 2022 kern.warn kernel: [  386.401473] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 4
Tue Aug 23 13:45:15 2022 kern.warn kernel: [  386.401541] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 4
Tue Aug 23 13:45:15 2022 daemon.notice wpa_supplicant[1769]: wlan1: CTRL-EVENT-DISCONNECTED bssid=c0:06:c3:08:1c:1a reason=4 locally_generated=1
Tue Aug 23 13:45:15 2022 user.warn mwan3-hotplug[10882]: hotplug called on WWAN_5G before mwan3 has been set up
Tue Aug 23 13:45:16 2022 daemon.notice netifd: Network device 'wlan1-1' link is down 
Tue Aug 23 13:45:16 2022 daemon.notice netifd: Network device 'wlan1-2' link is down
Tue Aug 23 13:45:16 2022 daemon.notice netifd: Interface 'GUEST_LAN_5G' has link connectivity loss
Tue Aug 23 13:45:16 2022 kern.info kernel: [  387.251133] br-lan: port 2(wlan1-1) entered disabled state
Tue Aug 23 13:45:17 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Aug 23 13:45:17 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Aug 23 13:45:17 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Aug 23 13:45:31 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Aug 23 13:45:31 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Aug 23 13:45:31 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Aug 23 13:45:31 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Aug 23 13:45:35 2022 daemon.info hostapd: wlan0-1: STA a8:6d:aa:9f:84:e5 IEEE 802.11: authenticated
Tue Aug 23 13:45:35 2022 daemon.info hostapd: wlan0-1: STA a8:6d:aa:9f:84:e5 IEEE 802.11: associated (aid 1)
Tue Aug 23 13:45:35 2022 daemon.notice hostapd: wlan1-1: Prune association for a8:6d:aa:9f:84:e5
Tue Aug 23 13:45:35 2022 daemon.notice hostapd: wlan1-1: AP-STA-DISCONNECTED a8:6d:aa:9f:84:e5
by
When the same frequency wireless interface is used as both, an access point and a client station, it is normal for the clients connected to the access point to be disconnected, when the router goes out of range and looses connectivity to the router/access point it is connected to as a client. That is how the device operates.

The solution could be to use one frequency wireless interface of RUTX11 as a client station, and the other frequency interface as an access point.