[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: WEP in Lucent silver card
On Sunday, 3 March 2002 at 12:23:55 -0700, Todd C. Miller wrote:
> In message <20020302210446.74bfcef0.danh@wzrd.com>
> so spake Dan Harnett (danh):
>
>> I wouldn't necessarily say that it interoperates better. The manual
>> page for wicontrol states the "-c" option as "Lucent only".
>
> The wicontrol man page contains many many lies. At some point I
> hope to clear those up. In the mean time, I'll just point out
> that '-p 0' (not documented) makes things work in IBSS mode for
> recent Lucent and Prism2 firmware.
Hmm, I"ve heard this before. I've just tried it, and it doesn't work
for me. This was done on a FreeBSD box, but I don't believe that that
makes any difference, since it's really the cards we're talking about,
and the driver is to all intents the same. It seems that once you
select demo ad hoc mode, it's relatively difficult to turn it off
again. I tried changing from -p 1 to -p 0, and from -c 1 to -c 0, and
it continued working, but after a reboot it didn't.
Starting from a freshly rebooted system, which set -c 0 and -p 0,
here's the transcript:
# ifconfig
ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.109.197.84 netmask 0xffffff00 broadcast 192.109.197.255
inet6 fe80::200:b4ff:fe33:6da2%ed0 prefixlen 64 scopeid 0x1
ether 00:00:b4:33:6d:a2
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
gif1: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
gif2: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
gif3: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
faith0: flags=8000<MULTICAST> mtu 1500
ray0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.109.197.245 netmask 0xffffffe0 broadcast 192.109.197.255
inet6 fe80::200:f1ff:fe10:f99f%ray0 prefixlen 64 scopeid 0xa
ether 00:00:f1:10:f9:9f
vlan: 0 parent interface: <none>
wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.109.197.222 netmask 0xffffffe0 broadcast 192.109.197.223
inet6 fe80::202:2dff:fe28:debf%wi0 prefixlen 64 scopeid 0xb
ether 00:02:2d:28:de:bf
# wicontrol
NIC serial number: [ 01UT15361085 ]
Station name: [ FreeBSD WaveLAN/IEEE node ]
SSID for IBSS creation: [ FreeBSD IBSS ]
Current netname (SSID): [ FreeBSD IBSS ]
Desired netname (SSID): [ FOOOO ]
Current BSSID: [ 44:44:44:44:44:44 ]
Channel list: [ 2047 ]
IBSS channel: [ 3 ]
Current channel: [ 10 ]
Comms quality/signal/noise: [ 0 27 27 ]
Promiscuous mode: [ Off ]
Port type (1=BSS, 3=ad-hoc): [ 0 ]
Note this
MAC address: [ 00:02:2d:28:de:bf ]
TX rate (selection): [ 3 ]
TX rate (actual speed): [ 2 ]
RTS/CTS handshake threshold: [ 2347 ]
Create IBSS: [ Off ]
And this.
Access point density: [ 1 ]
Power Mgmt (1=on, 0=off): [ 0 ]
Max sleep time: [ 100 ]
WEP encryption: [ Off ]
TX encryption key: [ 1 ]
Encryption keys: [ ][ ][ ][ ]
# ping firefly
PING firefly.lemis.com (192.109.197.196): 56 data bytes
^C
--- firefly.lemis.com ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
# wicontrol -c 1
# ping firefly
PING firefly.lemis.com (192.109.197.196): 56 data bytes
ping: sendto: Host is down
^C
--- firefly.lemis.com ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
# wicontrol -p 1
# wicontrol
NIC serial number: [ 01UT15361085 ]
Station name: [ FreeBSD WaveLAN/IEEE node ]
SSID for IBSS creation: [ FreeBSD IBSS ]
Current netname (SSID): [ FOOOO ]
Desired netname (SSID): [ FOOOO ]
Current BSSID: [ 02:02:2d:28:de:bf ]
Note the BSSID. It's the MAC address of this card with bit 1 set in
the first octet. This appears typical.
Channel list: [ 2047 ]
IBSS channel: [ 3 ]
Current channel: [ 3 ]
Comms quality/signal/noise: [ 0 27 27 ]
Promiscuous mode: [ Off ]
Port type (1=BSS, 3=ad-hoc): [ 1 ]
MAC address: [ 00:02:2d:28:de:bf ]
TX rate (selection): [ 3 ]
TX rate (actual speed): [ 2 ]
RTS/CTS handshake threshold: [ 2347 ]
Create IBSS: [ On ]
Access point density: [ 1 ]
Power Mgmt (1=on, 0=off): [ 0 ]
Max sleep time: [ 100 ]
WEP encryption: [ Off ]
TX encryption key: [ 1 ]
Encryption keys: [ ][ ][ ][ ]
# ping firefly
PING firefly.lemis.com (192.109.197.196): 56 data bytes
64 bytes from 192.109.197.196: icmp_seq=0 ttl=255 time=2.924 ms
^C
--- firefly.lemis.com ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.924/2.924/2.924/0.000 ms
It's barely possible that this is different in OpenBSD, but since I've
heard FreeBSD people talking about -p 0 as well, I consider it
unlikely. Questions to anybody who wants to try it:
1. Is my firmware recent enough? How do I find out?
2. Is this repeatable under OpenBSD?
3. Can you get it to work with -p 0? If so, what does the wicontrol
output look like?
Greg
--
Finger grog@lemis.com for PGP public key
See complete headers for address and phone numbers