Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Yuri wrote: Isn't it better to have 2 separate flags in CAPS: for example WEP and WEPHW? WEP would mean that WEP is supported and WEPHW would mean that it's supported through hardware. It wouldn't make sense. Flags are used to specify capabilities of the interface, not things provided by the operating system. Yuri - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkfF81YACgkQwMJqmJVx946NRQCggHH4abFDjkRObQst1QgXm2Wb UlAAn2Y9B4u9v1o2FYg38txv8VlYjysF =10Nx -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?
I have a Linksys PCI wireless card that is being attached by ral driver: ral0: Ralink Technology RT2561S mem 0xcffe8000-0xcffe irq 17 at device 10.0 on pci0 ral0: MAC/BBP RT2561C, RF RT2527 ral0: Ethernet address: 00:18:f8:2e:40:25 ral0: [ITHREAD] But when I do 'ifconfig ral0 list caps' it returns: ral0=2181e500IBSS,HOSTAP,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,WPA1,WPA2,BGSCAN and WEP isn't there. This looks amazing since WEP is older and very widespread. So how can I tell if this card can't really support WEP or it's the driver that can't support it? Also command: ifconfig ral0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 authmode open mode 11g mediaopt hostap succeeds though CAPS doesn't have WEP. Isn't this a bug? Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?
I have a Linksys PCI wireless card that is being attached by ral driver: ral0: Ralink Technology RT2561S mem 0xcffe8000-0xcffe irq 17 at device 10.0 on pci0 ral0: MAC/BBP RT2561C, RF RT2527 ral0: Ethernet address: 00:18:f8:2e:40:25 ral0: [ITHREAD] But when I do 'ifconfig ral0 list caps' it returns: ral0=2181e500IBSS,HOSTAP,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,WPA1,WPA2,BGSCAN and WEP isn't there. This looks amazing since WEP is older and very widespread. So how can I tell if this card can't really support WEP or it's the driver that can't support it? Also command: ifconfig ral0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 authmode open mode 11g mediaopt hostap succeeds though CAPS doesn't have WEP. Isn't this a bug? Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?
Yuri wrote: I have a Linksys PCI wireless card that is being attached by ral driver: ral0: Ralink Technology RT2561S mem 0xcffe8000-0xcffe irq 17 at device 10.0 on pci0 ral0: MAC/BBP RT2561C, RF RT2527 ral0: Ethernet address: 00:18:f8:2e:40:25 ral0: [ITHREAD] But when I do 'ifconfig ral0 list caps' it returns: ral0=2181e500IBSS,HOSTAP,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,WPA1,WPA2,BGSCAN and WEP isn't there. This looks amazing since WEP is older and very widespread. So how can I tell if this card can't really support WEP or it's the driver that can't support it? WEP is always supported. The WEP capability bit means the driver uses the hardware. Many driver writers were too lazy to implement full driver support and just fall back on the host to do crypto. Also command: ifconfig ral0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 authmode open mode 11g mediaopt hostap succeeds though CAPS doesn't have WEP. Isn't this a bug? No, see above. Sam ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?
WEP is always supported. The WEP capability bit means the driver uses the hardware. Many driver writers were too lazy to implement full driver support and just fall back on the host to do crypto. I see. I am sure anybody who doesn't know this will get confused and will have the same question. Isn't it better to have 2 separate flags in CAPS: for example WEP and WEPHW? WEP would mean that WEP is supported and WEPHW would mean that it's supported through hardware. Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?
On Wed, 27 Feb 2008, Sam Leffler wrote: Yuri wrote: I have a Linksys PCI wireless card that is being attached by ral driver: ral0: Ralink Technology RT2561S mem 0xcffe8000-0xcffe irq 17 at device 10.0 on pci0 ral0: MAC/BBP RT2561C, RF RT2527 ral0: Ethernet address: 00:18:f8:2e:40:25 ral0: [ITHREAD] But when I do 'ifconfig ral0 list caps' it returns: ral0=2181e500IBSS,HOSTAP,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,WPA1,WPA2,BGSCAN and WEP isn't there. This looks amazing since WEP is older and very widespread. I am about to do a talk on WEP versus WPA for a course in internet security. I became acquainted with the protocols through a 60 minutes story. http://tinyurl.com/2wucm3 WEP is not fully secure. WPA or WPA2 is the improvement. The above story notes that American businesses are in arears with respect to properly upgrading the wireless routers that they use for financial processing. So how can I tell if this card can't really support WEP or it's the driver that can't support it? WEP is always supported. The WEP capability bit means the driver uses the hardware. Many driver writers were too lazy to implement full driver support and just fall back on the host to do crypto. Also command: ifconfig ral0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 authmode open mode 11g mediaopt hostap succeeds though CAPS doesn't have WEP. Isn't this a bug? No, see above. Sam ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] *--* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *--* ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?
KAYVEN RIESE wrote: I am about to do a talk on WEP versus WPA for a course in internet security. I became acquainted with the protocols through a 60 minutes story. http://tinyurl.com/2wucm3 WEP is not fully secure. WPA or WPA2 is the improvement. The above story notes that American businesses are in arears with respect to properly upgrading the wireless routers that they use for financial processing. Sorry, Your response has nothing to do with the question. Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?
Pietro Cerutti wrote: It wouldn't make sense. Flags are used to specify capabilities of the interface, not things provided by the operating system. This is very confusing to user. User is assumed to have this bit of knowledge that WEP flag actually means only hardware support, not support in general. On another note WEP is actually supported by interface but driver authors didn't bother to use it. So WEP flag doesn't represent actual capabilities of the interface and this is again confusing. When I type 'ifconfig iface ...' I am mostly interested what can I use from that side, not what is supported by hardware. Is there any way to know what is logically supported by network interface as passed to 'ifconfig' vs. what is supported by hardware interface? Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?
On Wed, 27 Feb 2008, Yuri wrote: KAYVEN RIESE wrote: WEP is not fully secure. WPA or WPA2 is the improvement. The above story notes that American businesses are in arears with respect to properly upgrading the wireless routers that they use for financial processing. Sorry, Your response has nothing to do with the question. I tend to beg to differ. Backward compatibility standards imply the answer to your question (that was actually already answered anyway). I considered it relevant to realize the importance of WPA upgrade. Sorry if you already knew that and I wasted your time. Yuri *--* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *--* ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?
Yuri wrote: Pietro Cerutti wrote: It wouldn't make sense. Flags are used to specify capabilities of the interface, not things provided by the operating system. This is very confusing to user. User is assumed to have this bit of knowledge that WEP flag actually means only hardware support, not support in general. On another note WEP is actually supported by interface but driver authors didn't bother to use it. So WEP flag doesn't represent actual capabilities of the interface and this is again confusing. When I type 'ifconfig iface ...' I am mostly interested what can I use from that side, not what is supported by hardware. Is there any way to know what is logically supported by network interface as passed to 'ifconfig' vs. what is supported by hardware interface? If you cannot use a feature you'll get an error when you try to use it. There simply are not enough capability bits around to waste on features that are always true. If I reorg this stuff (and I intend to to split crypto out into a separate features word because we are out of bits) then I can look into expanding the status. To be honest you're the first person that's even noticed you can list capabilities in the 3+ years that's been in place (or at least made public mention). Hardly seems like something that's constantly confused people. Sam ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver?
Sam Leffler wrote: If you cannot use a feature you'll get an error when you try to use it. There simply are not enough capability bits around to waste on features that are always true. If I reorg this stuff (and I intend to to split crypto out into a separate features word because we are out of bits) then I can look into expanding the status. Exactly, I got errors while trying to use WEP with FreeBSD-based wireless access point. And I looked in four eyes at all options and capabilities. And I first thought that WEP support is a problem. Basically AP with WEP encryption doesn't work with this card. Now I wonder if this software-based WEP support can be responsible for this failure. To be honest you're the first person that's even noticed you can list capabilities in the 3+ years that's been in place (or at least made public mention). Hardly seems like something that's constantly confused people. Ok I will correct myself: this is very confusing to people who look and notice. Though there are not too many obviously. But caps are mentioned in the handbook. And it particularly says there: ifconfig /ath0/ list caps skip This output displays the card capabilities skip Various supported ciphers are also mentioned: WEP, TKIP, WPA2, etc., these informations are important to know what security protocols could be set on the Access Point. So from this one can conclude that WEP isn't supported. I guess it's good to mention here that WEP is always supported no matter what WEP flag says. Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
