Re: [osol-discuss] Re: [approach-discuss] Re: ioctl SIOCGENADDR returns ENOENT

2005-11-22 Thread Joerg Schilling
Shao Wu [EMAIL PROTECTED] wrote: On the other hand, the ioctl is no more ugly than fishing the MAC from ARP. The ablilty to be able to retrieve MAC from down interfaces is nice and essential for some applications. But I suspect it's more commen for poeple to look for up interfaces

Re: [osol-discuss] Re: [approach-discuss] Re: ioctl SIOCGENADDR returns ENOENT

2005-11-22 Thread Darren J Moffat
On Tue, 2005-11-22 at 15:54, Joerg Schilling wrote: Shao Wu [EMAIL PROTECTED] wrote: On the other hand, the ioctl is no more ugly than fishing the MAC from ARP. The ablilty to be able to retrieve MAC from down interfaces is nice and essential for some applications. But I suspect it's

Re: [osol-discuss] Re: [approach-discuss] Re: ioctl SIOCGENADDR returns ENOENT

2005-11-22 Thread James Carlson
Joerg Schilling writes: By tradition, you need to be root on UNIX in order to get permission to see the MAC address. I'd call that more of a DLPI implementation quirk than a tradition. -- James Carlson, KISS Network[EMAIL PROTECTED] Sun Microsystems / 1 Network Drive

Re: [osol-discuss] Re: [approach-discuss] Re: ioctl SIOCGENADDR returns ENOENT

2005-11-21 Thread James Carlson
Shao Wu writes: On the other hand, the ioctl is no more ugly than fishing the MAC from ARP. Right. Which you can already do with the existing ioctls. So, it's my suspicion that those asking for the feature either don't realize the limitations it'll have or don't care. I don't actually know