GL-AXT1800 and e3372h

[Barometer]

I'm trying to get the Huawei E3372h-320 to work with my AXT1800

1. The dongle works fine with my laptop. Pincode is disabled, so it always directly connects.
2. I've changed the AXT1800 IP from 192.186.8.1 to 192.168.10.1
3. I'm running firmware version 4.6.11

Tethering can't connect. Keeps on showing 'Connecting...'

My logs show:

Tue Jul  8 21:24:56 2025 user.notice firewall: Reloading firewall due to ifdown of tethering ()
Tue Jul  8 21:24:58 2025 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "tethering" ] } }
Tue Jul  8 21:25:15 2025 daemon.notice netifd: Interface 'tethering' is enabled
Tue Jul  8 21:25:15 2025 daemon.notice netifd: Network device 'eth3' link is up
Tue Jul  8 21:25:15 2025 daemon.notice netifd: Interface 'tethering' has link connectivity
Tue Jul  8 21:25:15 2025 daemon.notice netifd: Interface 'tethering' is setting up now
Tue Jul  8 21:25:15 2025 kern.err kernel: [ 1578.812080] cdc_ether 1-1:1.0 eth3: kevent 12 may have been dropped
Tue Jul  8 21:25:15 2025 daemon.notice netifd: tethering (19798): udhcpc: started, v1.33.2
Tue Jul  8 21:25:15 2025 daemon.notice netifd: tethering (19798): udhcpc: sending discover
Tue Jul  8 21:25:17 2025 daemon.info avahi-daemon[4171]: Joining mDNS multicast group on interface eth3.IPv6 with address fe80::21e:10ff:fe1f:0.
Tue Jul  8 21:25:17 2025 daemon.info avahi-daemon[4171]: New relevant interface eth3.IPv6 for mDNS.
Tue Jul  8 21:25:17 2025 daemon.info avahi-daemon[4171]: Registering new address record for fe80::21e:10ff:fe1f:0 on eth3.*.
Tue Jul  8 21:25:18 2025 daemon.notice netifd: tethering (19798): udhcpc: sending discover
Tue Jul  8 21:25:21 2025 daemon.notice netifd: tethering (19798): udhcpc: sending discover
Tue Jul  8 21:31:00 2025 daemon.notice netifd: tethering (19798): udhcpc: received SIGTERM
Tue Jul  8 21:31:00 2025 daemon.notice netifd: tethering (19798): udhcpc: entering released state
Tue Jul  8 21:31:00 2025 daemon.notice netifd: tethering (19798): Command failed: Permission denied
Tue Jul  8 21:31:00 2025 daemon.notice netifd: Interface 'tethering' is now down
Tue Jul  8 21:31:00 2025 daemon.info avahi-daemon[4171]: Interface eth3.IPv6 no longer relevant for mDNS.
Tue Jul  8 21:31:00 2025 daemon.info avahi-daemon[4171]: Leaving mDNS multicast group on interface eth3.IPv6 with address fe80::21e:10ff:fe1f:0.
Tue Jul  8 21:31:00 2025 daemon.info avahi-daemon[4171]: Withdrawing address record for fe80::21e:10ff:fe1f:0 on eth3.
Tue Jul  8 21:31:00 2025 daemon.notice netifd: Interface 'tethering' is disabled
Tue Jul  8 21:31:00 2025 daemon.notice netifd: Interface 'tethering' has link connectivity loss
Tue Jul  8 21:31:01 2025 user.notice firewall: Reloading firewall due to ifdown of tethering ()
Tue Jul  8 21:31:02 2025 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "tethering" ] } }
Tue Jul  8 21:31:04 2025 daemon.notice netifd: Interface 'tethering' is enabled
Tue Jul  8 21:31:04 2025 daemon.notice netifd: Network device 'eth3' link is up
Tue Jul  8 21:31:04 2025 daemon.notice netifd: Interface 'tethering' has link connectivity
Tue Jul  8 21:31:04 2025 daemon.notice netifd: Interface 'tethering' is setting up now
Tue Jul  8 21:31:04 2025 kern.err kernel: [ 1928.026490] cdc_ether 1-1:1.0 eth3: kevent 12 may have been dropped
Tue Jul  8 21:31:04 2025 daemon.notice netifd: tethering (21514): udhcpc: started, v1.33.2
Tue Jul  8 21:31:05 2025 daemon.notice netifd: tethering (21514): udhcpc: sending discover
Tue Jul  8 21:31:06 2025 daemon.info avahi-daemon[4171]: Joining mDNS multicast group on interface eth3.IPv6 with address fe80::21e:10ff:fe1f:0.
Tue Jul  8 21:31:06 2025 daemon.info avahi-daemon[4171]: New relevant interface eth3.IPv6 for mDNS.
Tue Jul  8 21:31:06 2025 daemon.info avahi-daemon[4171]: Registering new address record for fe80::21e:10ff:fe1f:0 on eth3.*.
Tue Jul  8 21:31:08 2025 daemon.notice netifd: tethering (21514): udhcpc: sending discover
Tue Jul  8 21:31:11 2025 daemon.notice netifd: tethering (21514): udhcpc: sending discover

[bruce]

Hi,

Checked the syslog, there are 3 times to send the dhcp discover to USB modem from the interface tethering, but the USB modem did not reply to the offer to router tethering.

1. Does USB modem support hi-link mode? If yes, please switch to this mode.

2. When connecting USB modem to a laptop, is its connection protocol RMDIS?
   For Windows, you can check the network interface through this interface:
   

   

[Barometer]

Hope this helps

[bruce]

The dongle does not reply to the dhcp offer IP initiated by the router.
However, if dongle is connected to PC, dongle seems to reply to dhcp offer, otherwise the PC cannot access dongle manage UI and Internet.
This seems strange.

You can share AXT1800 with me through GoodCloud, and connected the dongle, I will try to remote check it.
(Unsure definitely be resolved, if I checked that dongle does not reply dhcp offer)

Technical Support via GoodCloud - GL.iNet Router Docs 4

Please PM me the router real MAC address and login Web UI password.

[Barometer]

@Barometer

AXT1800

Done! Let me know if you can access the router

Maybe one more thing to add.

I had a Wireguard LAN2LAN VPN configured. In the config file the interface was still the old IP 192.168.8.1 instead of the 192.168.10.1.

I had the auto VPN connect setting still turned on.

And I could still access the router's admin page using the old 192.168.8.1 and the new 192.168.10.1 IP.

I remove the Wireguard VPN config entirely and restarted the device.

I now cannot access the admin page through 192.168.8.1 anymore, only through 192.168.10.1.

I was hoping this would also solve the issue but unfortunately the USB dongle still can't connect.