Fatal error when using Huawei E1820 USB 3G modem
-
Was a solution to this ever found?
-
This problem still exist in RC1 (i386-20110226-1429).
I also noted that when trying to use two USB 3G modems only one connects, the other gets USB_ERR_TIMEOUT.
RC1 is clearly not ready for production.
-
I also have the same problem with my Huawei 3g module.
Is there a way to set the PPP debug level to MAX?
pppd.log
May 3 16:31:18 ppp: process 41455 terminated May 3 16:31:18 ppp: [opt2_link0] Link: Shutdown May 3 16:31:18 ppp: [opt2] Bundle: Shutdown May 3 16:31:18 ppp: [opt2] IPV6CP: Close event May 3 16:31:18 ppp: [opt2] IPCP: Close event May 3 16:31:18 ppp: [opt2] IFACE: Close event May 3 16:31:18 ppp: fatal error, exiting May 3 16:31:18 ppp: [opt2] can't config [7c]:: Invalid argument May 3 16:31:18 ppp: [opt2] Bundle: Status update: up 1 link, total bandwidth 28800000 bps May 3 16:31:18 ppp: [opt2_link0] Link: Join bundle "opt2" May 3 16:31:18 ppp: [opt2_link0] Link: Matched action 'bundle "opt2" ""' May 3 16:31:18 ppp: [opt2_link0] LCP: authorization successful May 3 16:31:18 ppp: [opt2_link0] CHAP: rec'd SUCCESS #1 len: 4 May 3 16:31:18 ppp: [opt2_link0] CHAP: sending RESPONSE #1 len: 29 May 3 16:31:18 ppp: [opt2_link0] CHAP: Using authname "vodafone" May 3 16:31:18 ppp: [opt2_link0] Name: "UMTS_CHAP_SRVR" May 3 16:31:18 ppp: [opt2_link0] CHAP: rec'd CHALLENGE #1 len: 35 May 3 16:31:18 ppp: [opt2_link0] LCP: rec'd Discard Request #1 (Opened) May 3 16:31:18 ppp: [opt2_link0] LCP: LayerUp May 3 16:31:18 ppp: [opt2_link0] LCP: auth: peer wants CHAP, I want nothing May 3 16:31:18 ppp: [opt2_link0] LCP: state change Ack-Sent --> Opened May 3 16:31:18 ppp: [opt2_link0] MAGICNUM 7025c5a8 May 3 16:31:18 ppp: [opt2_link0] MRU 1500 May 3 16:31:18 ppp: [opt2_link0] ACCMAP 0x000a0000 May 3 16:31:18 ppp: [opt2_link0] PROTOCOMP May 3 16:31:18 ppp: [opt2_link0] ACFCOMP May 3 16:31:18 ppp: [opt2_link0] LCP: rec'd Configure Ack #1 (Ack-Sent) May 3 16:31:18 ppp: [opt2_link0] LCP: state change Req-Sent --> Ack-Sent May 3 16:31:18 ppp: [opt2_link0] ACFCOMP May 3 16:31:18 ppp: [opt2_link0] PROTOCOMP May 3 16:31:18 ppp: [opt2_link0] MAGICNUM 02d92385 May 3 16:31:18 ppp: [opt2_link0] AUTHPROTO CHAP MD5 May 3 16:31:18 ppp: [opt2_link0] ACCMAP 0x00000000 May 3 16:31:18 ppp: [opt2_link0] LCP: SendConfigAck #0 May 3 16:31:18 ppp: [opt2_link0] ACFCOMP May 3 16:31:18 ppp: [opt2_link0] PROTOCOMP May 3 16:31:18 ppp: [opt2_link0] MAGICNUM 02d92385 May 3 16:31:18 ppp: [opt2_link0] AUTHPROTO CHAP MD5 May 3 16:31:18 ppp: [opt2_link0] ACCMAP 0x00000000 May 3 16:31:18 ppp: [opt2_link0] LCP: rec'd Configure Request #0 (Req-Sent) May 3 16:31:18 ppp: [opt2_link0] MAGICNUM 7025c5a8 May 3 16:31:18 ppp: [opt2_link0] MRU 1500 May 3 16:31:18 ppp: [opt2_link0] ACCMAP 0x000a0000 May 3 16:31:18 ppp: [opt2_link0] PROTOCOMP May 3 16:31:18 ppp: [opt2_link0] ACFCOMP May 3 16:31:18 ppp: [opt2_link0] LCP: SendConfigReq #1 May 3 16:31:18 ppp: [opt2_link0] LCP: state change Starting --> Req-Sent May 3 16:31:18 ppp: [opt2_link0] LCP: Up event May 3 16:31:18 ppp: [opt2_link0] Link: UP event May 3 16:31:18 ppp: [opt2_link0] MODEM: chat script succeeded May 3 16:31:18 ppp: [opt2_link0] chat: Connected at 28800000. May 3 16:31:18 ppp: [opt2_link0] chat: Dialing server at *99#... May 3 16:31:18 ppp: [opt2_link0] chat: Detected Hayes compatible modem. May 3 16:31:18 ppp: [opt2_link0] LCP: LayerStart May 3 16:31:18 ppp: [opt2_link0] LCP: state change Initial --> Starting May 3 16:31:18 ppp: [opt2_link0] LCP: Open event May 3 16:31:18 ppp: [opt2_link0] Link: OPEN event May 3 16:31:18 ppp: [opt2] Bundle: Interface ng4 created May 3 16:31:18 ppp: web: web is not running May 3 16:31:18 ppp: process 41455 started, version 5.5 (root@bsd8x86.pingle.org 14:01 28-Feb-2011) May 3 16:31:18 ppp: May 3 16:31:18 ppp: Multi-link PPP daemon for FreeBSD/var/etc/mpd_3g.conf
startup: # configure the console set console close # configure the web server set web close default: pppclient: create bundle static opt2 set bundle enable ipv6cp set iface name ppp0 set iface disable on-demand set iface idle 0 set iface enable tcpmssfix set iface up-script /usr/local/sbin/ppp-linkup set iface down-script /usr/local/sbin/ppp-linkdown set ipcp ranges 0.0.0.0/0 10.64.64.0/0 #log -bund -ccp -chat -iface -ipcp -lcp -link create link static opt2_link0 modem set link action bundle opt2 set link disable multilink set link keep-alive 10 60 set link max-redial 0 set link disable chap pap set link accept chap pap eap set link disable incoming set link mtu 1492 set auth authname "vodafone" set auth password vodafone set modem device /dev/cuaU0.0 set modem script DialPeer set modem idle-script Ringback set modem watch -cd set modem var $DialPrefix "DT" set modem var $Telephone "*99#" set modem var $APN "live.vodafone.com" set modem var $APNum "1" open -
This user is also having the same problem:
http://forum.pfsense.org/index.php?action=profile;u=37021;sa=showPosts -
Please read this post about the MPD binary.
Maybe some files are outdated?
http://sourceforge.net/projects/mpd/forums/forum/44693/topic/4516341 -
This affects the new Huawei e398 LTE modem as well.
Relevant line reads:
ppp: [wan] can't config [1c]:: Invalid argument -
OK, Problem solved!!
See http://sourceforge.net/projects/mpd/forums/forum/44693/topic/4516341
Changed NG_PPP_MAX_BANDWIDTH in ng_ppp.h kernel file to a much higer value. The big BPS number of the K4505 Huawei modem is confusing the bandwidth maximum.
/* Max allowable link latency (miliseconds) and bandwidth (bytes/second/10) */ #define NG_PPP_MAX_LATENCY 1000 /* 1 second */ #define NG_PPP_MAX_BANDWIDTH 125000 /* 10 Mbits / second */a MPD developer is changing the source of MPD5 now, so maybe update PFsense with the new MPD code in the future??
-
Imported the fix done on mpd5 sources in pfSense.
-
Does the Huawei E398 work with RC3 or what's the status? I'm having some trouble getting go grips with if it works or not. Some people are having trouble with usb_modeswitch and for some other it works.
Could someone enlighten me?
-
Does the Huawei E398 work with RC3 or what's the status? I'm having some trouble getting go grips with if it works or not. Some people are having trouble with usb_modeswitch and for some other it works.
Could someone enlighten me?
The e398 works with the RC3. I use it on a laptop based home router an it serves well. (Thanks to ermal for the commit and GrandmasterB for the info). You may have to set it to 4G only on a Win PC first as I am uncertain if Linux and FreeBSD can set that parameter or how it will behave if set to auto.
The only issues I encounter in experimenting occur - or so I think for now - if other USB interfaces are activated. In my setup a reboot with an USB ethernet adapter and wireless adapter alongside the e398 - all with previously successfully assigned interfaces - saw an "interface mismatch" message and the interface assignment routine started. Removing and replacing the devices in some or other sequence saw the old assignments be picked up and the bootup completed. My impression is this is a usb-modeswitch issue with the e398 but more needs to be done to isolate what triggers it.