From: Willy Tarreau <w@1wt.eu>
To: Matthias Cramer <matthias.cramer@interway.ch>
Cc: James Chapman <jchapman@katalix.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: Wired behaviour with IPv6 over PPP
Date: Sat, 24 May 2008 06:29:11 +0200 [thread overview]
Message-ID: <20080524042911.GE6749@1wt.eu> (raw)
In-Reply-To: <4835C40B.60603@interway.ch>
On Thu, May 22, 2008 at 09:05:47PM +0200, Matthias Cramer wrote:
> James Chapman wrote:
> > Andrew Morton wrote:
> >> On Wed, 21 May 2008 14:56:43 +0200 Matthias Cramer
> >> <matthias.cramer@interway.ch> wrote:
> >>> I have a very wired behaviour when doing IPv6 over PPPoE.
> >>>
> >>> The situation:
> >>>
> >>> A linux box connected to a DSL Modem, on the other side is a Cisco
> >>> LNS which terminates the PPP session (actually L2TP).
> >>> I have control over both ends.
> >>>
> >>> When I have net.ipv6.conf.all.forwarding set to 0 then the ppp
> >>> Interface gets a IPv6 address from the Cisco via IP6CP.
> >>> When I have net.ipv6.conf.all.forwarding set to 1 them the ppp
> >>> Interface does not get an address, it has only a normal link local
> >>> address.
> >
> > What do you mean by normal link local address?
>
> a fe80:: address, which every IPv6 enabled Interface has...
>
> >
> >>> When I start the ppp session with forwarding set to 0 I can ping out
> >>> and there exists a default route to ppp0 , then I switch forwarding to 1
> >>> the default route disappears and therefore routing does not work any
> >>> longer.
> >
> > Did this work with previous kernel versions?
>
> No, in my opinion it never worked. But I thought that pppd does it wrong
> because id never got an IPv6 address. But I had always forwarding
> enabled. Now in this case i started pppd without forwarding enabled and
> got an address.
Well, at least it has been working for years in kernel 2.4 for me with
pppd 2.4.2b3 to 2.4.4 (I've not upgraded my firewall to 2.6 yet). So
it has definitely been working at some point.
Willy
next prev parent reply other threads:[~2008-05-24 4:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48341C0B.7010003@interway.ch>
2008-05-22 8:49 ` Wired behaviour with IPv6 over PPP Andrew Morton
2008-05-22 9:55 ` James Chapman
2008-05-22 19:05 ` Matthias Cramer
2008-05-23 10:46 ` James Chapman
2008-05-23 19:50 ` Matthias Cramer
2008-05-23 21:34 ` James Chapman
2008-05-24 4:29 ` Willy Tarreau [this message]
2008-05-28 9:59 ` Pascal Hambourg
2008-05-28 12:45 ` Willy Tarreau
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=20080524042911.GE6749@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=jchapman@katalix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.cramer@interway.ch \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).