Date: Fri, 14 Aug 2009 10:05:10 +0400 From: "Andrey V. Elsukov" <bu7cher@yandex.ru> To: d@delphij.net Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, Julian Elischer <julian@elischer.org>, freebsd-net@freebsd.org Subject: Re: RFC: interface description Message-ID: <4A84FE96.1070506@yandex.ru> In-Reply-To: <4A846AD3.3080301@delphij.net> References: <4A83EEA8.5080202@delphij.net> <4A840DA1.600@yandex.ru> <4A844FF2.9000307@elischer.org> <20090813182918.S93661@maildrop.int.zabbadoz.net> <4A846AD3.3080301@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Xin LI wrote: > The only question I have would be, that is it possible to uniquely > identify a NIC without assistance from kernel? For instance, one can > change an interface from being called "em0" to "eth0" and from "bge0" to > "em0". It's easy to track this information through ifconfig(8) with a > callback, clean up the file upon restart, but we can not prevent other > programs from calling IOCSIFNAME on the interface. Any idea for this? What about using interface index as a key(see if_nameindex(3))? -- WBR, Andrey V. Elsukov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A84FE96.1070506>