netdev - Re: [IPV6] addrconf: Fix IPv6 on tuntap tunnels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 15 Jun 2007 16:42:22 -0400
From:	Vlad Yasevich <vladislav.yasevich@...com>
To:	Oliver Hartkopp <oliver@...tkopp.net>
Cc:	David Miller <davem@...emloft.net>, herbert@...dor.apana.org.au,
	yoshfuji@...ux-ipv6.org, netdev@...r.kernel.org,
	koster@...ian.org.tw, socketcan@...tkopp.net,
	urs@...ogud.escape.de, florz@...rz.de
Subject: Re: [IPV6] addrconf: Fix IPv6 on tuntap tunnels

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
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html