From: Hadmut Danisch <hadmut@danisch.de>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Bill Fink <billfink@mindspring.com>,
David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, netdev@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 28282] New: forwarding turns autoconfiguration off
Date: Thu, 24 Mar 2011 16:07:10 +0100 [thread overview]
Message-ID: <4D8B5E1E.6060608@msgid.danisch.de> (raw)
In-Reply-To: <20110209074221.GA9790@electric-eye.fr.zoreil.com>
Hi all,
since the discussion seems to have completely died, just allow me a
simple question:
How would I configure a Linux machine to accept ipv6 prefix ads (because
they are dynamically assigned and advertised by my router) and to work
as a VPN tunnel end?
Remember: Linux does not allow autoconfiguration and routing at the same
time, without any good reason. The only reason I've seen so far is that
the Terminology in an RFC vaguely distinguishes between router machines
and nodes.
If you believe that Linux is correct here the way it is, just tell me
how to solve that problem with Linux.
best regards
Hadmut
next prev parent reply other threads:[~2011-03-24 15:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-28282-10286@https.bugzilla.kernel.org/>
2011-02-08 21:34 ` [Bugme-new] [Bug 28282] New: forwarding turns autoconfiguration off Andrew Morton
2011-02-08 21:44 ` David Miller
2011-02-08 22:12 ` Hadmut Danisch
2011-02-08 22:30 ` David Miller
2011-02-08 22:44 ` Francois Romieu
2011-02-08 22:59 ` Hadmut Danisch
2011-02-08 23:49 ` Francois Romieu
2011-02-09 4:47 ` Bill Fink
2011-02-09 7:42 ` Francois Romieu
2011-02-09 7:56 ` Hadmut Danisch
2011-03-24 15:07 ` Hadmut Danisch [this message]
2011-03-24 16:25 ` David Lamparter
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=4D8B5E1E.6060608@msgid.danisch.de \
--to=hadmut@danisch.de \
--cc=akpm@linux-foundation.org \
--cc=billfink@mindspring.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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.