LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   rename "wlan0_rename" to "eth0" (https://www.linuxquestions.org/questions/linux-wireless-networking-41/rename-wlan0_rename-to-eth0-618042/)

replica9000 02-01-2008 06:10 PM

rename "wlan0_rename" to "eth0"
 
Ok so the last 20 times I installed ndiswrapper, it called my wireless card "eth0" but this time I installed it on a amd64 kernel it called it "wlan0_rename"

Code:

lo        no wireless extensions.

eth1      no wireless extensions.

eth0      no wireless extensions.

wlan0_rename  IEEE 802.11g  ESSID:"ESSID"
          Mode:Managed  Frequency:2.462 GHz  Access Point: XX:XX:XX:XX:XX:XX
          Bit Rate=11 Mb/s  Tx-Power=27 dBm
          Retry min limit:7  RTS thr:off  Fragment thr=2346 B
          Encryption key:BEBB-A9E0-A27A-F879-E7B4-04B4-49
          Link Quality=68/100  Signal level=-42 dBm  Noise level=-71 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0  Missed beacon:0

eth1 is my wired connection

eth0 shows up, used to be my wireless

wlan0_rename works, but should be eth0 instead

So how can I make wlan0_rename as eth0 again?

TheMadIndian 02-01-2008 09:11 PM

Quote:

Originally Posted by replica9000 (Post 3042988)
Ok so the last 20 times I installed ndiswrapper, it called my wireless card "eth0" but this time I installed it on a amd64 kernel it called it "wlan0_rename"

Code:

lo        no wireless extensions.

eth1      no wireless extensions.

eth0      no wireless extensions.

wlan0_rename  IEEE 802.11g  ESSID:"ESSID"
          Mode:Managed  Frequency:2.462 GHz  Access Point: XX:XX:XX:XX:XX:XX
          Bit Rate=11 Mb/s  Tx-Power=27 dBm
          Retry min limit:7  RTS thr:off  Fragment thr=2346 B
          Encryption key:BEBB-A9E0-A27A-F879-E7B4-04B4-49
          Link Quality=68/100  Signal level=-42 dBm  Noise level=-71 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0  Missed beacon:0

eth1 is my wired connection

eth0 shows up, used to be my wireless

wlan0_rename works, but should be eth0 instead

So how can I make wlan0_rename as eth0 again?

In modprobe.conf you can change the alias to something like this

alias wlan0 ndiswrapper

from wlan0_rename

replica9000 02-01-2008 09:21 PM

Actually while I was looking into the problem, I noticed the b43 driver kicked in and ndiswrapper doesn't seem to work. The b43 seems more stable than the last time I used it so I might stick with that. But it still comes up as wlan0_rename.

during start up it says:
Code:

eth0: unknown hardware address type 801
sky2 eth0: addr xx:xx:xx:xx:xx:xx
udev: renamed network interface eth0 to eth1
udev: renamed network interface wmaster0 to eth0
sky2 eth1: enabling interface
sky2 eth1: Link is up at 100 Mbps, full duplex, flow control both
eth1: no IPv6 routers present
eth1: no IPv6 routers present


TheMadIndian 02-02-2008 09:03 AM

Quote:

Originally Posted by replica9000 (Post 3043170)
Actually while I was looking into the problem, I noticed the b43 driver kicked in and ndiswrapper doesn't seem to work. The b43 seems more stable than the last time I used it so I might stick with that. But it still comes up as wlan0_rename.

during start up it says:
Code:

eth0: unknown hardware address type 801
sky2 eth0: addr xx:xx:xx:xx:xx:xx
udev: renamed network interface eth0 to eth1
udev: renamed network interface wmaster0 to eth0
sky2 eth1: enabling interface
sky2 eth1: Link is up at 100 Mbps, full duplex, flow control both
eth1: no IPv6 routers present
eth1: no IPv6 routers present


whats in modprobe.conf?

replica9000 02-02-2008 11:32 AM

Quote:

Originally Posted by TheMadIndian (Post 3043578)
whats in modprobe.conf?

I don't have a modprobe.conf. just a folder modprobe.d

TheMadIndian 02-02-2008 03:48 PM

Quote:

Originally Posted by replica9000 (Post 3043716)
I don't have a modprobe.conf. just a folder modprobe.d

what distro is it?

replica9000 02-02-2008 04:08 PM

Quote:

Originally Posted by TheMadIndian (Post 3043925)
what distro is it?

Debian, I only seem to have this issue on the amd64 kernels.

When I had ndiswrapper installed on the amd64 kernel, it said alternative driver was "ssb" instead of the usual "b43" or "bcm43xx"

Edit: Also, I have ndiswrapper 1.49rc4 working on an older K7 kernel (as eth0), I tried the newer 1.51 and that doesn't seem to work under any kernel. I have not tried 1.49rc4 under the amd64 kernel yet (cuz the amd64 stopped reporting my batter life)

nadavkav 02-20-2008 02:57 PM

i have the same issue since i updated to kernel 2.6.24 with module b43.
on debian sid (updated)

a little bit uncomfortable :-(

nadavkav 02-20-2008 03:33 PM

apparently, changing a rule in the udev system helped a little bit
in file : /etc/udev/rules.d/z25_persistent-net.rules

from...
Code:

SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:12:17:b6:8d:e5", NAME="eth2"
to...
Code:

SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:12:17:b6:8d:e5", ATTR{type}=="1", NAME="eth2"
i still get a redundant wmaster0 interface which IS wireless !
ifconfig:
Code:

lo        no wireless extensions.

eth1      no wireless extensions.

wmaster0  no wireless extensions.

eth2      IEEE 802.11g  ESSID:"home"
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:18:39:BC:52:67
          Bit Rate=1 Mb/s  Tx-Power=27 dBm
          Retry min limit:7  RTS thr:off  Fragment thr=2346 B
          Encryption key:off
          Link Quality=71/100  Signal level=-64 dBm  Noise level=-69 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0  Missed beacon:0


replica9000 03-05-2008 07:35 PM

Quote:

Originally Posted by nadavkav (Post 3064165)
apparently, changing a rule in the udev system helped a little bit
in file : /etc/udev/rules.d/z25_persistent-net.rules

from...
Code:

SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:12:17:b6:8d:e5", NAME="eth2"
to...
Code:

SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:12:17:b6:8d:e5", ATTR{type}=="1", NAME="eth2"
i still get a redundant wmaster0 interface which IS wireless !
ifconfig:
Code:

lo        no wireless extensions.

eth1      no wireless extensions.

wmaster0  no wireless extensions.

eth2      IEEE 802.11g  ESSID:"home"
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:18:39:BC:52:67
          Bit Rate=1 Mb/s  Tx-Power=27 dBm
          Retry min limit:7  RTS thr:off  Fragment thr=2346 B
          Encryption key:off
          Link Quality=71/100  Signal level=-64 dBm  Noise level=-69 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0  Missed beacon:0


I tried this in mine. I get a slightly different result but it works.
I only get a 5.5 mb/s max connection even with excellent signal strength.
Greatly speeds up boot time when "waiting for /dev to be fully populated..."

I now have eth0 again instead of wlan0_rename

The only thing is this now shows up under ifconfig:
Code:

wmaster0  Link encap:UNSPEC  HWaddr 00-15-A6-C2-CE-49-65-75-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

EDIT: Changing the value of ATTR{type}=="1" to something other than 1 just changed eth0 to wlan0

replica9000 03-05-2008 08:40 PM

Quote:

Originally Posted by replica9000 (Post 3079475)
I only get a 5.5 mb/s max connection even with excellent signal strength.

Ok I think it's the driver itself that causes this, though last I ran a kernel higher than 2.6.23 it was working fine. If I force the router to transmit from auto to a higher set rate, the wireless will match.

Trim-X- 03-28-2008 10:39 AM

Very good, it's work. I've Debian Lenny and today I have installed the kernel 2.6.24-1. I use too the bc43 driver for my wifi card, and I had the same problem.

I want to understand what does this change :

Quote:

apparently, changing a rule in the udev system helped a little bit
in file : /etc/udev/rules.d/z25_persistent-net.rules
from...
Quote:

SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:12:17:b6:8d:e5", NAME="eth2"
to...
Code:

SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:12:17:b6:8d:e5", ATTR{type}=="1", NAME="eth2"

Can someone explain me please ?


All times are GMT -5. The time now is 08:10 PM.