On Monday 04 July 2016 17:37:00 Brian wrote: > On Mon 04 Jul 2016 at 15:37:42 +0100, Lisi Reisz wrote: > > On Monday 04 July 2016 15:16:23 Brian wrote: > > > > It isn't. It is just a short quotation to show the ipw 2200 and the > > DRIVERS=="?*", because it bothered me that the drivers bit just had a > > question mark, but apparently my worry about that was misplaced. Whole > > file beneath my signature. > > Full quotes are always preferable. If I were in your position I'd > regenerate the file. You've possibly got at least one device there > which is not on the machine.
No. I left the commented out line in case I needed to revert to it. It regenerated eth1, so I manually edited it to wlan0, but left the other line tehr ein case. > Let the system take care of things. > > Be that as it may, you appear to have all necessary firmware and > drivers. So, how do you fancy a bit of low level stuff? > > Reboot and first check firmware loading from 'journalctl'. root@debian-wheezy:/home/sarah# journalctl -b | grep 2200 Jul 04 18:01:31 debian-wheezy kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq Jul 04 18:01:31 debian-wheezy kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation Jul 04 18:01:31 debian-wheezy kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection Jul 04 18:01:31 debian-wheezy kernel: ipw2200 0000:03:03.0: firmware: direct-loading firmware ipw2200-bss.fw Jul 04 18:01:31 debian-wheezy kernel: ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels) Jul 04 18:01:48 debian-wheezy NetworkManager[1240]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1e.0/0000:03:03.0/ieee80211/phy0/rfkill0) (driver ipw2200) Jul 04 18:01:48 debian-wheezy NetworkManager[1240]: <info> (wlan0): new 802.11 WiFi device (driver: 'ipw2200' ifindex: 3) root@debian-wheezy:/home/sarah# > Then > issue the command 'wpa_cli'. > > 1. wpa-cli > You get a prompt ">". This is interactive mode. A selected > interface should be shown. TAB completion of commands works. > Command history is with the UP and DOWN keys. The following > commands are typed at the prompt. root@debian-wheezy:/home/sarah# wpa-cli bash: wpa-cli: command not found root@debian-wheezy:/home/sarah# aptitude search wpa-supplicant root@debian-wheezy:/home/sarah# aptitude search wpa_supplicant root@debian-wheezy:/home/sarah# aptitude search net-tools i net-tools - NET-3 networking toolkit root@debian-wheezy:/home/sarah# aptitude search wireless-tools i A wireless-tools - Tools for manipulating Linux Wireless Extensions root@debian-wheezy:/home/sarah# plus a good deal of Googling. I am stuck. Of what package is wpa-cli a part? Where will I find it?? Ah!! We have wpa-cli AND wpa_cli. Let's try wpa_cli root@debian-wheezy:/home/sarah# wpa_cli wpa_cli v2.3 Copyright (c) 2004-2014, Jouni Malinen <j...@w1.fi> and contributors This software may be distributed under the terms of the BSD license. See README for more details. Selected interface 'wlan0' Interactive mode <3>CTRL-EVENT-SCAN-RESULTS > add_network 0 <3>CTRL-EVENT-SCAN-RESULTS > set_network 0 ssid NETGEAR08 FAIL > set_network 0 ssid netgear08 FAIL <3>CTRL-EVENT-SCAN-RESULTS > add_network 1 <3>CTRL-EVENT-SCAN-RESULTS artwh > set_network psk xxxxxxx Invalid SET_NETWORK command: needs three arguments (network id, variable name, and value) > I'm stuck. Or out of my depth. Or drowning. Or all three. :-( But there seesm ot be a problem with my SSID Not set by me - perhaps I should change it. :-( Help!!! Lisi > 2. add_network > You'll probably get 0 for the network number. > > 3. set_network 0 ssid "Your_SSID" > The response should be "OK". > > 4. set_network psk "Your_passphrase" > The response should be "OK". > > 5. enable_network 0 > The response should be "OK". Authentication and association > should take place. > > 6. status 0 > Has it?
