All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Ploski <jpljpl@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-testX and pppd/pppoe stuck after connecting
Date: Sat, 25 Oct 2003 22:56:56 +0200 (CEST)	[thread overview]
Message-ID: <2523214.1067115416222.JavaMail.jpl@remotejava> (raw)

Hello,

Ever since I upgraded from 2.4.18 to 2.6.0-test? (now -test8),
I have been encountering problems with my pppd/pppoe setup.
Specifically, right after the ppp0 interface is brought up, and several
packets go through that interface (4-5 packets RX/TX), no more packets
are transmitted until I restart pppd and reconnect to my ISP.
ping www.google.com will report 100% packet loss, and I cannot see the
TX packet count on ppp0 increasing. Nothing suspicious appears in ppp.log.
More often than not, I have to reconnect multiple times until at last
a working connection is established.

I may have not included all required information, but I don't know what
might be useful in diagnosing this problem (this knowledge would possibly
let me correct it without posting). I believe it is kernel-related because
with 2.4.x everything works fine in the same circumstances. The software
versions are: pppd version 2.4.1, pppoe version 3.3 (from roaringpenguin.com)

I would be grateful if you CC'ed me in replies.

Best regards -
Jan Ploski


             reply	other threads:[~2003-10-25 20:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-25 20:56 Jan Ploski [this message]
2003-10-25 21:36 ` 2.6.0-testX and pppd/pppoe stuck after connecting Måns Rullgård
2003-10-26  3:04 ` Tim Schmielau
  -- strict thread matches above, loose matches on Subject: below --
2003-10-27 12:22 "Andrey Borzenkov" 
2003-10-27 12:38 Jan Ploski
2003-10-27 18:56 Andrey Borzenkov
2003-10-28 21:14 Jan Ploski
2003-11-17 20:27 Jan Ploski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2523214.1067115416222.JavaMail.jpl@remotejava \
    --to=jpljpl@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.