Re: [SLUG] eth1 or wlan1

From: Mason Mullins (mason_mullins@hotmail.com)
Date: Mon Aug 07 2006 - 11:17:45 EDT


----Original Message Follows----
From: "Jason Boxman" <jasonb@edseek.com>
Reply-To: slug@nks.net
To: slug@nks.net
Subject: Re: [SLUG] eth1 or wlan1
Date: Mon, 7 Aug 2006 11:03:25 -0400 (EDT)

Chuck Hast wrote:
> I was under the impression that when you set up a wireless lan nic it was
> assigned a device name of wlan something. Indeed on my desktop I have
> a wireless lan card and the wireless lan device is wlan0, the wired nic
card
> is eth0. But on my laptop eth0 is the wired device and eth1 is the wlan
> device, It appears that the nic management tool is trying to handle the
> ethernet device as though it was a wireless nic. I just disregard the
> wireless
> stuff for it, but it is not logical to step through a bunch of wireless
> params
> for a wired nic. What is involved in changing eth1 to wlan0? so that it
is
> more like what I am used to with other wireless card installs? Not sure
> why the system has set it's self up this way. I am using SuSE 10.1,
> but it was like that with 10.0 too.

Last I looked it depended entirely on the driver being used. hostap liked
to use wlanX whereas ndiswrapper prefers ethX for example.

I don't think ndiswrapper is the problem. I use it and mine is wlan0 and has
been on every NIC I've used, both internal and pcmcia.

That brings up a point. Is this a pcmcia card? If so, I'd take a look at the
pcmcia config file to ensure it's properly defined as I have seen that cause
some weird problems like that.

-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:46:46 EDT