Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't connect to internet with ZTE MF820 WL500gP #305

Closed
GoogleCodeExporter opened this issue Mar 29, 2015 · 8 comments
Closed

Can't connect to internet with ZTE MF820 WL500gP #305

GoogleCodeExporter opened this issue Mar 29, 2015 · 8 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Install firmware WL500gp-1.9.2.7-rtn-r4081
2. Plug in ZTE MF820 4g modem
3. Insert info (apn etc)
4. Connect with autodetect (cant connect with manual for some reason?)
5. Restart modem

What is the expected output? What do you see instead?

Calling WCDMA/UMTS/GPRS
Failed
Script /tmp/ppp/peers/wan0_chat.sh finished (pid 403), status = 0x3
Connect script failed
Calling WCDMA/UMTS/GPRS
Failed
Script /tmp/ppp/peers/wan0_chat.sh finished (pid 408), status = 0x3
Connect script failed
Calling WCDMA/UMTS/GPRS



What version of the product are you using?

Newest to this date.


Please provide any additional information below.

Jan  1 00:00:02 syslogd started: BusyBox v1.19.3
Jan  1 00:00:02 kernel: klogd started: BusyBox v1.19.3 (2012-04-02 21:13:42 MSK)
Jan  1 00:00:02 kernel: Linux version 2.6.22.19 (root@localhost) (gcc version 
4.5.3 (GCC) ) #2 Mon Apr 2 21:59:34 MSK 2012
Jan  1 00:00:02 kernel: CPU revision is: 00029006
Jan  1 00:00:02 kernel: Setting the PFC to its default value
Jan  1 00:00:02 kernel: Determined physical RAM map:
Jan  1 00:00:02 kernel:  memory: 02000000 @ 00000000 (usable)
Jan  1 00:00:03 dnsmasq[206]: started, version  cachesize 512
Jan  1 00:00:03 dnsmasq[206]: compile time options: IPv6 GNU-getopt no-RTC 
no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-scripts no-TFTP no-conntrack
Jan  1 00:00:03 dnsmasq-dhcp[206]: DHCP, IP range 192.168.1.101 -- 
192.168.1.254, lease time 1d
Jan  1 00:00:03 dnsmasq[206]: read /etc/hosts - 2 addresses
Jan  1 00:00:04 miniupnpd[208]: version 1.6 started
Jan  1 00:00:04 miniupnpd[208]: HTTP listening on port 57149
Jan  1 00:00:04 miniupnpd[208]: Listening for NAT-PMP traffic on port 5351
Jan  1 00:00:04 dnsmasq-dhcp[206]: DHCPREQUEST(br0) 192.168.1.213 
00:25:22:1e:cf:9a 
Jan  1 00:00:04 dnsmasq-dhcp[206]: DHCPACK(br0) 192.168.1.213 00:25:22:1e:cf:9a 
Ace-PC
Jan  1 00:00:04 kernel: usbcore: registered new interface driver usbfs
Jan  1 00:00:04 kernel: usbcore: registered new interface driver hub
Jan  1 00:00:04 kernel: usbcore: registered new device driver usb
Jan  1 00:00:04 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) 
Driver
Jan  1 00:00:04 kernel: PCI: Enabling device 0000:01:03.2 (0000 -> 0002)
Jan  1 00:00:04 kernel: ehci_hcd 0000:01:03.2: EHCI Host Controller
Jan  1 00:00:04 kernel: ehci_hcd 0000:01:03.2: new USB bus registered, assigned 
bus number 1
Jan  1 00:00:04 kernel: ehci_hcd 0000:01:03.2: irq 12, io mem 0x40004000
Jan  1 00:00:04 kernel: ehci_hcd 0000:01:03.2: USB 2.0 started, EHCI 1.00
Jan  1 00:00:05 kernel: usb usb1: configuration #1 chosen from 1 choice
Jan  1 00:00:05 kernel: hub 1-0:1.0: USB hub found
Jan  1 00:00:05 kernel: hub 1-0:1.0: 4 ports detected
Jan  1 00:00:05 kernel: uhci_hcd: USB Universal Host Controller Interface driver
Jan  1 00:00:05 kernel: PCI: Enabling device 0000:01:03.0 (0000 -> 0001)
Jan  1 00:00:05 kernel: uhci_hcd 0000:01:03.0: UHCI Host Controller
Jan  1 00:00:05 kernel: uhci_hcd 0000:01:03.0: new USB bus registered, assigned 
bus number 2
Jan  1 00:00:05 kernel: uhci_hcd 0000:01:03.0: irq 12, io base 0x00000100
Jan  1 00:00:05 kernel: usb 1-1: new high speed USB device using ehci_hcd and 
address 2
Jan  1 00:00:05 kernel: usb usb2: configuration #1 chosen from 1 choice
Jan  1 00:00:05 kernel: hub 2-0:1.0: USB hub found
Jan  1 00:00:05 kernel: hub 2-0:1.0: 2 ports detected
Jan  1 00:00:05 kernel: PCI: Enabling device 0000:01:03.1 (0000 -> 0001)
Jan  1 00:00:05 kernel: uhci_hcd 0000:01:03.1: UHCI Host Controller
Jan  1 00:00:05 kernel: uhci_hcd 0000:01:03.1: new USB bus registered, assigned 
bus number 3
Jan  1 00:00:05 kernel: uhci_hcd 0000:01:03.1: irq 12, io base 0x00000120
Jan  1 00:00:05 kernel: usb usb3: configuration #1 chosen from 1 choice
Jan  1 00:00:05 kernel: hub 3-0:1.0: USB hub found
Jan  1 00:00:05 kernel: hub 3-0:1.0: 2 ports detected
Jan  1 00:00:05 kernel: usb 1-1: configuration #1 chosen from 1 choice
Jan  1 00:00:05 kernel: usbcore: registered new interface driver usblp
Jan  1 00:00:06 kernel: usbcore: registered new interface driver usbserial
Jan  1 00:00:06 kernel: SCSI subsystem initialized
Jan  1 00:00:06 kernel: drivers/usb/serial/usb-serial.c: USB Serial support 
registered for generic
Jan  1 00:00:06 kernel: usbcore: registered new interface driver 
usbserial_generic
Jan  1 00:00:06 kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core
Jan  1 00:00:06 kernel: drivers/usb/serial/usb-serial.c: USB Serial support 
registered for GSM modem (1-port)
Jan  1 00:00:06 kernel: option 1-1:1.0: GSM modem (1-port) converter detected
Jan  1 00:00:06 kernel: usb 1-1: GSM modem (1-port) converter now attached to 
ttyUSB0
Jan  1 00:00:06 kernel: option 1-1:1.1: GSM modem (1-port) converter detected
Jan  1 00:00:06 kernel: usb 1-1: GSM modem (1-port) converter now attached to 
ttyUSB1
Jan  1 00:00:06 kernel: option 1-1:1.2: GSM modem (1-port) converter detected
Jan  1 00:00:06 kernel: usb 1-1: GSM modem (1-port) converter now attached to 
ttyUSB2
Jan  1 00:00:06 kernel: option 1-1:1.3: GSM modem (1-port) converter detected
Jan  1 00:00:06 kernel: usb 1-1: GSM modem (1-port) converter now attached to 
ttyUSB3
Jan  1 00:00:06 kernel: option 1-1:1.4: GSM modem (1-port) converter detected
Jan  1 00:00:07 kernel: usb 1-1: GSM modem (1-port) converter now attached to 
ttyUSB4
Jan  1 00:00:07 kernel: usbcore: registered new interface driver option
Jan  1 00:00:07 kernel: drivers/usb/serial/option.c: USB Driver for GSM modems: 
v0.7.2
Jan  1 00:00:07 kernel: usbcore: registered new interface driver cdc_acm
Jan  1 00:00:07 kernel: drivers/usb/class/cdc-acm.c: v0.26:USB Abstract Control 
Model driver for USB modems and ISDN adapters
Jan  1 00:00:07 kernel: Initializing USB Mass Storage driver...
Jan  1 00:00:07 kernel: usbcore: registered new interface driver usb-storage
Jan  1 00:00:07 kernel: USB Mass Storage support registered.
Jan  1 00:00:07 kernel: fuse init (API version 7.9)
Jan  1 00:00:09 dnsmasq-dhcp[206]: DHCPINFORM(br0) 192.168.1.213 
00:25:22:1e:cf:9a 
Jan  1 00:00:09 dnsmasq-dhcp[206]: DHCPACK(br0) 192.168.1.213 00:25:22:1e:cf:9a 
Ace-PC
Jan  1 00:00:09 WAN port: cable disconnected
Jan  1 00:00:10 pppd[402]: pppd 2.4.5 started by admin, uid 0
Jan  1 00:00:21 pppd[402]: Connect script failed
Jan  1 00:00:39 pppd[402]: Connect script failed
Jan  1 00:00:56 pppd[402]: Connect script failed


It recognizes the modem and everything but gives the status = 0x3 error 
everytime.

Thanks for the nice firmware! :)

Original issue reported on code.google.com by PowerDriver on 10 Apr 2012 at 11:42

@GoogleCodeExporter
Copy link
Author

rss: please take a look at problem

Original comment by lly.dev on 11 Apr 2012 at 5:58

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

You need to switch off the autodetection. Please try to choose an operable 
configuration of the Data and the User interface ports (0,1,2,3 or 4) at USB 
Network Devices - 3G/CDMA Modem page. We can add this port configuration to the 
file of known configurations.

If it will not work, please attach "Status & Log - Diagnostic Information".

Original comment by rssdev10@gmail.com on 11 Apr 2012 at 6:08

  • Changed state: Accepted
  • Added labels: Type-Support
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Phew - i got it to work, thank you guys SO SO much!

I'm running data port 3 and user interface port 2 - seems to work though it is 
a little unstable? But it works. The speed of the download/upload with the 
router seems limited to 10/10mbit i guess the router can't go any faster?

Everything is in the log - i tested all the data ports and interface ports. 
Search in the text file: WORKS and SAME ERROR to get to the succes or fail.

Thank you guys again! :D :D :D :D :D

Original comment by PowerDriver on 11 Apr 2012 at 8:10

  • Added labels: ****
  • Removed labels: ****

Attachments:

@GoogleCodeExporter
Copy link
Author

ok. Thanks. 

Speed limits are not limits of our firmware or of the router. See CPU 
utilization at the "System Utilization" page. I suppose it is a limitation of 
your ISP.

Also please check USSD queries. It will work if you have right selected user 
interface port. (Status & Log / USB PPP Log).

Original comment by rssdev10@gmail.com on 13 Apr 2012 at 6:56

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

I got speed limit problem too.
 mf820 direct plug into PC speedtest 30Mbits
 plug in WL-500GP down to 15Mbits

Original comment by wch...@gmail.com on 4 Oct 2012 at 12:54

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Look at the previous comment. It's either router CPU limitation (see CPU 
utilization at the "System Utilization" page) or modem CPU limitation (PC 
usually uses NDIS connection type, but firmware doesn't support it and uses RAS 
connection type which requires more CPU power), or both.

Original comment by ad...@vampik.ru on 4 Oct 2012 at 5:27

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Thanks
I got 90% CPU utilization in speedtest


Original comment by wch...@gmail.com on 4 Oct 2012 at 6:21

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by rssdev10@gmail.com on 31 Dec 2012 at 9:58

  • Changed state: Done
  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant