I have changed my e3372h from hilink to sitck model,but I can't get it work for my openwrt router
here are my configuration,someone please tell me what's the problem is ? thanks
root@OpenWrt:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r10601-4bd34911bc'
DISTRIB_TARGET='ar71xx/tiny'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r10601-4bd34911bc
Difficult to tell just from LuCI screenshots, but this post might help. Worth checking you've got all the requisite packages installed.
If you still have no luck, check the system log for clues.
thanks
I do install following packages and other extra packages for usb lte modem
usbutils
usb-modeswitch
kmod-usb-net-huawei-cdc-ncm
kmod-usb-net-cdc-ether
comgt-ncm
kmod-usb-serial
kmod-usb-serial-option
kmod-usb-serial-wwan
luci-proto-ncm
I added usename and password,but no effect
someone verified it need not usename and password
Can confirm that the E3372(h) works fine in NCM mode using /dev/ttyUSB0
No need to change anything apart from APN
Firmware 21.329.63.00.541 for those wondering.
TP-Link TL-WDR3600 (ar71xx) running trunk/master
thanks
I'd check the system log and dmesg, in that case. Feel free to post the outputs here; might spot something. Since you have TX bytes being transmitted, I'd say it's failing to obtain a DHCP lease.
#system (I try ifdown lte and ifup lte in the meantime)
Mon Jun 24 01:49:16 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:16 2019 daemon.notice netifd: lte (4438): sending -> AT
Mon Jun 24 01:49:16 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:16 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:16 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:16 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:16 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:16 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:16 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:16 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:16 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:16 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:16 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:16 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:16 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:16 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:16 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:16 2019 daemon.notice netifd: lte (4438): sending -> ATZ
Mon Jun 24 01:49:17 2019 daemon.notice netifd: lte (4438): sending -> ATQ0
Mon Jun 24 01:49:17 2019 daemon.notice netifd: lte (4438): sending -> ATV1
Mon Jun 24 01:49:18 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:18 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:18 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:18 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:18 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:18 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:18 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:18 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:18 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:18 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:18 2019 daemon.notice netifd: lte (4438): sending -> ATE1
Mon Jun 24 01:49:19 2019 daemon.notice netifd: lte (4438): sending -> ATS0=0
Mon Jun 24 01:49:19 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:19 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:19 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:19 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:19 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:19 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:19 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:19 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:19 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:19 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:19 2019 daemon.notice netifd: lte (4438): sending -> AT+CGDCONT=1,"IPV4V6","ctlte"
Mon Jun 24 01:49:20 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:20 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:20 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:20 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:20 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:20 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:20 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:20 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:20 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:20 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:20 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:20 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:20 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:20 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:20 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:20 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:20 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:20 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:20 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:20 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:20 2019 daemon.notice netifd: lte (4438): Configuring modem
Mon Jun 24 01:49:20 2019 daemon.notice netifd: lte (4438): Setting mode
Mon Jun 24 01:49:21 2019 daemon.notice netifd: lte (4438): sending -> AT^SYSCFGEX="030201",3fffffff,2,4,7fffffffffffffff,,
#dmesg
32.955798] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 33.007749] br-lan: port 2(wlan0) entered blocking state
[ 33.013336] br-lan: port 2(wlan0) entered disabled state
[ 33.019219] device wlan0 entered promiscuous mode
[ 34.759433] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 34.766317] br-lan: port 2(wlan0) entered blocking state
[ 34.771813] br-lan: port 2(wlan0) entered forwarding state
[ 34.815929] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 70.591449] random: crng init done
[ 70.594987] random: 6 urandom warning(s) missed due to ratelimiting
[ 157.182197] usb 1-1: new high-speed USB device number 2 using ehci-platform
[ 157.937863] usb 1-1: USB disconnect, device number 2
[ 158.722247] usb 1-1: new high-speed USB device number 3 using ehci-platform
[ 159.024776] option 1-1:1.0: GSM modem (1-port) converter detected
[ 159.031553] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[ 159.039372] option 1-1:1.1: GSM modem (1-port) converter detected
[ 159.046125] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[ 159.269039] huawei_cdc_ncm 1-1:1.2: MAC-Address: 00:1e:10:1f:00:00
[ 159.275583] huawei_cdc_ncm 1-1:1.2: setting rx_max = 16384
[ 159.304576] huawei_cdc_ncm 1-1:1.2: NDP will be placed at end of frame for this device.
[ 159.313414] huawei_cdc_ncm 1-1:1.2: cdc-wdm0: USB WDM device
[ 159.320471] huawei_cdc_ncm 1-1:1.2 wwan0: register 'huawei_cdc_ncm' at usb-ehci-platform-1, Huawei CDC NCM device, 00:1e:10:1f:00:00
thanks
Mon Jun 24 01:49:16 2019 daemon.warn cdns[1742]: No valid DNS resolver available
Mon Jun 24 01:49:16 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:16 2019 chinadns.c:613 sendto: Network unreachable
Mon Jun 24 01:49:16 2019 daemon.err chinadns[1743]: Mon Jun 24 01:49:16 2019 chinadns.c:613 sendto: Network unreachable
there we go.
Can you establish a connection if you plug the modem directly into a computer?
1 Like
I can establish a connection by hilink mode before,but now I don't know how to get it work on pc
by the way the simcard should be ok,because I have another simcard and the testing result is same
here are screenshoots when I plug it to win7 x64,it's weird,no signal but have simcard infomation,the simcard is ok.
I wonder whether it's the sitcick fw version problem,because everything is ok when I flash it back to hilink model
any advice will be appreciated
thanks
I think we've determined it's not a hardware problem. We see TX bytes being sent, and from your system log, it looks like the net interfaces are driven by the Linux huawei_cdc_ncm driver. We can also see your modem attempting to communicate. If you want to rule that out completely, you should:
check the firmware version (needs to be 21.xxx.xx.xx.xx);
run lsusb
on your router and check for USB ID 12d1:1506
Check the current mode by sending the AT command AT^SETPORT?
. You'll be looking for mode 16 for NCM and 1 for 3G
I do rather suspect it's a config problem, though. I've had similar problems, and I've first tried to get it working attached to my computer which is why I suggested that. A search of the internet should help if you're not sure how.
Finally, you could try getting it to work in 3G mode first, and then trying NCM. E.g.:
config interface 'modem_1_1'
option ifname '3g-modem'
option service 'umts'
option apn 'ctlte'
option proto '3g'
option device '/dev/ttyUSB1'
option dialnumber '*99#'
option metric '40'
option disabled '0'
See https://openwrt.org/docs/guide-user/network/wan/wan_interface_protocols for other options, in this case.
ok,I will try it later
thank you very much
after flash a new version of stick for my e3372-607,now it can be established a connection with apn "ctlte"
but it still can't work on my openwrt router
It also appears you haven't placed these Interfaces into a firewall zone.
I tried it,it does't work on my e3372-607
but my another cheap qualcomm mdm9600 usb modem works with proto "3g-wan "
thank you
I know but it should connect successfully at least
Possibly a long-shot, but try adding the dialnum
option to the interface; i.e:
config interface 'LTE'
option mode 'preferlte'
option apn 'ctlte'
option dialnum '*99#'
option proto 'ncm'
option ifname 'wwan0'
option device '/dev/ttyUSB0'
option ipv6 'auto'
option metric '40'
option delegate '0'
option disabled '0'
you might also add option delay '30'
, but I don't think it's really necessary with the E3372.
After you made any edits, make sure to do:
uci commit /etc/config/network
service network restart
2 Likes
it's working now !
thank you very much for your help
1 Like
glad to hear. For what it's worth, I've got a pull request outstanding to add the dialnum
option to LuCI. Hopefully, it'll be approved soon.
system
Closed
July 5, 2019, 10:33am
19
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.