Vodafone dongle?

[dog]

Since several google success reports for these dongles [around the world]
all have the
familiar format of <pppd scripts> which I've used since the 90's dialup
days, I assume that should work for me too.
In fact I connected, and was able to `ping` in 2 of about 40 sequence
attempts.
2 error messages keep coming up which are unfamiliar:-
1. What's about '8-bit clean'?
2. <different/wrong CHANNEL>: what's that?

This `Script` shows some of the tried combinations:------
#!/bin/sh
#DEV=/dev/ttyUSB0
#DEV=/dev/sg0
#DEV=/dev/sr1
#DEV=/dev/ttyUSB1
DEV=/dev/ttyACM0 <--- also tried with ACM1
echo "ATZ" >$DEV
head -n 2 $DEV
#echo 'AT+CGDCONT=1,"IP","web.yesss.at"' >$DEV
echo 'AT+CGDCONT=1,"IP","Vodafone" >$DEV
#echo 'AT+CGDCONT=1,"IP","internet" >$DEV
#echo 'AT+CGDCONT=1,"IP","3" >$DEV
#Init4 = AT+CGDCONT=1,"IP","hs.vodafone.ie"
#Init5 = AT+CGDCONT=1,"IP","3ireland.ie"
#"AT+CGDCONT=1,\"IP\"\"internet\""
#Init4 = AT+CGDCONT=1,"IP","3"
head -n 2 $DEV
echo 'ATD*99***1#' >$DEV
head -n 2 $DEV
sleep 1
/usr/sbin/pppd debug nodetach 460800 $DEV

--------- end of script, which usually gives:----

# ./Script <-- give output:--
ATZ

OK
ATZ

ATZ
------------
using channel 1
Using interface ppp0
Connect: ppp0 <--> /dev/ttyACM0
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc5c8e42f> <pcomp> <accomp>]
...
LCP: timeout sending Config-Requests
Connection terminated.
Receive serial link is not 8-bit clean:
Problem: all had bit 7 set to 0
Modem hangup
-----------------------------------------------
What's the problem here? 2 error-message-types which I've never seen
before:
1. 'not 8-bit clean'
2. <can't find the channel>
------------> tail -f /var/log/messages
shows the 30 second connection thus:------------
Jul 11 19:45:03 kongoni32 pppd[3574]: pppd 2.4.4 started by root, uid 0
Jul 11 19:45:03 kongoni32 kernel: PPP generic driver version 2.4.2
Jul 11 19:45:03 kongoni32 pppd[3574]: Using interface ppp0
Jul 11 19:45:03 kongoni32 pppd[3574]: Connect: ppp0 <--> /dev/ttyACM0
Jul 11 19:45:33 kongoni32 pppd[3574]: Connection terminated.
Jul 11 19:45:35 kongoni32 pppd[3574]: Modem hangup
Jul 11 19:45:35 kongoni32 pppd[3574]: Exit.
===
A different attempt gave:--
AT+CGDCONT=1,"IP","Vodafone" >$DEV
#echo AT+CGDCONT=1,IP,internet
ATD*99***1#

can't open routing table /proc/net/route: No such file or directory
using channel 2
Using interface ppp0
Connect: ppp0 <--> /dev/ttyACM0
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc5761cf9> <pcomp> <accomp>]
...
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc5761cf9> <pcomp> <accomp>]
LCP: timeout sending Config-Requests <--- hanging ?! exit via Ctrl/C
^CTerminating on signal 2
Connection terminated.
Receive serial link is not 8-bit clean: <-- what's this !?
Problem: all had bit 7 set to 0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> set /Script to /dev/ttyACM1 from /dev/ttyACM0 re. /var/log/messages
# /Script
ATZ

OKConnect: ppp0 <--> /dev/ttyACM1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xbbb29a91> <pcomp> <accomp>]
...
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xbbb29a91> <pcomp> <accomp>]
LCP: timeout sending Config-Requests
Connection terminated.
Receive serial link is not 8-bit clean:
Problem: all had bit 7 set to 0
Modem hangup
+++++++++++++++++++++++++++++++++++++++++
Jul 11 20:12:33 kongoni32 acpid: client connected from 7272[0:0]
Jul 11 20:12:33 kongoni32 acpid: 1 client rule loaded
Jul 11 20:14:10 kongoni32 pppd[7657]: pppd 2.4.4 started by root, uid 0
Jul 11 20:14:10 kongoni32 pppd[7657]: Using interface ppp0
Jul 11 20:14:10 kongoni32 pppd[7657]: Connect: ppp0 <--> /dev/ttyACM1
Jul 11 20:14:40 kongoni32 pppd[7657]: Connection terminated.
Jul 11 20:14:41 kongoni32 pppd[7657]: Modem hangup
Jul 11 20:14:41 kongoni32 pppd[7657]: Exit.
== Connected for 30 sec, like last test, BUT
? Why this NEW/DIFFERENT complaint ?
====================================================
In the following log, [apparently after the CD-ROM is switched to modem],
why are there *2*: ttyACM0 & ttyACM1 ?

Jul 12 06:55:24 kongoni32 kernel: usb 1-2: configuration #1 chosen from 1
choice
Jul 12 06:55:24 kongoni32 kernel: scsi7 : SCSI emulation for USB Mass
Storage
devices
Jul 12 06:55:24 kongoni32 kernel: cdc_acm 1-2:1.1: ttyACM0: USB ACM device
Jul 12 06:55:24 kongoni32 kernel: cdc_acm 1-2:1.3: ttyACM1: USB ACM device
Jul 12 06:55:24 kongoni32 kernel: usbcore: registered new interface driver
cdc_acm
Jul 12 06:55:24 kongoni32 kernel: cdc_acm: v0.26:USB Abstract Control Model
driver for USB modems and ISDN adapters
Jul 12 06:55:25 kongoni32 kernel: usb0 (cdc_ether): not using net_device_ops
yet
Jul 12 06:55:25 kongoni32 kernel: usb0: register 'cdc_ether' at
usb-0000:00:04.1-2, CDC Ethernet Device, 02:2f:28:9d:4b:9f
Jul 12 06:55:25 kongoni32 kernel: usbcore: registered new interface driver
cdc_ether
Jul 12 06:55:29 kongoni32 kernel: scsi 7:0:0:0: CD-ROM Vodafone
USB
SCSI CD-ROM 0001 PQ: 0 ANSI: 0
+++++++++++++++++
Jul 12 07:15:34 kongoni32 pppd[11722]: pppd 2.4.4 started by root, uid 0
Jul 12 07:15:34 kongoni32 pppd[11722]: Using interface ppp0
Jul 12 07:15:34 kongoni32 pppd[11722]: Connect: ppp0 <--> /dev/ttyACM1
Jul 12 07:15:34 kongoni32 kernel: PPP BSD Compression module registered
Jul 12 07:15:34 kongoni32 kernel: PPP Deflate Compression module registered
Jul 12 07:15:37 kongoni32 pppd[11722]: local IP address 10.140.214.3
Jul 12 07:15:37 kongoni32 pppd[11722]: remote IP address 10.0.0.1
Jul 12 07:17:12 kongoni32 ntpd[6468]: Listening on interface #4 ppp0,
10.140.214.3#123 Enabled
Jul 12 07:17:48 kongoni32 pppd[11722]: Terminating on signal 2
Jul 12 07:17:48 kongoni32 pppd[11722]: Connect time 2.2 minutes.
Jul 12 07:17:48 kongoni32 pppd[11722]: Sent 0 bytes, received 0 bytes.
Jul 12 07:17:48 kongoni32 pppd[11722]: Connection terminated.
Jul 12 07:17:49 kongoni32 pppd[11722]: Exit.

Please advise.

==TIA.

PS. switching the dongle from a CDROM to a modem, is a separate issue
which seems to work. Although I'm confused that [ AFAIR] `dmesg`
show a ttyACM0 and ttyACM1 ??

[James Carlson]

Post by dog
using channel 1
Using interface ppp0
Connect: ppp0 <--> /dev/ttyACM0
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc5c8e42f> <pcomp> <accomp>]
...
LCP: timeout sending Config-Requests
Connection terminated.
Problem: all had bit 7 set to 0
Modem hangup
-----------------------------------------------
What's the problem here? 2 error-message-types which I've never seen
1. 'not 8-bit clean'
2. <can't find the channel>

Sorry for the late reply. I've been away from netnews for a while.

The symptoms above are classic. They typically mean that pppd is
talking to a text mode prompt rather than to an actual PPP
implementation on the other side.

Several things can cause this, but they all boil down to a lack of PPP
at the other end.

One possibility is that the modem did not make a connection due to a
problem in the chat script, and so pppd is sending PPP messages to the
modem itself. The modem's "AT" interface is echoing them back mangled
(8th bit stripped), so that's the hint.

Another possibility is that the modem connected, but the peer presented
a shell prompt or a menu interface rather than starting PPP, possibly
(again) due to an error in the chat script. So, pppd is sending PPP
packets to the shell or other command-line interface and is getting back
mangled packets.

As a very rare possibility, it could be that the modem actually
established a connection with strange serial parameters (e.g., "7E1" --
7 bits, even parity, one stop bit). But I can count on one hand the
number of times that's happened. ;-}

Post by dog
can't open routing table /proc/net/route: No such file or directory

That's not a pppd problem. I don't know what that is.

Post by dog
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc5761cf9> <pcomp> <accomp>]
LCP: timeout sending Config-Requests <--- hanging ?! exit via Ctrl/C
^CTerminating on signal 2

A hang here indicates device driver trouble. That's not surprising if
you have some strange (possibly USB-based) device.

Post by dog
Connection terminated.
Receive serial link is not 8-bit clean: <-- what's this !?

Same as above. The underlying connection is failing, so you end up
launching pppd when the peer isn't speaking PPP at all.

pppd requires that the peer speaks PPP. Getting to that point is the
job of chat and/or the script that launches pppd.

I suggest, for ease of debugging, getting pppd out of the picture until
you can establish a basic connection. Use miniterm or 'cu' or some
other simple serial communications program and type the "AT" commands by
hand. Figure out what you need to do to (a) establish a connection and
(b) get the peer to run PPP. Once you've got that, you should be able
to write a working chat script.

Debugging problems in the chat script by looking at pppd error messages
almost certainly isn't going to work.

Post by dog
Jul 11 20:14:40 kongoni32 pppd[7657]: Connection terminated.
Jul 11 20:14:41 kongoni32 pppd[7657]: Modem hangup
Jul 11 20:14:41 kongoni32 pppd[7657]: Exit.
== Connected for 30 sec, like last test, BUT
? Why this NEW/DIFFERENT complaint ?

No echoed data, no error.

Post by dog
====================================================
In the following log, [apparently after the CD-ROM is switched to modem],
why are there *2*: ttyACM0 & ttyACM1 ?
Jul 12 06:55:24 kongoni32 kernel: usb 1-2: configuration #1 chosen from 1
choice
Jul 12 06:55:24 kongoni32 kernel: scsi7 : SCSI emulation for USB Mass
Storage
devices
Jul 12 06:55:24 kongoni32 kernel: cdc_acm 1-2:1.1: ttyACM0: USB ACM device
Jul 12 06:55:24 kongoni32 kernel: cdc_acm 1-2:1.3: ttyACM1: USB ACM device

Dunno. You'll need to talk to the author of that device driver. It's
not part of pppd and really has nothing to do with PPP; it's a Linux
kernel module.

Post by dog
Jul 12 06:55:25 kongoni32 kernel: usb0: register 'cdc_ether' at
usb-0000:00:04.1-2, CDC Ethernet Device, 02:2f:28:9d:4b:9f
Jul 12 06:55:25 kongoni32 kernel: usbcore: registered new interface driver
cdc_ether

"ether?" I don't know much about that device, but it sure looks to me
like it wants to use Ethernet-like protocol rather than PPP. Or maybe
(YUCK!) it wants PPPoE?