On 8/8/06, Chuck Hast <wchast@gmail.com> wrote:
>
> On 8/8/06, Todd <dumb-ass@acpdata.com> wrote:
> > Chuck Hast wrote:
> > > On 8/8/06, Sick Twist <thesicktwist@hotmail.com> wrote:
> > >> >From: "Chuck Hast" <wchast@gmail.com>
> > >> >Reply-To: slug@nks.net
> > >> >To: slug@nks.net
> > >> >Subject: [SLUG] eth1 or wlan1
> > >> >Date: Mon, 7 Aug 2006 09:17:23 -0400
> > >> >
> > >> >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.
> > >>
> > >> I'm not sure if SuSE uses this method but my Ubuntu box uses
> > >> /etc/iftab to
> > >> allow the user to define interface names. Check out man iftab.
> > >>
> > >
> > > It is not there. I looked for it but can not find it. There is a man
> > > page for it
> > > but no file.
> > >
> > Have you seen this article from SuSE? It explains how and why network
> > devices are named.
> >
> >
> http://www.novell.com/documentation/suse10/index.html?page=/documentation/suse10/adminguide/data/sec_basicnet_manconf.html
> >
> OK, I read it. Still not sure where to poke, it sort of looks like
> that is the way
> it is. It all appears to work ok, it just does not look right having a
> wireless
> nic card assigned eth1....
>
> Will continue to poke at it and try to see how to make it assign the wifi
> as
> wlan0.
> Tnx again...
I'm not sure if I understand the problem.... What does it matter whether
it's eth1 or wlan0? My eth1 has been running fine... Care to enlighten me
on why this is an issue?
-- > Chuck Hast -- KP4DJT -- > To paraphrase my flight instructor; > "the only dumb question is the one you DID NOT ask resulting in my going > out and having to identify your bits and pieces in the midst of torn > and twisted metal." > ----------------------------------------------------------------------- > 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 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:55:02 EDT