Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
Date: Sat Apr 07 2001 - 03:29:46 CDT
On Fri, 6 Apr 2001, Mark S. Mathews wrote:
> On Fri, 6 Apr 2001, Peter Kundrat wrote:
> > On Fri, Apr 06, 2001 at 01:08:12PM -0400, Mark S. Mathews wrote:
> > > > But such approach is not letting user software to find out device type and
> > > > securely call private ioctls (without risk to screw something up). So I do
> > >
> > > For the private ioctls we do a magic number test, so there isn't much risk
> > > of trouble.
> > Unless there is some other device that will be screwed by our magic test,
> > if i am not mistaken.
> That would only happen if wlanctl tried to ioctl a non-wlan device.
> The reason I'm considering this change is because I'd eventually like the
> wlan device to be a native 802.11 frame interface. We'd still support the
> ethernet top edge to prevent breakage of programs that use raw sockets.
> Therefore, I'd like to reserve "wlan" for 802.11 native interfaces and
> "eth" for 'post-ethernet conversion' type interfaces.
> Now, I guess we could do something like "weth" for the 'post conversion'
> What do you think?
I've read all the discussion and I think that it could be a good think to
provide ethX as an option (like for wavelan cards, I don't know if you
have test it). It could be very util for who want to use 802.11 interface
like true ethernet access ... (everything for this use ethX interface ...)
as Steve :o)
Linux WLAN Developer's List
For more information about this list see: