Bug #2038
closed
Some 3G WANs on 2.0.x do not come up on cold boot
0%
Description
When booting a alix 2c3 with a Huawei 3G device the intial device boot will not succeed. A reboot or a saving (any) wan interface will bring it up.
Investigation shows that after boot the device is initialized succesfully, the u3g driver configures it.
Adding sleep 60 as as shell or early shell cmd does not help.
in /var/etc only the mpd.script is generated, the required mpd_op2.conf is not generated untill save on the wan is pressed.
Updated by Seth Mos over 12 years ago
- Subject changed from 3G wan on 2.0 does not come up to 3G wan on 2.0.1 does not come up on cold boot
Updated by Chris Buechler over 12 years ago
- Subject changed from 3G wan on 2.0.1 does not come up on cold boot to Some 3G WANs on 2.0.x do not come up on cold boot
this is driver-specific, or otherwise somehow not universal to all cases. My 4G card comes up fine on 2.0 and 2.0.1 at boot time without touching anything.
Updated by Seth Mos almost 12 years ago
- Status changed from New to Resolved
This turned out to be a specific issue with ZTE modems and pin lock.
I've switched to a huawei modem and found a great page on the Huawei stats interface.
http://www.codeproject.com/Articles/120638/3G-Modem-Internet-Dialer
Updated by Seth Mos almost 12 years ago
Chapter 7.5 of the "HUAWEI UMTS Datacard Modem AT Command Interface Specification" lists the ^MODE messages to determine the network state.
Chapter 7.6 lists the ^RSSI messages
Chapter 7.3 lists the ^SRVSTATE messages, this way out of service or restricted can be handled as well. E.g. a terminated SIM.
Updated by Seth Mos almost 12 years ago
- Status changed from Resolved to New
The ZTE MF190 I have here doesn't like pfSense at all. Although the /dev/cuaU0.2 responds to AT and is willing to work our Chat script doesn't like it.
AT&F&C1&D2E0S0=0M1
Throws a error regardless
- Add manufacturer smarts for the setup and the monitoring of the 3G device. What I made now only works for huawei.
[2.1-DEVELOPMENT][root@leaf.dnsalias.org]/root(12): cu -l /dev/cuaU0.1 Connected ATZ OK AT&F&C1&D2E0S0=0M1 ERROR AT+CPIN? +CPIN: SIM PIN OK
Maybe the extra newline here causes grief when trying to unlock the sim.
Modem responds to ATI
ATI
Manufacturer: ZTE CORPORATION
Model: MF190
Revision: BD_MF190TLF3V1.0.0B04
IMEI: 869123007960800
+GCAP: +CGSM,+DS,+ES
OK
Updated by Seth Mos almost 12 years ago
With includes changes ZTE 3G dongle now comes up correctly.
Rewrote the stats utility to poke at the application port using AT commands, which more sticks are using.
Found a ZTE command set.
http://3g-modem.wetpaint.com/page/ZTE+AT-commands
Doesn't provide all the AT commands for detailed stats.
Updated by Seth Mos almost 12 years ago
Checked in support for the ZTE modem stats.
Should be easier to add new ones now too.
Do note that the ZTE modem will stay in data mode even if mpd is restarted, causing it to become a one time only connection afair.
Updated by Seth Mos almost 12 years ago
Found a generic 3G modem device wader that caters to a lot of existing kit. Biggest drawback is that it's python. Not feeling up for coding that in PHP.
https://github.com/andrewbird/wader/tree/master/plugins/devices
Andrew Bird maintains this device database, not sure what license it entails.
Updated by Christophe Prevotaux almost 10 years ago
Just had this problem with a HUAWEI E1752 on cuaU0.0
running on a :
- 2.1.3-RELEASE (amd64)
- built on Thu May 01 15:52:13 EDT 2014
- FreeBSD 8.3-RELEASE-p16
- CPU Type AMD G-T40E Processor
- 2 CPUs: 1 package(s) x 2 core(s)
- PC Engine APU
- Cold reboot the 3G modem fails to be detected and come up
- Warm reboot the 3G modem shows up just fine and works.
Model: E1752
Revision: 11.126.03.01.314¶
Updated by Christophe Prevotaux almost 10 years ago
Tried now with a ZTE MF668 it does start the u3g fine but it does not get an IP address from the mobile provider.
Updated by Chris Buechler over 9 years ago
- Status changed from New to Closed
This needs to be re-tested from scratch on 2.2 by someone who has the affected hardware. There's a good chance it's fixed in FreeBSD 10.1. I confirmed my Verizon UML290 works fine both after initial configuration, and cold and warm reboots, in 2.2.