From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: "lee Leahu " <lee@ricis.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: please help with pppoe
Date: Wed, 15 May 2002 22:43:20 +0200 [thread overview]
Message-ID: <200205152243.20100.Dieter.Nuetzel@hamburg.de> (raw)
On Wednesday 15 May 17:14, lee Leahu wrote:
LKM is the wrong place, but...
> i am running suse 7.3 professional.
> my kernel is 2.4.16-4gb (k_deflt made by suse)
First you should look at www.suse.de/www.suse.com.
They have a very good support database:
http://sdb.suse.de/en/sdb/html/index.html
> i have these packages installed
> smpppd-0.49-7 (and yes, smpppd is running)
> ppp-2.4.1-170
Good.
> rp-pppoe-3.4-1
Don't needed any more.
> my /etc/ppp/options file goes like this:
[-]
> mtu 1484
> mru 1484
As example for the German Telecom you need:
mtu 1492
mru 1492
It belongs into: /etc/ppp/peers/pppoe
#
# PPPoE options
#
plugin pppoe.so
#
# Plugin enables us to pipe the password to pppd, thus we don't have
# to put it into pap-secrets and chap-secrets. User is also passed
# on command line.
#
plugin passwordfd.so
#
noauth
usepeerdns
mru 1492
mtu 1492
# this is recommended
defaultroute
replacedefaultroute
hide-password
nodetach
# switch off all compressions (this is a must)
nopcomp
# this is recommended
novjccomp
noccp
> my /etc/ppp/pap-secret is like this
>
> "(username)@covad.net" * "(password)"
pap-secret is empty autogenerate with YaST2 (SuSE 7.3)
> i have been trying to get this pppoe to work by running:
> pppoe -I eth1
> pppoe -D -d 9 -I eth1
> adsl-start
Try with YaST/YaST2 (in this order).
Good luck.
Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel@hamburg.de
next reply other threads:[~2002-05-15 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 20:43 Dieter Nützel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-15 17:14 lee Leahu
2002-05-16 3:17 ` David
2002-05-16 5:23 ` Michael Schlenstedt
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=200205152243.20100.Dieter.Nuetzel@hamburg.de \
--to=dieter.nuetzel@hamburg.de \
--cc=lee@ricis.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®