Beryl GL-MT1300 unable to act as station/client

I just ordered two Beryls (GL-MT1300s), but neither of them is able to connect to my home WiFi. The home WiFi is using WPA2 Personal, and running with the same ESSID on both 2.4GHz and 5GHz. I’ve tried connecting on both the 2.4GHz and the 5GHz, as well as moving the Beryl closer to my primary router.

The UI shows “success” with joining, but then the main page shows no connection to the internet. My main router shows a brief (several seconds) connection from the Beryl, but no data.

When I look at the Beryl’s logs, this appears to repeat every 5 seconds or so (one full loop below):

Sun Sep  6 20:26:21 2020 daemon.notice netifd: Interface 'wwan' has link connectivity
Sun Sep  6 20:26:21 2020 user.info : [ 2894] gl-wifi-core>> bIsStaEnabled=1
Sun Sep  6 20:26:26 2020 daemon.notice netifd: Interface 'wwan' is enabled
Sun Sep  6 20:26:26 2020 daemon.notice netifd: Interface 'wwan' is setting up now
Sun Sep  6 20:26:26 2020 daemon.notice netifd: wwan (6276): udhcpc: started, v1.30.1
Sun Sep  6 20:26:26 2020 daemon.notice netifd: wwan (6276): udhcpc: sending discover
Sun Sep  6 20:26:26 2020 daemon.notice netifd: Network device 'apclix0' link is down
Sun Sep  6 20:26:26 2020 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Sun Sep  6 20:26:26 2020 daemon.notice netifd: wwan (6276): udhcpc: read error: Network is down, reopening socket
Sun Sep  6 20:26:26 2020 daemon.notice netifd: Network device 'rax0' link is down
Sun Sep  6 20:26:27 2020 daemon.notice netifd: wwan (6276): udhcpc: received SIGTERM
Sun Sep  6 20:26:27 2020 daemon.notice netifd: Interface 'wwan' is now down
Sun Sep  6 20:26:27 2020 daemon.notice netifd: Interface 'wwan' is disabled
Sun Sep  6 20:26:27 2020 daemon.notice netifd: Interface 'wwan' is enabled
Sun Sep  6 20:26:27 2020 daemon.notice netifd: Network device 'rax0' link is up
Sun Sep  6 20:26:27 2020 daemon.notice netifd: Network device 'apclix0' link is up
Sun Sep  6 20:26:27 2020 daemon.notice netifd: Interface 'wwan' has link connectivity
Sun Sep  6 20:26:27 2020 daemon.notice netifd: Interface 'wwan' is setting up now
Sun Sep  6 20:26:27 2020 daemon.notice netifd: wwan (6458): udhcpc: started, v1.30.1
Sun Sep  6 20:26:28 2020 daemon.notice netifd: wwan (6458): udhcpc: sending discover
Sun Sep  6 20:26:31 2020 daemon.notice netifd: wwan (6458): udhcpc: sending discover
Sun Sep  6 20:26:34 2020 daemon.notice netifd: wwan (6458): udhcpc: sending discover
Sun Sep  6 20:27:01 2020 daemon.notice netifd: Network device 'apclix0' link is down
Sun Sep  6 20:27:01 2020 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Sun Sep  6 20:27:01 2020 daemon.notice netifd: wwan (6458): udhcpc: read error: Network is down, reopening socket
Sun Sep  6 20:27:01 2020 daemon.notice netifd: Network device 'apclix0' link is up
Sun Sep  6 20:27:01 2020 daemon.notice netifd: Interface 'wwan' has link connectivity
Sun Sep  6 20:27:01 2020 user.info : [ 2894] gl-wifi-core>> bIsStaEnabled=1
Sun Sep  6 20:27:01 2020 daemon.notice netifd: wwan (6458): udhcpc: received SIGTERM
Sun Sep  6 20:27:01 2020 daemon.notice netifd: Interface 'wwan' is now down
Sun Sep  6 20:27:01 2020 daemon.notice netifd: Interface 'wwan' is disabled
Sun Sep  6 20:27:26 2020 user.info : [ 3494] gl-wifi-core>> Join wifi failed! (code=-5) ***
Sun Sep  6 20:27:27 2020 daemon.notice netifd: Network device 'apclix0' link is down
Sun Sep  6 20:27:27 2020 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Sun Sep  6 20:27:27 2020 daemon.notice netifd: Network device 'apclix0' link is up
Sun Sep  6 20:27:27 2020 daemon.notice netifd: Interface 'wwan' has link connectivity
Sun Sep  6 20:27:27 2020 user.info : [ 2894] gl-wifi-core>> bIsStaEnabled=1
Sun Sep  6 20:27:32 2020 daemon.notice netifd: Interface 'wwan' is enabled
Sun Sep  6 20:27:32 2020 daemon.notice netifd: Interface 'wwan' is setting up now

What’s going wrong? What does code -5 mean? And what can I try next?

1 Like
  • Can you connect with your phone using a random mac address?

  • Change the default IP to something different

  • Reset the router to factory default and try again

  • Try to connect using wire (RJ45 LAN - WAN) and see if is working

1 Like

Can you make sure you are using 3.201 firmware?

From the log, seems that it cannot get IP address from your main wifi

  • Yes, phone can connect with a random MAC address. I can also join with a laptop that has never been to this WiFi before.
  • The wireless network uses 192.168.1.1/24, which doesn’t conflict with the Beryl’s default 192.168.8.1/24
  • Resetting the router to factory default, going to the web UI, setting a new password, and joining the network without doing any other steps results in the same failure.
  • Connecting the router via ethernet works fine
  • Yep, failing with 3.201 firmware. Here’s a logread from a fresh network setup on 3.201 (which seems to be failing differently than on 3.200 :face_with_monocle:)
Sun Apr  4 00:40:05 2021 authpriv.notice dropbear[5697]: Password auth succeeded for 'root' from 192.168.8.155:51272
Sun Apr  4 00:42:48 2021 user.info : saved ssid ignore: not linksys 0
Sun Apr  4 00:42:48 2021 user.info : [  810] gl-sdk>> bIsSaved=0, ssid=not linksys, encryption=psk2, bssid=7x:Ax:Bx:5x:8x:Ax, wds=0, device=mt7615e5, identity=, channel=36
Sun Apr  4 00:42:48 2021 daemon.notice netifd: Network device 'apclix0' link is down
Sun Apr  4 00:42:48 2021 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Sun Apr  4 00:42:48 2021 daemon.notice netifd: wwan (3269): udhcpc: read error: Network is down, reopening socket
Sun Apr  4 00:42:48 2021 user.notice apcli: apclix0 down
Sun Apr  4 00:42:48 2021 daemon.notice netifd: wwan (3269): udhcpc: received SIGTERM
Sun Apr  4 00:42:48 2021 user.info : [ 2960] gl-wifi-core>> bIsStaEnabled=1
Sun Apr  4 00:42:49 2021 daemon.notice netifd: Interface 'wwan' is now down
Sun Apr  4 00:42:49 2021 daemon.notice netifd: Interface 'wwan' is disabled
Sun Apr  4 00:42:54 2021 daemon.notice netifd: Interface 'wwan' is enabled
Sun Apr  4 00:42:54 2021 user.info : [  817] gl-sdk>> wifi_join return=0, channel=-1
Sun Apr  4 00:42:54 2021 user.notice apcli: apcli0 down
Sun Apr  4 00:42:54 2021 daemon.notice netifd: Network device 'ra0' link is down
Sun Apr  4 00:42:55 2021 daemon.notice netifd: Network device 'ra0' link is up
Sun Apr  4 00:42:55 2021 daemon.notice netifd: Network device 'apcli0' link is up
Sun Apr  4 00:42:55 2021 daemon.notice netifd: Interface 'wwan' is disabled
Sun Apr  4 00:42:55 2021 daemon.notice netifd: Network device 'apcli0' link is up
Sun Apr  4 00:42:55 2021 daemon.notice netifd: Interface 'wwan' is enabled
Sun Apr  4 00:42:55 2021 daemon.notice netifd: Interface 'wwan' has link connectivity
Sun Apr  4 00:42:55 2021 daemon.notice netifd: Interface 'wwan' is setting up now
Sun Apr  4 00:42:55 2021 daemon.notice netifd: wwan (10040): udhcpc: started, v1.30.1
Sun Apr  4 00:42:55 2021 daemon.notice netifd: wwan (10040): udhcpc: sending discover
Sun Apr  4 00:42:58 2021 daemon.notice netifd: wwan (10040): udhcpc: sending discover
Sun Apr  4 00:43:01 2021 daemon.notice netifd: wwan (10040): udhcpc: sending discover
Sun Apr  4 00:43:54 2021 user.info : gl_health start->




For some new diagnostics, it looks like everything is fine from the Beryl side:

root@GL-MT1300:~# iwconfig apcli0
apcli0    RTWIFI SoftAP  ESSID:"not linksys"  
          Mode:Managed  Channel=36  Access Point: 7x:Ax:Bx:5x:8x:Ax   
          Bit Rate=400 Mb/s   
          
root@GL-MT1300:~# ifconfig apcli0
apcli0    Link encap:Ethernet  HWaddr 7x:Ax:Bx:5x:8x:Ax  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22 errors:0 dropped:18 overruns:0 frame:0
          TX packets:157 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4244 (4.1 KiB)  TX bytes:52822 (51.5 KiB)

And from the wireless side too:

The Beryl doesn’t seem to be getting an IP address. (It’s the only client on the network that has not gotten an IP). Any suggestions?

  • Create a portable hotspot with your mobile and see if Beryl can connect to it as it should

  • Shut down the main router for a couple of minutes (disconnect it from power source) and turn it on

  • Turn off 5G for the main router and see if Beryl can connect to the 2G WiFi

Portable hotspot works correctly.
Leaving the router off for 10 minutes didn’t fix the issue.
Turning the router to 2g only also didn’t fix the issue.

It still looks like the DHCP request isn’t working. On my main router’s side, I see Beryl with a wrong old IP (left over from the mobile hotspot): 192.168.9.x.

In the logs, I still see the DHCP requests being sent:

Tue May 4 16:14:48 2021 user.info : [ 810] gl-sdk>> bIsSaved=0, ssid=not linksys, encryption=psk2, bssid=7x:Ax:Bx:5x:8x:Ax, wds=0, device=mt7615e2, identity=, channel=1
Tue May 4 16:14:48 2021 user.notice apcli: apclix0 down
Tue May 4 16:14:49 2021 daemon.notice netifd: wwan (3266): udhcpc: sending renew to 172.20.10.1
Tue May 4 16:14:49 2021 daemon.notice netifd: wwan (3266): udhcpc: received SIGTERM
Tue May 4 16:14:49 2021 daemon.notice netifd: Interface ‘wwan’ is now down
Tue May 4 16:14:49 2021 daemon.notice netifd: Interface ‘wwan’ is disabled
Tue May 4 16:14:49 2021 daemon.warn dnsmasq[3077]: no servers found in /tmp/resolv.conf.auto, will retry
Tue May 4 16:14:49 2021 daemon.notice netifd: Network device ‘apclix0’ link is down
Tue May 4 16:14:49 2021 daemon.notice netifd: Interface ‘wwan’ has link connectivity loss
Tue May 4 16:14:49 2021 daemon.notice netifd: Network device ‘apclix0’ link is up
Tue May 4 16:14:49 2021 daemon.notice netifd: Interface ‘wwan’ has link connectivity
Tue May 4 16:14:49 2021 user.info : [ 2960] gl-wifi-core>> bIsStaEnabled=1
Tue May 4 16:14:54 2021 daemon.notice netifd: Interface ‘wwan’ is enabled
Tue May 4 16:14:54 2021 daemon.notice netifd: Interface ‘wwan’ is setting up now
Tue May 4 16:14:55 2021 daemon.notice netifd: wwan (21547): udhcpc: started, v1.30.1
Tue May 4 16:14:55 2021 user.info : [ 817] gl-sdk>> wifi_join return=0, channel=-1
Tue May 4 16:14:55 2021 daemon.notice netifd: wwan (21547): udhcpc: sending discover
Tue May 4 16:14:55 2021 daemon.notice netifd: Network device ‘apclix0’ link is down
Tue May 4 16:14:55 2021 daemon.notice netifd: Interface ‘wwan’ has link connectivity loss
Tue May 4 16:14:55 2021 user.notice apcli: apclix0 down
Tue May 4 16:14:55 2021 daemon.notice netifd: wwan (21547): udhcpc: read error: Network is down, reopening socket
Tue May 4 16:14:55 2021 daemon.notice netifd: Network device ‘rax0’ link is down
Tue May 4 16:14:55 2021 daemon.notice netifd: wwan (21547): udhcpc: received SIGTERM
Tue May 4 16:14:55 2021 daemon.notice netifd: Interface ‘wwan’ is now down
Tue May 4 16:14:55 2021 daemon.notice netifd: Interface ‘wwan’ is disabled
Tue May 4 16:14:55 2021 daemon.notice netifd: Interface ‘wwan’ is enabled
Tue May 4 16:14:56 2021 daemon.notice netifd: Network device ‘rax0’ link is up
Tue May 4 16:14:56 2021 daemon.notice netifd: Network device ‘apclix0’ link is up
Tue May 4 16:14:56 2021 daemon.notice netifd: Interface ‘wwan’ has link connectivity
Tue May 4 16:14:56 2021 daemon.notice netifd: Interface ‘wwan’ is setting up now
Tue May 4 16:14:56 2021 daemon.notice netifd: wwan (21711): udhcpc: started, v1.30.1
Tue May 4 16:14:56 2021 daemon.notice netifd: wwan (21711): udhcpc: sending discover
Tue May 4 16:14:58 2021 daemon.info dnsmasq-dhcp[3077]: DHCPREQUEST(br-lan) 192.168.8.155 hh:hh:hh:hh:hh:hh
Tue May 4 16:14:58 2021 daemon.info dnsmasq-dhcp[3077]: DHCPACK(br-lan) 192.168.8.155 hh:hh:hh:hh:hh:hh my-machine
Tue May 4 16:14:59 2021 daemon.notice netifd: wwan (21711): udhcpc: sending discover

Manually renewing DHCP lease also doesn’t work:

root@GL-MT1300:~# udhcpc -i apclix0 -r 192.168.1.177
udhcpc: started, v1.30.1
udhcpc: sending discover
udhcpc: sending discover
^C

However, I seem to be able to manually fix things!

root@GL-MT1300:~# ifconfig apclix0 inet 192.168.1.177
root@GL-MT1300:~# route add default gw 192.168.1.1
root@GL-MT1300:~# cat /etc/resolv.conf | sed -e ‘s/127.0.0.1/192.168.1.1/’ > /tmp/resolv.conf
root@GL-MT1300:~# cp /tmp/resolv.conf /etc/resolv.conf
root@GL-MT1300:~# rm /tmp/resolv.conf

At this point, the router has internet connectivity:

root@GL-MT1300:~# nslookup gl-inet.com
Server: 192.168.1.1
Address: 192.168.1.1#53

Name: gl-inet.com
Address 1: 52.41.190.83
*** Can’t find gl-inet.com: No answer
root@GL-MT1300:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: seq=0 ttl=59 time=44.836 ms
64 bytes from 1.1.1.1: seq=1 ttl=59 time=48.926 ms

And the web interface shows a connection:

But unfortunately, it’s not responding to DNS queries. And the internet connection seems to be intermittent:

root@GL-MT1300:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: seq=31 ttl=59 time=40.221 ms
64 bytes from 1.1.1.1: seq=32 ttl=59 time=60.564 ms
64 bytes from 1.1.1.1: seq=33 ttl=59 time=40.665 ms
64 bytes from 1.1.1.1: seq=34 ttl=59 time=40.415 ms
64 bytes from 1.1.1.1: seq=35 ttl=59 time=42.782 ms
64 bytes from 1.1.1.1: seq=36 ttl=59 time=41.409 ms
64 bytes from 1.1.1.1: seq=37 ttl=59 time=43.688 ms
64 bytes from 1.1.1.1: seq=38 ttl=59 time=43.486 ms
64 bytes from 1.1.1.1: seq=39 ttl=59 time=42.409 ms
64 bytes from 1.1.1.1: seq=40 ttl=59 time=41.225 ms
64 bytes from 1.1.1.1: seq=41 ttl=59 time=47.837 ms
^C
— 1.1.1.1 ping statistics —
42 packets transmitted, 11 packets received, 73% packet loss
round-trip min/avg/max = 40.221/44.063/60.564 ms

And a logread shows that the interface seems to be going up and down:

Tue May 4 16:49:52 2021 user.info mwan3rtmon[2676]: Detect rtchange event.
Tue May 4 16:49:53 2021 user.notice firewall: Reloading firewall due to ifup of wwan (apclix0)
Tue May 4 16:51:13 2021 user.info mwan3rtmon[2676]: Detect rtchange event.
Tue May 4 16:51:13 2021 user.notice firewall: Reloading firewall due to ifup of wwan (apclix0)
Tue May 4 16:52:33 2021 user.info mwan3rtmon[2676]: Detect rtchange event.
Tue May 4 16:52:33 2021 user.notice firewall: Reloading firewall due to ifup of wwan (apclix0)
Tue May 4 16:53:53 2021 user.info mwan3rtmon[2676]: Detect rtchange event.
Tue May 4 16:53:53 2021 user.notice firewall: Reloading firewall due to ifup of wwan (apclix0)
Tue May 4 16:55:13 2021 user.info mwan3rtmon[2676]: Detect rtchange event.
Tue May 4 16:55:13 2021 user.notice firewall: Reloading firewall due to ifup of wwan (apclix0)
Tue May 4 16:56:33 2021 user.info mwan3rtmon[2676]: Detect rtchange event.
Tue May 4 16:56:34 2021 user.notice firewall: Reloading firewall due to ifup of wwan (apclix0)
Tue May 4 16:57:53 2021 user.info mwan3rtmon[2676]: Detect rtchange event.
Tue May 4 16:57:53 2021 user.notice firewall: Reloading firewall due to ifup of wwan (apclix0)
Tue May 4 16:59:13 2021 user.info mwan3rtmon[2676]: Detect rtchange event.
Tue May 4 16:59:14 2021 user.notice firewall: Reloading firewall due to ifup of wwan (apclix0)
Tue May 4 17:00:34 2021 user.info mwan3rtmon[2676]: Detect rtchange event.
Tue May 4 17:00:34 2021 user.notice firewall: Reloading firewall due to ifup of wwan (apclix0)
Tue May 4 17:01:54 2021 user.info mwan3rtmon[2676]: Detect rtchange event.
Tue May 4 17:01:54 2021 user.notice firewall: Reloading firewall due to ifup of wwan (apclix0)

So my current state:

  • DHCP requests don’t seem to work
  • I can manually configure things to work, except for the Beryl’s DNS server
  • IP connectivity seems flakey; sometimes it works and sometimes it doesn’t. Probably due to interface going up and down.
  • Beryl is about 10 feet from main router with no obstacles in between; signal quality should be perfect.

Where/how can I capture additional logs? What do I try next?

Not sure if this is caused by mwan3.

Maybe disable it totally? You can check /etc/config/mwan3 and remove all the rules