Thread: [Ndiswrapper-general] how do I switch between 2 wlans?
Status: Beta
Brought to you by:
pgiri
From: sean d. <sea...@gm...> - 2008-02-24 04:05:11
|
I'm using ndiswrapper-1.52 on fedora 8 with a Broadcom 4311 chip. Works great. cat ifcfg-wlan0 DEVICE=wlan0 BOOTPROTO=dhcp ONBOOT=yes TYPE=Wireless ESSID=net1 I have 2 wlans. I'd like to be able to switch between them. iwlist wlan0 scan shows both. So I created ifcfg-wlan1: cat ifcfg-wlan1 DEVICE=wlan0 BOOTPROTO=dhcp ONBOOT=no TYPE=Wireless ESSID=net2 But that didn't work. ifdown wlan0 ifup wlan1 Determining IP information for wlan0... failed; no link present. Check cable? And ifup wlan0 then gives the same error. rmmod'ing and modprobe'ing ndiswrapper brings back wlan0. which makes me think this is somehow related. Any help appreciated. sean |
From: Pavel R. <pr...@gn...> - 2008-02-24 08:38:51
|
On Sat, 2008-02-23 at 22:46 -0500, sean darcy wrote: > So I created ifcfg-wlan1: > > cat ifcfg-wlan1 > DEVICE=wlan0 This should be wlan1, not wlan0. If you have more questions about those scripts, it's better to ask in a Fedora mailing list. This list is about the driver, and the scripts are Fedora specific. -- Regards, Pavel Roskin |
From: sean d. <sea...@gm...> - 2008-02-24 14:40:03
|
Pavel Roskin wrote: > On Sat, 2008-02-23 at 22:46 -0500, sean darcy wrote: > >> So I created ifcfg-wlan1: >> >> cat ifcfg-wlan1 >> DEVICE=wlan0 > > This should be wlan1, not wlan0. But ndiswrapper only creates wlan0. Doesn't matter if I name the script net2 or anything else, the device ndiswrapper created is wlan0 - correct? > > If you have more questions about those scripts, it's better to ask in a > Fedora mailing list. OK, I'll do that, but I don't know how specific the scripts are to fedora, but iwconfig takes the same inputs, and returns the same errors. This list is about the driver, and the scripts are > Fedora specific. > Again OK. But I thought this really was a driver question. Forget about the fedora scripts - use iwconfig - how do I get the driver created by ndiswrapper to point to different lans? sean |
From: Pavel R. <pr...@gn...> - 2008-02-24 20:55:21
|
On Sun, 2008-02-24 at 09:39 -0500, sean darcy wrote: > Pavel Roskin wrote: > > On Sat, 2008-02-23 at 22:46 -0500, sean darcy wrote: > > > >> So I created ifcfg-wlan1: > >> > >> cat ifcfg-wlan1 > >> DEVICE=wlan0 > > > > This should be wlan1, not wlan0. > > But ndiswrapper only creates wlan0. Doesn't matter if I name the script > net2 or anything else, the device ndiswrapper created is wlan0 - correct? I probably misinterpreted your words "I have 2 wlans". It looks like you have two networks, but one device. In this case, ndiswrapper is correct to create one device. What you need is roaming, and it should be implemented in the userspace, not in the driver. > > If you have more questions about those scripts, it's better to ask in a > > Fedora mailing list. > > OK, I'll do that, but I don't know how specific the scripts are to > fedora, but iwconfig takes the same inputs, and returns the same errors. I'm not going to participate in this thread, but if you want to get useful replies from others, I suggest that you are more explicit. The only error message you quoted was: "Determining IP information for wlan0... failed; no link present. Check cable?" I doubt iwconfig would produce that message. > Again OK. But I thought this really was a driver question. Forget about > the fedora scripts - use iwconfig - how do I get the driver created by > ndiswrapper to point to different lans? Set the ESSID and the WEP key: iwconfig wlan0 key 1234567890 open essid mynet Make sure the AP is valid - it confirms you are associated. Then configure the IP, either with dhclient, or with ifconfig and route. -- Regards, Pavel Roskin |