Re: wvdial problems
- From: ibuprofin@xxxxxxxxxxxxxxxxxxxxxx (Moe Trin)
- Date: Wed, 15 Aug 2007 22:08:39 -0500
On Wed, 15 Aug 2007, in the Usenet newsgroup comp.os.linux.misc, in article
<5ihnj6F3p5lfpU1@xxxxxxxxxxxxxxxxxx>, Gretch wrote:
Moe Trin <ibuprofin@xxxxxxxxxxxxxxxxxxxxxx> wrote:
OK - two things: 1. Are you absolutely positive that the ISP wants
the '@starband.net' part of the username?
Absolutely positive, yes.
Just checking - it's not at all common, but pppd isn't getting to the
place where the password is involved, so I can't tell one way or the
other. I'll make a note of this "different" ISP. ;-)
2. The password may need to be quoted if it has anything other
than the characters A-Za-z0-9 (alphanumerics only).
The password contains "&" and is quoted in /etc/ppp/{pap,chap}-secrets.
OK - we should be in business then.
$ cat /usr/local/bin/dialstarband
#!/bin/bash
exec /usr/sbin/pppd connect "/usr/sbin/chat -f /etc/ppp/dialscript" \
debug persist usepeerdns lock defaultroute noipdefault nodetach \
/dev/ttyS1 115200 crtscts user gretchen@xxxxxxxxxxxx
OK
$ cat /etc/ppp/dialscript
ABORT BUSY ABORT 'NO CARRIER' "" AT&F0S11=50 OK ATDTxxxxxxx CONNECT \d\c
OK
S11=50 simply controls the pulse rate, impatient as I am.
That's the minimum in many telephone systems - the defaults for a modem
are usually in the range of 60 to 90 (milliseconds). Unless you are
trying to dial a long (10 or more digit number), the time savings isn't
very much. I doubt it's relevant to our problem though.
$ cat /etc/ppp/*ap-secrets
gretchen@xxxxxxxxxxxx * "myPassword"
# [same for /etc/ppp/{pap,chap,srp}-secrets]
OK - one of those should work ;-)
The "usepeerdns" option allows the above symlink to be functional.
OK
$ grep -v "^#" /etc/ppp/options
$
Good - you know about scripting!
Serial connection established.
using channel 12
Using interface ppp0
Connect: ppp0 <--> /dev/ttyS1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xb51d9a8e> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xb51d9a8e> <pcomp> <accomp>]
That looks OK, but I'd sure like to have seen the timestamps to the left.
There is a failure mode where the responses only occur at 19 second
intervals. This indicates a serial port IRQ problem. I _think_ that the
earlier posts of the wvdial output suggests this is not the case.
Modem hangup
Connection terminated.
Terminating on signal 2. # Ctrl-C applied.
Did they hang up on you, or was that the result of you doing a ^C? I have
seen some PoPs take as long as ten seconds (3 or 4 'sent [LCP ConfReq'
cycles] before they pull their finger out and start talking back.
It seems to send but not receive the response ... is there some other
pppd option required? ... "passive" doesn't alter the result ...
No, this should be working. Let's change the call to 'chat' from 'chat
-f' to 'chat -vf' which turns on logging out of the chat script.
/etc/syslog.conf needs to stick daemon.=debug (for pppd) and local2.=info
(for chat) into a convenient place.
http://linux.die.net/man/8/pppd has much to consider. I've been searching
the Usenet archives and the web for the possibility, as well as manually
trying sveral other options, but haven't yet found it or them.
One thing we're missing is some details. What distribution? What modem?
What version of pppd? This smells of a modem/serial problem rather
than a pppd problem, but I can't see anything yet.
Thank you for your most excellent advice.
Hold off on the thanks until we get it working ;-)
Old guy
.
- Follow-Ups:
- Re: wvdial problems
- From: Gretch
- Re: wvdial problems
- References:
- wvdial problems
- From: Gretch
- Re: wvdial problems
- From: Igmar Palsenberg
- Re: wvdial problems
- From: Gretch
- Re: wvdial problems
- From: Moe Trin
- Re: wvdial problems
- From: Gretch
- wvdial problems
- Prev by Date: Re: /dev/random entropy population
- Next by Date: exhibition rather than dancer woulds necessarily
- Previous by thread: Re: wvdial problems
- Next by thread: Re: wvdial problems
- Index(es):
Relevant Pages
|
