FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
632 views 11 comments
by anonymous

RUT950 with firmware RUT9_R_00.07.02.1 

Product code RUT9500022C0 batch no. 126 

Serial 1119661678 

Configured as AP and client. Drops WiFi on AP completely several times per day. When that starts happening it keeps happening constantly. During the periods that it does work the logs shows constant dhcp renewals. There are about eight different clients connected of which five are permanent, the rest are mobile devices. Log shows “WiFi client disconnected” and than “WiFi client connected” over and over for all devices page after page.

by anonymous

Very similar or same problem with my RUT955.

See my own description.

by anonymous
I had another dhcp server running in the network. Stupid, my mistake.

Edit on 18/07/2022

Well, I really thought I solved it but the problem is still the same. There are between 5 and 8 WiFi clients connected to this router and they all loose connection at the same time. On an iPhone or iPad the WiFi symbol disappears completely.
by anonymous

Any more hints to a solution would be very welcome. If this device keeps this way I have to replace it, this is hopeless.

From a shell I looked at the logging with" root@Teltonika-RUT950:~# logread -f -e hostapd

Wed Aug  3 14:52:08 2022 daemon.info hostapd: wlan0-1: STA 00:80:a3:ca:7b:93 IEEE 802.11: authenticated
Wed Aug  3 14:52:08 2022 daemon.info hostapd: wlan0-1: STA 00:80:a3:ca:7b:93 IEEE 802.11: associated (aid 3)
Wed Aug  3 14:52:08 2022 daemon.notice hostapd: wlan0-1: AP-STA-CONNECTED 00:80:a3:ca:7b:93
Wed Aug  3 14:52:08 2022 daemon.info hostapd: wlan0-1: STA 00:80:a3:ca:7b:93 RADIUS: starting accounting session 2F3429ED86FC80EE
Wed Aug  3 14:52:08 2022 daemon.info hostapd: wlan0-1: STA 00:80:a3:ca:7b:93 WPA: pairwise key handshake completed (RSN)
Wed Aug  3 14:57:25 2022 daemon.notice hostapd: wlan0-1: AP-STA-POLL-OK 00:80:a3:ca:7b:93
Wed Aug  3 15:01:13 2022 daemon.info hostapd: wlan0-1: STA 00:80:a3:ca:7b:93 WPA: group key handshake completed (RSN)
Wed Aug  3 15:01:13 2022 daemon.info hostapd: wlan0-1: STA cc:50:e3:63:6d:8d WPA: group key handshake completed (RSN)
Wed Aug  3 15:01:13 2022 daemon.info hostapd: wlan0-1: STA 84:0d:8e:a9:fb:96 WPA: group key handshake completed (RSN)
Wed Aug  3 15:06:25 2022 daemon.notice hostapd: wlan0-1: AP-STA-POLL-OK 00:80:a3:ca:7b:93
Wed Aug  3 15:11:13 2022 daemon.info hostapd: wlan0-1: STA 00:80:a3:ca:7b:93 WPA: group key handshake completed (RSN)
Wed Aug  3 15:11:13 2022 daemon.info hostapd: wlan0-1: STA cc:50:e3:63:6d:8d WPA: group key handshake completed (RSN)
Wed Aug  3 15:11:13 2022 daemon.info hostapd: wlan0-1: STA 84:0d:8e:a9:fb:96 WPA: group key handshake completed (RSN)
Wed Aug  3 15:16:23 2022 daemon.notice hostapd: wlan0-1: AP-STA-POLL-OK 00:80:a3:ca:7b:93
Wed Aug  3 15:21:13 2022 daemon.info hostapd: wlan0-1: STA 00:80:a3:ca:7b:93 WPA: group key handshake completed (RSN)
Wed Aug  3 15:21:13 2022 daemon.info hostapd: wlan0-1: STA 84:0d:8e:a9:fb:96 WPA: group key handshake completed (RSN)
Wed Aug  3 15:21:13 2022 daemon.info hostapd: wlan0-1: STA cc:50:e3:63:6d:8d WPA: group key handshake completed (RSN)
Wed Aug  3 15:26:15 2022 daemon.notice hostapd: wlan0-1: AP-STA-POLL-OK 00:80:a3:ca:7b:93
Wed Aug  3 15:31:13 2022 daemon.info hostapd: wlan0-1: STA 00:80:a3:ca:7b:93 WPA: group key handshake completed (RSN)
Wed Aug  3 15:31:13 2022 daemon.info hostapd: wlan0-1: STA cc:50:e3:63:6d:8d WPA: group key handshake completed (RSN)
Wed Aug  3 15:31:13 2022 daemon.info hostapd: wlan0-1: STA 84:0d:8e:a9:fb:96 WPA: group key handshake completed (RSN)
Wed Aug  3 15:36:23 2022 daemon.notice hostapd: wlan0-1: AP-STA-POLL-OK 00:80:a3:ca:7b:93
Wed Aug  3 15:41:13 2022 daemon.info hostapd: wlan0-1: STA 00:80:a3:ca:7b:93 WPA: group key handshake completed (RSN)
Wed Aug  3 15:41:13 2022 daemon.info hostapd: wlan0-1: STA cc:50:e3:63:6d:8d WPA: group key handshake completed (RSN)
Wed Aug  3 15:41:13 2022 daemon.info hostapd: wlan0-1: STA 84:0d:8e:a9:fb:96 WPA: group key handshake completed (RSN)
Wed Aug  3 15:46:22 2022 daemon.notice hostapd: wlan0-1: AP-STA-POLL-OK 00:80:a3:ca:7b:93

And this goes on and on day and night. On a client like an iPad or laptop you can see the WiFi icon just disappear.

Or like this:
root@Teltonika-RUT950:~# logread -f -e dnsmasq-dhcp
Thu Aug  4 08:41:47 2022 daemon.info dnsmasq-dhcp[31473]: DHCPDISCOVER(br-lan) cc:50:e3:63:6d:8d
Thu Aug  4 08:41:47 2022 daemon.info dnsmasq-dhcp[31473]: DHCPOFFER(br-lan) 10.10.10.140 cc:50:e3:63:6d:8d
Thu Aug  4 08:41:47 2022 daemon.info dnsmasq-dhcp[31473]: DHCPREQUEST(br-lan) 10.10.10.140 cc:50:e3:63:6d:8d
Thu Aug  4 08:41:47 2022 daemon.info dnsmasq-dhcp[31473]: DHCPACK(br-lan) 10.10.10.140 cc:50:e3:63:6d:8d SensESP-Volts
Thu Aug  4 08:41:48 2022 daemon.info dnsmasq-dhcp[31473]: DHCPDISCOVER(br-lan) 84:0d:8e:a9:fb:96
Thu Aug  4 08:41:48 2022 daemon.info dnsmasq-dhcp[31473]: DHCPOFFER(br-lan) 10.10.10.83 84:0d:8e:a9:fb:96
Thu Aug  4 08:41:48 2022 daemon.info dnsmasq-dhcp[31473]: DHCPREQUEST(br-lan) 10.10.10.83 84:0d:8e:a9:fb:96
Thu Aug  4 08:41:48 2022 daemon.info dnsmasq-dhcp[31473]: DHCPACK(br-lan) 10.10.10.83 84:0d:8e:a9:fb:96 SensESP-Temps
Thu Aug  4 08:42:24 2022 daemon.info dnsmasq-dhcp[31473]: DHCPDISCOVER(br-lan) 00:80:a3:ca:7b:93
Thu Aug  4 08:42:24 2022 daemon.info dnsmasq-dhcp[31473]: DHCPOFFER(br-lan) 10.10.10.72 00:80:a3:ca:7b:93
Thu Aug  4 08:42:24 2022 daemon.info dnsmasq-dhcp[31473]: DHCPREQUEST(br-lan) 10.10.10.72 00:80:a3:ca:7b:93
Thu Aug  4 08:42:24 2022 daemon.info dnsmasq-dhcp[31473]: DHCPACK(br-lan) 10.10.10.72 00:80:a3:ca:7b:93 ShipModul
Thu Aug  4 08:52:14 2022 daemon.info dnsmasq-dhcp[31473]: DHCPDISCOVER(br-lan) cc:50:e3:63:6d:8d
Thu Aug  4 08:52:14 2022 daemon.info dnsmasq-dhcp[31473]: DHCPOFFER(br-lan) 10.10.10.140 cc:50:e3:63:6d:8d
Thu Aug  4 08:52:14 2022 daemon.info dnsmasq-dhcp[31473]: DHCPREQUEST(br-lan) 10.10.10.140 cc:50:e3:63:6d:8d
Thu Aug  4 08:52:14 2022 daemon.info dnsmasq-dhcp[31473]: DHCPACK(br-lan) 10.10.10.140 cc:50:e3:63:6d:8d SensESP-Volts
Thu Aug  4 08:52:14 2022 daemon.info dnsmasq-dhcp[31473]: DHCPDISCOVER(br-lan) 84:0d:8e:a9:fb:96
Thu Aug  4 08:52:14 2022 daemon.info dnsmasq-dhcp[31473]: DHCPOFFER(br-lan) 10.10.10.83 84:0d:8e:a9:fb:96
Thu Aug  4 08:52:15 2022 daemon.info dnsmasq-dhcp[31473]: DHCPREQUEST(br-lan) 10.10.10.83 84:0d:8e:a9:fb:96
Thu Aug  4 08:52:15 2022 daemon.info dnsmasq-dhcp[31473]: DHCPACK(br-lan) 10.10.10.83 84:0d:8e:a9:fb:96 SensESP-Temps

by anonymous
Last weekend I reset the router to factory settings and started over. Actually started over three times because the router kept going back to the login page; surely caused by dropping its WiFi. This must indicate the device is broken because I didn't do anything yet...

At some point I got it more or less stable and managed to configure AP and client again so at least I had WiFi on board (some of the time at least). But as you can see in my previous post it is still unstable.

What hasn't been discussed before is that I use two different WiFi antennas. One factory and the other one is a weatherproof high up the mast of the boat. Can using two different types cause these problems? I think it is unlikely because this outside antenna is of high quality and when attached to a different router works perfectly.

1 Answer

0 votes
by anonymous
Hello,

Can you please check if the device's wi-fi antennas are firmly attached and are not loose?

Can you verify that the network of the source Wi-Fi and RUT950 should not be the same?

Also, can you please share the troubleshoot file using the private message?

Regards,

Shivang
by anonymous
Hi Shivang,

Thanks for looking into this. I've send you the requested troubleshoot file in a PM.

Ed
by anonymous

For completeness of this topic:

Yes, the antenna's are both firmly attached and the WiFi client and AP are using completely different subnets.

What I think is happening: The WiFi the router is connecting to is an unstable (marina) AP. I see lots of messages in syslog:

Wed Jul 20 12:21:28 2022 daemon.notice wpa_supplicant[2084]: wlan0: CTRL-EVENT-BEACON-LOSS
Wed Jul 20 12:21:30 2022 daemon.notice wpa_supplicant[2084]: wlan0: CTRL-EVENT-BEACON-LOSS

So I'm not expecting a great connection but I do expect the local AP to stay up and running. And it can clearly be seen on devices (iPhone, iPad, Windows-laptop) that de WiFi is completely gone. The problem now is that all devices on board that use WiFi lose the connection regularly. So I think the WiFi between the router and marina disconnects- and reconnects immediately, but then restarts its AP as well. And that should not happen.

by anonymous

Hello,
CTRL-EVENT-BEACON-LOSS indicates that there is some inactivity between the devices and thus connection is terminated. Could you check if your access point has some settings for beacon intervals and try to increase it?
Would it be possible to get more details, regarding wireless settings of the access point you connect your router to: band, transmit power, channel, etc?
Also, could you describe the environment the devices are in, how far apart RUT is from the access point?
I would also like you to connect to the router via CLI/SSH and post the output of the commands "iw wlan0 info" and "iwinfo wlan0 scan".
Best regards,
by anonymous

Beacon interval is a setting below "Allow legacy 802.11b rates" which I have disabled a few days ago, but problem remains.
Requested more details "band, transmit power, channel, etc":
Seen from 'Status->Wireless':

SSID        Jachthaven Liesveld
Status      Running
Band        2.4GHz
Signal      65%
Bitrate     130.0 Mbit/s
Mode        Client
Encryption  WPA2 PSK (CCM)

"Describe the environment":
Outside placed professional WiFi antenna in mast of boat with direct line of sight to marina AP, within about 100 meters.

by anonymous

"iw wlan0 info":
Interface wlan0
    ifindex 14
    wdev 0x2
    addr 00:1e:42:42:ea:fb
    ssid Jachthaven Liesveld
    type managed
    wiphy 0
    channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
    txpower 17.00 dBm
    multicast TXQ:
        qsz-byt    qsz-pkt    flows    drops    marks    overlmt    hashcol    tx-bytes    tx-packets
        0    0    0    0    0    0    0    0        0

"iwinfo wlan0 scan":
Cell 01 - Address: 00:C0:CA:AA:83:77
          ESSID: "WiFiCampPro2-AA8377"
          Mode: Master  Channel: 5
          Signal: -44 dBm  Quality: 66/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 02 - Address: FA:92:BF:0C:43:DE
          ESSID: "Heeren aan de Haven - Gasten"
          Mode: Master  Channel: 11
          Signal: -49 dBm  Quality: 61/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 03 - Address: F4:92:BF:0C:43:DE
          ESSID: "Heeren aan de Haven"
          Mode: Master  Channel: 11
          Signal: -55 dBm  Quality: 55/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 04 - Address: FE:92:BF:0C:43:DE
          ESSID: "Van Dalen"
          Mode: Master  Channel: 11
          Signal: -49 dBm  Quality: 61/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 05 - Address: E4:A7:C5:18:3F:EE
          ESSID: "VirginM"
          Mode: Master  Channel: 1
          Signal: -66 dBm  Quality: 44/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 06 - Address: 00:30:44:1E:2A:A5
          ESSID: "L3325"
          Mode: Master  Channel: 12
          Signal: -66 dBm  Quality: 44/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 07 - Address: A0:EC:80:47:16:DB
          ESSID: "H368N4716DB"
          Mode: Master  Channel: 3
          Signal: -65 dBm  Quality: 45/70
          Encryption: mixed WPA/WPA2 PSK (TKIP, CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 08 - Address: 38:F8:89:05:E4:3A
          ESSID: "ARNOLDA-WIFI"
          Mode: Master  Channel: 5
          Signal: -57 dBm  Quality: 53/70
          Encryption: mixed WPA/WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 09 - Address: AC:64:62:6E:1E:5C
          ESSID: "H369A6E1E5C"
          Mode: Master  Channel: 11
          Signal: -69 dBm  Quality: 41/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 10 - Address: FA:8F:CA:30:10:87
          ESSID: unknown
          Mode: Master  Channel: 11
          Signal: -66 dBm  Quality: 44/70
          Encryption: none
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 11 - Address: 16:92:BF:0C:47:BB
          ESSID: unknown
          Mode: Master  Channel: 11
          Signal: -62 dBm  Quality: 48/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown


 

by anonymous

Cell 12 - Address: 06:92:BF:0C:47:BB
          ESSID: "Van Dalen"
          Mode: Master  Channel: 11
          Signal: -69 dBm  Quality: 41/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 13 - Address: 7E:8A:20:B1:8C:C3
          ESSID: unknown
          Mode: Master  Channel: 1
          Signal: -63 dBm  Quality: 47/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 14 - Address: C0:06:C3:76:F3:AD
          ESSID: "Viator"
          Mode: Master  Channel: 11
          Signal: -80 dBm  Quality: 30/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 15 - Address: C2:06:C3:66:F3:AD
          ESSID: unknown
          Mode: Master  Channel: 11
          Signal: -78 dBm  Quality: 32/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 16 - Address: F4:92:BF:0C:47:BB
          ESSID: "Heeren aan de Haven"
          Mode: Master  Channel: 11
          Signal: -64 dBm  Quality: 46/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 17 - Address: 3C:37:86:AA:E2:EE
          ESSID: "NTGR_E2EC"
          Mode: Master  Channel: 1
          Signal: -68 dBm  Quality: 42/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 18 - Address: 68:89:75:0A:8E:1A
          ESSID: "Xperia XZ_7e9c_ext"
          Mode: Master  Channel: 1
          Signal: -74 dBm  Quality: 36/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 19 - Address: F6:92:BF:0C:47:BB
          ESSID: "Heeren aan de Haven - Gasten"
          Mode: Master  Channel: 11
          Signal: -62 dBm  Quality: 48/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 20 - Address: 3A:9D:92:2E:2B:BF
          ESSID: "DIRECT-922EABBF"
          Mode: Master  Channel: 2
          Signal: -62 dBm  Quality: 48/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 21 - Address: 78:8A:20:B1:8C:C3
          ESSID: "Jachthaven Liesveld"
          Mode: Master  Channel: 1
          Signal: -67 dBm  Quality: 43/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

Cell 22 - Address: 02:92:BF:0C:43:DE
          ESSID: unknown
          Mode: Master  Channel: 11
          Signal: -48 dBm  Quality: 62/70
          Encryption: WPA2 PSK (CCMP)
          HT Operation:
                    Primary Channel: 0
                    Secondary Channel Offset: no secondary
                    Channel Width: unknown

by anonymous
But let's not forget the REAL problem:

The RUT950 completely drops it's AP several times per hour. Always, and always has. Day and night, every day.
Whatever the (bad) connection is via the WiFi client to the outside world, the router should NEVER drop it's local AP.