Beryl GL-MT1300 unable to act as station/client

[FMS]

@silkweb

• 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

• 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

@alzhao

Can you make sure you are using 3.201 firmware?

• 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 )

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?