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  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:	Sat, 16 Jun 2007 17:55:55 +1000
From:	Herbert Xu <>
To:	David Miller <>
Subject: Re: [IPV6] addrconf: Fix IPv6 on tuntap tunnels

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
> > 
> > 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? :-)

I don't think we need any more patches since right now MTU >= IPV6_MIN_MTU
is the only condition we require before we allow IPv6 addresses to be added
to an interface.

The original patch simply confused this basic IPv6 address support with
IPv6 autoconfiguration.

Visit Openswan at
Email: Herbert Xu ~{PmV>HI~} <>
Home Page:
PGP Key:
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists