Herbert Xu wrote:
> On Fri, Jun 15, 2007 at 03:14:57PM -0700, David Miller wrote:
>>> 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
On Fri, Jun 15, 2007 at 03:14:57PM -0700, David Miller wrote:
>
> > 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
> >
> > Autoc
David Miller wrote:
> From: Vlad Yasevich <[EMAIL PROTECTED]>
> 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: cont
From: Vlad Yasevich <[EMAIL PROTECTED]>
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
>
> Autoc
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)
ED]>
> Date: Thu, 14 Jun 2007 18:16:07 +1000
>
>
>> [IPV6] addrconf: Fix IPv6 on tuntap tunnels
>>
>> The recent patch that added ipv6_hwtype is broken on tuntap tunnels.
>> Indeed, it's broken on any device that does not pass the ipv6_hwty
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Thu, 14 Jun 2007 18:16:07 +1000
> [IPV6] addrconf: Fix IPv6 on tuntap tunnels
>
> The recent patch that added ipv6_hwtype is broken on tuntap tunnels.
> Indeed, it's broken on any device that does not pass the ipv6_hwtype
> tes
Hi Dave:
[IPV6] addrconf: Fix IPv6 on tuntap tunnels
The recent patch that added ipv6_hwtype is broken on tuntap tunnels.
Indeed, it's broken on any device that does not pass the ipv6_hwtype
test.
The reason is that the original test only applies to autoconfiguration,
not IPv6 support.
