Huawei E3372 not working on Beryl AX

Routers Cellular, USB modems
1

Hi,

I’m having issues getting my Huawei E3372h modem with Beryl despite multiple attempts. The stick is already configured to start in stick mode and is working out of the box on Windows machines (starting the connection manager) , Asuswrt 3004 and ROOTer golder orb.

However on my Beryl 4.8.1 it simply refuses to work. My mobile provider is Digi Romania.

I have tried both 3g and NCM protocols but no dice, the modem looks like it’s connecting and during the handshake something breaks and it restarts the process.

I’d appreciate some help since I’ve spent many hours trying to get this to work on Beryl before an upcoming trip, which is the whole reason I’ve bought the router in the first place. Since the same modem works out of the box on the others firmwares, it’s very likely a configuration issue with Beryl.

Below the logs:

Thu Feb 12 23:18:12 2026 user.info modem: (ncm.sh:61) manufacturer:huawei
Thu Feb 12 23:18:12 2026 daemon.notice netifd: modem_1_1 (16262): sending -> AT
Thu Feb 12 23:18:13 2026 daemon.notice netifd: modem_1_1 (16262): sending -> ATZ
Thu Feb 12 23:18:13 2026 daemon.notice netifd: modem_1_1 (16262): sending -> ATQ0
Thu Feb 12 23:18:14 2026 daemon.notice netifd: modem_1_1 (16262): sending -> ATV1
Thu Feb 12 23:18:15 2026 daemon.notice netifd: modem_1_1 (16262): sending -> ATE1
Thu Feb 12 23:18:15 2026 daemon.notice netifd: modem_1_1 (16262): sending -> ATS0=0
Thu Feb 12 23:18:16 2026 daemon.notice netifd: modem_1_1 (16262): sending -> AT+CGDCONT=1,"IP","internet"
Thu Feb 12 23:18:25 2026 user.info modem: (ncm.sh:26) (unlock_special_model_sim_pin)sim_status:READY modem_bus:1-1 interface:modem_1_1 device:/dev/ttyUSB1 pincode: iccid:XXXX
Thu Feb 12 23:18:25 2026 user.info modem: (ncm.sh:100) Configuring modem
Thu Feb 12 23:18:25 2026 user.info modem: (ncm.sh:113) Setting mode
Thu Feb 12 23:18:25 2026 daemon.notice netifd: modem_1_1 (16262): sending -> AT^SYSCFGEX="030201",3fffffff,2,4,7fffffffffffffff,,
Thu Feb 12 23:18:26 2026 user.info modem: (ncm.sh:123) Starting network modem_1_1
Thu Feb 12 23:18:26 2026 user.info modem: (ncm.sh:127) Connecting modem
Thu Feb 12 23:18:27 2026 daemon.notice netifd: modem_1_1 (16262): sending -> AT^NDISDUP=1,1,"internet"
Thu Feb 12 23:18:27 2026 user.info modem: (ncm.sh:137) Setting up wwan0
Thu Feb 12 23:18:27 2026 daemon.notice netifd: Interface 'modem_1_1' is now up
Thu Feb 12 23:18:27 2026 daemon.notice netifd: Network device 'wwan0' link is up
Thu Feb 12 23:18:27 2026 daemon.notice netifd: Network alias 'wwan0' link is up
Thu Feb 12 23:18:27 2026 daemon.notice netifd: Interface 'modem_1_1_4' is enabled
Thu Feb 12 23:18:27 2026 daemon.notice netifd: Interface 'modem_1_1_4' has link connectivity
Thu Feb 12 23:18:27 2026 daemon.notice netifd: Interface 'modem_1_1_4' is setting up now
Thu Feb 12 23:18:27 2026 daemon.notice netifd: modem_1_1_4 (17462): udhcpc: started, v1.33.2
Thu Feb 12 23:18:27 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Thu Feb 12 23:18:27 2026 daemon.notice netifd: modem_1_1_4 (17462): udhcpc: sending discover
Thu Feb 12 23:18:29 2026 daemon.info avahi-daemon[8866]: Joining mDNS multicast group on interface wwan0.IPv6 with address fe80::21e:10ff:fe1f:0.
Thu Feb 12 23:18:29 2026 daemon.info avahi-daemon[8866]: New relevant interface wwan0.IPv6 for mDNS.
Thu Feb 12 23:18:29 2026 daemon.info avahi-daemon[8866]: Registering new address record for fe80::21e:10ff:fe1f:0 on wwan0.*.
Thu Feb 12 23:18:29 2026 daemon.info gl_modem: (modem_cm.c:1413) Dial-up is successful using network configuration,dialing consumed a total of 29 seconds
Thu Feb 12 23:18:29 2026 daemon.info gl_modem: (modem_cm.c:1488) Exit the dialing process
Thu Feb 12 23:18:30 2026 daemon.notice netifd: modem_1_1_4 (17462): udhcpc: sending discover
Thu Feb 12 23:18:33 2026 daemon.notice netifd: modem_1_1_4 (17462): udhcpc: sending discover
Thu Feb 12 23:19:08 2026 user.notice kmwan: config json str={ "op": 2, "data": { "cells": [ { "interface": "modem_1_1", "netdev": "wwan0", "track_mode": "passive", "addr_type": 4, "force_ip": "0.0.0.0", "tracks": [ { "type": "ping", "ip": "1.1.1.1" }, { "type": "ping", "ip": "8.8.8.8" }, { "type": "ping", "ip": "208.67.222.222" }, { "type": "ping", "ip": "208.67.220.220" } ] } ] } }
Thu Feb 12 23:19:08 2026 kern.debug kernel: [ 6703.133312] [add_dev_config 319]add node success. iface:modem_1_1, dev:wwan0, ifindex:5
Thu Feb 12 23:19:08 2026 daemon.info gl-repeater[3169]: (repeater.lua:1741) interface modem_1_1 status offline
Thu Feb 12 23:19:09 2026 user.notice firewall: Reloading firewall due to ifup of modem_1_1 (wwan0)
Thu Feb 12 23:19:26 2026 user.info modem: (modem_network_recover_detection.sh:80) (modem_network_recover) dection 15 s interface modem_1_1 is offline and the network is restart...
Thu Feb 12 23:19:26 2026 daemon.info gl_modem: (modem_cm.c:1324) Enter the dialing process
Thu Feb 12 23:19:27 2026 daemon.info gl_modem: (modem_cm.c:1351) Now that the simcard is ready, try dialing...
Thu Feb 12 23:19:27 2026 daemon.info gl_modem: (modem_cm.c:1380) curr dial imsi:226050073656531
Thu Feb 12 23:19:27 2026 daemon.info gl_modem: (modem_cm.c:1396) network configuration exists
Thu Feb 12 23:19:27 2026 daemon.info gl_modem: (modem_cm.c:1408) Start dial form network...
Thu Feb 12 23:19:27 2026 daemon.info gl_modem: (modem_cm.c:1107) Start performing the dialing action...
Thu Feb 12 23:19:27 2026 daemon.notice netifd: modem_1_1_4 (17462): udhcpc: received SIGTERM
Thu Feb 12 23:19:27 2026 daemon.notice netifd: modem_1_1_4 (17462): udhcpc: entering released state
Thu Feb 12 23:19:27 2026 user.err modem: (ncm.sh:27) Stopping network modem_1_1
Thu Feb 12 23:19:27 2026 daemon.notice netifd: modem_1_1_4 (17462): Command failed: Permission denied
Thu Feb 12 23:19:27 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Thu Feb 12 23:19:27 2026 daemon.notice netifd: Interface 'modem_1_1_4' is now down
Thu Feb 12 23:19:27 2026 daemon.notice netifd: Network alias '' link is down
Thu Feb 12 23:19:27 2026 daemon.notice netifd: Interface 'modem_1_1_4' has link connectivity loss
Thu Feb 12 23:19:27 2026 daemon.notice netifd: Interface 'modem_1_1_4' is disabled
Thu Feb 12 23:19:27 2026 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "modem_1_1" ] } }
Thu Feb 12 23:19:27 2026 kern.debug kernel: [ 6722.381461] kmwan: Delete node:modem_1_1
Thu Feb 12 23:19:27 2026 user.notice firewall: Reloading firewall due to ifdown of modem_1_1 ()
Thu Feb 12 23:19:27 2026 daemon.notice netifd: modem_1_1 (19053): sending -> AT^NDISDUP=1,0
Thu Feb 12 23:19:28 2026 daemon.notice netifd: modem_1_1 (19053): Command failed: Permission denied
Thu Feb 12 23:19:28 2026 daemon.notice netifd: Interface 'modem_1_1' is now down
Thu Feb 12 23:19:28 2026 daemon.info avahi-daemon[8866]: Interface wwan0.IPv6 no longer relevant for mDNS.
Thu Feb 12 23:19:28 2026 daemon.info avahi-daemon[8866]: Leaving mDNS multicast group on interface wwan0.IPv6 with address fe80::21e:10ff:fe1f:0.
Thu Feb 12 23:19:28 2026 daemon.info avahi-daemon[8866]: Withdrawing address record for fe80::21e:10ff:fe1f:0 on wwan0.
Thu Feb 12 23:19:28 2026 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "modem_1_1" ] } }
Thu Feb 12 23:19:28 2026 user.notice firewall: Reloading firewall due to ifdown of modem_1_1 ()

Thank you!

3

Can you share device to support via Goodcloud for remote troubleshooting? We want to check more router configurations.

4

Sent the PM. The modem is attached but stopped since it keeps going in loops.

As a side note, consider supporting diagnostics logs instead of remote access, the latter is much more intrusive and a security nightmare.

5

Thank you for your suggestion. We will consider it. Additionally, the USB modem is working now. It need to switch to the /dev/ttyUSB1 interface to obtain the IP.

6

Thank you! I didn’t expect such a fast turnaround. Was it just switching the interface to /dev/ttyUSB1 change or was there anything else needed?

Thanks!

7

Yeah just need to change the dial port to /dev/ttyUSB1

8

@Cathy was this fixed in the FW since our dialogue here? https://forum.gl-inet.com/t/re-e3372h-607-in-stick-mode-on-beryl-ax-mt3000-not-working-unreliable-connection/57545

9

Johnsomer's issue is related to the dial-up port and not related to the firmware. However, the firmware that I shared previously was a beta version. The latest one has added the SMS fixes. I recommend you upgrade to the latest stable version if having issue.

10

Actually it was more whether the Stick mode E3372s (vs E3372h Hi Link) now worked on the Beryl AX or GLiNET Routers?

Asking as @JohnSomers mentioned:

  • Huawei E3372h modem
  • with Beryl
  • configured to start in stick mode (E3372s)
  • working ... on Windows machines (starting the connection manager)
  • However on my Beryl 4.8.1 it simply refuses to work....

Then you said:

  • Additionally, the USB modem is working now.
  • It need to switch to the /dev/ttyUSB1 interface to obtain the IP.

Which is what prompted me to ask whether the E3372h (if converted to 'Stick' mode i.e. E3372s) was finally compatible?

11

It's not fully compatible. Mostly it can connect to internet via NCM protocol. Although they all operate in Stick mode, the built-in firmware may vary. Do you have the issue? Can you share the log to check again?

12

Hi Cathy,

Originally I converted the E3372h to stick mode E3372s to take advantage of the CDC-WDMx protocol and native stick mode speeds.

When we couldn’t make it work last time I converted it back to HiLink mode.

I can convert it back to Stick mode if there is clear direction that stick mode now works with Beryl AX. Can you let me know if this is the case please. If you have made no improvements in that regard i will leave it in HiLink mode. Thanks

Edit - the issue I meant to link to was the better performing cdc protocol which you advised you removed, see E3372h-607 in stick mode on Beryl AX (MT3000) not working / unreliable connection - #23 by SmurfonToast

k.

13

Hi @SmurfonToast Sorry the GL-GUI still does not support the cdc-wdmX connection at the moment.

​​​​​​​​​

14

No worries, thanks for clarifying.

Saves me converting the thing to stick mode again.

1 Like