From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Oliver Hartkopp <oliver@hartkopp.net>
Cc: David Miller <davem@davemloft.net>,
herbert@gondor.apana.org.au, yoshfuji@linux-ipv6.org,
netdev@vger.kernel.org, koster@debian.org.tw,
socketcan@hartkopp.net, urs@isnogud.escape.de, florz@florz.de
Subject: Re: [IPV6] addrconf: Fix IPv6 on tuntap tunnels
Date: Fri, 15 Jun 2007 16:42:22 -0400 [thread overview]
Message-ID: <4672F9AE.6070400@hp.com> (raw)
In-Reply-To: <467259DD.7030703@hartkopp.net>
Oliver Hartkopp wrote:
> Hallo David, hello Herbert,
>
> indeed i have some concerns about reverting the patch as i do not see
> that the MTU is the right thing to distinguish whether a netdevice is
> capable to have IPv4/IPv6. E.g. is decnet able to run IPv6?
>
> IMHO the autoconf (in any case) should only handle netdevices that are
> capable to be auto configured (e.g. with IPv6).
>
> So the question looks like:
> "Is this device capable to be auto configured with IPv6?"
> and not
> "Is the devices MTU >= IPV6_MIN_MTU ?"
No, the questions should really be:
1. Is IPV6 supported over this media type.
yes: got to 2
no: stop
2. Is the device MTU >= IPV6_MIN_MTU
yes: continue
no: stop
Autoconfiguration is a layer on top of IPv6. Whether it's enabled
or not should not dictate whether IPv6 addressed may be configured or not.
-vlad
next prev parent reply other threads:[~2007-06-15 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 8:16 [IPV6] addrconf: Fix IPv6 on tuntap tunnels Herbert Xu
2007-06-14 20:03 ` David Miller
2007-06-15 9:20 ` Oliver Hartkopp
2007-06-15 20:42 ` Vlad Yasevich [this message]
2007-06-15 22:14 ` David Miller
2007-06-16 7:55 ` Herbert Xu
2007-06-18 17:56 ` Vlad Yasevich
2007-06-16 12:33 ` Oliver Hartkopp
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=4672F9AE.6070400@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=florz@florz.de \
--cc=herbert@gondor.apana.org.au \
--cc=koster@debian.org.tw \
--cc=netdev@vger.kernel.org \
--cc=oliver@hartkopp.net \
--cc=socketcan@hartkopp.net \
--cc=urs@isnogud.escape.de \
--cc=yoshfuji@linux-ipv6.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).