From: Brian Murphy brimurph@remus.rutgers.edu
To: lartc@vger.kernel.org
Subject: [LARTC] 2.4.1 Kernel
Date: Fri, 02 Feb 2001 19:22:59 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416958@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416957@msgid-missing>
<PRE>Ok, I compiled ppp into the kernel and upgraded pppd to vesrion 2.4.0b1.
Everything's working now.
Thanks,
-Brian Murphy
On Fri, 2 Feb 2001, Arthur van Leeuwen wrote:
><i> On Fri, 2 Feb 2001, Brian Murphy wrote:
</I>><i>
</I>><i> [snip, pppoe not working in 2.4]
</I>><i>
</I>><i> > Has anyone conquered this problem? I really would like to continue using
</I>><i> > iptables........
</I>><i>
</I>><i> Err... the adsl systems I've seen don't use pppoe, unfortunately, so I can't
</I>><i> really say. However, I seem to recall the 2.4.1 kernel coming with a pppoe
</I>><i> driver itself, so you should be able to get that to work...
</I>><i>
</I>><i> Doei, Arthur. (Who has seen ADSL systems using pptp and multiple NAT...
</I>><i> major ugliness...)
</I>><i>
</I>><i> --
</I>><i> /\ / | <A HREF="mailto:arthurvl@sci.kun.nl">arthurvl@sci.kun.nl</A> | Work like you don't need the money
</I>><i> /__\ / | A friend is someone with whom | Love like you have never been hurt
</I>><i> / \/__ | you can dare to be yourself | Dance like there's nobody watching
</I>><i>
</I>><i>
</I>><i> _______________________________________________
</I>><i> LARTC mailing list / <A HREF="mailto:LARTC@mailman.ds9a.nl">LARTC@mailman.ds9a.nl</A>
</I>><i> <A HREF="http://mailman.ds9a.nl/mailman/listinfo/lartc">http://mailman.ds9a.nl/mailman/listinfo/lartc</A> HOWTO: <A HREF="http://ds9a.nl/2.4Routing/">http://ds9a.nl/2.4Routing/</A>
</I>><i>
</I>
</PRE>
next prev parent reply other threads:[~2001-02-02 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 18:11 [LARTC] 2.4.1 Kernel Arthur
2001-02-02 19:22 ` Brian [this message]
2001-02-02 20:45 ` Brian
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=marc-lartc-98373940416958@msgid-missing \
--to=lartc@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.