Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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
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
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
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)
Last edited by replica9000; 02-02-2008 at 04:16 PM.
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
Last edited by replica9000; 03-05-2008 at 07:50 PM.
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.
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...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.