Subject: Re: setting link-level addresses
To: Daniel Hagerty <hag@linnaean.org>
From: Ignatios Souvatzis <ignatios@theory.cs.uni-bonn.de>
List: tech-net
Date: 07/29/2003 16:12:08
--h31gzZEtNLTqOjlF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 29, 2003 at 12:13:44AM -0400, Daniel Hagerty wrote:
> David Young <dyoung@pobox.com> writes:
>=20
> > Dheeraj and Daniel,
> >=20
> > I'm glad you two are working on this.
> >=20
> > I am concerned that I will not be able to easily restore the link-level
> > address to the hardware default. Have you thought about how to do that?
>=20
>     I'm imagining from your statement that the in kernel code that
> does this now doesn't manage this; I haven't checked.
>=20
>     My offhand feeling would be to pay 20 bytes of extra sockaddr_dl
> to maintain the burned in address in core, and expose it to userland
> as SIOCD*ADDR of the primary restoring the burned in (and maybe return
> EFOOBAR if the primary is already the burned in).

Hm? No, return success.
	-is

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

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBPyaAdTCn4om+4LhpAQFVXQgAwZN3ikPL/BcnXOhLWORy3ezWm3kSwfgM
rKM2uN6Mz8n7LJg9aU8fvziSqvCsIv/mBAYgtvMxSeZURqM/qKLziaa7oDmi2RnX
KpateiJVqKuhgHxWb4R8cFwKuQgmO/xt9+cEU5NTKAftByjaZyWA6VI2Mjsq7oMF
ghG+FJhxZyPBvMtZ9rXtJ6LvdbobEqcpYnUNzYcm+GKl088bND7+EnHcze3gfgDp
msKtbJE31odLGODiPa83YBah+ZX9CnVOTwmBR8Wh+2nZv4APQh8+j7zbxbgyU1SQ
SBDrG6wqopzwtZts5bABlm06TaJEk20BSyXuX7nIMQpVQ24pmuTx0w==
=6tj/
-----END PGP SIGNATURE-----

--h31gzZEtNLTqOjlF--