Feisty dialup connection problems

[sktsee]

On Sun, 27 May 2007 21:15:54 +0930, squareyes wrote:
[snip]
> 
> Have tried default isp, and including my isp name, in pppconfig setup no 
> difference.  (pon   pon internode)
> Log shows it's connecting then dropping out "refused"
> 
> May 27 14:11:02 here chat[5820]: ATDT0198331337^M^M
> May 27 14:11:02 here chat[5820]: CONNECT
> May 27 14:11:02 here chat[5820]:  -- got it
> May 27 14:11:02 here chat[5820]: send (\d)
> May 27 14:11:03 here pppd[5814]: Serial connection established.
> May 27 14:11:03 here pppd[5814]: Using interface ppp0
> May 27 14:11:03 here pppd[5814]: Connect: ppp0 <--> /dev/ttyS2
> May 27 14:11:05 here pppd[5814]: Remote message: Request Denied
> May 27 14:11:05 here pppd[5814]: Connection terminated.
> May 27 14:11:06 here pppd[5814]: Exit.
> 

I use dial-up as well, and comparing your log snippet with one from my
machine below, it seems to point to an authentication problem.

May 27 07:31:16 quark chat[5051]: CONNECT
May 27 07:31:16 quark chat[5051]:  -- got it 
May 27 07:31:16 quark chat[5051]: send (\d)
May 27 07:31:17 quark pppd[5049]: Serial connection established.
May 27 07:31:17 quark pppd[5049]: Using interface ppp0
May 27 07:31:17 quark pppd[5049]: Connect: ppp0 <--> /dev/ttySM0
May 27 07:31:19 quark pppd[5049]: PAP authentication succeeded
May 27 07:31:19 quark kernel: [ 1059.963103] PPP BSD Compression module registered
May 27 07:31:19 quark kernel: [ 1060.035508] PPP Deflate Compression module registered

To further diagnose your ppp connection, I would recommend examining the
ppp session setup between your machine and your ISP. You can do that by
enabling the debug option for pppd in /etc/ppp/options. Look for #debug
and uncomment the line. The debugging output will be in /var/log/syslog
despite what's written in /etc/ppp/options or the pppd or chat manpages.

Here's what you should see when you try to connect:
(watchout for wrap)

May 27 08:40:25 quark chat[6700]: CONNECT
May 27 08:40:25 quark chat[6700]:  -- got it 
May 27 08:40:25 quark chat[6700]: send (\d)
May 27 08:40:26 quark pppd[6698]: Serial connection established.
May 27 08:40:26 quark pppd[6698]: using channel 3
May 27 08:40:26 quark pppd[6698]: Using interface ppp0
May 27 08:40:26 quark pppd[6698]: Connect: ppp0 <--> /dev/ttySM0
May 27 08:40:27 quark pppd[6698]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x4b837727> <pcomp> <accomp>]
May 27 08:40:27 quark pppd[6698]: rcvd [LCP ConfReq id=0xca <asyncmap 0xa0000> <auth pap> <magic 0xa199da48> <pcomp> <accomp>]
May 27 08:40:27 quark pppd[6698]: sent [LCP ConfAck id=0xca <asyncmap 0xa0000> <auth pap> <magic 0xa199da48> <pcomp> <accomp>]
May 27 08:40:27 quark pppd[6698]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x4b837727> <pcomp> <accomp>]
May 27 08:40:27 quark pppd[6698]: sent [LCP EchoReq id=0x0 magic=0x4b837727]
May 27 08:40:27 quark pppd[6698]: sent [PAP AuthReq id=0x1 user="sktsee at tulsaconnect.com" password=<hidden>]
May 27 08:40:27 quark pppd[6698]: rcvd [LCP EchoRep id=0x0 magic=0xa199da48]
May 27 08:40:27 quark pppd[6698]: rcvd [PAP AuthAck id=0x1 ""]
May 27 08:40:27 quark pppd[6698]: PAP authentication succeeded
May 27 08:40:27 quark pppd[6698]: sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
May 27 08:40:27 quark pppd[6698]: sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]

The rest of the log covers ip address assignment and DNS, but what you are 
looking for is to make sure you get a successful authentication message. 
Of course if your are using a different authentication method other than PAP
(like CHAP), then you'll see a different confirmation message. 

[snip]

-- 
sktsee