From owner-freebsd-questions@FreeBSD.ORG Fri Mar 25 02:03:38 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD674106566C for ; Fri, 25 Mar 2011 02:03:38 +0000 (UTC) (envelope-from lcampbell@ironclad.mobi) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4F0958FC15 for ; Fri, 25 Mar 2011 02:03:37 +0000 (UTC) Received: by bwz12 with SMTP id 12so755105bwz.13 for ; Thu, 24 Mar 2011 19:03:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.74.11 with SMTP id s11mr187995bkj.43.1301018616863; Thu, 24 Mar 2011 19:03:36 -0700 (PDT) Received: by 10.204.175.2 with HTTP; Thu, 24 Mar 2011 19:03:36 -0700 (PDT) In-Reply-To: References: Date: Thu, 24 Mar 2011 20:03:36 -0600 Message-ID: From: Lawton Campbell To: Ryan Coleman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: ppp.conf for Verizon Mifi 2200? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2011 02:03:38 -0000 On Thu, Mar 24, 2011 at 5:24 PM, Ryan Coleman wr= ote: > Sounds alot like my query for the Virgin Mobile one ... I got NOWHERE. > :\ Haha yeah, I was really excited when I originally found your thread. What does yours do if you give it my ppp.conf (with your phone/authname/authkey subbed in)? Does it also get stuck sending LCP requests for configuration and never receiving an intelligible reply? > On Mar 24, 2011, at 5:31 PM, Lawton Campbell wrote: > >> Hey freebsd-questions! >> >> I've been trying to get a Verizon MiFi 2200 to work on my 8.2-RELEASE >> box for the past couple of days and can't seem to get the ppp.conf to >> work properly. I found a couple of recent threads about similar >> devices (apparently it's just novatel stuff that gets repackaged for >> different 3G providers) -- >> >> http://www.mail-archive.com/freebsd-net@freebsd.org/msg36160.html >> >> It doesn't look like they got the Virgin Mobile version of the device >> working, unfortunately. I'm stuck in a slightly different place, so >> making a new thread (dunno if freebsd-net or freebsd-questions is more >> appropriate, so erring to -questions). Anyway, let's get started! >> Going to walkthrough what I have so far, then finally get to where I'm >> stuck and detail some questions. >> >> # THUS FAR >> >> One quirk of the device is that you have to detach /dev/cd0 when it >> mounts to expose the modem interface for u3g to grab. Looking at >> usbconfig, the relevant identifiers for the device are >> >> =A0idVendor =3D 0x1410 >> =A0idProduct =3D 0x5041 >> >> AFAIK, u3gstub is supposed to take care of this automagically, but >> perhaps either I've misread the man page or it's missing the >> vendor/product IDs. In any case, it's probably easy enough to fix with >> a devd rule, so I'm not too worried about it. In any case, when the >> device is attached, `camcontrol eject cd0` (or whatever cd# is >> generated) has to be run -- >> >> root@ffffff> camcontrol eject cd0 >> >> Which gives us -- >> >> Mar 25 06:06:36 ffffff kernel: ugen1.2: at usbus= 1 >> Mar 25 06:06:36 ffffff kernel: u3g0: on usbus1 >> Mar 25 06:06:36 ffffff kernel: u3g0: Found 5 ports. >> >> root@ffffff> ls /dev/cuaU0.* >> /dev/cuaU0.0 =A0 =A0 =A0/dev/cuaU0.1.init /dev/cuaU0.2.lock /dev/cuaU0.4 >> /dev/cuaU0.0.init /dev/cuaU0.1.lock /dev/cuaU0.3 =A0 =A0 =A0/dev/cuaU0.4= .init >> /dev/cuaU0.0.lock /dev/cuaU0.2 =A0 =A0 =A0/dev/cuaU0.3.init /dev/cuaU0.4= .lock >> /dev/cuaU0.1 =A0 =A0 =A0/dev/cuaU0.2.init /dev/cuaU0.3.lock >> >> I just grabbed the stock ppp.conf from the handbook >> (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/userppp.html) >> with some bits removed (the login chat script, specifically -- we'll >> know if that's broken when we get there). >> >> root@ffffff> cat /etc/ppp/ppp.conf >> default: >> set log Phase Chat LCP IPCP CCP tun command >> ident user-ppp VERSION (built COMPILATIONDATE) >> set speed 115200 >> set device /dev/cuaU0.0 >> set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ >> =A0 =A0 =A0 \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT" >> >> set timeout 180 >> enable dns >> >> mifi: >> set phone "#777" >> set authname "XXXMYNUMBER@vzw3g.com" >> set authkey "vzw" >> >> set ifaddr 10.23.0.1 10.23.0.2 255.255.255.255 0.0.0.0 >> add default HISADDR >> >> However, when I run `ppp -ddial mifi`, I get -- >> >> Mar 25 06:17:43 ffffff ppp[10491]: tun0: Chat: Send: AT^M >> Mar 25 06:17:43 ffffff ppp[10491]: tun0: Chat: Expect(5): OK >> Mar 25 06:17:49 ffffff ppp[10491]: tun0: Chat: Expect timeout >> Mar 25 06:17:49 ffffff ppp[10491]: tun0: Warning: Chat script failed >> >> Which means we're not even communicating with the modem. Kinda weird >> -- I think it's a problem in the dial script. Let's just take out the >> non-default dial script and see what happens: >> >> root@ffffff> cat /etc/ppp/ppp.conf >> default: >> set log Phase Chat LCP IPCP CCP tun command >> ident user-ppp VERSION (built COMPILATIONDATE) >> set speed 115200 >> set device /dev/cuaU0.1 >> >> set timeout 180 >> enable dns >> >> mifi: >> set phone "#777" >> set authname "XXXMYNUMBER@vzw3g.com" >> set authkey "vzw" >> >> set ifaddr 10.23.0.1 10.23.0.2 255.255.255.255 0.0.0.0 >> add default HISADDR >> >> Mar 25 06:20:15 ffffff ppp[10518]: tun0: Phase: deflink: closed -> openi= ng >> Mar 25 06:20:15 ffffff ppp[10518]: tun0: Phase: deflink: Connected! >> Mar 25 06:20:15 ffffff ppp[10518]: tun0: Phase: deflink: opening -> dial >> Mar 25 06:20:15 ffffff ppp[10518]: tun0: Phase: deflink: dial -> carrier >> Mar 25 06:20:16 ffffff ppp[10518]: tun0: Phase: deflink: /dev/cuaU0.1 >> doesn't support CD >> Mar 25 06:20:16 ffffff ppp[10518]: tun0: Phase: deflink: carrier -> logi= n >> Mar 25 06:20:16 ffffff ppp[10518]: tun0: Phase: deflink: login -> lcp >> Mar 25 06:20:16 ffffff ppp[10518]: tun0: LCP: FSM: Using "deflink" as >> a transport >> Mar 25 06:20:16 ffffff ppp[10518]: tun0: LCP: deflink: State change >> Initial --> Closed >> Mar 25 06:20:16 ffffff ppp[10518]: tun0: LCP: deflink: State change >> Closed --> Stopped >> Mar 25 06:20:17 ffffff ppp[10518]: tun0: LCP: deflink: LayerStart >> Mar 25 06:20:17 ffffff ppp[10518]: tun0: LCP: deflink: >> SendConfigReq(1) state =3D Stopped >> Mar 25 06:20:17 ffffff ppp[10518]: tun0: LCP: =A0ACFCOMP[2] >> Mar 25 06:20:17 ffffff ppp[10518]: tun0: LCP: =A0PROTOCOMP[2] >> Mar 25 06:20:17 ffffff ppp[10518]: tun0: LCP: =A0ACCMAP[6] 0x00000000 >> Mar 25 06:20:17 ffffff ppp[10518]: tun0: LCP: =A0MRU[4] 1500 >> Mar 25 06:20:17 ffffff ppp[10518]: tun0: LCP: =A0MAGICNUM[6] 0x72c1cbf0 >> Mar 25 06:20:17 ffffff ppp[10518]: tun0: LCP: deflink: State change >> Stopped --> Req-Sent >> Mar 25 06:20:21 ffffff ppp[10518]: tun0: LCP: deflink: >> SendConfigReq(1) state =3D Req-Sent >> Mar 25 06:20:21 ffffff ppp[10518]: tun0: LCP: =A0ACFCOMP[2] >> Mar 25 06:20:21 ffffff ppp[10518]: tun0: LCP: =A0PROTOCOMP[2] >> Mar 25 06:20:21 ffffff ppp[10518]: tun0: LCP: =A0ACCMAP[6] 0x00000000 >> Mar 25 06:20:21 ffffff ppp[10518]: tun0: LCP: =A0MRU[4] 1500 >> Mar 25 06:20:21 ffffff ppp[10518]: tun0: LCP: =A0MAGICNUM[6] 0x72c1cbf0 >> Mar 25 06:20:21 ffffff ppp[10518]: tun0: Phase: Unknown protocol >> 0x0013 (reserved (transparency inefficient)) >> Mar 25 06:20:21 ffffff ppp[10518]: tun0: LCP: deflink: >> SendProtocolRej(1) state =3D Req-Sent >> >> Aha! So we've got a connection to the provider at this point, but >> they're not responding properly to our LCP configuration requests. Not >> quite sure why, to be honest. A little bit of googling turns up this >> thread: >> >> http://lists.freebsd.org/pipermail/freebsd-usb/2009-August/007241.html >> >> Which suggests adding "disable pred1 deflate deflate24 protocomp >> acfcomp shortseq vj mppe" to the ppp.conf. After making this >> modification, I get the following response -- >> >> Mar 25 06:24:49 ffffff ppp[10593]: tun0: LCP: deflink: State change >> Closed --> Stopped >> Mar 25 06:24:50 ffffff ppp[10593]: tun0: LCP: deflink: LayerStart >> Mar 25 06:24:50 ffffff ppp[10593]: tun0: LCP: deflink: >> SendConfigReq(1) state =3D Stopped >> Mar 25 06:24:50 ffffff ppp[10593]: tun0: LCP: =A0ACCMAP[6] 0x00000000 >> Mar 25 06:24:50 ffffff ppp[10593]: tun0: LCP: =A0MRU[4] 1500 >> Mar 25 06:24:50 ffffff ppp[10593]: tun0: LCP: =A0MAGICNUM[6] 0x09fbbcd0 >> Mar 25 06:24:50 ffffff ppp[10593]: tun0: LCP: deflink: State change >> Stopped --> Req-Sent >> Mar 25 06:24:54 ffffff ppp[10593]: tun0: LCP: deflink: >> SendConfigReq(1) state =3D Req-Sent >> Mar 25 06:24:54 ffffff ppp[10593]: tun0: LCP: =A0ACCMAP[6] 0x00000000 >> Mar 25 06:24:54 ffffff ppp[10593]: tun0: LCP: =A0MRU[4] 1500 >> Mar 25 06:24:54 ffffff ppp[10593]: tun0: LCP: =A0MAGICNUM[6] 0x09fbbcd0 >> Mar 25 06:24:57 ffffff ppp[10593]: tun0: LCP: deflink: >> SendConfigReq(1) state =3D Req-Sent >> >> So now we're not getting _anything_ back from the provider. It looks >> like `disable acfcomp` is what's squelching those errors, but frankly >> I have no idea what acfcomp is or does. I suspect that the modem isn't >> really speaking PPP, but I don't know how to try PPPoE or anything >> else. At this point I am completely confounded. Any ideas? >> >> (I'm off-list, so please CC me!) >> >> Thanks :) >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.= org" > >