It seems that the comgt package does not handle the Huawei 3G USB dongle E176 correctly (and probably other Huawei dongles too). My dongle appears as ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem and 3G/UMTS
connections work well. However, no connection is established if only 2G/GPRS is available: the pppd chat script fails with NO CARRIER although the dongle is registered to the network (via 2G). As outlined in this wiki or this
blog, Huawei chips use the AT^SYSCFG command to set 2G or 3G mode, which is not implemented in comgt at the moment. Thus I wrote a patch for /lib/network/3g.sh which adds support for the "service" option in the network
configuration with Huawei dongles. By default (if no "service" option is specified) also 2G is used when 3G is unavailable. The Huawei dongle is detected analogously to other chips (the output of gcom -d /dev/ttyUSB0 -s
/etc/gcom/getcardinfo.gcom is scanned for huawei).
Some further information: The AT^SYSCFG command seems to be respected only once after the dongle is attached (or after the host is powered up). Resetting the dongle seems to render the serial port unusable in some cases.
However, the patch sets a useful mode by default which should cover most use cases (3G preferred, but 2G allowed) and if 3G-only or 2G-only mode is required the device can be power cycled.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33212 3c298f89-4303-0410-b956-a3cf2f4a3e73
This adds in support for ttyACM devices in the 3g hotplug script.
Signed-off-by: Matthew Eaton <wrt at divinehawk.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@25621 3c298f89-4303-0410-b956-a3cf2f4a3e73
This patch adds a chat script and makes some modifications to
/lib/network/3g.sh to enable seamless use of CDMA/EVDO modems in
addition to the existing GPRS/UMTS support. Modifications to 3g.sh
are:
- Added 'chat' variable to point at the appropriate script
- Added 'evdo' and 'cdma' as acceptable 'service' values, and skip
the whole gcom initialization bit
- Changed pppd connection speed from 460800 to more widely supported
115200; in my experience, this is not your actual connection speed,
but at what speed pppd sends setup commands to the interface.
This kinda eliminates the need for /etc/ppp/3g.connect - I think I've
replaced that functionality, but in a slightly more standardized
method, using the 'connect' variable understood by PPP.
Signed-off-by: RB<aoz.syn@gmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@10347 3c298f89-4303-0410-b956-a3cf2f4a3e73
