Re: ndis0 does not associate since update to RELENG_6
On Wednesday 18 January 2006 02:58, Bill Paul wrote: > # ifconfig ndis0 ssid "yourssid" bssid up you can say bssid any adding bssid seems to be crucial for associating certain wlcards especial when using ndis and 11g then for using wep you may try as wepmode on weptxkey 1 wepkey 0x0101010111 João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[Fixed] Re: ndis0 does not associate since update to RELENG_6
[EMAIL PROTECTED] (Bill Paul) wrote: > > Is there a way I can provide more information? > > You haven't said yet what manufacturer/model your access point is. It's a Netgear WGT624 (Hardwareversion V3H1/Firmwareversion V1.1.125_1.1.1GR). I tried to associate ndis0 with wi0 in hostap mode and got the same results. > You also haven't said what Windows driver version you're using, but > you need to cheat a bit to figure that out. I usually do: > > % strings -e l foo.sys > Near the end of the output, there should be a bunch of version > information, including the vendor name of whoever built the driver > (in this case Intel). You might try downloading the latest driver > from Intel. (They have a generic one for their Centrino wireless > devices.) The old driver which was shipped with the Laptop: StringFileInfo 040904B0 Comments NDIS 5 Miniport Driver for Win2000 CompanyName Intel Corporation FileDescription Intel Wireless LAN Driver FileVersion 8010-28 Driver InternalName w22n50.SYS LegalCopyright Copyright Intel Corporation 2004 OriginalFilename w22n50.SYS ProductName Intel Wireless LAN Adapter VarFileInfo Translation The "new" one I downloaded from Intel today: StringFileInfo 040904B0 Comments NDIS 5.1 Miniport Driver CompanyName Intel Corporation FileDescription Intel Wireless LAN Driver FileVersion 9003-9 Driver InternalName w29n51.SYS LegalCopyright Copyright Intel Corporation 2004 OriginalFilename w29n51.SYS ProductName Intel Wireless LAN Adapter VarFileInfo Translation > You also haven't said what sort of laptop this is. Wouldn't hurt to > know that either. IBM ThinkPad R51 UN0K6GE. > Unfortunately, this is the sort of thing that can only be debugged > with the system sitting in front of me. I can't do it by remote > control, and I can't know exactly what information to ask you. I have > to experiment, and I can't do that from here. > > You should turn WEP off completely, make sure the AP is set for open > authentication mode, and try getting it to authenticate without WEP > first. It's one less variable to worry about. Try using the following: > > # ifconfig ndis0 ssid "" up > > # ifconfig ndis0 ssid "yourssid" bssid up Specifying the bssid is the solution. ifconfig ndis0 ssid ec60bfg3b4 bssid wepkey 1:0x\ deftxkey 1 wepmode on up Works with the new and the old driver and with both APs. [EMAIL PROTECTED] ~ $ifconfig ndis0 ndis0: flags=8843 mtu 1500 inet6 fe ... 7500%ndis0 prefixlen 64 scopeid 0x3 inet 192.168.0.32 netmask 0xff00 broadcast 192.168.0.255 ether 00 ... 00 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) status: associated ssid ec60bfg3b4 channel 11 bssid 00:... authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 100 protmode CTS Thanks for your time Bill. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: ndis0 does not associate since update to RELENG_6
> > What command do you type to try to get it to associate? > > kldload wlan_wep.ko > kldload w22n50_sys.ko > > ifconfig ndis0 ssid ec60bfg3b4 wepkey 1:0xhexkey \ > deftxkey 1 wepmode on > ifconfig ndis0 inet 192.168.0.32 up > [...] > It was my experience that ifconfig on 6.0 will not chose the first > key by default. I always have to add deftxkey 1. > > I can't use your exact command because I know my wepkey only in > hexadecimal. > > But if I disable WEP in the access point and use > ifconfig ndis0 ssid ec60bfg3b4 up > it fails to associate (or even to set the ssid) as well: > > [EMAIL PROTECTED] ~ #ifconfig ndis0 > ndis0: flags=8843 mtu 1500 > inet6 fe ... 7500%ndis0 prefixlen 64 scopeid 0x3 > ether 00: ... :00 > media: IEEE 802.11 Wireless Ethernet autoselect > status: no carrier > ssid "" channel 1 > authmode OPEN privacy OFF txpowmax 100 protmode CTS > > > You don't state what command you actually use. You should have > > specified it in your e-mail. Note that usually the WEP key has to be > > either 5 or 13 characters. > > You're right, sorry. > > I use the hexadecimal notation and my key is correctly recognised as > 104-bit. > > ifconfig ndis0 ssid ec60bfg3b4 wepkey 1:0xhexkey \ > deftxkey 1 wepmode on > ifconfig ndis0 inet 192.168.0.32 up > > The two commands above work for iwi0, wi0 and ath0. > > I use the same shell script I used on 5.4. The only > change I made was adding "deftxkey 1" which wasn't > needed before. > > > > Is anybody else using this device with FreeBSD 6.0? > > > > I've tested the 2200BG myself with the NDISulator 6.0 and I've been > > able to get it to associate with 11g networks. I don't know what's > > wrong in your case. > > Is there a way I can provide more information? You haven't said yet what manufacturer/model your access point is. You also haven't said what Windows driver version you're using, but you need to cheat a bit to figure that out. I usually do: % strings -e l foo.sys or % strings -e l foo_sys.ko Near the end of the output, there should be a bunch of version information, including the vendor name of whoever built the driver (in this case Intel). You might try downloading the latest driver from Intel. (They have a generic one for their Centrino wireless devices.) You also haven't said what sort of laptop this is. Wouldn't hurt to know that either. Unfortunately, this is the sort of thing that can only be debugged with the system sitting in front of me. I can't do it by remote control, and I can't know exactly what information to ask you. I have to experiment, and I can't do that from here. You should turn WEP off completely, make sure the AP is set for open authentication mode, and try getting it to authenticate without WEP first. It's one less variable to worry about. Try using the following: # ifconfig ndis0 ssid "" up # ifconfig ndis0 ssid "yourssid" bssid up Don't fiddle with the channel setting. Windows drivers don't let you set the channel unless you're in ad-hoc mode. (Some drivers erroneously process channel selectin requests in infrastructure mode too, but the results can be unpredictable.) -Bill -- = -Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu [EMAIL PROTECTED] | Wind River Systems = you're just BEGGING to face the moose = ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ndis0 does not associate since update to RELENG_6
[EMAIL PROTECTED] (Bill Paul) wrote: > > I fail to get the following device working since my update > > from RELENG_5 to RELENG_6 a few days ago: > > > > [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 > > rev=0x05 hdr=0x00 vendor = 'Intel Corporation' > > device = 'PRO/Wireless 2200BG Network Connection' > > class= network > > > > It worked fine with 5.4 and was recognised as > > > > ndis0: mem > > 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci > > ndis0: NDIS API version: 5.0 > > ndis0: Ethernet address: 00: ... :00 > > ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 5.5Mbps 11Mbps > > ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps > > 54Mbps > > > > On 6.0 it is still recognised, but the last two lines are missing. > > That's normal. > > > I'm using GENERIC, the driver module was generated with ndisgen > > out of w22n51.inf and w22n50.sys. This is the combination I alway > > used. > > > > ndis0 can scan for access points, but can't associate with or > > without WEP encryption. > > What command do you type to try to get it to associate? kldload wlan_wep.ko kldload w22n50_sys.ko ifconfig ndis0 ssid ec60bfg3b4 wepkey 1:0xhexkey \ deftxkey 1 wepmode on ifconfig ndis0 inet 192.168.0.32 up > > [EMAIL PROTECTED] ~ $ifconfig ndis0 list scan > > SSIDBSSID CHAN RATE S:N INT CAPS > > ec60bfg3b4 00: ... :a8 11 54M 149:0 100 > > EP ??? ??? ??? ??? ??? ??? WME > > > > [EMAIL PROTECTED] ~ $ifconfig ndis0 > > ndis0: flags=8843 mtu 1500 > > inet 192.168.0.32 netmask 0xff00 broadcast 192.168.0.255 > > inet6 fe80: ... :7500%ndis0 prefixlen 64 scopeid 0x5 > > ether 00: ... :00 > > media: IEEE 802.11 Wireless Ethernet autoselect > > status: no carrier > > ssid "" channel 1 > > authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit > > txpowmax 100 protmode CTS > > > > I found a similar problem which should be fixed in current, > > but I don't know if the changes already hit stable. > > http://freebsd.rambler.ru/bsdmail/freebsd-current_2005/msg11802.html > > > > My problem is not exactly the same though, I have no trouble setting > > the bssid. > > You should be able to do: > > # ifconfig ndis0 ssid ec60bfg3b4 wepmode on wepkey "0123456789123" up It was my experience that ifconfig on 6.0 will not chose the first key by default. I always have to add deftxkey 1. I can't use your exact command because I know my wepkey only in hexadecimal. But if I disable WEP in the access point and use ifconfig ndis0 ssid ec60bfg3b4 up it fails to associate (or even to set the ssid) as well: [EMAIL PROTECTED] ~ #ifconfig ndis0 ndis0: flags=8843 mtu 1500 inet6 fe ... 7500%ndis0 prefixlen 64 scopeid 0x3 ether 00: ... :00 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid "" channel 1 authmode OPEN privacy OFF txpowmax 100 protmode CTS > You don't state what command you actually use. You should have > specified it in your e-mail. Note that usually the WEP key has to be > either 5 or 13 characters. You're right, sorry. I use the hexadecimal notation and my key is correctly recognised as 104-bit. ifconfig ndis0 ssid ec60bfg3b4 wepkey 1:0xhexkey \ deftxkey 1 wepmode on ifconfig ndis0 inet 192.168.0.32 up The two commands above work for iwi0, wi0 and ath0. I use the same shell script I used on 5.4. The only change I made was adding "deftxkey 1" which wasn't needed before. > > Is anybody else using this device with FreeBSD 6.0? > > I've tested the 2200BG myself with the NDISulator 6.0 and I've been > able to get it to associate with 11g networks. I don't know what's > wrong in your case. Is there a way I can provide more information? Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: ndis0 does not associate since update to RELENG_6
in message <[EMAIL PROTECTED]>, wrote Fabian Keil thusly... > > Parv <[EMAIL PROTECTED]> wrote: > > > in message <[EMAIL PROTECTED]>, > > wrote Fabian Keil thusly... > > > > > > Fabian Keil <[EMAIL PROTECTED]> wrote: > > > > > > > I fail to get the following device working since my update > > > > from RELENG_5 to RELENG_6 a few days ago: > > > > > > > > [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 > > > > rev=0x05 hdr=0x00 vendor = 'Intel Corporation' > > > > device = 'PRO/Wireless 2200BG Network Connection' > > > > class= network > > > > > > I found a work around. It still works > > > with /usr/ports/net/iwi-firmware/: > > > > I also found the same about ndis driver. I was not even able to > > assign a ssid, mode, or a channel to a ndis0 interface. > > > > At least net/iwi-firmware works w/ WPA (even if the interface > > causes freeze after waking up from long sleep on IBM Thinkpad > > T42; > > Did you try to load and unload if_iwi.ko in /etc/rc.resume and > /etc/rc.suspend? No, i hadn't; currently i am doing it manually when i am not sure about the length of the sleep state. I should look in to it, hunh.? > > BTW, when i read that you "found a work around", i was expecting > > a work around to make ndis work. > > I'm sorry for my misleading wording then. Of course it's just a > work around to get the PRO/Wireless 2200BG working at all. No problem. Actually, i myself am happy as long as there is some way to have a secure (semi-)stable wireless connection, on FreeBSD, w/ not-too-expensive hardware. > It's just that I had forgotten about the existence of iwi. The > last days I was using em0 to connect my Laptop to the network. > Getting if_iwi to work after my initial posting was a relief. Same here, almost. I had not looked particularly hard in iwi or ndis -- but was aware of both -- until my sister's nagging broke me to buy a wireless AP/router. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ndis0 does not associate since update to RELENG_6
Parv <[EMAIL PROTECTED]> wrote: > in message <[EMAIL PROTECTED]>, > wrote Fabian Keil thusly... > > > > Fabian Keil <[EMAIL PROTECTED]> wrote: > > > > > I fail to get the following device working since my update > > > from RELENG_5 to RELENG_6 a few days ago: > > > > > > [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 > > > rev=0x05 hdr=0x00 vendor = 'Intel Corporation' > > > device = 'PRO/Wireless 2200BG Network Connection' > > > class= network > I also found the same about ndis driver. I was not even able to > assign a ssid, mode, or a channel to a ndis0 interface. I forgot to confirm that I can't assign ssid and channel as well. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: ndis0 does not associate since update to RELENG_6
> I fail to get the following device working since my update > from RELENG_5 to RELENG_6 a few days ago: > > [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 > hdr=0x00 vendor = 'Intel Corporation' > device = 'PRO/Wireless 2200BG Network Connection' > class= network > > It worked fine with 5.4 and was recognised as > > ndis0: mem > 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci > ndis0: NDIS API version: 5.0 > ndis0: Ethernet address: 00: ... :00 > ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 5.5Mbps 11Mbps > ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > > On 6.0 it is still recognised, but the last two lines are missing. That's normal. > I'm using GENERIC, the driver module was generated with ndisgen > out of w22n51.inf and w22n50.sys. This is the combination I alway used. > > ndis0 can scan for access points, but can't associate with or without > WEP encryption. What command do you type to try to get it to associate? > [EMAIL PROTECTED] ~ $ifconfig ndis0 list scan > SSIDBSSID CHAN RATE S:N INT CAPS > ec60bfg3b4 00: ... :a8 11 54M 149:0 100 > EP ??? ??? ??? ??? ??? ??? WME > > [EMAIL PROTECTED] ~ $ifconfig ndis0 > ndis0: flags=8843 mtu 1500 > inet 192.168.0.32 netmask 0xff00 broadcast 192.168.0.255 > inet6 fe80: ... :7500%ndis0 prefixlen 64 scopeid 0x5 > ether 00: ... :00 > media: IEEE 802.11 Wireless Ethernet autoselect > status: no carrier > ssid "" channel 1 > authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax > 100 protmode CTS > > I found a similar problem which should be fixed in current, > but I don't know if the changes already hit stable. > http://freebsd.rambler.ru/bsdmail/freebsd-current_2005/msg11802.html > > My problem is not exactly the same though, I have no trouble setting > the bssid. You should be able to do: # ifconfig ndis0 ssid ec60bfg3b4 wepmode on wepkey "0123456789123" up You don't state what command you actually use. You should have specified it in your e-mail. Note that usually the WEP key has to be either 5 or 13 characters. > Additionally I can't set the mode to 11g: You don't have to do that. It'll associate with 11g automatically. > Is anybody else using this device with FreeBSD 6.0? I've tested the 2200BG myself with the NDISulator 6.0 and I've been able to get it to associate with 11g networks. I don't know what's wrong in your case. -Bill -- = -Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu [EMAIL PROTECTED] | Wind River Systems = you're just BEGGING to face the moose = ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ndis0 does not associate since update to RELENG_6
Parv <[EMAIL PROTECTED]> wrote: > in message <[EMAIL PROTECTED]>, > wrote Fabian Keil thusly... > > > > Fabian Keil <[EMAIL PROTECTED]> wrote: > > > > > I fail to get the following device working since my update > > > from RELENG_5 to RELENG_6 a few days ago: > > > > > > [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 > > > rev=0x05 hdr=0x00 vendor = 'Intel Corporation' > > > device = 'PRO/Wireless 2200BG Network Connection' > > > class= network > > > > I found a work around. It still works > > with /usr/ports/net/iwi-firmware/: > > I also found the same about ndis driver. I was not even able to > assign a ssid, mode, or a channel to a ndis0 interface. > > At least net/iwi-firmware works w/ WPA (even if the interface causes > freeze after waking up from long sleep on IBM Thinkpad T42; Did you try to load and unload if_iwi.ko in /etc/rc.resume and /etc/rc.suspend? > BTW, when i read that you "found a work around", i was expecting a > work around to make ndis work. I'm sorry for my misleading wording then. Of course it's just a work around to get the PRO/Wireless 2200BG working at all. It's just that I had forgotten about the existence of iwi. The last days I was using em0 to connect my Laptop to the network. Getting if_iwi to work after my initial posting was a relief. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: ndis0 does not associate since update to RELENG_6
in message <[EMAIL PROTECTED]>, wrote Fabian Keil thusly... > > Fabian Keil <[EMAIL PROTECTED]> wrote: > > > I fail to get the following device working since my update > > from RELENG_5 to RELENG_6 a few days ago: > > > > [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 > > rev=0x05 hdr=0x00 vendor = 'Intel Corporation' > > device = 'PRO/Wireless 2200BG Network Connection' > > class= network > > I found a work around. It still works with /usr/ports/net/iwi-firmware/: I also found the same about ndis driver. I was not even able to assign a ssid, mode, or a channel to a ndis0 interface. At least net/iwi-firmware works w/ WPA (even if the interface causes freeze after waking up from long sleep on IBM Thinkpad T42; or after some time of good/stable connectivity, ping to Linksys WRT54G (router, running as a AP/switch) goes unanswered). BTW, when i read that you "found a work around", i was expecting a work around to make ndis work. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ndis0 does not associate since update to RELENG_6
Fabian Keil <[EMAIL PROTECTED]> wrote: > I fail to get the following device working since my update > from RELENG_5 to RELENG_6 a few days ago: > > [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 > rev=0x05 hdr=0x00 vendor = 'Intel Corporation' > device = 'PRO/Wireless 2200BG Network Connection' > class= network I found a work around. It still works with /usr/ports/net/iwi-firmware/: [EMAIL PROTECTED] ~ $ifconfig iwi0 iwi0: flags=8843 mtu 1500 inet 192.168.0.32 netmask 0xff00 broadcast 192.168.0.255 inet6 fe ... :7500%iwi0 prefixlen 64 scopeid 0x5 ether 00: ... :00 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (OFDM/48Mbps) status: associated ssid ec60bfg3b4 channel 11 bssid 00:...:a8 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 100 protmode CTS bintval 100 Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
