Repeater Will Not Connect - Stuck with "Getting..." Notification

buntspext · 2024-10-02T09:39:32.209Z

Today, for the first time i ran into a connection problem (SSID: RRX Hotspot) with op24 (4.6.4). It looked like using non-op24 version. The router did not get an ip.

Screenshot 2024-10-02 at 11.29.222698×1646 266 KB

Log attached.
logread_02_oct_2024.tar (122.5 KB)

alzhao · 2024-10-02T09:50:12.891Z

Thanks for the log.

Not sure if it is relate to DFS. I am asking developers to have a check.

Wed Oct  2 11:27:42 2024 daemon.notice wpa_supplicant[2781]: sta1: SME: Trying to authenticate with 70:b3:17:87:20:af (SSID='WIFI@DB' freq=5700 MHz)
Wed Oct  2 11:27:42 2024 kern.info kernel: [ 1551.963141] sta1: authenticate with 70:b3:17:87:20:af (local address=0a:e9:f6:a3:e9:d8)
Wed Oct  2 11:27:42 2024 kern.info kernel: [ 1551.971160] sta1: send auth to 70:b3:17:87:20:af (try 1/3)
Wed Oct  2 11:27:42 2024 daemon.notice wpa_supplicant[2781]: sta1: Trying to associate with 70:b3:17:87:20:af (SSID='WIFI@DB' freq=5700 MHz)
Wed Oct  2 11:27:42 2024 kern.info kernel: [ 1551.983910] sta1: authenticated
Wed Oct  2 11:27:42 2024 kern.info kernel: [ 1551.991547] sta1: associate with 70:b3:17:87:20:af (try 1/3)
Wed Oct  2 11:27:42 2024 kern.info kernel: [ 1552.015582] sta1: RX AssocResp from 70:b3:17:87:20:af (capab=0x1101 status=0 aid=45)
Wed Oct  2 11:27:42 2024 daemon.notice netifd: Network device 'sta1' link is up
Wed Oct  2 11:27:42 2024 daemon.notice netifd: Interface 'wwan' has link connectivity
Wed Oct  2 11:27:42 2024 daemon.notice netifd: Interface 'wwan' is setting up now
Wed Oct  2 11:27:42 2024 daemon.notice wpa_supplicant[2781]: sta1: Associated with 70:b3:17:87:20:af
Wed Oct  2 11:27:42 2024 kern.info kernel: [ 1552.032111] sta1: associated
Wed Oct  2 11:27:42 2024 daemon.notice wpa_supplicant[2781]: sta1: CTRL-EVENT-CONNECTED - Connection to 70:b3:17:87:20:af completed [id=5 id_str=]
Wed Oct  2 11:27:42 2024 daemon.notice netifd: Interface 'wwan' is disabled
Wed Oct  2 11:27:42 2024 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Wed Oct  2 11:27:42 2024 daemon.info gl-repeater[2125]: (repeater.lua:380) connected to WIFI@DB
Wed Oct  2 11:27:42 2024 kern.info kernel: [ 1552.080189] br-lan: port 3(wlan1) entered blocking state
Wed Oct  2 11:27:42 2024 kern.info kernel: [ 1552.085625] br-lan: port 3(wlan1) entered disabled state
Wed Oct  2 11:27:42 2024 kern.info kernel: [ 1552.091006] mt798x-wmac 18000000.wifi wlan1: entered allmulticast mode
Wed Oct  2 11:27:42 2024 kern.info kernel: [ 1552.097864] mt798x-wmac 18000000.wifi wlan1: entered promiscuous mode
Wed Oct  2 11:27:42 2024 kern.debug kernel: [ 1552.105134] sta1: Limiting TX power to 25 dBm as advertised by 70:b3:17:87:20:af
Wed Oct  2 11:27:42 2024 daemon.notice netifd: Interface 'wwan' is now down
Wed Oct  2 11:27:42 2024 daemon.notice hostapd: wlan1: interface state DISABLED->COUNTRY_UPDATE
Wed Oct  2 11:27:42 2024 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->DFS
Wed Oct  2 11:27:42 2024 daemon.notice hostapd: wlan1: DFS-CAC-START freq=5700 chan=140 sec_chan=1, width=1, seg0=138, seg1=0, cac_time=60s
Wed Oct  2 11:27:42 2024 daemon.notice wpa_supplicant[2781]: sta1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Wed Oct  2 11:27:42 2024 user.notice firewall: Reloading firewall due to ifdown of wwan ()
Wed Oct  2 11:27:43 2024 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wwan" ] } }
Wed Oct  2 11:27:44 2024 daemon.info gl-repeater[2125]: (repeater-nl80211.lua:504) bypass cac for phy1
Wed Oct  2 11:27:44 2024 kern.info kernel: [ 1554.051875] bypass cac for wlan1
Wed Oct  2 11:27:44 2024 daemon.notice hostapd: wlan1: DFS-CAC-COMPLETED success=1 freq=5700 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5690 cf2=0
Wed Oct  2 11:27:45 2024 daemon.notice netifd: Network device 'wlan1' link is up

buntspext · 2024-10-02T11:09:42.389Z

Just happened again. I had to switch trains (was disconnected from RRX Hotspot network). Then i boarded a new train. No ip. When i reconnected the network with a new MAC then i immediatly got an IP.

Log attached
logread.tar (185 KB)

buntspext · 2024-10-02T11:54:14.349Z

I found another problem and not sure if its related in any way. After a long time i used the android app (2.6.0) again. In the network list there is nothing displayed under saved networks. See difference between web and app Version.

App:

Screenshot_20241002_134429_glinet1080×2340 132 KB

Web:

Screenshot 2024-10-02 at 13.44.361304×1390 93.8 KB

alzhao · 2024-10-04T04:13:29.089Z

From the log it seems that the connection is failed, not the same as before (connected but didn't get IP).

When it use a new mac address to connect, it connected without problem.

alzhao · 2024-10-04T04:14:01.255Z

I tested my iOS app and it is sill fine. I will let other guys to have a check.

Samongl · 2024-10-05T06:42:47.652Z

I've been struggling with the same "getting" but never connecting issue at several hotels in Spain.

This firmware appears to have worked, though the other stable firmware releases (4.6.2, nor the latest which is 4.6.4) worked.

alzhao · 2024-10-07T04:53:10.546Z

In the smartphone app, extend the left menu

image408×889 49.7 KB

Enable the app log and you will see the log icon.

image597×861 51.6 KB

Then go to repeater section, when you have the "empty" saved network list, click the "log" icon and extend the log. pls post the log here.

tonyx · 2024-10-21T10:11:25.900Z

This worked like a charm! meanwhile version 4.6.8 did not work and I have no idea why. Does it break auto-update though?

buntspext · 2024-10-21T10:47:21.567Z

alzhao:

Then go to repeater section, when you have the "empty" saved network list, click the "log" icon and extend the log. pls post the log here.

Sorry. For the late reply. Just tried with version 4.6.6-op24 and problem still exists. This is the log:

4.zip (9.7 KB)

alzhao · 2024-10-23T09:13:06.128Z

Thanks for the log. From the log actually the API response with the saved ap list.

I am asking developers to check why it is not displayed.

alzhao · 2024-10-23T09:42:44.604Z

Confirmed that the app has bugs and will update.

acong · 2024-10-23T09:45:35.128Z

Confirmed to be an App bug and will be fixed in the next version.

buntspext · 2024-10-23T10:05:41.722Z

Thanks for the info. Then i will wait for the next version.

alzhao · 2024-11-07T07:30:54.635Z

3 posts were split to a new topic: MT3000 4.6.6 repeater cannot get IP address

Monoman · 2024-11-20T05:44:20.514Z

I'm not using the App. I'm using the web admin interface and the latest stable firmware from October 2024. Is there an ETA for a release in the stable channel? What about the beta?

alzhao · 2024-11-20T08:21:47.388Z

I am not sure which problem you refer to.

This post contains multiple questions.

On Oct 2 @buntspext posted a bug of the app. Which @acong was referring to.

If you mean MT3000 cannot get IP address, pls use the op24 firmware.

acong · 2024-11-20T08:38:22.360Z

The bug of not displaying saved wifi has been fixed in the v2.6.0 release

buntspext · 2024-11-20T11:23:20.171Z

Yesterday while sitting on a bus i found, that the App-bug might be still there, while connected via app and not connected via wifi.

But i was not able to reproduce the problem. Maybe somebody else can test.

Monoman · 2024-11-20T12:01:33.544Z

I apologize for my incomplete reply. I am using a GL-X3000 that is currently stuck on "Getting ..." when trying to setup as a repeater in my current location. I have adjusted a variety of settings that are covered in this topic and another I found in another forum section. My router is running the latest stable firmware (4.4.13). I looked at the release notes for the latest beta (4.7.1) but I do not see any mention of this problem being fixed in that version.

I am not sure what the op24 firmware is or where to get it.