I checked the log. Is the log obtained immediatelly when the repeater failed?
I don’t have too much info about the repeater connection from t his log.
Does Beryl AX found the wifi network?
What is the wifi band and channel?
What is the exact message from the UI? Maybe give a screenshot.
I never understood the fuss with captive portals. I’ve never had an issue with my Beryl AX. I login once and every time I open my laptop back up from sleep I’m immediately back on the network. No re-authentication needed.
Yes that was immediately after the repeater failed. I have waited a couple more minutes before exporting the attached logs.
The Beryl AX does see the wifi network whenever I do a scan.
Mode AX, Channel 44 (5220MHz), Width 80 MHz.
Exact message is
“Connection failed will retry later…
Could not find network, please check the SSID and security type you entered.
While attempting to reconnect, your router will periodically scan for Wi-Fi networks, and your
guest Wi-Fi network will be temporarily unavailable during this scan.”
The above message is what shows up after waiting for a couple minutes with the generic Connection failed will retry later message.
I have screenshots of the above but since I’m a new user I’m only allowed to have one attachment.
logread.zip (24.7 KB)I
If I remember correctly I believe the issues stem from the type of authentication that the captive portal uses. When the captive portal uses this “special” authentication the MediaTek chipset routers have problems where the Qualcomm based routers do not (or maybe it’s the other way around).
Did you ket settings when you upgrade/downgrade firmware?
If yes can you reset the firmware and check again?
I did not keep settings when I flashed between 4.4.6, 4.5.0 beta, 4.5.0 snapshot.
All instances did not connect to the wifi
I did a bit more testing, mainly on 4.5.0 beta. I upgraded without keeping the settings. I also checked how my laptop was connecting to the WiFi and matched those settings with the Beryl AX via the Wireless Menu.
Laptop was connecting by WIFI 4 (802.11n), WPA2-Personal, 5GHz, Channel 44.
I disabled 2.4GHz on the Beryl AX, and forced it to n/ac (no ax) on the 5GHz at Channel 44 and still no luck.
I’ve attached the logs, I tried many times so maybe you can decipher it better than I can. One thing that stood out was there was an association timeout with code 16 and from what I can find online it means “Authentication rejected due to timeout waiting for next frame in sequence”
From what I can see, the SSID goes in and out (disappears and comes back) whenever I try to connect to it. In LuCi, I can see that it shows up, then disappears as well.
I’m checking out of this hotel tomorrow but would be a good use case for firmware upgrades. I found the Beryl AX also cannot connect (and see the SSID) to an industrial rugged modem/router (Brand: MicroHard) I have access to that gives out 2.4GHz but that’s another issue.
logread.zip (33.7 KB)
Please try this temporary firmware.
It worked! I flashed without keeping settings and it connected the first try. I’ve attached the logread for your reference.
Just for more data. Speedtest directly to the hotel AP on my phone I was able to get 25.1Mbps down/4.8Mbps up. Through the MT3000 repeating the hotel AP 4.4Mbps down/4.2Mbps up.
The front LED is still blinking like it’s not connected to an AP/source.
Let me know if you have any other questions. Luckily I was able to test this before I checked out.
Thanks for your hard work!
logread.zip (33.0 KB)
The LED issue is because that this is a testing firmware, with various bugs.
The speed may not be able to solve easily because the situation can be complicated.
Hello,
I’m having a very similar issue on firmware 4.4.6 but instead of hotel wifi, I’m trying to work in repeater mode with VPN client enabled and I can’t connect to some home wifi routers while others work just fine. I’m attaching my log where I try to connect to one of the “faulty” networks. Can you look into it? I see a lot of these entries: wrong IE_HT_CAP.
Also, can you please re-upload the temporary firmware somewhere else as the link you have provided is expired? Thanks.
logread.zip (27.4 KB)
Please try this temporary firmware.
Thank you for your quick reply but when I click this link, I can only see
The transfer you requested has been deleted.
just like for the previous link. Can you please double check? Thanks.
Thanks for the link. I flashed this file over FW 4.5.0 (also tried over 4.4.6 with the same effect) and while it did solve the issue with connecting to the “faulty” WiFi networks, it seems to have affected the WireGuard VPN client functionality. I can’t connect to my defined endpoint which worked just fine before the update. It’s stuck at “The client is starting, please wait…” and the logs say nothing about VPN/wireguard/wg.
Did you try to delete the WG profile and create it from scratch?
Yes, I did remove it and re-import the .conf file I have. It’s puzzling that there is literally nothing about wireguard in the log when trying to run the client on this firmware.
Post output of wg show fr each endpoint.
Redact as required.
root@flint:~# wg show
interface: wgserver
public key:[redacted]=
private key: (hidden)
listening port: 51820
fwmark: 0x80000
peer: [redacted]=
preshared key: (hidden)
endpoint: 192.168.71.137:48285
allowed ips: 10.0.71.2/32, 192.168.118.0/24
latest handshake: 1 minute, 2 seconds ago
transfer: 1.16 MiB received, 13.10 MiB sent
persistent keepalive: every 25 seconds
There is literally no output. I am connected to WiFi in repeater mode, AdGuard is disabled. I re-imported the conf file once again and it’s stuck at “The client is starting, please wait…” while I’m running the command.
root@GL-MT3000:~# wg show
root@GL-MT3000:~#
cat /etc/config/wireguard for all saved confs as Clientcat /etc/config/wireguard_server if running as ServerHere’s an example of a Client. MTU may be different (eg: 1420) & preshared keys are optional (but recommended where possible):
config peers 'peer_[redacted]'
option group_id '[redacted]'
option name 'myName'
option end_point '[redacted]:51820'
option private_key '[redacted]'
option public_key '[redacted]'
option presharedkey_enable '1'
option preshared_key '[redacted]'
option persistent_keepalive '25'
option ipv6_enable '0'
option mtu '1320'
option allowed_ips '0.0.0.0/0'
option local_access '1'
option default_metric '0'
option masq '1'
option address_v4 '10.0.0.2/24'