Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Aug 2006 13:26:40 -0500
From:      Brooks Davis <brooks@one-eyed-alien.net>
To:        Pat Lashley <patl@volant.org>
Cc:        freebsd-net@freebsd.org, Doug Barton <dougb@freebsd.org>, Fredrik Lindberg <fli+freebsd-net@shapeshifter.se>
Subject:   Re: Zeroconfig and Multicast DNS
Message-ID:  <20060824182640.GA37561@lor.one-eyed-alien.net>
In-Reply-To: <0EC404BA0CA363942D250766@garrett.local>
References:  <20060823221835.GA28978@lor.one-eyed-alien.net> <23D2619F6BACE4E728178EE5@garrett.local> <44ED3BD1.3030206@shapeshifter.se> <AC5769F16F9730CABCCC4E61@garrett.local> <44EDA9A5.2050108@shapeshifter.se> <BE1059C6974AD43BC382E107@garrett.local> <44EDBDD0.4050000@shapeshifter.se> <7CC9AC69410B69EBD31122E4@garrett.local> <44EDDB8C.9090504@shapeshifter.se> <0EC404BA0CA363942D250766@garrett.local>

next in thread | previous in thread | raw e-mail | index | archive | help

--LZvS9be/3tNcYl/X
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 24, 2006 at 10:55:15AM -0400, Pat Lashley wrote:
> >If you want to communicate with an LLA host, fine, obtain an LLA
> >address otherwise take a hike.
>=20
> I'd make that '..., obtain an LLA address, or figure out how to do it via=
=20
> ARP, otherwise...'
>=20
> >My LLA implementation already does this..it never removes an address
> >from a interface it didn't set itself, and it always sets address
> >as aliases.
>=20
> That already makes it one step better than the Linux implementation I was=
=20
> working with last year...
>=20
> >             There is also an option to force it to assign
> >(as an alias) a LLA address even if the interface is already is
> >configured with another address.
>=20
> I think that I'd reverse the default on that. There should normally be no=
=20
> harm in having an LLA address, as long as we've got the non-LLA preferenc=
e=20
> stuff working correctly. It is quite likely that the LLA address would=20
> never actually be used; but so what?

Unless we modify the IPv4 routing code to actually know that different
interfaces with LLAs are on different subnets, we will need to insure
that there is only one interface with an LLA on it at once.  The
modification probably makes sense, but I have no idea what it would
entail.

-- Brooks

--LZvS9be/3tNcYl/X
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFE7e9fXY6L6fI4GtQRAgVeAJkBV08nqh7McHrQ71JRSTvLXsyLhQCfX2hz
VDT8nhRZOcxnCWFvWWoiJDc=
=Rw36
-----END PGP SIGNATURE-----

--LZvS9be/3tNcYl/X--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060824182640.GA37561>