ndiswrapper

Sebastian Kaps wrote:
> Hi!
> 
> I'm now getting these messages when I do 'modprobe ndiswrapper':
> ,----
> | ndiswrapper version 0.11+CVS loaded (preempt=yes,smp=no)
> | PCI: Enabling device 0000:00:0b.0 (0000 -> 0002)
> | PCI: Found IRQ 12 for device 0000:00:0b.0
> | ndiswrapper: using irq 12
> | ndiswrapper (NdisAcquireSpinLock:907): Windows driver trying to use uninitialized lock cbadd774, fixing it.
> | ndiswrapper (setup_dev:1342): unable to get mac address from driver

When did you check out? We fixed a minor bug last night which caused 
exactly the error line above. If in doubt, please try again with the 
current version.

Jan

Hi!

> When did you check out? 

Yesterday afternoon (GMT).

> We fixed a minor bug last night which caused exactly the error line
> above. If in doubt, please try again with the current version.

Thanks! It works now:
,----
| ndiswrapper version 0.11+CVS loaded (preempt=yes,smp=no)
| PCI: Enabling device 0000:00:0b.0 (0000 -> 0002)
| PCI: Found IRQ 12 for device 0000:00:0b.0
| ndiswrapper: using irq 12
| ndiswrapper (NdisAcquireSpinLock:907): Windows driver trying to use uninitialized lock cb057b74, fixing it.
| wlan0: ndiswrapper ethernet device 00:04:e2:a5:ad:12 using driver 2802w
| wlan0: encryption modes supported: WEP, WPA with TKIP, AES/CCMP
| ndiswrapper: driver 2802w () added
`----
-- 
Ciao, Sebastian

Hi!

Ok, now I got the interface up and running but it won't talk to my AP.
I can use "iwlist wlan0 scan" to bring up information about my AP, but I
can't set the essid, bit rate and the AP's MAC:

# iwconfig wlan0
wlan0     IEEE 802.11g  ESSID:off/any  Nickname:"server"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:00:00:00:00:00   
          Bit Rate=2 Mb/s   Tx-Power:32 dBm   
          RTS thr=2347 B   Fragment thr=2346 B   
          Encryption key:0303-2383-3353-9343-8373-6343-13   Security mode:restricted
          Power Management:off
          Link Quality:100  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:3  Invalid misc:156   Missed beacon:0

# iwconfig wlan0 rate 54M
# iwconfig wlan0 00:04:0E:1F:23:4C
# iwconfig wlan0 essid WLAN
# iwconfig wlan0
wlan0     IEEE 802.11g  ESSID:off/any  Nickname:"server"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:00:00:00:00:00   
          Bit Rate=2 Mb/s   Tx-Power:32 dBm   
          RTS thr=2347 B   Fragment thr=2346 B   
          Encryption key:0303-2383-3353-9343-8373-6343-13   Security mode:restricted
          Power Management:off
          Link Quality:100  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:3  Invalid misc:164   Missed beacon:0

:-?

-- 
Ciao, Sebastian

Le 26.10.2004 13:03:31, Sebastian Kaps a =E9crit=A0:
>Hi!
>
>Ok, now I got the interface up and running but it won't talk to my AP.
>I can use "iwlist wlan0 scan" to bring up information about my AP, but
>I
>can't set the essid, bit rate and the AP's MAC:
>
># iwconfig wlan0
>wlan0     IEEE 802.11g  ESSID:off/any  Nickname:"server"
>          Mode:Managed  Frequency:2.437 GHz  Access Point:
>00:00:00:00:00:00
>          Bit Rate=3D2 Mb/s   Tx-Power:32 dBm
>          RTS thr=3D2347 B   Fragment thr=3D2346 B
>          Encryption key:0303-2383-3353-9343-8373-6343-13   Security
>mode:restricted
>          Power Management:off
>          Link Quality:100  Signal level:0  Noise level:0
>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>          Tx excessive retries:3  Invalid misc:156   Missed beacon:0
>
># iwconfig wlan0 rate 54M
># iwconfig wlan0 00:04:0E:1F:23:4C
># iwconfig wlan0 essid WLAN
># iwconfig wlan0
>wlan0     IEEE 802.11g  ESSID:off/any  Nickname:"server"
>          Mode:Managed  Frequency:2.437 GHz  Access Point:

which channel is using your access point ?

>00:00:00:00:00:00
>          Bit Rate=3D2 Mb/s   Tx-Power:32 dBm
>          RTS thr=3D2347 B   Fragment thr=3D2346 B
>          Encryption key:0303-2383-3353-9343-8373-6343-13   Security
>mode:restricted
>          Power Management:off
>          Link Quality:100  Signal level:0  Noise level:0
>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>          Tx excessive retries:3  Invalid misc:164   Missed beacon:0
>
>:-?
>
>--
>Ciao, Sebastian
>

Jean-Luc

Hi Jean-Luc!

>> # iwconfig wlan0
>> wlan0     IEEE 802.11g  ESSID:off/any  Nickname:"server"
>> Mode:Managed  Frequency:2.437 GHz  Access Point:

> which channel is using your access point ?

The AP uses Channel 6.
2.437 should be the correct value and I'm also able to change it with
iwconfig.

-- 
Ciao, Sebastian

On Tue, Oct 26, 2004 at 01:33:14PM +0200, Sebastian Kaps wrote:
hi Sebastien,

> Hi Jean-Luc!
>=20
> >> # iwconfig wlan0
> >> wlan0     IEEE 802.11g  ESSID:off/any  Nickname:"server"
> >> Mode:Managed  Frequency:2.437 GHz  Access Point:
>=20
> > which channel is using your access point ?
>=20
> The AP uses Channel 6.
> 2.437 should be the correct value and I'm also able to change it with
> iwconfig.

yes, should be right, but anyway in my case, the card has found the correct
frequency from its own.

For your information, here is my /etc/network/interface
(mostly from the FAQ)

auto wlan0
iface wlan0 inet static
    address 192.168.1.11
    netmask 255.255.255.0
    gateway 192.168.1.1
    wireless_key BB90340FA82B6FD7D26A1DC735
    wireless_essid WANADOO-79EB
    pre-up if grep -q ndiswrapper /proc/modules; then :; else modprobe ndis=
wrapper; fi


And here is a result of a iwconfig (I use channel 10):

wlan0   IEEE 802.11g  ESSID:"WANADOO-79EB" =20
        Mode:Managed  Frequency:2.457 GHz  Access Point: 00:90:4B:84:F7:96 =
 =20
        Bit Rate:24 Mb/s   Tx-Power:32 dBm  =20
        RTS thr:2347 B   Fragment thr:2346 B  =20
        Encryption key:BB90-340F-A82B-6FD7-D26A-1DC7-35 Security mode:restr=
icted
        Power Management:off
        Link Quality:96/100 Signal level:-67 dBm Noise level:-256 dBm
        Rx invalid nwid:0  Rx invalid crypt:0 Rx invalid frag:0
	Tx excessive retries:744 Invalid misc:9123 Missed beacon:0
										-
Regards


Jean-Luc
>=20
> --=20
> Ciao, Sebastian

Hi Jean-Luc!

> yes, should be right, but anyway in my case, the card has found the correct
> frequency from its own.

I'm not sure if I did initially set the channel, so maybe it was
auto-detected too.

> For your information, here is my /etc/network/interface
> (mostly from the FAQ)

Thanks. I didn't know about the wireless_<function> options.
Anyway, that doesn't change anything. I still can't set the ESSID.
Am I correct that I have to set the ESSID to the correct value in order
to get it all working?

-- 
Ciao, Sebastian

On Tue, Oct 26, 2004 at 01:03:31PM +0200, Sebastian Kaps wrote:

> # iwconfig wlan0 00:04:0E:1F:23:4C

What does this do?  I can't find this 'no keyword' syntax referenced
in the iwconfig manpage, and I don't have hardware to test on.  Does
it set the AP?

Hi Adrian!

>> # iwconfig wlan0 00:04:0E:1F:23:4C

> What does this do?  

Oh, sorry. This was supposed to mean "iwconfig wlan0 ap ...".

-- 
Ciao, Sebastian

Le 26.10.2004 15:17:56, Sebastian Kaps a =E9crit=A0:
>Hi Jean-Luc!
>
>> yes, should be right, but anyway in my case, the card has found the
>correct
>> frequency from its own.
>
>I'm not sure if I did initially set the channel, so maybe it was
>auto-detected too.
>
>> For your information, here is my /etc/network/interface
>> (mostly from the FAQ)
>
>Thanks. I didn't know about the wireless_<function> options.
>Anyway, that doesn't change anything. I still can't set the ESSID.
>Am I correct that I have to set the ESSID to the correct value in =20
> order
>to get it all working?

No, if the essid is left blank you can see "any" and it will be set =20
according to the negociation with the access point

sen man (7) wireless for the wirelesss functions in /etc/network/=20
interfaces

>
>--
>Ciao, Sebastian


J-L

Hi Jean-Luc!

> No, if the essid is left blank you can see "any" and it will be set  
> according to the negociation with the access point

Ah, I see. So what do I have to do to force the card to negotiate with
the access point? I'm new to WLAN, so excuse me if I don't see the
obvious.

> sen man (7) wireless for the wirelesss functions in /etc/network/ 
> interfaces

Yes, I've already found it.

-- 
Ciao, Sebastian

Le 26.10.2004 17:44:48, Sebastian Kaps a =E9crit=A0:
>Hi Jean-Luc!
>
>> No, if the essid is left blank you can see "any" and it will be set
>> according to the negociation with the access point
>
>Ah, I see. So what do I have to do to force the card to negotiate with
>the access point? I'm new to WLAN, so excuse me if I don't see the
>obvious.

In *my* case, I've to press a button on the access point for it to =20
register a new WiFI device, maybe it is the same in your case?

The following command will give you the access points and ad-hoc cells =20
available around:

iwlist wlan0 scan

>
>> sen man (7) wireless for the wirelesss functions in /etc/network/
>> interfaces
>
>Yes, I've already found it.
>
>--
>Ciao, Sebastian

J-L

Hi Jean-Luc!

> In *my* case, I've to press a button on the access point for it to  
> register a new WiFI device, maybe it is the same in your case?

My AP doesn't have such a button. According to its documentation I don't
need to register any WiFi device. I guess this is just needed if there's
an authentication mechanism based on a device's MAC address.

> The following command will give you the access points and ad-hoc cells  
> available around:
> iwlist wlan0 scan

Yes, I know that. I can "see" my access point:
,----
| wlan0     Scan completed :
|           Cell 01 - Address: 00:04:0E:1F:23:4C
|                     ESSID:"WLAN"
|                     Protocol:IEEE 802.11g
|                     Mode:Managed
|                     Frequency:2.437 GHz (Channel 6)
|                     Quality:0/100  Signal level:-86 dBm  Noise level:-256 dBm
|                     Encryption key:on
|                     Bit Rate:1 Mb/s
|                     Bit Rate:2 Mb/s
|                     Bit Rate:5.5 Mb/s
|                     Bit Rate:11 Mb/s
|                     Bit Rate:6 Mb/s
|                     Bit Rate:9 Mb/s
|                     Bit Rate:12 Mb/s
|                     Bit Rate:18 Mb/s
|                     Bit Rate:24 Mb/s
|                     Bit Rate:36 Mb/s
|                     Bit Rate:48 Mb/s
|                     Bit Rate:54 Mb/s
|                     Extra:bcn_int=200
|                     Extra:atim=2
`----
So what do I have to do now?
As far as I understand, I have to set the ESSID on the wlan card to
"WLAN" (which does not work) and then it's supposed to work.
Or am I wrong?

-- 
Ciao, Sebastian

Le 26.10.2004 20:00:06, Sebastian Kaps a =E9crit=A0:
>Hi Jean-Luc!
>
>> In *my* case, I've to press a button on the access point for it to
>> register a new WiFI device, maybe it is the same in your case?
>
>My AP doesn't have such a button. According to its documentation I
>don't
>need to register any WiFi device. I guess this is just needed if
>there's
>an authentication mechanism based on a device's MAC address.
>
>> The following command will give you the access points and ad-hoc
>cells
>> available around:
>> iwlist wlan0 scan
>
>Yes, I know that. I can "see" my access point:
>,----
>| wlan0     Scan completed :
>|           Cell 01 - Address: 00:04:0E:1F:23:4C
>|                     ESSID:"WLAN"
>|                     Protocol:IEEE 802.11g
>|                     Mode:Managed
>|                     Frequency:2.437 GHz (Channel 6)
>|                     Quality:0/100  Signal level:-86 dBm  Noise
>level:-256 dBm
>|                     Encryption key:on
>|                     Bit Rate:1 Mb/s
>|                     Bit Rate:2 Mb/s
>|                     Bit Rate:5.5 Mb/s
>|                     Bit Rate:11 Mb/s
>|                     Bit Rate:6 Mb/s
>|                     Bit Rate:9 Mb/s
>|                     Bit Rate:12 Mb/s
>|                     Bit Rate:18 Mb/s
>|                     Bit Rate:24 Mb/s
>|                     Bit Rate:36 Mb/s
>|                     Bit Rate:48 Mb/s
>|                     Bit Rate:54 Mb/s
>|                     Extra:bcn_int=3D200
>|                     Extra:atim=3D2
>`----
>So what do I have to do now?
>As far as I understand, I have to set the ESSID on the wlan card to
>"WLAN" (which does not work) and then it's supposed to work.
>Or am I wrong?

Yes, it should be 'WLAN'

Now, there are 2 things to notice:
- he Signal level of -86 dbm is very poor, but maybe this is only a bad =20
sample

- the access point is set to "encryption key: on"
Are you sure of your key?

>
>--
>Ciao, Sebastian

J-L

Hi Jean-Luc!

I got it! The problem was that the key mode defaults to "restricted"
while on my AP it is "open". After changing that, it worked. Finally :-)

-- 
Ciao, Sebastian

On Tue, Oct 26, 2004 at 03:15:14PM +0200, Martin H. Goldammer wrote:

> And setting is still not possible, iwconfig wlan0 rate 11M still
> says "Error for wireless request "Set Bit Rate" (8B20) : SET failed
> on device wlan0 ; Operation not supported."
>
> Do you have any idea?

Unfortunately, I don't.  I know my madwifi seemed to prefer specifying
the whole '11Mb/s', but that might have just been a mistaken
observation.

You can try that, but if it doesn't work, I really have no idea.

Dirk Vornheder wrote:

>I compile cvs version with DEBUG=3 but i get only this:
>
>Oct 26 11:04:36 pcneu kernel: ndiswrapper version 0.11+CVS loaded 
>(preempt=no,smp=no)
>Oct 26 11:04:36 pcneu loadndisdriver: loadndisdriver: main(479): version 0.11 
>started
>Oct 26 11:04:42 pcneu kernel: ndiswrapper (NdisWriteErrorLogEntry:195): log: 
>C000138A, length: 3 (c0000001)
>Oct 26 11:04:42 pcneu kernel:
>Oct 26 11:04:42 pcneu kernel: ndiswrapper (ndis_init_one_usb:1668): Windows 
>driver couldn't initialize the device (C0010006)
>Oct 26 11:04:42 pcneu kernel: wlanuig: probe of 4-5:1.0 failed with error -22
>Oct 26 11:04:42 pcneu kernel: usbcore: registered new driver wlanuig
>Oct 26 11:04:42 pcneu kernel: ndiswrapper: driver wlanuig ( ,10/31/2003, 
>1.0.3) added
>
>  
>
Check your log file under /var/log/messages (sometimes also 
/var/log/syslog). Depending on your systems configuration, not every 
kernel messages is printed on the console. Also make sure that you load 
the correct version of ndiswrapper, e.g. by explicitely calling insmod 
<path>/ndiswrapper.ko.

Jan