Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 Aug 2006 16:21:10 -0500
From:      Brooks Davis <brooks@one-eyed-alien.net>
To:        Pat Lashley <patl+freebsd@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:  <20060823212110.GD27961@lor.one-eyed-alien.net>
In-Reply-To: <C408C9E0406302DF5EE12E67@garrett.local>
References:  <44E9F991.7020309@shapeshifter.se> <DD49A62B2AB4E38804FB10B6@garrett.local> <44EA1926.2000501@shapeshifter.se> <9C04919EE684029A410DE208@garrett.local> <44EAC40E.9000904@shapeshifter.se> <3E654CC0217F90E20FCD806E@garrett.local> <44EC90B7.6090908@shapeshifter.se> <44ECB0F2.9040300@FreeBSD.org> <C408C9E0406302DF5EE12E67@garrett.local>

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

--UfEAyuTBtIjiZzX6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 23, 2006 at 02:12:20PM -0400, Pat Lashley wrote:
> >If no one else steps forward, I will be glad to lead the charge to get an
> >implementation of this committed. Before I do though, we'll need to get=
=20
> >some
> >basic questions answered (some of which have already been discussed here=
).
> >
> >1. What are the other *BSDs doing in this area?
> >2. What are the linux flavors doing?
> >3. What is the minimal set of features we should support? (I think this=
=20
> >list
> >starts with LLA, but that's just a gut feeling atm.)
>=20
> I would agree that LLA is part of the minimal set; and as I mentioned=20
> before, it is the only part for which there is currently no FreeBSD=20
> solution. It should be possible to enable LLA on a per-NIC basis in=20
> rc.conf; and it should be possible to have both LLA and non-LLA addresses=
=20
> on the same port so that a FreeBSD host can easily operate in a mixed=20
> environment. (This also makes it easier for portable machines to handle=
=20
> being moved between a zeroconf-based environment and a more traditional=
=20
> DHCP environment.)

I don't see how we can do the fallback stuff with our current
infrastructure.  You could do it with profile.sh, but our current
infrastructure isn't really suited to it.  In some ways what we really
need is an all knowing IPv4 address configuration program that can probe
the link and decide if it should a) use a static IP, b) use DHCP, or c)
use an LLA.  It's possible we could do this in a shell script, but I'm
not sure we'd want to.

-- Brooks

--UfEAyuTBtIjiZzX6
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFE7MbFXY6L6fI4GtQRApwfAKC015TZUTHng/4OPmCqYTo8UWOfVQCeLZcz
wYBpTfHzggq7ThCTpO6OgAc=
=umaF
-----END PGP SIGNATURE-----

--UfEAyuTBtIjiZzX6--



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