Re: wvdial problems

In news:slrnfc7ftd.3er.ibuprofin@xxxxxxxxxxxxxxxxx,
Moe Trin <ibuprofin@xxxxxxxxxxxxxxxxxxxxxx> wrote:

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.

Sorry, the time diff was 3 seconds between the "sent [", as indicated below
in the more complete "chat -vf" output.

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.

I'm inclined to agree with you, because the modem works flawlessly when
connecting to a different ISP.

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 did a ^C to interrupt the repeated dialings caused by the "persist"
option, but it seems to my limited understanding as if the ISP's peer
(actually, the "contracted authentication service" according to their
Support people) is dropping the connection before the default (? since no
man page due to small HD) lcp-max-configure 10 is reached.

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.

I suspect that's the case here, but I've tried the lcp-restart 10 option in
an effort to delay the 3-second interval, but it causes the Modem hangup
before the second "sent [LCP ...", re-enforcing the perception that it's the
ISP terminating the connection for some arcane reason. I posted a request to
an M$ newsgroup hoping for a method to log the details of the successful
dialup that occurs using that OS.

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.

$ grep ppp /etc/syslog.conf
# ppp dialup messages
local2.=info;daemon.=debug /var/log/ppp-debug.log

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.

I both respect and trust your judgement, but am reluctant to conclude a
modem/serial problem unless this particular ISP is addressing some feature
that the modem/serial/pppd combination is incapable of completing for some
reason; it works fine with other ISPs.

RH7.1 Linux version 2.4.20-28.7 (yes, ancient OS on an ancient box with a
tiny HD, used solely as an iptables-protected router with no other services
for a LAN; I will endure the inevitable scolding in order to solve the
dialup problem with this one ISP, thanks. I've assaulted this box from
outside to my satisfaction and it drops all but related, established packets
to other machines on the LAN with more modern, robust OS's)

$ pppd --version
pppd version 2.4.1 #yupper, also ancient

Relevant (?) extracts from dmesg:
Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ
SERIAL_PCI ISAPNP enabled
ttyS0 at 0x03f8 (irq = 4) is a 16550A
ttyS1 at 0x02f8 (irq = 3) is a 16550A
ttyS2 at 0x03e8 (irq = 4) is a 16550A
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2

$ cat /proc/interrupts
CPU0
0: 1869444 XT-PIC timer
1: 3 XT-PIC keyboard
2: 0 XT-PIC cascade
8: 9 XT-PIC rtc
11: 18282 XT-PIC eth0
14: 17940 XT-PIC ide0
15: 0 XT-PIC ide1
NMI: 0
ERR: 0

I'm not sure how to identify the modem itself without excavating it from the
box (and perhaps not even then), but I'll do that if you think it's
necessary. It's a card rather than integral w/ the backplane, but there's no
info about it in /proc/pci, or /var/log/{messages,boot.log} that I can find.

Currently, after 3 "persist" dialings and ^C:
Aug 15 22:29:24 linux0 chat[4034]: abort on (BUSY)
Aug 15 22:29:24 linux0 chat[4034]: abort on (NO CARRIER)
Aug 15 22:29:24 linux0 chat[4034]: send (AT&F0S11=50^M)
Aug 15 22:29:25 linux0 chat[4034]: expect (OK)
Aug 15 22:29:25 linux0 chat[4034]: AT&F0S11=50^M^M
Aug 15 22:29:25 linux0 chat[4034]: OK
Aug 15 22:29:25 linux0 chat[4034]: -- got it
Aug 15 22:29:25 linux0 chat[4034]: send (ATDTxxxxxxx^M)
Aug 15 22:29:25 linux0 chat[4034]: expect (CONNECT)
Aug 15 22:29:25 linux0 chat[4034]: ^M
Aug 15 22:29:43 linux0 chat[4034]: ATDTxxxxxxx^M^M
Aug 15 22:29:43 linux0 chat[4034]: CONNECT
Aug 15 22:29:43 linux0 chat[4034]: -- got it
Aug 15 22:29:43 linux0 chat[4034]: send (\dc^M^M)
Aug 15 22:29:44 linux0 pppd[4033]: using channel 17
Aug 15 22:29:45 linux0 pppd[4033]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magic 0xa38e6a4a> <pcomp> <accomp>]
Aug 15 22:29:48 linux0 pppd[4033]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magic 0xa38e6a4a> <pcomp> <accomp>]
Aug 15 22:30:21 linux0 chat[4067]: abort on (BUSY)
Aug 15 22:30:21 linux0 chat[4067]: abort on (NO CARRIER)
Aug 15 22:30:21 linux0 chat[4067]: send (AT&F0S11=50^M)
Aug 15 22:30:21 linux0 chat[4067]: expect (OK)
Aug 15 22:30:21 linux0 chat[4067]: AT&F0S11=50^M^M
Aug 15 22:30:21 linux0 chat[4067]: OK
Aug 15 22:30:21 linux0 chat[4067]: -- got it
Aug 15 22:30:21 linux0 chat[4067]: send (ATDTxxxxxxx^M)
Aug 15 22:30:21 linux0 chat[4067]: expect (CONNECT)
Aug 15 22:30:21 linux0 chat[4067]: ^M
Aug 15 22:30:39 linux0 chat[4067]: ATDTxxxxxxx^M^M
Aug 15 22:30:39 linux0 chat[4067]: CONNECT
Aug 15 22:30:39 linux0 chat[4067]: -- got it
Aug 15 22:30:39 linux0 chat[4067]: send (\dc^M^M)
Aug 15 22:30:40 linux0 pppd[4033]: using channel 18
Aug 15 22:30:41 linux0 pppd[4033]: sent [LCP ConfReq id=0x2 <asyncmap 0x0>
<magic 0x9ae89157> <pcomp> <accomp>]
Aug 15 22:30:44 linux0 pppd[4033]: sent [LCP ConfReq id=0x2 <asyncmap 0x0>
<magic 0x9ae89157> <pcomp> <accomp>]
Aug 15 22:31:17 linux0 chat[4091]: abort on (BUSY)
Aug 15 22:31:17 linux0 chat[4091]: abort on (NO CARRIER)
Aug 15 22:31:17 linux0 chat[4091]: send (AT&F0S11=50^M)
Aug 15 22:31:17 linux0 chat[4091]: expect (OK)
Aug 15 22:31:17 linux0 chat[4091]: AT&F0S11=50^M^M
Aug 15 22:31:17 linux0 chat[4091]: OK
Aug 15 22:31:17 linux0 chat[4091]: -- got it
Aug 15 22:31:17 linux0 chat[4091]: send (ATDTxxxxxxx^M)
Aug 15 22:31:18 linux0 chat[4091]: expect (CONNECT)
Aug 15 22:31:18 linux0 chat[4091]: ^M
Aug 15 22:31:36 linux0 chat[4091]: ATDTxxxxxxx^M^M
Aug 15 22:31:36 linux0 chat[4091]: CONNECT
Aug 15 22:31:36 linux0 chat[4091]: -- got it
Aug 15 22:31:36 linux0 chat[4091]: send (\dc^M^M)
Aug 15 22:31:37 linux0 pppd[4033]: using channel 19
Aug 15 22:31:38 linux0 pppd[4033]: sent [LCP ConfReq id=0x3 <asyncmap 0x0>
<magic 0x9dc42833> <pcomp> <accomp>]



.

Relevant Pages

  • Re: Is there a minimum dialup speed that Vista can cope with?
    ... I no longer ring Eircom ... internet/phone bundle with another ISP, UTV (Eircom just rakes in the line ... I'm keeping modem logs because the line quality fluctuates many times ... hardware/software to fail with this slow connection. ...
    (microsoft.public.windows.vista.networking_sharing)
  • Re: wvdial problems
    ... when connecting to a different ISP. ... OK - that basically rules out the modem. ... Support people) is dropping the connection before the default (? ... I've subscribed to a new ISP where the local dialup number ...
    (comp.os.linux.misc)
  • Re: [SLE] Dialup problems
    ... What I have is a normal external 56k modem. ... Break the connection manually. ... # Defaultroute: no: pppd will not set the default route to the remote ip ...
    (SuSE)
  • Re: Creating ISP connection ADSL
    ... The ISP is Wanadoo. ... The ADSL modem is an Alcatel ... I cannot get it to create a new connection icon ... THE MODEM ATTACHED and DO NOT plug it in until indicated by the installation ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: often need to stop and start DNS service....
    ... If the ISP is re-initializing the cable modem, ... > (DHCP clients renew at some percentage of lease expiration, ... Linksys or Netgear for my connection ...
    (microsoft.public.win2000.dns)