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.
+1 vote
769 views 2 comments
by

Hello,

I have my RUT950 a long time, and it worked brilliantly (Fixed WAN + Wifi fallback + mobile fallback).

But for some reason, after some updates, it refuses to connect (or at least get a DHCP IP address) from the wifi config.

I already tried to completely factory reset it, reconfigure it, etc... Only the fixed and the mobile connection do get a DHCP address, the Wifi (STA) does NOT get any address anymore. It worked perfectly before....

=> Can I try something ? 
=> How should I get any feedback of what the DHCP call does ?
=> the logs do not provide much info...

I already tried several different AP's and wifi networks, with different subnets and ranges... nothing works... Even tried mobile AP on my phone...
When I do a scan, I can see all AP's. When I connect, and use the WPA key, it seems to connect and seems to validate... But then no IP....

I also tried multi AP's, deleted them, with and without the AP-mode  etc... Nothing helps !

Really need some help with this .... please

3 Answers

0 votes
by anonymous

Hi,

May i know if you are using the latest firmware for RUT9XX Series? 
Kindly check the latest firmware here: https://wiki.teltonika.lt/view/RUT950_Firmware_Downloads 

When upgrading it is best to uncheck the keep all settings in the firmware upgrade window. 

Hope it helps. 

Thank you and have a nice day!

Regards,
Jerome

by
I am having the same problem - specifically with RUT950. I do not have this problem with a RUT240 in the office. Running as STN, connecting to local AP, looking at the SSH console, logread, it attempts 3 times to authenticate and then fails. I've double checked security settings, as well as upgraded firmware to 6.07.3 - there is no solution to the problem.

Mon Dec 21 17:08:32 2020 user.info Messaged[8511]: Start from new event "WiFi" "WiFi client connected: 44:D9:E7:FD:7C:87  "
Mon Dec 21 17:10:02 2020 daemon.notice wpa_supplicant[3392]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="insights"
Mon Dec 21 17:10:04 2020 daemon.notice wpa_supplicant[3392]: wlan0: SME: Trying to authenticate with 44:d9:e7:fd:7c:87 (SSID='insights' freq=2412 MHz)
Mon Dec 21 17:10:04 2020 kern.info kernel: [  368.240000] wlan0: authenticate with 44:d9:e7:fd:7c:87
Mon Dec 21 17:10:04 2020 kern.info kernel: [  368.260000] wlan0: send auth to 44:d9:e7:fd:7c:87 (try 1/3)
Mon Dec 21 17:10:04 2020 kern.info kernel: [  368.380000] wlan0: send auth to 44:d9:e7:fd:7c:87 (try 2/3)
Mon Dec 21 17:10:04 2020 kern.info kernel: [  368.490000] wlan0: send auth to 44:d9:e7:fd:7c:87 (try 3/3)
Mon Dec 21 17:10:05 2020 kern.info kernel: [  368.610000] wlan0: authentication with 44:d9:e7:fd:7c:87 timed out
Mon Dec 21 17:10:05 2020 daemon.notice wpa_supplicant[3392]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="insights" auth_failures=7 duration=90 reason=CONN_FAILED
0 votes
by anonymous
Hello,

Could you please post what yours logread says? Is it trying to connect but fails?  If so what kind of error it is giving?

And please double check if your antennas a screwed on correctly.

Best regards,
VidasKac.
by
I have the same problem. Can connect to the wifi network with my handy but with the router it connects but does not get an ip address. I tested this with 2 different networks where i see the ssid in the scan and enter the correct password but never get an ip. But when i offer an ap with my handy by tethering it works fine!?

Have the latest fw.

Any ideas?
0 votes
by anonymous

I am having the same problem - specifically with RUT950. I do not have this problem with a RUT240 in the office. Running as STN, connecting to local AP, looking at the SSH console, logread, it attempts 3 times to authenticate and then fails. I've double checked security settings, as well as upgraded firmware to 6.07.3 - there is no solution to the problem.

Mon Dec 21 17:08:32 2020 user.info Messaged[8511]: Start from new event "WiFi" "WiFi client connected: 44:D9:E7:FD:7C:87  "
Mon Dec 21 17:10:02 2020 daemon.notice wpa_supplicant[3392]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="insights"
Mon Dec 21 17:10:04 2020 daemon.notice wpa_supplicant[3392]: wlan0: SME: Trying to authenticate with 44:d9:e7:fd:7c:87 (SSID='insights' freq=2412 MHz)
Mon Dec 21 17:10:04 2020 kern.info kernel: [  368.240000] wlan0: authenticate with 44:d9:e7:fd:7c:87
Mon Dec 21 17:10:04 2020 kern.info kernel: [  368.260000] wlan0: send auth to 44:d9:e7:fd:7c:87 (try 1/3)
Mon Dec 21 17:10:04 2020 kern.info kernel: [  368.380000] wlan0: send auth to 44:d9:e7:fd:7c:87 (try 2/3)
Mon Dec 21 17:10:04 2020 kern.info kernel: [  368.490000] wlan0: send auth to 44:d9:e7:fd:7c:87 (try 3/3)
Mon Dec 21 17:10:05 2020 kern.info kernel: [  368.610000] wlan0: authentication with 44:d9:e7:fd:7c:87 timed out
Mon Dec 21 17:10:05 2020 daemon.notice wpa_supplicant[3392]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="insights" auth_failures=7 duration=90 reason=CONN_FAILED