Weird kppp/pppd problem

Weird kppp/pppd problem

Post by Stephen Marl » Thu, 22 Apr 1999 04:00:00



I'm running SuSE 6.0 with kernel 2.2.6 and since upgrading to KDE 1.1
I've had the strangest problem with kppp. Basically, the kppp with KDE
1.0 works perfectly but the 1.1 version either fails to connect (eg to
my work) or pppd spews out Protocol-Reject messages at a tremenous rate
(eg connecting to telinco).

The arguments to pppd are identical and lsmod looks fine in either case.
The only difference I've noticed is that kppp 1.1 loads the ppp module
upfront when it's invoked, whereas 1.0 leaves it to pppd.  I can't think
of any reason why they should behave differently as I thought that pppd
handled the protocol independently of kppp. Is there something weird
done to the line or the other end before ppp comes up?

I've included some log files in from each case. I haven't used the debug
option to pppd but if it will help someone diagnose the problem I'll
repost the gories. Any hints or advice would be greatly appreciated.

KDE 1.0 KPPP
------------
pppd /dev/ttyS0 38400 crtscts defaultroute -detach -chap user tfi000000

# less /var/log/messages
Apr 20 21:57:14 dewdrop kernel: CSLIP: code copyright 1989 Regents of the University of California
Apr 20 21:57:14 dewdrop kernel: PPP: version 2.3.3 (demand dialling)
Apr 20 21:57:14 dewdrop kernel: PPP line discipline registered.
Apr 20 21:57:14 dewdrop kernel: registered device ppp0
Apr 20 21:57:14 dewdrop pppd[783]: pppd 2.3.7 started by root, uid 0
Apr 20 21:57:14 dewdrop pppd[783]: Using interface ppp0
Apr 20 21:57:14 dewdrop pppd[783]: Connect: ppp0 <--> /dev/ttyS0
Apr 20 21:57:15 dewdrop pppd[783]: Remote message: ^F
Apr 20 21:57:15 dewdrop kernel: PPP BSD Compression module registered
Apr 20 21:57:15 dewdrop kernel: PPP Deflate Compression module registered
Apr 20 21:57:15 dewdrop pppd[783]: local  IP address 212.1.145.43
Apr 20 21:57:15 dewdrop pppd[783]: remote IP address 10.42.42.42
Apr 20 21:57:32 dewdrop pppd[783]: Terminating on signal 15.
Apr 20 21:57:38 dewdrop pppd[783]: Connection terminated.
Apr 20 21:57:38 dewdrop pppd[783]: Connect time 0.4 minutes.
Apr 20 21:57:38 dewdrop pppd[783]: Sent 405 bytes, received 374 bytes.
Apr 20 21:57:39 dewdrop pppd[783]: Exit.

KDE 1.1 KPPP
------------
pppd /dev/ttyS0 38400 crtscts defaultroute -detach -chap user tfi000000

# less /var/log/messages
Apr 20 21:51:22 dewdrop kernel: CSLIP: code copyright 1989 Regents of the University of California
Apr 20 21:51:23 dewdrop kernel: PPP: version 2.3.3 (demand dialling)
Apr 20 21:51:23 dewdrop kernel: PPP line discipline registered.
Apr 20 21:51:23 dewdrop kernel: registered device ppp0
Apr 20 21:51:55 dewdrop pppd[744]: pppd 2.3.7 started by root, uid 0
Apr 20 21:51:55 dewdrop pppd[744]: Using interface ppp0
Apr 20 21:51:55 dewdrop pppd[744]: Connect: ppp0 <--> /dev/ttyS0
Apr 20 21:51:55 dewdrop pppd[744]: Remote message: ^F
Apr 20 21:51:55 dewdrop kernel: PPP BSD Compression module registered
Apr 20 21:51:55 dewdrop kernel: PPP Deflate Compression module registered
Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported protocol 0x5265
Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported protocol 0x5072
Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported protocol 0x5072
Apr 20 21:51:56 dewdrop pppd[744]: local  IP address 212.1.147.200
Apr 20 21:51:56 dewdrop pppd[744]: remote IP address 10.42.42.42
Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported protocol 0x5072
Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported protocol 0x6c6f
Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported protocol 0x7265
Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported protocol 0x5072
Apr 20 21:52:27 dewdrop last message repeated 674 times
Apr 20 21:52:57 dewdrop last message repeated 670 times
Apr 20 21:52:57 dewdrop pppd[744]: Terminating on signal 15.
Apr 20 21:53:03 dewdrop pppd[744]: Connection terminated.
Apr 20 21:53:03 dewdrop pppd[744]: Connect time 1.2 minutes.
Apr 20 21:53:03 dewdrop pppd[744]: Sent 69483 bytes, received 81469 bytes.
Apr 20 21:53:04 dewdrop pppd[744]: Exit.

--
stephen

 
 
 

Weird kppp/pppd problem

Post by JanW. Roelof » Thu, 22 Apr 1999 04:00:00



> I'm running SuSE 6.0 with kernel 2.2.6 and since upgrading to KDE 1.1
> I've had the strangest problem with kppp. Basically, the kppp with KDE
> 1.0 works perfectly but the 1.1 version either fails to connect (eg to
> my work) or pppd spews out Protocol-Reject messages at a tremenous rate
> (eg connecting to telinco).

[ knip ]

Hi,

Try 'Pause 1' in the kppp Login Script. It worked for me.

--
Gr.
JW

 
 
 

Weird kppp/pppd problem

Post by Stephen Marl » Fri, 23 Apr 1999 04:00:00



> Try 'Pause 1' in the kppp Login Script. It worked for me.

I am using PAP.

--

 
 
 

Weird kppp/pppd problem

Post by Dan Glove » Sun, 25 Apr 1999 04:00:00




>I'm running SuSE 6.0 with kernel 2.2.6 and since upgrading to KDE 1.1
>I've had the strangest problem with kppp. Basically, the kppp with KDE
>1.0 works perfectly but the 1.1 version either fails to connect (eg to
>my work) or pppd spews out Protocol-Reject messages at a tremenous rate
>(eg connecting to telinco).

OK, you don't seem to have got much response, please bear in mind that I
don't use SuSE or kppp, though I do know a small amount about PPP in
general.

Quote:>The arguments to pppd are identical and lsmod looks fine in either case.
>The only difference I've noticed is that kppp 1.1 loads the ppp module
>upfront when it's invoked, whereas 1.0 leaves it to pppd. [...]

Purely guesswork, but I wonder if they do that to prove that the ppp
module can be loaded and so can issue an error message straight away
rather than waiting for pppd to fail?  The error messages from kppp
didn't seem terribly helpful in the first version...

It's probably not significant.

Quote:>I've included some log files in from each case. I haven't used the debug
>option to pppd but if it will help someone diagnose the problem I'll
>repost the gories. Any hints or advice would be greatly appreciated.

Debug output *might* help, but make sure you don't end up posting your
username and password in the process, er and since you're getting *lots*
of messages it would be useful to prune the log somewhat.  However, that
might not be necessary.

Quote:>KDE 1.0 KPPP
>------------
>pppd /dev/ttyS0 38400 crtscts defaultroute -detach -chap user tfi000000

About the only "unusual" thing is refusing CHAP, but there's no harm in
that since you want to use PAP.

Quote:>Apr 20 21:57:14 dewdrop pppd[783]: pppd 2.3.7 started by root, uid 0

Hmm.  Time for me to think about upgrading from 2.3.5, possibly?  I
wonder what new features/fixes it includes...

Quote:>Apr 20 21:57:14 dewdrop pppd[783]: Using interface ppp0
>Apr 20 21:57:14 dewdrop pppd[783]: Connect: ppp0 <--> /dev/ttyS0
>Apr 20 21:57:15 dewdrop pppd[783]: Remote message: ^F
>Apr 20 21:57:15 dewdrop kernel: PPP BSD Compression module registered
>Apr 20 21:57:15 dewdrop kernel: PPP Deflate Compression module registered

Right, so you've got two compression modules available...

All looks fairly normal.

Quote:>KDE 1.1 KPPP
>------------
>pppd /dev/ttyS0 38400 crtscts defaultroute -detach -chap user tfi000000
>Apr 20 21:51:55 dewdrop kernel: PPP BSD Compression module registered
>Apr 20 21:51:55 dewdrop kernel: PPP Deflate Compression module registered

Same again: next lines split for easier reading.

Quote:>Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported
>protocol 0x5265
>Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported
>protocol 0x5072
>Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for
>unsupported protocol 0x5072

However, it does seem to have worked:

Quote:>Apr 20 21:51:56 dewdrop pppd[744]: local  IP address 212.1.147.200
>Apr 20 21:51:56 dewdrop pppd[744]: remote IP address 10.42.42.42

The "unsupported protocol" messages seem to be:
0x5072 - rather a lot of these!
0x5265
0x6c6f

I'm having a bit of trouble relating these back to the compression
modules, but I wonder if you'd like to try adding:

alias ppp-compress-21 off
alias ppp-compress-24 off
alias ppp-compress-26 off

to /etc/conf.modules and seeing if the messages go away (obviously so
will any compression...)

Otherwise I think the debug output will be needed.

Quote:>Apr 20 21:52:57 dewdrop pppd[744]: Terminating on signal 15.

Was this a deliberate closedown by you, or did something else kill it?
--

Today's Excuse:
  floating point processor overflow
 
 
 

Weird kppp/pppd problem

Post by Moritz Moeller-Herrma » Sun, 25 Apr 1999 04:00:00



Quote:>I'm running SuSE 6.0 with kernel 2.2.6 and since upgrading to KDE 1.1
>I've had the strangest problem with kppp. Basically, the kppp with KDE
>1.0 works perfectly but the 1.1 version either fails to connect (eg to
>my work) or pppd spews out Protocol-Reject messages at a tremenous rate
>(eg connecting to telinco).

># less /var/log/messages
>Apr 20 21:51:22 dewdrop kernel: CSLIP: code copyright 1989 Regents of the University of California
>Apr 20 21:51:23 dewdrop kernel: PPP: version 2.3.3 (demand dialling)
>Apr 20 21:51:23 dewdrop kernel: PPP line discipline registered.
>Apr 20 21:51:23 dewdrop kernel: registered device ppp0
>Apr 20 21:51:55 dewdrop pppd[744]: pppd 2.3.7 started by root, uid 0
>Apr 20 21:51:55 dewdrop pppd[744]: Using interface ppp0
>Apr 20 21:51:55 dewdrop pppd[744]: Connect: ppp0 <--> /dev/ttyS0

Here:                                   ^^^^^^^^^^^^^^^^^^^^^^^^
Quote:>Apr 20 21:51:55 dewdrop pppd[744]: Remote message: ^F
>Apr 20 21:51:55 dewdrop kernel: PPP BSD Compression module registered
>Apr 20 21:51:55 dewdrop kernel: PPP Deflate Compression module registered
>Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported protocol 0x5265
>Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported protocol 0x5072
>Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported protocol 0x5072
>Apr 20 21:51:56 dewdrop pppd[744]: local  IP address 212.1.147.200
>Apr 20 21:51:56 dewdrop pppd[744]: remote IP address 10.42.42.42
>Apr 20 21:51:56 dewdrop pppd[744]: Protocol-Reject for unsupported protocol 0x5072

Hah! I had the same error! Downgrade pppd to 2.3.5 and it should work again.
Or upgrade to the just released kppp 1.6x (seen on Freshmeat.net). I think the
bug is fixed there.

The problem is (something like) that kppp connects the terminal/stdout to the ppp0 interface for some
reason and pppd prints out some info there in version 2.3.7. This gets in
some kind of positive feedback loop because the output is mixed with the ppp protocol.

--

Get my public pgp / gpg key from                        # Open Source(TM)
http://webrum.uni-mannheim.de/jura/moritz/pubkeymoritz  # but also
KDE forever! Use Linux to impress your friends!         # Open Minded!

 
 
 

Weird kppp/pppd problem

Post by Stephen Marl » Sun, 25 Apr 1999 04:00:00



> The problem is (something like) that kppp connects the terminal/stdout
> to the ppp0 interface for some reason and pppd prints out some info
> there in version 2.3.7. This gets in some kind of positive feedback
> loop because the output is mixed with the ppp protocol.

Bingo! I went back to 2.3.5 and everything is fine. Thanks to you and
Dan Glover for taking the time to respond :^D

--

 
 
 

Weird kppp/pppd problem

Post by Dan Glove » Mon, 26 Apr 1999 04:00:00





>> The problem is (something like) that kppp connects the terminal/stdout
>> to the ppp0 interface for some reason and pppd prints out some info
>> there in version 2.3.7. This gets in some kind of positive feedback
>> loop because the output is mixed with the ppp protocol.
>Bingo! I went back to 2.3.5 and everything is fine. Thanks to you and
>Dan Glover for taking the time to respond :^D

Hmm.  I'm wondering if upgrading to ppp-2.3.7 is a good idea.  Still,
I'm not using kppp and I'm assuming that's the thing which is actually
broken...

Dan

--

Today's Excuse:
  telnet: Unable to connect to remote host: Connection refused

 
 
 

Weird kppp/pppd problem

Post by Stephen Marl » Tue, 27 Apr 1999 04:00:00



> Hmm.  I'm wondering if upgrading to ppp-2.3.7 is a good idea.  Still,
> I'm not using kppp and I'm assuming that's the thing which is actually
> broken...

I upgraded my kppp and it now works OK with pppd 2.3.7.

--

 
 
 

1. weird kppp problem

Greetings,

I just got pre-DR3 installed on my 9500/180/MP and I'm really pleased with
the new look of MkLinux.  However, I've got a problem with kppp that I
haven't been able to track down.  

When I connect to my local ISP the screen goes blank when the ppp session
is actually started.  If I move the mouse around and select different
regions of the screen, I can slowly find windows and icons that I can
bring back when I click on them.  I can also hunt for the menu bar and
select refresh desktop but that doesn't help. The best I can do is just
march around the desktop and drag windows over everything to bring the
desktop back into view.  Has anyone else experienced this and/or have any
suggestions about how to solve it?

Many thanks!

Cory

2. mirro boot vs clone boot

3. Kppp/Network - weird problem

4. NE2000+ and RedHat 4.0

5. Weird kppp/netscape problem

6. 16-bit Ensoniq Wavetable Sound Card

7. pppd problem with kppp

8. iptables and https

9. Kppp and pppd Problems

10. kppp and pppd problem

11. KPPP and PPPD Problem

12. kppp-pppd problem

13. Weird problem running pppd and chat.