disabling client use of SLAAC
Mark Smith
nanog at 85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org
Sat Mar 6 22:41:02 CET 2010
On Sat, 6 Mar 2010 11:56:34 -0500
Mark Kamichoff <prox at prolixium.com> wrote:
> On Sat, Mar 06, 2010 at 09:36:56AM +1030, Mark Smith wrote:
> > On Fri, 5 Mar 2010 21:32:00 +0100
> > Marco Hogewoning <marcoh at marcoh.net> wrote:
> >
> > >
> > > On 5 mrt 2010, at 21:24, Brian E Carpenter wrote:
> > >
> > > > On 2010-03-05 22:24, Mikael Abrahamsson wrote:
> > > > ...
> > > >> The M and O flags says "get info via DHCP", but it seems they don't mean
> > > >> "do NOT use SLAAC" if I read http://www.ietf.org/rfc/rfc2462.txt correctly?
> > > >>
> > > >> So bottom line, how to make clients not use SLAAC with a Cisco router?
> > > >>
> > > >
> > > > Note that this is known to be a tricky area in mutlti-vendor, multi-o/s
> > > > situations.
> > >
> > >
> > > <snip>
> > >
> > > Can't agree more. In the meantime, what about extending the subnet mask a few bits (/80) on the lan ?
> >
> > Why?
>
> Autoconf doesn't work for on >64 bit prefixes, so extending it to an 80
> is a [interesting] way of disabling it completely.
>
So is announcing RA Prefix Information options without the
autonomous address-configuration flag set. I'd doubt anybody
would be willing to standardise hack like that when there is already a
proper way to stop nodes autoconfiguring addresses.
Regards,
Mark.
More information about the ipv6-ops
mailing list