Puli (repeater mode) won’t see Beryl AX WiFi

I previously posted this and then accidentally deleted it instead of editing :frowning:

Anyhow: I have Puli and Beryl AX, both on the latest firmware.

I am trying to connect Puli (as repeater) to Beryl AX.

I log in to Puli admin panel, go to repeater, and look for available WiFi networks. Puli identifies several available networks, but my Beryl AX 2.4GHz network doesn’t appear. I have rebooted both Puli and Beryl AX. Nothing seems to help.

I tried manually adding SSID & password. Also fails.

I have a Mudi V2 (also in repeater mode) - it sees and connects immediately to Beryl AX WiFi.

What is the problem with repeater mode working on Puli? Is there a feasible solution?

Thanks.

Any input at all? @bruce @admon @rain @alzhao

Thank you!

Hello,

  1. Are the Beryl AX WiFi 5GHz SSID and 2.4GHz the same?
    If they are the same, please modify the 2.4GHz to a different one.

  2. In Puli, Luci -> Network -> Wireless -> Scan, can it scan the Beryl AX 2.4GHz WiFi?

  3. In Puli, GL GUI -> Internet -> Repeater, manually fill in Beryl AX's WiFi information, save, and export syslog after three minutes

Thank you, @Bruce.

Band SSID’s are different - in fact, they are the factory default on both Puli and Beryl AX.

I will try the other points you mention and then report back to you.

Thank you.

@bruce

  1. Band SSID’s are different (they are factory original).

  2. No, Puli does not see Beryl AX network. It sees many other networks, but not Beryl.

  3. Here is the log:

Wed Apr 2 10:08:15 2025 daemon.notice netifd: Interface 'modem_1_1_2' is now down
Wed Apr 2 10:08:20 2025 daemon.err lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:192) call scan trigger fail, wait 11s
Wed Apr 2 10:08:25 2025 daemon.err lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:192) call scan trigger fail, wait 7s
Wed Apr 2 10:08:45 2025 user.info : luci: accepted login on / for root from 192.168.85.131
Wed Apr 2 10:11:17 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1483) new scan task...
Wed Apr 2 10:11:17 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1495) Scan starting...
Wed Apr 2 10:11:18 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1637) .tmp.phy0.sta0: scan...
Wed Apr 2 10:11:23 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1675) .tmp.phy0.sta0: found 16 networks
Wed Apr 2 10:11:23 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1538) scan finished
Wed Apr 2 10:13:29 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1483) new scan task...
Wed Apr 2 10:13:29 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1495) Scan starting...
Wed Apr 2 10:13:30 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1637) .tmp.phy0.sta0: scan...GL-MT3000-e73
Wed Apr 2 10:13:35 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1675) .tmp.phy0.sta0: found 10 networks
Wed Apr 2 10:13:35 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1538) scan finished
Wed Apr 2 10:13:37 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:897) Switching...
Wed Apr 2 10:13:37 2025 daemon.err lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:912) not found matched BSS for 'GL-MT3000-e73'
Wed Apr 2 10:13:37 2025 daemon.err lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:770) not found available network
Wed Apr 2 10:13:37 2025 daemon.err lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:771) reconnect in 30 seconds...
Wed Apr 2 10:14:36 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1483) new scan task...
Wed Apr 2 10:14:36 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1495) Scan starting...
Wed Apr 2 10:14:36 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1483) new scan task...
Wed Apr 2 10:14:37 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1637) .tmp.phy0.sta0: scan...GL-MT3000-e73
Wed Apr 2 10:14:42 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1675) .tmp.phy0.sta0: found 10 networks
Wed Apr 2 10:14:42 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1637) .tmp.phy0.sta0: scan...GL-MT3000-e73
Wed Apr 2 10:14:48 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1675) .tmp.phy0.sta0: found 0 networks
Wed Apr 2 10:14:48 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:1538) scan finished
Wed Apr 2 10:14:50 2025 daemon.info lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:897) Switching...
Wed Apr 2 10:14:50 2025 daemon.err lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:770) not found available network
Wed Apr 2 10:14:50 2025 daemon.err lua: (...07/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:771) reconnect in 30 seconds...

Hello,

Please SSH to router, execute this command to check if the Beryl AX 2.4G WiFi on the scan list:

iwinfo wlan0 scan

Hi @bruce

The Beryl AX network does not appear. This is the output:

root@192.168.85.1's password:

BusyBox v1.35.0 (2023-04-09 12:27:46 UTC) built-in shell (ash)


| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || || |
|
_____|| |
||||___||| |____|
|
| W I R E L E S S F R E E D O M

OpenWrt 22.03.4, r20123-38ccc47687

root@GL-XE300:~# iwinfo wlan0 scan
Cell 01 - Address: 18:A6:F7:EB:6C:16
ESSID: "TP-LINK_6C16"
Mode: Master Channel: 2
Signal: -73 dBm Quality: 37/70
Encryption: WPA2 PSK (CCMP)
HT Operation:
Primary Channel: 2
Secondary Channel Offset: above
Channel Width: 40 MHz or higher

Cell 02 - Address: E4:BE:ED:4A:D2:D0
ESSID: "Royal"
Mode: Master Channel: 8
Signal: -64 dBm Quality: 46/70
Encryption: mixed WPA/WPA2 PSK (TKIP, CCMP)
HT Operation:
Primary Channel: 8
Secondary Channel Offset: no secondary
Channel Width: 20 MHz

Cell 03 - Address: EC:08:6B:8B:72:8A
ESSID: "TP-LINK_728A"
Mode: Master Channel: 5
Signal: -83 dBm Quality: 27/70
Encryption: mixed WPA/WPA2 PSK (CCMP)
HT Operation:
Primary Channel: 5
Secondary Channel Offset: above
Channel Width: 40 MHz or higher

Cell 04 - Address: 44:DF:65:65:FD:A6
ESSID: "Karina222"
Mode: Master Channel: 7
Signal: -76 dBm Quality: 34/70
Encryption: mixed WPA/WPA2 PSK (TKIP, CCMP)
HT Operation:
Primary Channel: 7
Secondary Channel Offset: no secondary
Channel Width: 20 MHz

Cell 05 - Address: 04:8D:38:C5:78:35
ESSID: "220"
Mode: Master Channel: 8
Signal: -90 dBm Quality: 20/70
Encryption: mixed WPA/WPA2 PSK (TKIP, CCMP)
HT Operation:
Primary Channel: 8
Secondary Channel Offset: below
Channel Width: 20 MHz

Cell 06 - Address: 84:D8:1B:61:4E:0F
ESSID: "Kv-213"
Mode: Master Channel: 11
Signal: -66 dBm Quality: 44/70
Encryption: WPA2 PSK (CCMP)
HT Operation:
Primary Channel: 11
Secondary Channel Offset: below
Channel Width: 20 MHz

Cell 07 - Address: 18:D6:C7:73:81:50
ESSID: "user-107279"
Mode: Master Channel: 2
Signal: -82 dBm Quality: 28/70
Encryption: WPA2 PSK (CCMP)
HT Operation:
Primary Channel: 2
Secondary Channel Offset: above
Channel Width: 40 MHz or higher

Cell 08 - Address: CC:2D:E0:E6:A6:37
ESSID: "frzozulya"
Mode: Master Channel: 1
Signal: -83 dBm Quality: 27/70
Encryption: WPA2 PSK (CCMP)
HT Operation:
Primary Channel: 1
Secondary Channel Offset: above
Channel Width: 20 MHz

Cell 09 - Address: 3C:84:6A:76:F1:1E
ESSID: "user-107279_EXT"
Mode: Master Channel: 2
Signal: -90 dBm Quality: 20/70
Encryption: mixed WPA/WPA2 PSK (CCMP)
HT Operation:
Primary Channel: 2
Secondary Channel Offset: above
Channel Width: 40 MHz or higher

Cell 10 - Address: D4:35:38:AB:93:21
ESSID: "Albatros"
Mode: Master Channel: 11
Signal: -89 dBm Quality: 21/70
Encryption: mixed WPA/WPA2 PSK (TKIP, CCMP)
HT Operation:
Primary Channel: 11
Secondary Channel Offset: no secondary
Channel Width: 40 MHz or higher

Same problem found on GL-B3000 as repeater. It cannot find GL-MT3000.

The only way to connect is typing the SSID and click to connect.

It seems odd that this is the first time GL have seen this problem because the problem has been publicly discussed for quite some time. The problem appears to affect Mango, Shadow, Puli and possibly other GL models trying to connect (in repeater mode) to certain other GL models.

In fact, community testing and troubleshooting seems to conclude that Mango/Shadow/Puli (and possibly other models) can see some GL router models ONLY if:

  • Both devices are N-only mode
  • Both devices are locked to 20MHz channel bandwidth
  • Both devices are on channel 1 (sometimes), 6 or 11

Why?

How to fix the root of this problem?

Thank you.

@renato manual entry of the SSID & password works on GL-B3000.

Manual entry does not work on Mango/Shadow/Puli and possibly other devices - this is what needs to be resolved.

@bruce

Hi Bruce. Are you able to advise something after reviewing the output (above) from iwinfo wlan0 scan?

Thanks!

Which Wi-Fi mode do you set to the Beryl Ax AP?

I just encountered a similar issue, if I set the Wi-Fi mode to the one that doesn't include the old protocols, for example, no 802.11a support for 5GHz AP, then my phone will not see it. After I add back the 802.11a support then, all works well.

I see you are using the 2.4GHz mode, if no 802.11b support, some stations may not be able to see the beacon packet. This may also lead to the issue of association as some stations may require 802.11b as a mandatory.

Hi @xenkuo

No B mode on my Beryl AX. B mode is disabled by default, for good reason.

Mango/Shadow/Puli/etc. All support B/G/N according to the spec, and I don’t see any asterisk in the documentation that would lead me to believe they require sniffing for B-mode beacon packets to connect via G or N.

Maybe.

Perhaps @bruce or someone else can contribute a definitive answer.

Just for kicks, I tried a couple more scenarios:

Enable B on Beryl AX. Failed.

Enable B on both Puli and Beryl AX. Failed.

Thanks for the useful feedback about the mode-b test.
This is a very interesting topic; some other tests may help to narrow down the root cause:

  1. I see you the Channel as automatic, are you able to share which channel the Beryl AX is using?
  2. You may set Berly AX to the same channel that the other AP is using and Puli can see them, then manually fill Beryl AX's info to trigger an association.
  3. It will be very helpful as well if you can use another device to trace the 802.11 traffic when the association happens. I imagine there will be some communication between the two routers when the association happens.

I would like to reproduce the issue by myself if I have the two routers, but the reality is I only have Beryl AX...

It is a very odd bug that seems have been present for a very long time. But for some reason there isn’t much effort to resolve it.

@bruce Any thoughts? Thank you.

hello, EvolvePlease
We tried to reproduce it on our side and found that Puli can scan out Beryl's network properly and can relay on it. So, could you tell us what kind of wireless configuration you have for Beryl and Puli? If it's convenient, you can export the configuration of Beryl and Puli via luci and send privately to me.

@weiming.he

Both config files sent privately.