Hello Martynas,
this is the follow up to this topic:
WIFI connects but does not get IP address
The problem happened again. WIFI is connected but does not get an IP address.
Here is the log file you requested. After rebooting the RUTX11 WIFI1 was connected again:
I cannot post the content of the system log file because I get this message when I try:
Dietmar
It looks like you’re connecting to a Marina Hotspot with many users - saying this as they’re using a /23 subnet mask for their DHCP pool.
Could it be that the problem is on their side and and that moment you simply get no IP as there’s no free IP address for you and their DHCP pool is maxed out?
You can check what the default lease time is for their DHCP leases and eventually talk to them to reduce the lease time to let’s say 1 hour (or less) - which should be perfectly fine for a public hotspot.
Sure that is possible but now is winter time and hardly anybode is there. Talking to “them” is very difficult since there is nobody around who could check this situation.
But when I reboot the RUTX11 is gets an IP address immediately.
Could it be that the DHCP client is giving up trying to get an IP address after some time?
Because this state will persist until I reboot the router.
Dietmar
Hello Dietmar,
Could you let us know which RutOS firmware version is installed on your RUTX11? If it’s outdated, please update it to the latest version, RUTX_R_00.07.11.3.
Additionally, could you please provide the logs from System → Maintenance → Events Log when the router connects to the Marina Hotspot AP but fails to obtain an IP address?
As @TeWe mentioned, it’s also possible that the issue is on the Marina Hotspot side, such as a long DHCP server IP lease time.
Kind regards and happy upcoming holidays!
The firmware is 7.10. I am a bit hesitant to start a firmware update from remote. The site is 600km away.
The Internet connection went down on 12/19 at around 16:00. Here is the events log around this time frame.
| 3457 | 2024-12-20 02:37:57 | Mobile Data | Info | Mobile data disconnected (internal modem) |
|---|---|---|---|---|
| 3456 | 2024-12-20 02:37:55 | Failover | Info | WAN (mob1s2a1) is down, no more backups to switch |
| 3455 | 2024-12-20 02:37:16 | Failover | Info | WAN (mob1s2a1) is down, no more backups to switch |
| 3454 | 2024-12-20 02:37:04 | Failover | Info | WAN (mob1s2a1) is down, no more backups to switch |
| 3453 | 2024-12-20 02:37:03 | Network Operator | Info | Connected to HT HR HT HR operator (internal modem) |
| 3452 | 2024-12-20 02:37:03 | Network Type | Info | Joined LTE network (internal modem) |
| 3451 | 2024-12-20 02:37:03 | Mobile Data | Info | Mobile data connected (internal modem) |
| 3450 | 2024-12-20 02:37:00 | Failover | Info | Switched to backup WAN (mob1s2a1) |
| 3449 | 2024-12-20 02:36:53 | Failover | Info | Switched to backup WAN (mob1s2a1) |
| 3448 | 2024-12-20 02:36:42 | Mobile Data | Info | Mobile data disconnected (internal modem) |
| 3447 | 2024-12-20 02:36:41 | Failover | Info | WAN (mob1s2a1) is down, no more backups to switch |
| 3446 | 2024-12-20 02:36:03 | Failover | Info | WAN (mob1s2a1) is down, no more backups to switch |
| 3445 | 2024-12-20 02:35:50 | Failover | Info | WAN (mob1s2a1) is down, no more backups to switch |
| 3444 | 2024-12-20 02:35:48 | Network Operator | Info | Connected to HT HR HT HR operator (internal modem) |
| 3443 | 2024-12-18 11:51:53 | Fota | Notice | Firmware update to RUTX_R_00.07.11.3 is now available |
| 3442 | 2024-12-18 11:25:16 | SMS | Notice | SMS received from: HR_Telekom (internal modem) |
| 3441 | 2024-12-17 16:22:27 | SMS | Notice | SMS received from: HR_Telekom (internal modem) |
| 3440 | 2024-12-17 14:32:44 | Fota | Notice | Firmware update to RUTX_R_00.07.11.3 is now available |
| 3439 | 2024-12-17 14:32:42 | Web UI | Notice | Password auth succeeded for admin on HTTP from 198.18.1.220 |
| 3438 | 2024-12-17 13:46:15 | SMS | Info | Sent 3 PDUs to +436 |
| 3437 | 2024-12-17 13:46:12 | SMS | Notice | SMS received from: HR_Telekom (internal modem) |
| 3436 | 2024-12-17 13:26:17 | SMS | Info | Sent 1 PDUs to +436 |
| 3435 | 2024-12-17 13:26:15 | SMS | Notice | SMS received from: HR_Telekom (internal modem) |
| 3434 | 2024-12-17 13:16:42 | SMS | Info | Sent 1 PDUs to +436 |
| 3433 | 2024-12-17 13:16:41 | SMS | Notice | SMS received from: HR_Telekom (internal modem) |
| 3432 | 2024-12-17 10:41:54 | Startup | Notice | Device startup completed |
| 3431 | 2024-12-17 10:41:54 | Startup | Info | Device startup after unexpected shutdown |
| 3430 | 2024-12-17 10:41:32 | WiFi | Notice | OCY60: WiFi client connected: 10:97:BD:E4:52:4C |
| 3429 | 2024-12-17 10:41:32 | WiFi | Notice | OCY60: WiFi client connected: 44:17:93:E3:B7:48 |
| 3428 | 2024-12-17 10:41:32 | WiFi | Notice | OCY60: WiFi client connected: 44:17:93:E3:5F:0C |
| 3427 | 2024-12-17 10:41:32 | WiFi | Notice | OCY60: WiFi client connected: 10:97:BD:E4:38:64 |
| 3426 | 2024-12-17 10:41:05 | CONFIG | Notice | User “admin” changed events_reporting configuration |
| 3425 | 2024-12-17 10:22:21 | Web UI | Notice | Password auth succeeded for admin on HTTP from 198.18.1.220 |
| 3424 | 2024-12-17 08:11:14 | SMS | Info | Sent 1 PDUs to +43676852503222 |
| 3423 | 2024-12-17 08:10:13 | Startup | Notice | Device startup completed |
| 3422 | 2024-12-17 08:09:53 | WiFi | Notice | OCY60: WiFi client connected: 44:17:93:E3:B7:48 |
| 3421 | 2024-12-17 08:09:53 | WiFi | Notice | OCY60: WiFi client connected: 44:17:93:E3:5F:0C |
| 3420 | 2024-12-17 08:09:52 | WiFi | Notice | OCY60: WiFi client connected: 10:97:BD:E4:52:4C |
| 3419 | 2024-12-17 08:09:52 | WiFi | Notice | OCY60: WiFi client connected: 10:97:BD:E4:38:64 |
| 3418 | 2024-12-17 08:09:26 | WiFi | Notice | OCY60: WiFi client disconnected: 44:17:93:E3:B7:48 |
| 3417 | 2024-12-17 08:09:26 | WiFi | Notice | OCY60: WiFi client disconnected: 10:97:BD:E4:52:4C |
| 3416 | 2024-12-17 08:09:26 | WiFi | Notice | OCY60: WiFi client disconnected: 44:17:93:E3:5F:0C |
| 3415 | 2024-12-17 08:09:26 | WiFi | Notice | OCY60: WiFi client disconnected: 10:97:BD:E4:38:64 |
| 3414 | 2024-12-17 08:09:07 | SIM status | Info | SIM state changed to not inserted (internal modem) |
| 3413 | 2024-12-17 08:08:47 | CONFIG | Notice | sms_utils configuration has been changed |
| 3412 | 2024-12-17 08:08:47 | SMS | Notice | SMS received from: +4367 (internal modem) |
| 3411 | 2024-12-17 08:08:47 | Reboot | Info | Request from SMS |
| 3410 | 2024-12-15 18:02:27 | Fota | Notice | Firmware update to RUTX_R_00.07.11.2 is now available |
| 3409 | 2024-12-15 18:02:16 | Startup | Notice | Device startup completed |
Dietmar
Hi…
They use some kind of portal to provide WiFi to his guests?
Do you remember… When using a PC… How long is the lease time to renew the ip address?
No portal.
I never connected a PC without the router.
But the router is connecting fine for month and then it gets into this state. After a reboot it is connecting nicely for several month before it happens again.
Dietmar
okay…
Maybe it is not a good solution… but… help a litlle, until find a better solution.
okay?
I looked at this before but there is no condition “WIFI connected but no IP address obtained”.
Simply going for a ping would reboot the router when the boat leaves the harbor.
Why so complicated?
Let him scheduled reboot every day at 04:00 in the morning (so by time instead of lost signal) and you should be fine.
Even if - for whatever reason - he doesn’t get an IP today, he will most likely get one tomorrow morning at 04:00 worst case.
And if this is still not good enough or too long to wait, you can always reboot manually via SMS command.
RUTX11 Auto Reboot - Teltonika Networks Wiki
[go all the way down to ‘Reboot Scheduler’]
