Re: PPP trashed in 2.1.109?

Bruce A. Locke (blocke@lizard.org)
Sat, 18 Jul 1998 01:13:57 -0400 (EDT)


> On Fri, 17 Jul 1998, Bruce A. Locke wrote:
>
> > Hello...
> >
> > As the subject states I believe that PPP in 2.1.109 is trashed. I have
> > spoken to several ppl on irc and have heard a report of one person's kernel
> > "sending fragmented packets from random ip sources". While I have not had
> > this problem, my problem with 2.1.109 is worse... I can't even connect.
> >
> > The same exact script and config files that work perfect (ie: first time,
> > 99% of the time) with 2.1.106 work 0.001% of the time with 2.1.109.
> > It's _not_ the script!!!! :)
> >
> > The following is a snippet from my /var/log/messages file:
> >
> [...]
> > Jul 17 15:48:21 capsize pppd[370]: LCP: timeout sending Config-Requests
> [...]
>

Ok... I followed the suggestions posted on here which were to upgrade pppd
(I am now running 2.3.5) and make sure I was using the passive flag (which I
have been doing since I started working with linux :)

Nothing has changed. I still get that damn LCP error with 2.1.109 and I
can't figure it out. :/ The scripts work perfectly fine with 2.1.106 and just
don't work with 2.1.109. The only change was the kernel.

But to prove that it wasn't a script/config problem I read the ppp docs and
man page and whipped up a custom pppd command (which I type in manually).
Again it works fine first try with 2.1.106 with both my original version of
pppd and 2.3.5.

Here is the line:

pppd connect 'chat -v "" ATDT2232000 CONNECT "" ogin: myuserid word: \
mypassword' /dev/ttyS2 115200 debug crtscts modem defaultroute passive \
noipdefault

The line works with 2.1.106 but not with 2.1.109 (thus proving that my
problem does not involve redhat's ifup, etc.)

The following is an example of the log when I fiddled with kdebug:

Jul 18 00:52:30 capsize pppd[571]: pppd 2.3.5 started by root, uid 0
Jul 18 00:52:31 capsize chat[572]: send (ATDT2232000^M)
Jul 18 00:52:31 capsize chat[572]: expect (CONNECT)
Jul 18 00:52:54 capsize chat[572]: ATDT2232000^M^M
Jul 18 00:52:54 capsize chat[572]: CONNECT
Jul 18 00:52:54 capsize chat[572]: -- got it
Jul 18 00:52:54 capsize chat[572]: send (^M)
Jul 18 00:52:54 capsize chat[572]: expect (ogin:)
Jul 18 00:52:54 capsize chat[572]: 115200^M
[.. snip isp's /etc/issue, etc ..]
Jul 18 00:52:56 capsize chat[572]: 1-S6 login:
Jul 18 00:52:56 capsize chat[572]: -- got it
Jul 18 00:52:56 capsize chat[572]: send (myuserid^M)
Jul 18 00:52:56 capsize chat[572]: expect (word:)
Jul 18 00:52:56 capsize chat[572]: myuserid^M
Jul 18 00:52:56 capsize chat[572]: Password:
Jul 18 00:52:56 capsize chat[572]: -- got it
Jul 18 00:52:56 capsize chat[572]: send (mypassword^M)
Jul 18 00:52:57 capsize pppd[571]: Serial connection established.
Jul 18 00:52:58 capsize kernel: ppp_ioctl: set dbg flags to 190000
Jul 18 00:52:58 capsize kernel: ppp_ioctl: set flags to 190000
Jul 18 00:52:58 capsize kernel: ppp_tty_ioctl: set xasyncmap
Jul 18 00:52:58 capsize kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jul 18 00:52:58 capsize kernel: ppp_ioctl: set flags to 190000
Jul 18 00:52:58 capsize kernel: ppp_ioctl: set mru to 5dc
Jul 18 00:52:58 capsize kernel: ppp_tty_ioctl: set rcv asyncmap 0
Jul 18 00:52:58 capsize pppd[571]: Using interface ppp0
Jul 18 00:52:58 capsize pppd[571]: Connect: ppp0 <--> /dev/ttyS2
Jul 18 00:52:58 capsize kernel: ppp_ioctl: set flags to 190000
Jul 18 00:53:28 capsize pppd[571]: LCP: timeout sending Config-Requests
Jul 18 00:53:58 capsize kernel: ppp: channel ppp0 closing.
Jul 18 00:53:58 capsize pppd[571]: Hangup (SIGHUP)
Jul 18 00:53:58 capsize pppd[571]: Modem hangup
Jul 18 00:53:58 capsize pppd[571]: Connection terminated.
Jul 18 00:53:59 capsize pppd[571]: Exit.

The following is a section of my /var/log/messages for when PPP successfully
connects under 2.1.106 with the same pppd command:

Jul 18 01:00:46 capsize pppd[357]: Serial connection established.
Jul 18 01:00:47 capsize kernel: ppp_tty_ioctl: set flags to 190000
Jul 18 01:00:47 capsize kernel: ppp_tty_ioctl: set flags to 190000
Jul 18 01:00:47 capsize kernel: ppp_tty_ioctl: set xasyncmap
Jul 18 01:00:47 capsize kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jul 18 01:00:47 capsize kernel: ppp_tty_ioctl: set flags to 190000
Jul 18 01:00:47 capsize kernel: ppp_tty_ioctl: set mru to 5dc
Jul 18 01:00:47 capsize kernel: ppp_tty_ioctl: set rcv asyncmap 0
Jul 18 01:00:47 capsize kernel: ppp_tty_ioctl: set flags to 190000
Jul 18 01:00:47 capsize pppd[357]: Using interface ppp0
Jul 18 01:00:47 capsize pppd[357]: Connect: ppp0 <--> /dev/ttyS2
Jul 18 01:00:49 capsize kernel: ppp_tty_ioctl: set xmit asyncmap 0
Jul 18 01:00:49 capsize kernel: ppp_tty_ioctl: set flags to f190003
Jul 18 01:00:49 capsize kernel: ppp_tty_ioctl: set mru to 5dc
Jul 18 01:00:49 capsize kernel: ppp_tty_ioctl: set rcv asyncmap 0
Jul 18 01:00:49 capsize kernel: ppp_tty_ioctl: set flags to f190003
Jul 18 01:00:49 capsize kernel: ppp_tty_ioctl: set flags to f190043
Jul 18 01:00:49 capsize modprobe: can't locate module ppp-compress-21
Jul 18 01:00:49 capsize modprobe: can't locate module ppp-compress-26
Jul 18 01:00:49 capsize modprobe: can't locate module ppp-compress-24
Jul 18 01:00:49 capsize kernel: ppp_tty_ioctl: set maxcid to 16
Jul 18 01:00:49 capsize kernel: ppp_tty_ioctl: set flags to f19004f
Jul 18 01:00:49 capsize kernel: ppp: channel ppp0 going up for IP packets!
Jul 18 01:00:49 capsize pppd[357]: local IP address 209.203.144.9
Jul 18 01:00:49 capsize pppd[357]: remote IP address 209.203.129.1

The only reason I can think of is that ppp support in the kernel was broken
(at least partially) with the recent modifications of the pppd code.
Please someone prove me wrong :)

----------------------------------------------------------------------
Bruce A. Locke blocke@lizard.org
http://www.lizard.org/blocke/
http://www.lizard.org/dragonlinux

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html