Vodafone woes

Only able to get online briefly tonight, after getting home late from work, then eating, then playing with trying to get the Vodafone USB modem going for awhile.

I have it essentially setup like smokey01. And I tried the things he suggested.

However, before that, when I started Wary, mysteriously modeswitching started working again, and PupDial recognised /dev/ttyUSB1.

But, I have noticed something very strange in the PupDial log:

This is from smokey01:



I also have an APN entered in PupDial, but this is my log:



...why doesn't it send the APN info, as in smokey01's case?

My wvdial.conf has:

---

Comments

different numbers
Username: 01micko
looking at that, smokey has [i]*99***1#[/i] whereas you have *99# . ??? (.. and is smokey's log that old?) Cheers

Re smokey01 diffs
Username: BarryK
"Smokey01 would be using an older version of PupDial. '*99#' is what the Vodafone docs say to use. But, I did try '*99***1' made no difference.

missing #
Username: aarf
"*99***1# you are still missing the hash# of the end of the number. try this exact sequence: firstly always plug in the turn-on phone (usb modem dongle) when you boot not plug-in after you boot. second if it fails to auto-connect in puppeee1/fluppy4 you need to disconnect the usb cable from the laptop and then reconnect the USB cable (usb mod dongle), then reboot with the cable still connected plugged in. if the icons show that there is no connection still try the browser because it may be connected but the icons say that it isn't.

missing lines
Username: zygo
"That's a very small wvdial.conf ! Was it made by Pupdial?

Huawei E1552
Username: Raffy
"There were noted problems in the use of 3G device in Puppy, so I add my own experience here and hope that it could help diagnose the problem. Here is the output of pgprs-connect in Quirky 130 (Device works even when plugged in after boot): [code]Press CTRL-C to close the connection at any stage! defining PDP context... AT OK AT+CPIN="1234" ERROR AT+CGDCONT=1,"IP","Correct-APN-was-here" OK ATH OK ATE1 OK AT+CSQ waiting for connect... +CSQ: 99,99 OK ATD*99***1# NO CARRIER Connect script failed Exit status is 0 DISCONNECTED Press ENTER to quit Press r ENTER to reconnect/try again[/code] Some notes: 1. Is it proper that the PIN is sent at the beginning? (Anyway, there is an error there-I have not changed any PIN, so there should be no error.) 2. No carrier error: Is the connect script strict as to the protocol used? This ISP offers CHAP while others use PAP. Are there settings in /etc/ppp that should be changed? Or is the error simply in the "ATD" (should it be ATDT instead)?

re: chap
Username: 01micko
"As Raffy said 2 posts ago, and I needed for my virgin modem, maybe appending [i]-chap[/i] (under barney) to /etc/ppp/options would work.? (Even though Virgin say it is pap authentication). I did set up some Vodafone dongles awhile ago, but forget the settings! Cheers

Vodafone
Username: wombat01
"Barry, I am unable to do any testing at the moment as my friend has my modem in Katherine. She tells me it is working fine. My modem is a different model to yours which may make a difference. There is plenty of information in the forums where rerwin and I were testing my modem. I did have trouble with the latest version of puppeee as it would not connect but the previous release did. It sounds like you may be having a similar problem. rerwin (Richard) would be the best person to assist. Smokey01

Registration
Username: alec78
"Barrie, It is frequently posted on the web that a 3G USB modem needs to be used initially under Windows, I think this is to facilitate registration of the modem with the ISP. BTW I use *99# when setting up PupDial, and did you tick the Stupid Mode box? In addition I would suggest using a previous variant of Puppy, i.e. one not using the latest kernel. Things have taken a backward step re 3g USB modems with the latest kernel, I had to go back to running modprobe to get my E169G recognised under lupu-512.

My HowTo
Username: ecube
"This is my humble "HowTo" 1. Use PupDial to identify the modem. 2. Close PupDial. (If you use it, it will overwrite wvdial.conf) 3. Create the file /etc/wvdial.conf [code] [Dialer Defaults] Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Init3 = AT+CGDCONT=1,"IP","--- your APN ---" Password = internet Phone = *99# Modem Type = USB Modem Stupid Mode = 1 Baud = 460800 Dial Command = ATDT Modem = /dev/ttyUSB0 ISDN = 0 Username = gprs [/code] 4. run /usr/bin/wvdialshell.

Register User First in Windows
Username: Raffy
"Thanks for the reminder, alec78. (In my case,) Not even the carrier's documentation states that profile registration and selection of network type (under Tools-Options) are needed before the device can be used.

Success with Quirky Retro 120 (Firefox)
Username: Raffy
"Having registered my profile in Windows and chosen "3G preferred" in the network type, I retried plugging the device (as Grub is booting Quirky retro 120) and had success. Mysteriously, the dialup number (which worked OK) changed to *99# when I was filling in my profile (in Windows). The menu used to display *99***1# Bottomline - it's slow (compared to 512kbps broadband).

UMTS wvdial APN vodafone
Username: proformix
"Hi Barry Perhaps you should check the APN if it is correct - try AT+CGDCONT? in e.g. picocom: My example: At+cgdcont? +CGDCONT: 1,"IP","xyz","0.0.0.0",0,0 OK

T Mobile UK
Username: BitcoinAde
"I'm having similar problems with a TMobile dongle in the UK, worked great on both windows and puppy, then for some reason it stopped, by then I had several versions of Puppy distribution on various DVDS, tried them all, same problem, yet still works fine on windows. My conclusion is that the modem has 'changed' somehow, either it's firmware has been upgraded remotely, or it is suffering from getting too hot internally. The reason I say that is that occaisionally, it will work again on Puppy. I eithere get the Bad Sim error or it goes through the process of connecting and then repeatedly falls over again Here is the output. --> Sending: AT+CGDCONT=1,"IP","preconnect" AT+CGDCONT=1,"IP","preconnect" OK --> Modem initialized. --> Sending: ATDT*99# --> Waiting for carrier. ATDT*99# CONNECT --> Carrier detected. Starting PPP immediately. --> Starting pppd at Mon Jun 18 23:47:25 2012 --> pid of pppd: 20043 --> Disconnecting at Mon Jun 18 23:47:26 2012 --> The PPP daemon has died: A modem hung up the phone (exit code = 16) --> man pppd explains pppd error codes in more detail. --> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information. --> Auto Reconnect will be attempted in 5 seconds --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 ATQ0 V1 E1 S0=0 &C1 &D2 OK --> Sending: AT+CGDCONT=1,"IP","preconnect" AT+CGDCONT=1,"IP","preconnect" OK --> Modem initialized.

Dont overstep the load limit
Username: K Godt
"BitcoinAde, I have the same problem when i overstepped the 5GB up/down load limit that puts me back into ISDN-64Kb/s-8KB/s mode . Both pgprs-connect and pupdial . Both providers . This did not happened much but i think it happened and was no problem before . The one modem/provider gives me always no carrier and the other hangs the modem or does not send magics back to me . I am guessing an AT command would do it, but have not found out for now . The hints in which pupdial did not work for me to force 2G, mainly because my modem accepts only three variable for AT+COPS=0,1,2 .

Tags: wary