[Ndiswrapper-general] Re: iwconfig command sequence + centrino
Status: Beta
Brought to you by:
pgiri
From: <ndi...@xa...> - 2004-03-15 18:00:29
|
To clarify, this issue affects me using 0.5 and 0.5-CVS (2004-03-15). giri@ wrote: > Can you try the CVS version (I am not sure if you are using 0.5 > release or CVS) and see if that works with either order? Actually you > should be able to do it all as > > iwconfig wlan0 mode Managed essid SSID key open KEY > dhclient wlan0 Yes, specifying all the options with a single command works fine for me. azoff@ wrote: > Did you think of 'modprobe ndiswrapper' or are you using another module? I have wlan0 set up as a modprobe alias. I've copied in some debug output below which may help. In the case where I issue the iwconfig commands in the wrong order (i.e. where I try to set the WEP key before the ESSID), followed by dhclient to set up my IP settings, this is the output I get: NdisUnchainBufferAtBack: 00000000 [repeated many times] NdisMCancelTimer NdisUnchainBufferAtBack: 00000000 [repeated many times] NdisQueryBufferSafe c22cf620, dff07ec0, dff07eb4 NdisUnchainBufferAtBack: c22cf620 NdisUnchainBufferAtBack: 00000000 NdisIndicateStatus 4001000b NdisIndicateStatusComplete NdisUnchainBufferAtBack: 00000000 [repeated many times] NdisQueryBufferSafe c22cf600, dff07ec0, dff07eb4 NdisUnchainBufferAtBack: c22cf600 NdisUnchainBufferAtBack: 00000000 NdisMCancelTimer NdisIndicateStatus 4001000b NdisIndicateStatusComplete NdisUnchainBufferAtBack: 00000000 NdisUnchainBufferAtBack: 00000000 NdisIndicateStatus 4001000b NdisIndicateStatusComplete NdisIndicateStatus 4001000b NdisIndicateStatusComplete ndis_open NdisUnchainBufferAtBack: 00000000 NdisQueryBufferSafe c22cf600, dff07d9c, dff07da8 NdisQueryBufferSafe c22cf600, dff07d7c, dff07d68 send_packets returning 00000103 NdisUnchainBufferAtBack: 00000000 NdisQueryBufferSafe c22cf600, dff07d9c, dff07da8 NdisQueryBufferSafe c22cf600, dff07d7c, dff07d68 send_packets returning 00000103 NdisQueryBufferSafe c22cf600, dff07d9c, dff07da8 NdisQueryBufferSafe c22cf600, dff07d7c, dff07d68 send_packets returning 00000103 NdisQueryBufferSafe c22cf600, dff07d9c, dff07da8 NdisQueryBufferSafe c22cf600, dff07d7c, dff07d68 send_packets returning 00000103 NdisQueryBufferSafe c22cf600, dff07d9c, dff07da8 NdisQueryBufferSafe c22cf600, dff07d7c, dff07d68 send_packets returning 00000103 NdisQueryBufferSafe c22cf600, dff07d9c, dff07da8 NdisQueryBufferSafe c22cf600, dff07d7c, dff07d68 send_packets returning 00000103 NdisUnchainBufferAtBack: 00000000 NdisQueryBufferSafe c22cf600, dff07d9c, dff07da8 NdisQueryBufferSafe c22cf600, dff07d7c, dff07d68 send_packets returning 00000103 NdisQueryBufferSafe c833c940, dff07d9c, dff07da8 NdisQueryBufferSafe c833c940, dff07d7c, dff07d68 send_packets returning 00000103 NdisQueryBufferSafe c833c940, dff07d9c, dff07da8 NdisQueryBufferSafe c833c940, dff07d7c, dff07d68 send_packets returning 00000103 If I issue the commands in the correct order, traffic flows between my box and the AP, and dmesg output is rather different, containing lots of lines like this NdisMIndicateReceivePacket entry packet_recycler Packet recycler running packet_recycler Picking packet at d176d428! NdisUnchainBufferAtBack: d14ae9e0 NdisUnchainBufferAtBack: 00000000 NdisQueryBufferSafe d299fa00, dff07d9c, dff07da8 NdisQueryBufferSafe d299fa00, dff07d7c, dff07d68 NdisGetFirstBufferFromPacketSafe: d1ae0c80 NdisQueryBufferSafe d299fa00, dff07ce4, dff07cd8 NdisQueryBufferOffset: entry NDIS_BUFFER_TO_SPAN_PAGES Contact me if you need more info, --Rob. |