Modify

Opened 8 years ago

Last modified 4 years ago

#819 investigate enhancement

Support 3G dongle: ZTE AC2726

Reported by: amanullang@… Owned by: matthijs
Priority: normal Milestone:
Component: fon-network-3g Version: N/A
Severity: unknown
Cc: Hardware: both

Description

please help me....very2 stressful.can't connect my ZTE AC2726 evdo modem..i had try all the configuration.

from root@fonera (Putty)

cat /proc/bus/usb/devices

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=19d2 ProdID=fff1 Rev= 0.00
S:  Manufacturer=ZTE, Incorporated
S:  Product=ZTE CDMA Tech
C:* #Ifs= 6 Cfg#= 1 Atr=a0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=128ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=84(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=87(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=07(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=88(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=08(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=86(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=06(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 5 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=89(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=0a(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms

Apps/umtsd.lua

config 'umtsdevice' 'option19D2FFF5'
	option 'data' '/dev/ttyUSB0'
	option 'cmd' '/dev/ttyUSB0'
	option 'vendor' 'ZTE'
	option 'model' 'AC2726'

umtsd.lua

-- some dummy data
local model
local vendor

local data = "/dev/ttyUSB0"
local cmd = "/dev/ttyUSB0"

and

	local f = io.open("/tmp/chat_umts", "w")
	if f then
		f:write("ABORT \"NO CARRIER\"\n"..
			"ABORT \"NO DIALTONE\"\n"..
			"ABORT \"ERROR\"\n"..
			"ABORT \"NO ANSWER\"\n"..
			"ABORT \"BUSY\"\n"..
			"\"\" \"ATZ\"\n"..
			"OK \"ATH\"\n"..
			"OK AT+CGDCONT=1,\"IP\",\""..apn.."\"\n"..
			"OK \"ATD#777\"\n"..
			"\"CONNECT\" \"\"")
		f:close()
		service:start(unpack(params))
		if service:status() == true then
			return ONLINE
		end

this is the logread

root@Fonera:~# logread
Feb 17 13:04:06 Fonera user.debug kernel: option 1-1:1.2: usb_probe_interface
Feb 17 13:04:06 Fonera user.debug kernel: option 1-1:1.2: usb_probe_interface - got id
Feb 17 13:04:06 Fonera user.info kernel: option 1-1:1.2: GSM modem (1-port) converter detected
Feb 17 13:04:06 Fonera user.info kernel: usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
Feb 17 13:04:06 Fonera user.warn kernel: ttyusb -> 1 ttyUSB2 option 19D2FFF1
Feb 17 13:04:06 Fonera user.debug kernel: option 1-1:1.3: usb_probe_interface
Feb 17 13:04:06 Fonera user.debug kernel: option 1-1:1.3: usb_probe_interface - got id
Feb 17 13:04:06 Fonera user.info kernel: option 1-1:1.3: GSM modem (1-port) converter detected
Feb 17 13:04:06 Fonera user.info kernel: usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
Feb 17 13:04:06 Fonera user.warn kernel: ttyusb -> 1 ttyUSB3 option 19D2FFF1
Feb 17 13:04:06 Fonera user.debug kernel: option 1-1:1.4: usb_probe_interface
Feb 17 13:04:06 Fonera user.debug kernel: option 1-1:1.4: usb_probe_interface - got id
Feb 17 13:04:06 Fonera user.info kernel: option 1-1:1.4: GSM modem (1-port) converter detected
Feb 17 13:04:06 Fonera user.info kernel: usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
Feb 17 13:04:06 Fonera user.warn kernel: ttyusb -> 1 ttyUSB4 option 19D2FFF1
Feb 17 13:04:06 Fonera user.info kernel: usbcore: registered new interface driver option
Feb 17 13:04:06 Fonera user.info kernel: drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.2
Feb 17 13:04:06 Fonera user.debug kernel: eth0.2: add 01:00:5e:00:00:01 mcast address to master interface
Feb 17 13:04:06 Fonera user.info kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB modem (1 port)
Feb 17 13:04:06 Fonera user.info kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB modem (3 port)
Feb 17 13:04:06 Fonera user.info kernel: usbcore: registered new interface driver sierra
Feb 17 13:04:06 Fonera user.info kernel: drivers/usb/serial/sierra.c: USB Driver for Sierra Wireless USB modems: v.1.0.6
Feb 17 13:04:06 Fonera user.debug kernel: eth0.2: del 01:00:5e:00:00:01 mcast address from vlan interface
Feb 17 13:04:06 Fonera user.debug kernel: eth0.2: del 01:00:5e:00:00:01 mcast address from master interface
Feb 17 13:04:06 Fonera user.warn kernel: fuse init (API version 7.8)
Feb 17 13:04:06 Fonera user.warn kernel: fuse distribution version: 2.7.3
Feb 17 13:04:06 Fonera user.info kernel: usbcore: registered new interface driver uvcvideo
Feb 17 13:04:06 Fonera user.info kernel: USB Video Class driver (SVN r215)
Feb 17 13:04:06 Fonera user.debug kernel: eth0.1: add 01:00:5e:00:00:01 mcast address to master interface
Feb 17 13:04:07 Fonera user.info kernel: eth0.1: dev_set_promiscuity(master, 1)
Feb 17 13:04:07 Fonera user.info kernel: device eth0 entered promiscuous mode
Feb 17 13:04:07 Fonera user.info kernel: device eth0.1 entered promiscuous mode
Feb 17 13:04:07 Fonera user.info kernel: br-lan: port 1(eth0.1) entering learning state
Feb 17 13:04:07 Fonera user.info kernel: br-lan: topology change detected, propagating
Feb 17 13:04:07 Fonera user.info kernel: br-lan: port 1(eth0.1) entering forwarding state
Feb 17 13:04:07 Fonera user.notice root: serial is SVloKVT6YZ
Feb 17 13:04:07 Fonera user.emerg syslog: 3g hotplug
Feb 17 13:04:07 Fonera user.emerg syslog: 19d2:fff1 /etc/usb_modeswitch/19d2:fff1
Feb 17 13:04:07 Fonera user.emerg syslog: starting usb_modeswitch
Feb 17 13:04:07 Fonera user.emerg syslog: 3g hotplug
Feb 17 13:04:07 Fonera user.info : Looking for target devices ...
Feb 17 13:04:07 Fonera user.info :  No devices in target mode or class found
Feb 17 13:04:07 Fonera user.info : Looking for default devices ...
Feb 17 13:04:07 Fonera user.info :  No default device found. Is it connected? Bye.
Feb 17 13:04:08 Fonera user.emerg syslog: 3g hotplug
Feb 17 13:04:08 Fonera user.emerg syslog: 3g hotplug
Feb 17 13:04:08 Fonera user.emerg syslog: 3g hotplug
Feb 17 13:04:08 Fonera user.emerg syslog: 3g hotplug
Feb 17 13:04:08 Fonera user.emerg syslog: 3g hotplug
Feb 17 13:04:09 Fonera user.info : ifconfig: SIOCGIFFLAGS: No such device
Feb 17 13:04:09 Fonera user.info : rt3052(rt3052): disable failed
Feb 17 13:04:09 Fonera user.info : sh: auto: bad number
Feb 17 13:04:09 Fonera user.info : ifconfig: down: error fetching interface information: Device not found
Feb 17 13:04:09 Fonera user.info : ifconfig: down: error fetching interface information: Device not found
Feb 17 13:04:09 Fonera user.warn kernel: RX DESC a35e1000  size = 2048
Feb 17 13:04:09 Fonera user.warn kernel: <-- RTMPAllocTxRxRingMemory, Status=0
Feb 17 13:04:09 Fonera user.warn kernel: Key1Str is Invalid key length(0) or Type(0)
Feb 17 13:04:09 Fonera user.warn kernel: Key1Str is Invalid key length(0) or Type(0)
Feb 17 13:04:09 Fonera user.warn kernel: Key2Str is Invalid key length(0) or Type(0)
Feb 17 13:04:09 Fonera user.warn kernel: Key2Str is Invalid key length(0) or Type(0)
Feb 17 13:04:09 Fonera user.warn kernel: Key3Str is Invalid key length(0) or Type(0)
Feb 17 13:04:09 Fonera user.warn kernel: Key3Str is Invalid key length(0) or Type(0)
Feb 17 13:04:09 Fonera user.warn kernel: Key4Str is Invalid key length(0) or Type(0)
Feb 17 13:04:09 Fonera user.warn kernel: Key4Str is Invalid key length(0) or Type(0)
Feb 17 13:04:09 Fonera user.warn kernel: 1. Phy Mode = 9
Feb 17 13:04:09 Fonera user.warn kernel: 2. Phy Mode = 9
Feb 17 13:04:09 Fonera user.warn kernel: 3. Phy Mode = 9
Feb 17 13:04:09 Fonera user.warn kernel: RTMPSetPhyMode: channel is out of range, use first channel=0
Feb 17 13:04:09 Fonera user.warn kernel: MCS Set = ff ff 00 00 01
Feb 17 13:04:09 Fonera user.warn kernel: SYNC - BBP R4 to 20MHz.l
Feb 17 13:04:09 Fonera user.warn kernel: SYNC - BBP R4 to 20MHz.l
Feb 17 13:04:09 Fonera user.warn kernel: SYNC - BBP R4 to 20MHz.l
Feb 17 13:04:09 Fonera user.warn kernel: SYNC - BBP R4 to 20MHz.l
Feb 17 13:04:10 Fonera user.warn kernel: SYNC - BBP R4 to 20MHz.l
Feb 17 13:04:10 Fonera user.notice kernel: scsi 0:0:0:0: Direct-Access     ZTE      USB Storage FFF1 2.31 PQ: 0 ANSI: 2
Feb 17 13:04:10 Fonera user.notice kernel: sd 0:0:0:0: Attached scsi removable disk sda
Feb 17 13:04:10 Fonera user.debug kernel: usb-storage: device scan complete
Feb 17 13:04:10 Fonera user.warn kernel: SYNC - BBP R4 to 20MHz.l
Feb 17 13:04:10 Fonera user.warn kernel: SYNC - BBP R4 to 20MHz.l
Feb 17 13:04:11 Fonera user.warn kernel: SYNC - BBP R4 to 20MHz.l
Feb 17 13:04:11 Fonera user.warn kernel: SYNC - BBP R4 to 20MHz.l
Feb 17 13:04:11 Fonera user.warn kernel: SYNC - BBP R4 to 20MHz.l
Feb 17 13:04:12 Fonera user.warn kernel: SYNC - BBP R4 to 20MHz.l
Feb 17 13:04:12 Fonera user.warn kernel: Main bssid = 00:18:84:88:fd:64
Feb 17 13:04:12 Fonera user.warn kernel: <==== rt28xx_init, Status=0
Feb 17 13:04:12 Fonera user.warn kernel: 0x1300 = 00064320
Feb 17 13:04:12 Fonera user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Feb 17 13:04:13 Fonera user.info kernel: br-lan: port 1(eth0.1) entering learning state
Feb 17 13:04:13 Fonera user.info kernel: br-lan: topology change detected, propagating
Feb 17 13:04:13 Fonera user.info kernel: br-lan: port 1(eth0.1) entering forwarding state
Feb 17 13:04:14 Fonera user.info kernel: device ra0 entered promiscuous mode
Feb 17 13:04:14 Fonera user.info kernel: br-lan: port 2(ra0) entering learning state
Feb 17 13:04:14 Fonera user.info kernel: br-lan: topology change detected, propagating
Feb 17 13:04:14 Fonera user.info kernel: br-lan: port 2(ra0) entering forwarding state
Feb 17 13:04:14 Fonera user.info : ifconfig ra1 down
Feb 17 13:04:15 Fonera user.info : Loading defaults
Feb 17 13:04:15 Fonera user.info : Loading synflood protection
Feb 17 13:04:15 Fonera user.info : Adding custom chains
Feb 17 13:04:16 Fonera user.info : Loading zones
Feb 17 13:04:16 Fonera user.info : iptables: Chain already exists
Feb 17 13:04:16 Fonera user.info : iptables: Chain already exists
Feb 17 13:04:16 Fonera user.info : iptables: Chain already exists
Feb 17 13:04:16 Fonera user.info : iptables: Chain already exists
Feb 17 13:04:16 Fonera user.info : iptables: Chain already exists
Feb 17 13:04:16 Fonera user.info : iptables: Chain already exists
Feb 17 13:04:16 Fonera user.info : Loading rules
Feb 17 13:04:16 Fonera user.info : Loading forwarding
Feb 17 13:04:16 Fonera user.info : Loading redirects
Feb 17 13:04:16 Fonera user.info : Loading includes
Feb 17 13:04:16 Fonera user.info :    /etc/firewall.fon
Feb 17 13:04:16 Fonera user.info :    FWallFON
Feb 17 13:04:17 Fonera user.info :    FWallDaemon
Feb 17 13:04:17 Fonera user.info : killall: chilli: no process killed
Feb 17 13:04:17 Fonera user.notice root: adding br-lan to firewall zone lan
Feb 17 13:04:18 Fonera user.notice root: adding tun-ovpn to firewall zone vpn
Feb 17 13:04:18 Fonera daemon.info avahi-daemon[1508]: Found user 'nobody' (UID 65534) and group 'nogroup' (GID 65534).
Feb 17 13:04:18 Fonera daemon.info avahi-daemon[1508]: Successfully dropped root privileges.
Feb 17 13:04:18 Fonera daemon.info avahi-daemon[1508]: avahi-daemon 0.6.25 starting up.
Feb 17 13:04:18 Fonera daemon.warn avahi-daemon[1508]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Feb 17 13:04:18 Fonera daemon.warn avahi-daemon[1508]: Failed to open /etc/resolv.conf: No such file or directory
Feb 17 13:04:18 Fonera daemon.info avahi-daemon[1508]: No service file found in /tmp/mdns/.
Feb 17 13:04:18 Fonera daemon.info avahi-daemon[1508]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.10.1.
Feb 17 13:04:18 Fonera daemon.info avahi-daemon[1508]: New relevant interface br-lan.IPv4 for mDNS.
Feb 17 13:04:18 Fonera daemon.info avahi-daemon[1508]: Network interface enumeration completed.
Feb 17 13:04:18 Fonera daemon.info avahi-daemon[1508]: Registering new address record for 192.168.10.1 on br-lan.IPv4.
Feb 17 13:04:18 Fonera daemon.info avahi-daemon[1508]: Registering HINFO record with values 'MIPS'/'LINUX'.
Feb 17 13:04:19 Fonera user.notice root: setting up led : powerg
Feb 17 13:04:19 Fonera daemon.info avahi-daemon[1508]: Server startup complete. Host name is Fonera.local. Local service cookie is 747774664.
Feb 17 13:04:19 Fonera user.notice root: setting up led : wifi
Feb 17 13:04:19 Fonera user.crit syslog: fonstated - v2.0
Feb 17 13:04:19 Fonera user.crit fonstated: loaded fontimer for "/bin/thinclient dummy" period=17280
Feb 17 13:04:19 Fonera user.crit fonstated: loaded fontimer for "/etc/fonstated/RestartNtpclient" period=17280
Feb 17 13:04:19 Fonera user.crit fonstated: loaded fontimer for "/etc/init.d/fonsmcd" period=12
Feb 17 13:04:19 Fonera user.crit fonstated: loaded fontimer for "/etc/fonstated/StartHttpd" period=2150
Feb 17 13:04:19 Fonera user.crit fonstated: starting chillispot fonstate plugin
Feb 17 13:04:19 Fonera user.crit fonstated: added fontimer libcallback period=60
Feb 17 13:04:19 Fonera user.crit fonstated: added fontimer libcallback period=17280
Feb 17 13:04:19 Fonera user.crit fonstated: added fonevent hotspot_decount -> libcallback 1
Feb 17 13:04:19 Fonera user.crit fonstated: added fonevent hotspot_inccount -> libcallback 1
Feb 17 13:04:19 Fonera user.crit fonstated: added fonevent hotspot_resetcount -> libcallback 1
Feb 17 13:04:19 Fonera user.crit fonstated: added fonevent hotspot_wdt_start -> libcallback 1
Feb 17 13:04:19 Fonera user.crit fonstated: added fonevent hotspot_wdt_stop -> libcallback 1
Feb 17 13:04:19 Fonera user.crit fonstated: enqueue --> UMTS
Feb 17 13:04:19 Fonera user.crit fonstated: enqueue --> SetupHosts
Feb 17 13:04:19 Fonera user.crit fonstated: enqueue --> BootServices
Feb 17 13:04:19 Fonera user.crit fonstated: enqueue --> FWallDaemon
Feb 17 13:04:19 Fonera user.crit fonstated: enqueue --> StartTorrent
Feb 17 13:04:19 Fonera user.crit fonstated: running event /etc/fonstated/UMTS
Feb 17 13:04:20 Fonera user.notice root: runnow --> /etc/fonstated/ConfigFON
Feb 17 13:04:21 Fonera user.notice root: runnow --> /etc/fonstated/ConfigWan
Feb 17 13:04:22 Fonera user.notice root: scan_umts
Feb 17 13:04:22 Fonera user.notice root: scan_umts
Feb 17 13:04:22 Fonera user.crit fonstated: finished running /etc/fonstated/UMTS
Feb 17 13:04:22 Fonera user.crit fonstated: running event /etc/fonstated/SetupHosts
Feb 17 13:04:22 Fonera user.crit fonstated: finished running /etc/fonstated/SetupHosts
Feb 17 13:04:22 Fonera user.crit fonstated: running event /etc/fonstated/BootServices
Feb 17 13:04:22 Fonera user.notice root: scan_umts
Feb 17 13:04:22 Fonera user.notice root: runnow --> /etc/fonstated/Redirect
Feb 17 13:04:23 Fonera user.notice root: runnow --> /etc/fonstated/StartFonsmcd
Feb 17 13:04:23 Fonera user.notice root: runnow --> /etc/fonstated/RestartMountd
Feb 17 13:04:23 Fonera user.notice root: runnow --> /etc/fonstated/StartHttpd
Feb 17 13:04:23 Fonera user.crit mountd[1882]: Starting OpenWrt (auto)mountd V1
Feb 17 13:04:24 Fonera user.crit mountd[1882]: trying to mount /tmp/run/mountd/ as the autofs root
Feb 17 13:04:24 Fonera user.crit fonstated: finished running /etc/fonstated/BootServices
Feb 17 13:04:24 Fonera user.crit fonstated: running event /etc/fonstated/FWallDaemon
Feb 17 13:04:24 Fonera user.notice root: runnow --> /etc/fonstated/SetupDlmd
Feb 17 13:04:25 Fonera authpriv.info dropbear[1919]: Not backgrounding
Feb 17 13:04:25 Fonera user.crit fonstated: finished running /etc/fonstated/FWallDaemon
Feb 17 13:04:25 Fonera user.crit fonstated: running event /etc/fonstated/StartTorrent
Feb 17 13:04:25 Fonera user.crit fonstated: finished running /etc/fonstated/StartTorrent
Feb 17 13:04:25 Fonera user.emerg syslog: starting onlined
Feb 17 13:04:25 Fonera daemon.info avahi-daemon[1508]: Got SIGHUP, reloading.
Feb 17 13:04:25 Fonera daemon.info avahi-daemon[1508]: Loading service file /tmp/mdns//smb.service.
Feb 17 13:04:25 Fonera daemon.warn avahi-daemon[1508]: Failed to open /etc/resolv.conf: No such file or directory
Feb 17 13:04:25 Fonera user.crit fonstated: enqueue --> StartFonsmcd
Feb 17 13:04:25 Fonera user.crit fonstated: running event /etc/fonstated/StartFonsmcd
Feb 17 13:04:25 Fonera user.crit fonstated: finished running /etc/fonstated/StartFonsmcd
Feb 17 13:04:26 Fonera daemon.info avahi-daemon[1508]: Service "LaFonera" (/tmp/mdns//smb.service) successfully established.
Feb 17 13:04:26 Fonera daemon.info avahi-daemon[1508]: Got SIGHUP, reloading.
Feb 17 13:04:26 Fonera daemon.info avahi-daemon[1508]: Loading service file /tmp/mdns//ssh.service.
Feb 17 13:04:26 Fonera daemon.warn avahi-daemon[1508]: Failed to open /etc/resolv.conf: No such file or directory
Feb 17 13:04:26 Fonera user.notice root: runnow --> /etc/fonstated/FWallDaemon
Feb 17 13:04:27 Fonera daemon.info avahi-daemon[1508]: Service "Fonera2.0 SSH" (/tmp/mdns//ssh.service) successfully established.
Feb 17 13:04:28 Fonera daemon.info dnsmasq[2027]: started, version 2.45 cachesize 150
Feb 17 13:04:28 Fonera daemon.info dnsmasq[2027]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
Feb 17 13:04:28 Fonera daemon.info dnsmasq[2027]: DHCP, IP range 192.168.10.100 -- 192.168.10.250, lease time 12h
Feb 17 13:04:28 Fonera user.info syslog: whitelist file: /etc/fon/whitelist.dnsmasq
Feb 17 13:04:28 Fonera daemon.info dnsmasq[2027]: using local addresses only for domain lan
Feb 17 13:04:28 Fonera daemon.warn dnsmasq[2027]: failed to access /tmp/resolv.conf.auto: No such file or directory
Feb 17 13:04:28 Fonera daemon.info dnsmasq[2027]: read /etc/hosts - 2 addresses
Feb 17 13:04:28 Fonera daemon.err dnsmasq[2027]: failed to read /etc/ethers:No such file or directory
Feb 17 13:04:34 Fonera daemon.info fonsmcd[1866]: Sucessfully started
Feb 17 13:04:55 Fonera user.crit fonstated: enqueue --> HotspotStop
Feb 17 13:04:55 Fonera user.crit fonstated: running event /etc/fonstated/HotspotStop
Feb 17 13:04:56 Fonera user.crit fonstated: finished running /etc/fonstated/HotspotStop
Feb 17 13:05:28 Fonera authpriv.info dropbear[3600]: Child connection from 192.168.10.239:1882
Feb 17 13:05:34 Fonera authpriv.notice dropbear[3600]: password auth succeeded for 'root' from 192.168.10.239:1882

Attachments (0)

Change History (23)

comment:1 Changed 8 years ago by matthijs

  • Status changed from new to investigate
  • Summary changed from can't connect my usb modem to ZTE AC2726 3G modem does not work

comment:2 Changed 8 years ago by amanullang@…

sorry,i mean it is an EVDO modem...

comment:3 Changed 8 years ago by matthijs

Hmm, EV-DO seems to be a fancy and new 3G wifi-like protocol I've never heard of so far. Not sure if that changes things, though.

It seems this device needs usb_modeswitch to work, according to http://forums.remote-exploit.org/backtrack-4-working-hardware/23722-dual-mode-usb-modem-storage-modem-like-zte-ac2726-zte-ac8710-other-brand.html

I don't know if that should be configured somewhere explicitely right now.

comment:4 Changed 8 years ago by amanullang@…

i still dont understand with your link...can you teach me step by step?

comment:5 Changed 8 years ago by amanullang@…

i think the problem is not the 3g or evdo.but,the modem is the storage too..

comment:6 Changed 8 years ago by matthijs

Sorry, the link wasn't meant as a howto to get this working, just as a reference to other developers that this stick needs modeswitch. I'm no expert on 3G support in the Fonera, so I can't offer a direct solution right now.

comment:7 Changed 8 years ago by amanullang@…

please...anyone help me??

comment:8 Changed 8 years ago by matthijs

  • Owner set to matthijs
  • Severity set to unknown
  • Status changed from investigate to accepted
  • Type changed from request to bug

Through extensive debugging through IRC, we managed to get this working. Some highlights: The modem doesn't understand AT+CPIN? or AT+COPS, talks only through ttyUSB0 it seems and needs ATDT#777 to dial (not AT+CGDCONT=1 it seems).

This page suggests that this simple dialing also works for another ZTE modem, and I'll get another modem to test soon. It seems that all ZTE modems might need the same treatment.

I'll polish this up into a "zte" modem for umtsd, and hopefully we can get a bunch of ZTE modems supported at the same time.

comment:9 Changed 8 years ago by amanullang@…

still not stable...sometimes diconnected,sometimes connected...

comment:10 Changed 7 years ago by amanullang@…

i was upgrading the new firmware(2.3.6.1). and its happend again,my usbmodem can't connected.it's keep dialing..please help??i already forget how to solve this in terminal (i'm using mac,for remembering)..thx b4!

  • Show quoted text -

comment:11 Changed 7 years ago by matthijs

I looked around my IRC log a bit, but I can't figure out what all the changes were exactly... The most important one seems to be to change the dialing number in /Apps/umtsd.lua to #777

You might also need to play around with the ttyUSBx numbers.

comment:12 Changed 7 years ago by amanullang@…

i'm forgot how to do that...i have all the files from you.umts.so, umtsd, opkg_4564-3.1_mipsel.ipk, umtsd.lua, 19d2%3Afff1, luci...but,i dont now how to copying these files..can you tell me step by step?

comment:13 Changed 7 years ago by matthijs

I think that copying your umtsd.lua to /Apps and the 19d2:fff1 file to /etc/usb_modeswitch.d is probably enough, so you could try that first.

comment:14 Changed 7 years ago by amanullang@…

could you tell me how to doing it? I really forgot..how to go inside this fonera.

comment:15 Changed 7 years ago by matthijs

See reportbugs for info on connecting using WinSCP.

comment:16 Changed 7 years ago by amanullang@…

once again,how to use winscp?

comment:17 Changed 7 years ago by matthijs

Sorry, I can't tell you exactly where to click and what to type. Please just try using WinSCP first. If you have specific problems, feel free to ask about them, but this is too general. Google might be helpful as well.

Using WinSCP, you should be able to navigate to the /Apps folder and upload your umtsd.lua file and navigate to /etc/usb_modeswitch.d and upload your 19d2:111f file.

comment:18 Changed 7 years ago by amanullang@…

ok..i'll try first..

comment:19 Changed 7 years ago by amanullang@…

what should i put in the host name on winscp?

comment:20 Changed 7 years ago by matthijs

From reportbugs:

Login details are the same as for SSH: Use "fonera" or the ip address of your fonera for host, "root" as username and the dashboard password as password.

comment:21 Changed 7 years ago by amanullang@…

keep dialing and still not connected...

comment:22 Changed 7 years ago by amanullang@…

could you tell me what should i do next?

comment:23 Changed 5 years ago by matthijs

  • Hardware changed from 2.0n (FON2300) to both
  • Status changed from accepted to investigate
  • Summary changed from ZTE AC2726 3G modem does not work to Support 3G dongle: ZTE AC2726
  • Type changed from bug to enhancement
  • Version changed from 2.3.6.0 (Gari) to N/A

As part of the upcoming 2.3.7.0 firmware release, we're reviewing old open tickets to see if they are still relevant, which is why you get this response now.

We will revamp the 3G point at some point in the future. When this happens, we'll need to revisit supporting this 3G stick as well.

Add Comment

Modify Ticket

Action
as investigate The owner will remain matthijs.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.