On Thu, 3 Jul 2008, Edd Barrett wrote: > Hi, > > If you get the wep key (or network name) wrong when configuring iwi network > drivers the card becomes useless until you reboot. This is annoying when at a > friends house and I mistype the key for example. I have tried taking the > interface down and back up, it makes no difference. > > Is there a way of resetting the card altogether? > > thinky% ifconfig iwi0 > iwi0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:12:f0:79:36:41 > groups: wlan > media: IEEE802.11 autoselect > status: no network > ieee80211: nwid "" 100dBm > thinky% sudo ifconfig iwi0 nwid SquishMitten nwkey > 0xedd1edd2edd3edd4edd5edd666 > thinky% sudo dhclient iwi0 > DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 7 > DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 9 > DHCPOFFER from 192.168.1.254 > DHCPREQUEST on iwi0 to 255.255.255.255 port 67 > DHCPACK from 192.168.1.254 > bound to 192.168.1.69 -- renewal in 43200 seconds. > thinky% ifconfig iwi0 > iwi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:12:f0:79:36:41 > groups: wlan egress > media: IEEE802.11 autoselect > status: active > ieee80211: nwid SquishMitten chan 1 bssid 00:11:95:54:90:97 77dB nwkey > <not displayed> 100dBm > inet6 fe80::212:f0ff:fe79:3641%iwi0 prefixlen 64 scopeid 0x1 > inet 192.168.1.69 netmask 0xffffff00 broadcast 192.168.1.255 > thinky% sudo ifconfig iwi0 nwid SquishMitten nwkey > 0xedd1edd2edd3edd4edd5edd667 > thinky% sudo dhclient iwi0 > DHCPREQUEST on iwi0 to 255.255.255.255 port 67 > DHCPREQUEST on iwi0 to 255.255.255.255 port 67 > DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 7 > DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 8 > DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 15 > ^C > thinky% ifconfig iwi0 > iwi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:12:f0:79:36:41 > groups: wlan egress > media: IEEE802.11 autoselect > status: no network > ieee80211: nwid SquishMitten nwkey <not displayed> 100dBm > inet6 fe80::212:f0ff:fe79:3641%iwi0 prefixlen 64 scopeid 0x1 > inet 192.168.1.69 netmask 0xffffff00 broadcast 192.168.1.255 > thinky% sudo ifconfig iwi0 nwid SquishMitten nwkey > 0xedd1edd2edd3edd4edd5edd666 > thinky% sudo dhclient iwi0 > DHCPREQUEST on iwi0 to 255.255.255.255 port 67 > DHCPREQUEST on iwi0 to 255.255.255.255 port 67 > DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 5 > DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 6 > DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 6 > DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 13 > DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 19 > ^C > thinky% ifconfig iwi0 > iwi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:12:f0:79:36:41 > groups: wlan egress > media: IEEE802.11 autoselect > status: no network > ieee80211: nwid SquishMitten nwkey <not displayed> 100dBm > inet6 fe80::212:f0ff:fe79:3641%iwi0 prefixlen 64 scopeid 0x1 > inet 192.168.1.69 netmask 0xffffff00 broadcast 192.168.1.255 > > Thanks
I have similar behavior using bwi(4) driver, although I'm using WPA2. But it's something worst since I can use for some minutes when I lost the connection. After that, I can't even make nfe(4) run. The only "solution" I found is reboot. Since this isn't a solution, when possible, I prefer to use nfe(4) Ethernet connection. Cheers,
