From: Oliver Hartkopp <socketcan@hartkopp.net>
To: David Miller <davem@davemloft.net>
Cc: vladislav.yasevich@hp.com, 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: Sat, 16 Jun 2007 14:33:15 +0200 [thread overview]
Message-ID: <4673D88B.5000805@hartkopp.net> (raw)
In-Reply-To: <20070615.151457.98556461.davem@davemloft.net>
David Miller wrote:
> From: Vlad Yasevich <vladislav.yasevich@hp.com>
> Date: Fri, 15 Jun 2007 16:42:22 -0400
>
>
>> 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.
>>
>
> Sounds good to me, patches? :-)
>
Yes, to me it sounds also very good.
I'm not that deep in IPv6 and i do not know about all the media types
that support IPv6, e.g. if a whitelist (as i suggested) is the better
way - or a blacklist.
So i would just support the request from David for patches :-)
Best regards,
Oliver
prev parent reply other threads:[~2007-06-16 12:33 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
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 [this message]
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=4673D88B.5000805@hartkopp.net \
--to=socketcan@hartkopp.net \
--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=urs@isnogud.escape.de \
--cc=vladislav.yasevich@hp.com \
--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).