ppp trouble - part 2

I've installed Mandrake 10.1 on my laptop but am still unable to maintain
a connection to my ISP using my Zonet ZFM5600-CF pcmcia modem.

I set up KPPP with the following results:

Mar 10 23:26:20 peabody kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Mar 10 23:26:20 peabody cardmgr[2313]: socket 1: Serial or Modem
Mar 10 23:26:20 peabody kernel: ttyS0 at I/O 0x3f8 (irq = 3) is a 16550A
Mar 10 23:31:46 peabody kernel: CSLIP: code copyright 1989 Regents of the University of California
Mar 10 23:31:46 peabody kernel: PPP generic driver version 2.4.2
Mar 10 23:31:46 peabody pppd[5306]: pppd 2.4.2 started by joe, uid 501
Mar 10 23:31:46 peabody pppd[5306]: Using interface ppp0
Mar 10 23:31:46 peabody pppd[5306]: Connect: ppp0 <--> /dev/ttyS0
Mar 10 23:31:46 peabody pppd[5306]: PAP authentication succeeded
Mar 10 23:31:47 peabody kernel: PPP BSD Compression module registered
Mar 10 23:31:47 peabody kernel: PPP Deflate Compression module registered
Mar 10 23:31:47 peabody pppd[5306]: not replacing existing default route to eth0 [192.168.1.1]
Mar 10 23:31:47 peabody pppd[5306]: local IP address 4.155.51.134
Mar 10 23:31:47 peabody pppd[5306]: remote IP address 209.247.22.50
Mar 10 23:31:47 peabody pppd[5306]: primary DNS address 209.244.0.3
Mar 10 23:31:47 peabody pppd[5306]: secondary DNS address 209.244.0.4
Mar 10 23:33:38 peabody pppd[5306]: Hangup (SIGHUP)
Mar 10 23:33:38 peabody pppd[5306]: Modem hangup
Mar 10 23:33:38 peabody pppd[5306]: Connection terminated.
Mar 10 23:33:38 peabody pppd[5306]: Connect time 1.9 minutes.
Mar 10 23:33:38 peabody pppd[5306]: Sent 87 bytes, received 378 bytes.
Mar 10 23:33:38 peabody pppd[5306]: Connect time 1.9 minutes.
Mar 10 23:33:38 peabody pppd[5306]: Sent 87 bytes, received 378 bytes.
Mar 10 23:33:38 peabody pppd[5306]: Exit.


At this point I realized I had a default route to my ethernet card and issued
'/sbinroute del default'. I also edited my '/etc/ppp/options' file deleting
the 'usepeerdns' and 'noipdefault' so now my options file contains: crtsrcts,
defaultroute and noauth. Now KPPP gives:


Mar 10 23:52:23 peabody pppd[6257]: pppd 2.4.2 started by joe, uid 501
Mar 10 23:52:23 peabody pppd[6257]: Using interface ppp0
Mar 10 23:52:23 peabody pppd[6257]: Connect: ppp0 <--> /dev/ttyS0
Mar 10 23:52:53 peabody pppd[6257]: LCP: timeout sending Config-Requests
Mar 10 23:52:53 peabody pppd[6257]: Connection terminated.
Mar 10 23:52:53 peabody pppd[6257]: Exit.

I forgot the debug option but wanted to check before trying anything else.
Any ideas?

--
clear skies,
Joe

http://users.erols.com/jringer3/astro1.htm

Joe R <(E-Mail Removed)> wrote:
> I've installed Mandrake 10.1 on my laptop but am still unable to
> maintain a connection to my ISP using my Zonet ZFM5600-CF pcmcia
> modem.

> I set up KPPP with the following results:

> Mar 10 23:26:20 peabody kernel: cs: memory probe 0xa0000000-0xa0ffffff:
> clean.
> Mar 10 23:26:20 peabody cardmgr[2313]: socket 1: Serial or Modem
> Mar 10 23:26:20 peabody kernel: ttyS0 at I/O 0x3f8 (irq = 3) is a 16550A

I'm not sure this has anything to do with the problem but IRQ 4 is
the usual IRQ configured for ttyS0 and one of any serial devices
built into MBs these days usually matches that. IRQ 3 is correct
only if the card's serial device actually uses IRQ3. IRQ 3 is the
usual IRQ configured for ttyS1. Perhaps cardmgr or kppp checks and
does the right thing since the connections succeed.

> Mar 10 23:31:46 peabody kernel: CSLIP: code copyright 1989 Regents of
> the University of California
> Mar 10 23:31:46 peabody kernel: PPP generic driver version 2.4.2
> Mar 10 23:31:46 peabody pppd[5306]: pppd 2.4.2 started by joe, uid 501
> Mar 10 23:31:46 peabody pppd[5306]: Using interface ppp0
> Mar 10 23:31:46 peabody pppd[5306]: Connect: ppp0 <--> /dev/ttyS0
> Mar 10 23:31:46 peabody pppd[5306]: PAP authentication succeeded
> Mar 10 23:31:47 peabody kernel: PPP BSD Compression module registered
> Mar 10 23:31:47 peabody kernel: PPP Deflate Compression module registered
> Mar 10 23:31:47 peabody pppd[5306]: not replacing existing default route
> to eth0 [192.168.1.1]
> Mar 10 23:31:47 peabody pppd[5306]: local IP address 4.155.51.134
> Mar 10 23:31:47 peabody pppd[5306]: remote IP address 209.247.22.50
> Mar 10 23:31:47 peabody pppd[5306]: primary DNS address 209.244.0.3
> Mar 10 23:31:47 peabody pppd[5306]: secondary DNS address 209.244.0.4
> Mar 10 23:33:38 peabody pppd[5306]: Hangup (SIGHUP)
> Mar 10 23:33:38 peabody pppd[5306]: Modem hangup
> Mar 10 23:33:38 peabody pppd[5306]: Connection terminated.
> Mar 10 23:33:38 peabody pppd[5306]: Connect time 1.9 minutes.
> Mar 10 23:33:38 peabody pppd[5306]: Sent 87 bytes, received 378 bytes.
> Mar 10 23:33:38 peabody pppd[5306]: Connect time 1.9 minutes.
> Mar 10 23:33:38 peabody pppd[5306]: Sent 87 bytes, received 378 bytes.
> Mar 10 23:33:38 peabody pppd[5306]: Exit.


> At this point I realized I had a default route to my ethernet
> card and issued '/sbinroute del default'. I also edited my
> '/etc/ppp/options' file deleting the 'usepeerdns' and 'noipdefault'
> so now my options file contains: crtsrcts, defaultroute and
> noauth. Now KPPP gives:


> Mar 10 23:52:23 peabody pppd[6257]: pppd 2.4.2 started by joe, uid 501
> Mar 10 23:52:23 peabody pppd[6257]: Using interface ppp0
> Mar 10 23:52:23 peabody pppd[6257]: Connect: ppp0 <--> /dev/ttyS0
> Mar 10 23:52:53 peabody pppd[6257]: LCP: timeout sending Config-Requests
> Mar 10 23:52:53 peabody pppd[6257]: Connection terminated.
> Mar 10 23:52:53 peabody pppd[6257]: Exit.

> I forgot the debug option but wanted to check before trying
> anything else. Any ideas?

Hello again.

Adding the debug option isn't likely to help. The 30 second LCP
timeout is almost always a sign that 10 LCP Configure-Requests
were sent, there was no response by the peer, and so pppd exited.
(BTW, somewhere there has to be another file used by pppd or kppp
that contains at least the pppd option "user <Your_ISP_Username>"
since PAP authentication occurred when a PPP link was established
before the hangup in the first instance.)

Something weird may be happening as a result of the hangup - it's
very hard for me to believe that the modified options file causes
the problem. Do you know whether or not the LCP timeout still
happens with the modified options file if you shutdown the laptop,
turn it completely off, and then turn it back on and try to connect?

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." Benjamin Franklin */

On Fri, 11 Mar 2005 15:11:45 -0600, Clifford Kite wrote:
>
>
>> At this point I realized I had a default route to my ethernet
>> card and issued '/sbinroute del default'. I also edited my
>> '/etc/ppp/options' file deleting the 'usepeerdns' and 'noipdefault'
>> so now my options file contains: crtsrcts, defaultroute and
>> noauth. Now KPPP gives:
>
>
>> Mar 10 23:52:23 peabody pppd[6257]: pppd 2.4.2 started by joe, uid 501
>> Mar 10 23:52:23 peabody pppd[6257]: Using interface ppp0
>> Mar 10 23:52:23 peabody pppd[6257]: Connect: ppp0 <--> /dev/ttyS0
>> Mar 10 23:52:53 peabody pppd[6257]: LCP: timeout sending Config-Requests
>> Mar 10 23:52:53 peabody pppd[6257]: Connection terminated.
>> Mar 10 23:52:53 peabody pppd[6257]: Exit.
>
>> I forgot the debug option but wanted to check before trying
>> anything else. Any ideas?
>
> Hello again.
>
> Adding the debug option isn't likely to help. The 30 second LCP
> timeout is almost always a sign that 10 LCP Configure-Requests
> were sent, there was no response by the peer, and so pppd exited.
> (BTW, somewhere there has to be another file used by pppd or kppp
> that contains at least the pppd option "user <Your_ISP_Username>"
> since PAP authentication occurred when a PPP link was established
> before the hangup in the first instance.)
>
> Something weird may be happening as a result of the hangup - it's
> very hard for me to believe that the modified options file causes
> the problem. Do you know whether or not the LCP timeout still
> happens with the modified options file if you shutdown the laptop,
> turn it completely off, and then turn it back on and try to connect?

Hadn't tried that, but there have been several developments.

1. Manufacture told me to return it because it should have been fine
under XP. So I sent it back for replacement.

2. I used the scanmodem program to probe my internal winmodem while
the pcmcia card was still installed. Turns out the pcmcia modem is a
winmodem needing the 'slhc.ko.gz' driver, which comes with Mandrake.

But...
"Intel, Agere Systems and Linuxant are firmly expected to continue
support into 2.6.nn, though the Intel HaM software will not be
updated to 2.6.n service"

Looks like a good replacement might not be a viable modem with Linux?
Guess I'll find out.:-)

--
clear skies,
Joe

http://users.erols.com/jringer3/astro1.htm

Joe R <(E-Mail Removed)> wrote:
> On Fri, 11 Mar 2005 15:11:45 -0600, Clifford Kite wrote:

>> Something weird may be happening as a result of the hangup - it's
>> very hard for me to believe that the modified options file causes
>> the problem. Do you know whether or not the LCP timeout still
>> happens with the modified options file if you shutdown the laptop,
>> turn it completely off, and then turn it back on and try to connect?

> Hadn't tried that, but there have been several developments.

> 1. Manufacture told me to return it because it should have been fine
> under XP. So I sent it back for replacement.

> 2. I used the scanmodem program to probe my internal winmodem while
> the pcmcia card was still installed. Turns out the pcmcia modem is a
> winmodem needing the 'slhc.ko.gz' driver, which comes with Mandrake.

> But...
> "Intel, Agere Systems and Linuxant are firmly expected to continue
> support into 2.6.nn, though the Intel HaM software will not be
> updated to 2.6.n service"

> Looks like a good replacement might not be a viable modem with Linux?
> Guess I'll find out.:-)

If the PCMCIA modem card is replaced with one that works under XP
then it might work for you under Linux. Since the log for pppd
where PPP negotiations reached CCP negotiations showed IP addresses
negotiated later, even though negotiating MS-PPC with MPPC failed,
there's a chance that it will work without CCP - despite my initial
comments about why the hangup occurred. When the replacement card
comes try it with the pppd noccp option added to find out.

Since the 2.6 series is up to 2.6.11 (and so into 2.6.nn), there's
hope for the winmodem too.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/

> Looks like a good replacement might not be a viable modem with Linux?
> Guess I'll find out.:-)

Have you tried putting "passive" on in your /etc/ppp/options file or as a
parm to pppd? I had a strange routing issue a long while ago and doing
just that fixed it. It also solved kppp's inabilities where wvdail didn't
have a problem. A lot of pppd settings are ISP specific though.

Shadow_7