Re: eth1 instead of wlan0

On Mon, 05 Dec 2005 07:13:22 -0700, Valentin Guillen wrote:

> On Mon, 05 Dec 2005 04:40:15 +0000, boskone wrote:
>
>
>> My question is, how do I get the system to identify the interface as
>> wlan0?
>>
>> Thanks
>> M Hasse
>
> I use SuSE 9.2 and what follows is pertinent to that version. But it may
> provide us with clues how to proceed.
>
> My wireless config file is found here:
>
> /etc/sysconfig/network/ifcfg-wlan-id-xx:xx:xx:xx:xx:xx and the actual file
> name contains the MAC address of the device, which I've changed to x's for
> the sake of privacy. So the file name is ifcfg-wlan-id-xx:xx:xx:xx:xx:xx
>
> You'll notice that there is no numerical designation of the interface
> number found, as in wlan0 or wlan4, in the name of it's configuration file.
>
> So I would try the following to see if it would work for you: Make a
> backup copy of the current config file, and rename it, perhaps even move
> it to some other location. Then, take a copy of the current config file,
> and rename it to
>
> ifcfg-wlan-id-____________________ and put in your device's MAC address
> where I've put the underscore. Put this renamed copy back wherever it is
> found in Suse 10. Test the system out by rebooting, and then lauanching
> YaST to see if Yast recognizes the device as wlan0 instead of eth0
>
>
> I have several WiFi devices, and a couple of them also get recognized by
> YaST with the ethX designation instead of wlanX. I even have a a couple
> of devices which incorporate Ralink chipsets, which get configured with
> the ra0 designation instead of eth0 or wlan0. My guess is that whoever
> writes the configuration script for the device class gets to choose the
> designation they want to use.
>
> If this suggestion does not work for you, you can rename the original
> config file back to it's original file name and put it back where you
> found it.
>
>
> Hope that helps you.....
>
> Valentin
Thanks for the feedback.
This is also where the file is at and the same naming convention in 10.0.
However, I needed to rename the file ifcfg-eth1 in order for the system to
even attempt to connect through the wireless lan. After I get it to
recognize the card by doing this, I still have to run iwconfig eth1 enc
XXXX-XXXX-XX then commit to get my card to connect to the router. By
doing this, I lose all the advanced wireless "stuff" in YaST.

I was hoping to force the system to name it wlan0. I'll live with what I
have for now, but hope to find some solution as this worked just fine in
9.3 (maybe I'll roll it back to 9.3)

M Hasse
.

Relevant Pages

  • FileSystemWatcher Folder Rename
    ... We are using FileSystemWatcher class in a windows service to monitor a ... This path is configured in a config file. ... open up Windows Explorer and rename d:\abc to d:\xyz. ...
    (microsoft.public.dotnet.general)
  • Re: eth1 instead of wlan0
    ... I use SuSE 9.2 and what follows is pertinent to that version. ... My wireless config file is found here: ... You'll notice that there is no numerical designation of the interface ... backup copy of the current config file, and rename it, perhaps even move ...
    (alt.os.linux.suse)
  • Re: using a config file
    ... I think you better check the docs for the configurations settings in .NET ... an app.config is the name of the config file managed by the framework, ... The reason you do not see it being used nowhere is cause the framework is ... > I'd also like to know how to rename the file and still have it work. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: using a config file
    ... > The previous programmer used a config file to load parameters for a ... You don't want to rename that file. ... Visual Studio will copy app.config ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: [opensuse] configuring printer via YaST
    ... I.e. with the old YaST printer module yast2-printer-2.16.32 ... because it uses the YaST "INI" agent to manipulate cupsd.conf ... When the cupsd config file /etc/cups/cupsd.conf is broken ...
    (SuSE)