LTE-Modem Huawei E352
-
Could be a different firmware version
Good point, worth to check. As I recall it was 2 different hw mods of E352, each with it's own fw.
-
What I've noticed though: This time I get a response from cuaU0.2 instead of 0.0
I've changed to that, tried, same error.
It's literally the exact same hardware.Could be a different firmware version but it's probably configured with a different composition, the modem port listed in a different order. Try running at the responding prompt:
at^setport?
Some useful info on that in Andrewz's post he linked earlier.
Steve
Sadly "AT^SETPORT?" gives me bad English. "COMMAND NOT SUPPORT"
CuaU0.2 leaves the following messages from time to time:
^RSSI: 2
^RSSI: 3
^RSSI: 6
^RSSI: 2
^RSSI: 5I take it that's normal? So it does do something. Sadly, I don't understand what.
Seems like it changed the channel a few times, but I'm not getting anything else.EDIT01:
Ok it does not seem to be the string. If I copy the Init String, i get an "OK" as response. Nothing after that, but I'd consider "OK" an acceptable response.EDIT02:
Just checked /boot/loader.conf, because it kept telling me an error to accept some Intel license agreement (in dmesg).
There I found something that seemed off to me..hw.usb.no_pf="1"
Might that have anything to do with it? (The second pfsense has the same entry though)
EDIT03:
I just realized something. I figured both sticks are the same. They are not. I'll admit I've never looked that closely, but since there is no sticker on it, it took me until now to realize:
I ran an ATI - Modem: Huawei E122
Revision: 11.009.02.00.55
So it is a different model altogether. Does that change anything?
EDIT04:
I've checked the second computer again. Here's what I noticed/what struck me as odd:ugen0.2: <hua wei="" huawei="" mobile=""> at usbus0 u3g0 on uhub0 u3g0: <3G Modem> on usbus0 u3g0: Found 3 ports. umass0 on uhub0 umass0: <usb mass="" storage=""> on usbus0 umass1 on uhub0 umass1: <usb mass="" storage=""> on usbus0 ugen0.3: <vendor 0x1a40="" usb="" 2.0="" hub=""> at usbus0 uhub1 on uhub0 cd0 at umass-sim0 bus 0 scbus2 target 0 lun 0 cd0: <huawei mass="" storage="" 2.31=""> Removable CD-ROM SCSI-2 device cd0: 40.000MB/s transfers cd0: 29MB (15222 2048 byte sectors) cd0: quirks=0x10<10_BYTE_ONLY> da0 at umass-sim1 bus 1 scbus3 target 0 lun 0 da0: <huawei sd="" storage="" 2.31=""> Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da0: quirks=0x2 <no_6_byte>ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 (disconnected) ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 (disconnected) ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 (disconnected) ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 (disconnected) ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 (disconnected) ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 ugen0.5: <vendor 0x8087="" product="" 0x07dc=""> at usbus0 (disconnected) ng0: changing name to 'ppp0' ng0: changing name to 'ppp0' ng0: changing name to 'ppp0' ng0: changing name to 'ppp0'</vendor></vendor></vendor></vendor></vendor></vendor></vendor></vendor></vendor></vendor></vendor></vendor></no_6_byte></huawei></huawei></vendor></usb></usb></hua>
- It would seem that stick is recognized as modem, mass storage and disk drive.
- ugen0.5 looks like it keeps connecting and then disconnecting again
- Whatever ng0 is, apparently it keeps changing the name to ppp0 about 15 times in the output.
-
OK, let me answer some of your questions.
E122 should generally work. ^SETPORT is not available in the older models, so try AT^U2DIAG? and AT^U2DIAG=?
Otherwise you can try installing usb_modeswitch.
^RSSI: 2, etc is absolutely normal, this is how signal level is reported, it should be a command to switch this off.
ng0: changing name to 'ppp0' is normal as well, but this should occur only once.
Frequent disconnects are usually related to power issues and/or bad cables. Try to use relatively short USB extension cable, 15-20 cm if you have one; plugging the modem into the USB port directly is not always the best choice. -
Both give me an error, sadly.
The setup is basically this:
PC - NIC01 - WAN
- NIC02 - LAN - SWITCH
- USB01 - Huawei E122 - so, yes it is connected directly.
besides Power and a KVM switch (USB), nothing else is connected.What would you recommend otherwise? Trying a different USB port?
EDIT01:
Wait.. hang on.. if I copy it instead of typing it, "AT^U2DIAG?" works.
^U2DIAG: 268 -
^U2DIAG: 268
This means M+CD+SD+UI
modem (M)
NAND-flashmemory drive (CD)
microSD-drive (SD)
PC UI interface (UI)Try AT^U2DIAG=0 to keep modem and PC UI only. Re-insert modem afterwards and see how the ports will be recognized by the OS. Then check which port responds to AT-commands.
If you have a choice - try another USB port.
-
Ok now this is weird.
I've had it working on both machines for a while (changed USB port on the other one and that seemed to work).
Now after a single reboot, it stopped working again.
It went full circle. What is going on?Edit01:
The first one that was working:
cuaU0.0Apr 4 08:32:23 ppp [opt1_link0] LCP: Down event Apr 4 08:32:23 ppp [opt1_link0] Link: DOWN event Apr 4 08:32:23 ppp [opt1_link0] MODEM: chat script failed Apr 4 08:32:23 ppp [opt1_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label. Apr 4 08:32:10 ppp [opt1_link0] Link: reconnection attempt 1
cuaU0.1
Apr 4 08:35:53 ppp [opt1_link0] Link: reconnection attempt 1 in 3 seconds Apr 4 08:35:53 ppp [opt1_link0] LCP: Down event Apr 4 08:35:53 ppp [opt1_link0] Link: DOWN event Apr 4 08:35:53 ppp [opt1_link0] MODEM: chat script failed Apr 4 08:35:53 ppp [opt1_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label. Apr 4 08:35:50 php-fpm /interfaces.php: Starting 3gstats.php on device 'cuaU0.2' for interface 'opt1'
- but why cuaU0.2? I just set it to 0.1 ???
cuaU0.2
Apr 4 08:38:17 ppp [opt1_link0] LCP: Down event Apr 4 08:38:17 ppp [opt1_link0] Link: DOWN event Apr 4 08:38:17 ppp [opt1_link0] MODEM: chat script failed Apr 4 08:38:17 ppp [opt1_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label. Apr 4 08:38:16 check_reload_status updating dyndns opt1 Apr 4 08:38:14 check_reload_status Restarting ipsec tunnels Apr 4 08:38:14 php-fpm /interfaces.php: Starting 3gstats.php on device 'cuaU0.2' for interface 'opt1'
It's like the modem just said: "No. I don't want to any more." and quit.
I'm going to try removing and reconfiguring the PPP settings, but I fear that might not solve the issue.
Edit02:
I don't quite understand why the log says "0.2" on all three of them. Fact is, I've tried all three and none of them want to connect anymore.
I'll try again via SSH if I can get any response from AT, but I'd really appreciate some help understanding this weird behaviour.Edit03:
cu -s 115200 -l cuaU0.0 - Connected, then does not react to anything, not even ~. cu -s 115200 -l cuaU0.1 - Connected, does not react to AT, but reacts to ~. cu -s 115200 -l cuaU0.2 - not Connected, I can type just about anything, but it's going nowhere.
Edit04:
After 8-10 minutes I got a response on cuaU0.2: "unsupported speed 115200"
What on earth broke to cause this? -
Ok so a second reboot and reconfiguration fixed it for #1.
The second one spits out this:
Apr 4 23:45:15 ppp process 87668 terminated Apr 4 23:45:15 ppp [opt2_link0] Link: Shutdown Apr 4 23:45:15 ppp [opt2] Bundle: Shutdown Apr 4 23:45:14 ppp waiting for process 87668 to die... Apr 4 23:45:13 ppp [opt2] IPV6CP: Close event Apr 4 23:45:13 ppp [opt2] IPCP: Close event Apr 4 23:45:13 ppp [opt2] IFACE: Close event Apr 4 23:45:13 ppp caught fatal signal TERM Apr 4 23:45:13 ppp waiting for process 87668 to die... Apr 4 23:45:12 ppp [opt2_link0] CHAT: Detected Custom modem. Apr 4 23:45:12 ppp [opt2_link0] LCP: LayerStart Apr 4 23:45:12 ppp [opt2_link0] LCP: state change Initial --> Starting Apr 4 23:45:12 ppp [opt2_link0] LCP: Open event Apr 4 23:45:12 ppp [opt2_link0] Link: OPEN event Apr 4 23:45:12 ppp [opt2] Bundle: Interface ng0 created Apr 4 23:45:12 ppp web: web is not running Apr 4 23:45:12 ppp process 77865 terminated Apr 4 23:45:12 ppp [opt2_link0] Link: Shutdown Apr 4 23:45:12 ppp waiting for process 77865 to die... Apr 4 23:45:12 ppp [opt2] Bundle: Shutdown Apr 4 23:45:11 ppp [opt2_link0] LCP: Down event Apr 4 23:45:11 ppp [opt2_link0] LCP: LayerFinish Apr 4 23:45:11 ppp [opt2_link0] LCP: state change Starting --> Initial Apr 4 23:45:11 ppp [opt2_link0] LCP: Close event Apr 4 23:45:11 ppp [opt2_link0] Link: giving up after 10 reconnection attempts Apr 4 23:45:11 ppp [opt2_link0] Link: DOWN event Apr 4 23:45:11 ppp [opt2_link0] MODEM: chat script failed Apr 4 23:45:11 ppp [opt2_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label. Apr 4 23:45:11 ppp waiting for process 77865 to die... Apr 4 23:45:11 ppp process 87668 started, version 5.8 (nobody@pfSense_v2_4_1_amd64-pfSense_v2_4_1-job-01 16:32 21-Oct-2017)
-
Hi All,
I am using Pfsense 2.4.3 on protectli volte FW 10001. It has one SIM slot. I inserted the sim to it.. but it is not recognizing it. following are the dmsg logs.
ng0: changing name to 'ppp0'
em0: link state changed to UP
em1: link state changed to UP
pflog0: promiscuous mode enabled
ng0: changing name to 'ppp0'
ng0: changing name to 'ppp0'
ng0: changing name to 'ppp0'
ng0: changing name to 'ppp0'
ng0: changing name to 'ppp0'
ng0: changing name to 'ppp0'
ng0: changing name to 'ppp0'
ng0: changing name to 'ppp0'
ng0: changing name to 'ppp0'
ng0: changing name to 'ppp0'and PPP logs are below
pr 9 17:36:02 ppp waiting for process 41396 to die…
Apr 9 17:36:02 ppp [opt1] Bundle: Shutdown
Apr 9 17:36:02 ppp [opt1_link0] Link: Shutdown
Apr 9 17:36:02 ppp process 41396 terminated
Apr 9 17:36:03 ppp web: web is not running
Apr 9 17:36:03 ppp [opt1] Bundle: Interface ng0 created
Apr 9 17:36:03 ppp [opt1_link0] Link: OPEN event
Apr 9 17:36:03 ppp [opt1_link0] LCP: Open event
Apr 9 17:36:03 ppp [opt1_link0] LCP: state change Initial –> Starting
Apr 9 17:36:03 ppp [opt1_link0] LCP: LayerStart
Apr 9 17:36:16 ppp [opt1_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label.
Apr 9 17:36:16 ppp [opt1_link0] MODEM: chat script failed
Apr 9 17:36:17 ppp [opt1_link0] Link: DOWN event
Apr 9 17:36:17 ppp [opt1_link0] LCP: Down event
Apr 9 17:36:17 ppp [opt1_link0] Link: reconnection attempt 1 in 3 seconds
Apr 9 17:36:21 ppp [opt1_link0] Link: reconnection attempt 1
Apr 9 17:36:34 ppp [opt1_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label.
Apr 9 17:36:34 ppp [opt1_link0] MODEM: chat script failed
Apr 9 17:36:35 ppp [opt1_link0] Link: DOWN event
Apr 9 17:36:35 ppp [opt1_link0] LCP: Down event
Apr 9 17:36:35 ppp [opt1_link0] Link: reconnection attempt 2 in 1 seconds
Apr 9 17:36:37 ppp [opt1_link0] Link: reconnection attempt 2
Apr 9 17:36:52 ppp [opt1_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label.
Apr 9 17:36:52 ppp [opt1_link0] MODEM: chat script failed
Apr 9 17:36:53 ppp [opt1_link0] Link: DOWN event
Apr 9 17:36:53 ppp [opt1_link0] LCP: Down event
Apr 9 17:36:53 ppp [opt1_link0] Link: reconnection attempt 3 in 4 seconds
Apr 9 17:36:58 ppp [opt1_link0] Link: reconnection attempt 3
Apr 9 17:37:00 ppp Multi-link PPP daemon for FreeBSD
Apr 9 17:37:00 ppp process 81036 started, version 5.8 (nobody@pfSense_v2_4_2_amd64-pfSense_v2_4_2-job-14 18:47 16-Nov-2017)
Apr 9 17:37:00 ppp waiting for process 9503 to die…
Apr 9 17:37:00 ppp caught fatal signal TERM
Apr 9 17:37:00 ppp [opt1] IFACE: Close event
Apr 9 17:37:00 ppp [opt1] IPCP: Close event
Apr 9 17:37:00 ppp [opt1] IPV6CP: Close event
Apr 9 17:37:01 ppp waiting for process 9503 to die…
Apr 9 17:37:02 ppp [opt1] Bundle: Shutdown
Apr 9 17:37:02 ppp [opt1_link0] Link: Shutdown
Apr 9 17:37:02 ppp process 9503 terminated
Apr 9 17:37:02 ppp web: web is not running
Apr 9 17:37:02 ppp [opt1] Bundle: Interface ng0 created
Apr 9 17:37:02 ppp [opt1_link0] Link: OPEN event
Apr 9 17:37:02 ppp [opt1_link0] LCP: Open event
Apr 9 17:37:02 ppp [opt1_link0] LCP: state change Initial –> Starting
Apr 9 17:37:02 ppp [opt1_link0] LCP: LayerStart
Apr 9 17:37:02 ppp [opt1_link0] uu_lock(cuau0): device in use
Apr 9 17:37:02 ppp [opt1_link0] MODEM: Fail to open serial port /dev/cuau0 on speed 115200
Apr 9 17:37:02 ppp [opt1_link0] Link: DOWN event
Apr 9 17:37:02 ppp [opt1_link0] LCP: Down event
Apr 9 17:37:02 ppp [opt1_link0] Link: reconnection attempt 1 in 4 secondsAny help please.
-
Are you also using a Huawei E352? Otherwise this should be in a new thread.
It seems likely you are not using that since that has it's own SIM slot. In which case what modem hardware are you using?
Also we are not Protectli support. If you are having a hardware issue with something they supplied you should ask them directly.
Steve
-
Out of curiosity, what does your Init-String look like?
Something along these lines?
AT&F&C1&D2E0S0=0M1
Because according to the information given to me:
M0 or M Speaker off, completely silent during dialing M3 is also common, but different on many brands M1 Speaker on until remote carrier detected (i.e. until the other modem is heard) M2 Speaker always on (data sounds are heard after CONNECT)
Removing the M1 at the end fixed it for me.