Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #169609 > unrolled thread
| Started by | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| First post | 2016-07-02 02:20 +0200 |
| Last post | 2016-07-10 13:20 +0200 |
| Articles | 12 on this page of 72 — 8 participants |
Back to article view | Back to linux.debian.user
Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-02 02:20 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-02 03:50 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-02 15:10 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-02 18:00 +0200
Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 16:00 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-04 16:20 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 16:40 +0200
Re: Laptop wireless problem Jörg-Volker Peetz <jvpeetz@web.de> - 2016-07-02 16:40 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-02 18:10 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-02 18:20 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-02 20:30 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 00:20 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-03 11:30 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 12:50 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-03 14:00 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 14:50 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 16:00 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 16:10 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 18:00 +0200
Re: Laptop wireless problem Jörg-Volker Peetz <jvpeetz@web.de> - 2016-07-03 19:20 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-03 16:00 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-03 11:50 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 12:50 +0200
Re: Laptop wireless problem Jörg-Volker Peetz <jvpeetz@web.de> - 2016-07-02 21:20 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 16:00 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-03 21:10 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 22:30 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-03 22:50 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 23:50 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-04 09:50 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 14:10 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-04 15:50 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 16:10 +0200
Re: Laptop wireless problem - very slight tangent David Wright <deblis@lionunicorn.co.uk> - 2016-07-05 17:10 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 17:20 +0200
Re: Laptop wireless problem - very slight tangent David Wright <deblis@lionunicorn.co.uk> - 2016-07-05 17:40 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 18:00 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-05 18:30 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-05 18:30 +0200
Re: Laptop wireless problem - very slight tangent Brian <ad44@cityscape.co.uk> - 2016-07-05 20:50 +0200
Re: Laptop wireless problem - very slight tangent Cindy-Sue Causey <butterflybytes@gmail.com> - 2016-07-04 02:30 +0200
Re: Laptop wireless problem - very slight tangent Dan Purgert <dan@djph.net> - 2016-07-04 13:30 +0200
Re: Laptop wireless problem - very slight tangent Nicolas George <george@nsup.org> - 2016-07-04 14:30 +0200
Re: Laptop wireless problem - very slight tangent Dan Purgert <dan@djph.net> - 2016-07-04 16:20 +0200
Re: Laptop wireless problem - very slight tangent Nicolas George <george@nsup.org> - 2016-07-04 16:30 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-02 22:20 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-04 18:30 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 19:00 +0200
Re: Laptop wireless problem - very slight tangent Brian <ad44@cityscape.co.uk> - 2016-07-04 19:50 +0200
POSSIBLY SOLVED Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 20:20 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 19:40 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 21:00 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-04 22:20 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 23:50 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 00:10 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-04 18:40 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 19:40 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-04 20:10 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 20:40 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-04 21:00 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 21:00 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-05 01:10 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 00:40 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 01:10 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-05 10:30 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 16:00 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 16:10 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 16:20 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem David Wright <deblis@lionunicorn.co.uk> - 2016-07-05 17:20 +0200
Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 00:40 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 01:40 +0200
FIXED - I hope!! Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-10 13:20 +0200
Page 4 of 4 — ← Prev page 1 2 3 [4]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-04 21:00 +0200 |
| Subject | Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRhg6-IL-11@gated-at.bofh.it> |
| In reply to | #169704 |
On Monday 04 July 2016 19:32:47 Lisi Reisz wrote: > Thanks for the help. I either try and make a fool of myself, or learn > nothing. Sorry, again. Punctuation. Try; and make a fool of myself; or don't try, and learn nothing. Lisi
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-07-05 01:10 +0200 |
| Subject | Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRla2-3od-3@gated-at.bofh.it> |
| In reply to | #169696 |
On Mon 04 Jul 2016 at 18:30:47 +0100, Lisi Reisz wrote: > root@debian-wheezy:/home/sarah# wpa_cli That is the correct command. > 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' An interface called 'wlan0' has been found, That is good. There is a live wireless card available, > Interactive mode > > <3>CTRL-EVENT-SCAN-RESULTS > > add_network > 0 This is the number the added network has been allocated. Stick with it. Do not deviate from it. Do not refer at any time to another number. > <3>CTRL-EVENT-SCAN-RESULTS > > set_network 0 ssid NETGEAR08 > FAIL Are you sure "NETGEAR08" is the SSID? Check with scan followed by scan_results at the prompt. The name is case sensitive. If it is correct then set_network 0 ssid "NETGEAR08" should give OK and not FAIL. ***** The SSID must have quotation marks round it. ***** > > set_network 0 ssid netgear08 > FAIL The SSID is case-sensitive, Quotation marks are obligitory. > <3>CTRL-EVENT-SCAN-RESULTS > > add_network > 1 You are configuring network number 0, not network number 1. Do not change horses etc, etc. > <3>CTRL-EVENT-SCAN-RESULTS artwh > > set_network psk xxxxxxx You have no network number in the command. This is what the response tells you. > Invalid SET_NETWORK command: needs three arguments > (network id, variable name, and value) In my opinion there is nothing untoward in the working of your network card. If there was the kernel would not have found it and modules and firmware would not have been loaded. Addendum -------- I notice just now you have succeeded in demonstrating the correctness of my assertion in the last paragraph. But I'll post this anyway.
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-05 00:40 +0200 |
| Subject | Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRkGZ-2Z3-9@gated-at.bofh.it> |
| In reply to | #169679 |
On Monday 04 July 2016 23:36:44 Lisi Reisz wrote: > 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. 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? > > Trying again. > > > Reboot and first check firmware loading from 'journalctl'. > > root@debian-wheezy:/home/sarah# journalctl -b | grep 2200 > Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Intel(R) PRO/Wireless > 2200/2915 Network Driver, 1.2.2kmprq > Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Copyright(c) 2003-2006 Intel > Corporation > Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Detected Intel PRO/Wireless > 2200BG Network Connection > Jul 04 23:10:49 debian-wheezy kernel: ipw2200 0000:03:03.0: firmware: > direct-loading firmware ipw2200-bss.fw > Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Detected geography ZZD (13 > 802.11bg channels, 0 802.11a channels) > Jul 04 23:11:06 debian-wheezy NetworkManager[1239]: <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 23:11:07 debian-wheezy NetworkManager[1239]: <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. > > > > 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? > > I don't *believe* it! > > > 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 > > > set_network 0 ssid "NETGEAR08" > > OK > <3>CTRL-EVENT-SCAN-RESULTS > > > set_network psk "yyyyyyyyyyyyy" > > Invalid SET_NETWORK command: needs three arguments > (network id, variable name, and value) > <3>CTRL-EVENT-SCAN-RESULTS > <3>CTRL-EVENT-SCAN-RESULTS > <3>CTRL-EVENT-SCAN-RESULTS > <3>CTRL-EVENT-SCAN-RESULTS > > > set_network 0 psk "yyyyyyyyyyyyy" > > OK > <3>CTRL-EVENT-SCAN-RESULTS > > > enable network 0 > > OK > <3>CTRL-EVENT-SCAN-RESULTS > <3>Trying to associate with xx:xx:xx:xx:xx (SSID='NETGEAR08' freq=2437 MHz) > <3>Association request to the driver failed > <3>Associated with xx:xx:xx:xx:xx > <3>WPA: Key negotiation completed with xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP] > <3>CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx completed [id=0 > id_str=] > <3>CTRL-EVENT-SCAN-RESULTS > > [1]+ Stopped wpa_cli > root@debian-wheezy:/home/sarah# ping 192.168.0.1 > PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. > 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.475 ms > 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.491 ms > 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.483 ms > 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.429 ms > ^C > --- 192.168.0.1 ping statistics --- > 4 packets transmitted, 4 received, 0% packet loss, time 2999ms > rtt min/avg/max/mdev = 0.429/0.469/0.491/0.032 ms > root@debian-wheezy:/home/sarah# ping www.google.co.uk > PING www.google.co.uk (216.58.213.163) 56(84) bytes of data. > 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=1 ttl=57 > time=12.5 ms > 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=2 ttl=57 > time=12.4 ms > 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=3 ttl=57 > time=13.2 ms > 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=4 ttl=57 > time=11.6 ms > 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=5 ttl=57 > time=12.1 ms > ^C > --- www.google.co.uk ping statistics --- > 5 packets transmitted, 5 received, 0% packet loss, time 4007ms > rtt min/avg/max/mdev = 11.610/12.405/13.225/0.526 ms > root@debian-wheezy:/home/sarah# > > > Brilliant! \o/ \o/ But what next?? > > I stand rebuked for my lack of faith. :-( > > I hope that it is not permanent as i am about to change the passphrase - > but I suppose that I could always call it network 1 in future. > > I really can't start dancing jigs around the house at this time of night > at my age!!!! > > Lisi I forgot in all teh joy of it owtrking: 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 > status 0 bssid=00:8e:f2:8f:58:58 freq=0 ssid=NETGEAR08 id=0 mode=station pairwise_cipher=CCMP group_cipher=CCMP key_mgmt=WPA2-PSK wpa_state=COMPLETED address=xx:xx:xx:xx:xx uuid=<string-of-numbers>
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-05 01:10 +0200 |
| Subject | Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRla2-3od-31@gated-at.bofh.it> |
| In reply to | #169731 |
On Monday 04 July 2016 23:39:26 Lisi Reisz wrote: > On Monday 04 July 2016 23:36:44 Lisi Reisz wrote: > > 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. 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? > > > > Trying again. > > > > > Reboot and first check firmware loading from 'journalctl'. > > > > root@debian-wheezy:/home/sarah# journalctl -b | grep 2200 > > Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Intel(R) PRO/Wireless > > 2200/2915 Network Driver, 1.2.2kmprq > > Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Copyright(c) 2003-2006 > > Intel Corporation > > Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Detected Intel > > PRO/Wireless 2200BG Network Connection > > Jul 04 23:10:49 debian-wheezy kernel: ipw2200 0000:03:03.0: firmware: > > direct-loading firmware ipw2200-bss.fw > > Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Detected geography ZZD (13 > > 802.11bg channels, 0 802.11a channels) > > Jul 04 23:11:06 debian-wheezy NetworkManager[1239]: <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 23:11:07 debian-wheezy NetworkManager[1239]: <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. > > > > > > 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? > > > > I don't *believe* it! > > > > > > 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 > > > > > set_network 0 ssid "NETGEAR08" > > > > OK > > <3>CTRL-EVENT-SCAN-RESULTS > > > > > set_network psk "yyyyyyyyyyyyy" > > > > Invalid SET_NETWORK command: needs three arguments > > (network id, variable name, and value) > > <3>CTRL-EVENT-SCAN-RESULTS > > <3>CTRL-EVENT-SCAN-RESULTS > > <3>CTRL-EVENT-SCAN-RESULTS > > <3>CTRL-EVENT-SCAN-RESULTS > > > > > set_network 0 psk "yyyyyyyyyyyyy" > > > > OK > > <3>CTRL-EVENT-SCAN-RESULTS > > > > > enable network 0 > > > > OK > > <3>CTRL-EVENT-SCAN-RESULTS > > <3>Trying to associate with xx:xx:xx:xx:xx (SSID='NETGEAR08' freq=2437 > > MHz) <3>Association request to the driver failed > > <3>Associated with xx:xx:xx:xx:xx > > <3>WPA: Key negotiation completed with xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP] > > <3>CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx completed [id=0 > > id_str=] > > <3>CTRL-EVENT-SCAN-RESULTS > > > > [1]+ Stopped wpa_cli > > root@debian-wheezy:/home/sarah# ping 192.168.0.1 > > PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. > > 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.475 ms > > 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.491 ms > > 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.483 ms > > 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.429 ms > > ^C > > --- 192.168.0.1 ping statistics --- > > 4 packets transmitted, 4 received, 0% packet loss, time 2999ms > > rtt min/avg/max/mdev = 0.429/0.469/0.491/0.032 ms > > root@debian-wheezy:/home/sarah# ping www.google.co.uk > > PING www.google.co.uk (216.58.213.163) 56(84) bytes of data. > > 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=1 > > ttl=57 time=12.5 ms > > 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=2 > > ttl=57 time=12.4 ms > > 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=3 > > ttl=57 time=13.2 ms > > 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=4 > > ttl=57 time=11.6 ms > > 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=5 > > ttl=57 time=12.1 ms > > ^C > > --- www.google.co.uk ping statistics --- > > 5 packets transmitted, 5 received, 0% packet loss, time 4007ms > > rtt min/avg/max/mdev = 11.610/12.405/13.225/0.526 ms > > root@debian-wheezy:/home/sarah# > > > > > > Brilliant! \o/ \o/ But what next?? > > > > I stand rebuked for my lack of faith. :-( > > > > I hope that it is not permanent as i am about to change the passphrase - > > but I suppose that I could always call it network 1 in future. > > > > I really can't start dancing jigs around the house at this time of night > > at my age!!!! > > > > Lisi > > I forgot in all teh joy of it owtrking: > > 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 > > > status 0 > > bssid=xx > freq=0 > ssid=NETGEAR08 > id=0 > mode=station > pairwise_cipher=CCMP > group_cipher=CCMP > key_mgmt=WPA2-PSK > wpa_state=COMPLETED > address=xx:xx:xx:xx:xx > uuid=<string-of-numbers> I was doing this over ssh, which reduces the validity of most of the tests, because the ethernet has to be up for me to connect. Grr. I was born with some brains, but I don't know where they have gone to. :-( Lisi Now to do them on the machine.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-07-05 10:30 +0200 |
| Subject | Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRtTX-jt-1@gated-at.bofh.it> |
| In reply to | #169731 |
On Mon 04 Jul 2016 at 23:39:26 +0100, Lisi Reisz wrote: > > status 0 > bssid=00:8e:f2:8f:58:58 > freq=0 > ssid=NETGEAR08 > id=0 > mode=station > pairwise_cipher=CCMP > group_cipher=CCMP > key_mgmt=WPA2-PSK > wpa_state=COMPLETED > address=xx:xx:xx:xx:xx > uuid=<string-of-numbers> You have a fully functional wireless card. It has authenticated and associated with the access point. Association can be confirmed with iwconfig. If you have physical access (and only if you have) to the machine bring down the wired connection with ifdown -v eth0 Check with route -n Now obtain an IP address for the wlan0 interface with dhclient -v wlan0 The wireless connection lasts as long as the machine is not powered off or rebooted.
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-05 16:00 +0200 |
| Subject | Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRz3k-3vi-13@gated-at.bofh.it> |
| In reply to | #169751 |
On Tuesday 05 July 2016 09:26:00 Brian wrote: > On Mon 04 Jul 2016 at 23:39:26 +0100, Lisi Reisz wrote: > > > status 0 > > > > bssid=00:8e:f2:8f:58:58 > > freq=0 > > ssid=NETGEAR08 > > id=0 > > mode=station > > pairwise_cipher=CCMP > > group_cipher=CCMP > > key_mgmt=WPA2-PSK > > wpa_state=COMPLETED > > address=xx:xx:xx:xx:xx > > uuid=<string-of-numbers> > > You have a fully functional wireless card. It has authenticated and > associated with the access point. Association can be confirmed with > iwconfig. > > If you have physical access (and only if you have) to the machine > bring down the wired connection with > > ifdown -v eth0 > > Check with > > route -n > > Now obtain an IP address for the wlan0 interface with > > dhclient -v wlan0 > > The wireless connection lasts as long as the machine is not powered > off or rebooted. But the dns stops working if you plug the ethernet cable in. Just plug it in. Don't do anything. But it must be recognised to have nay effect. It is now unplugged again, but dns has still stopped working. :-( Still, this is great!!! Thank you, Brian. I have filed the method for bringing up wireless manually separately in case my google foo deserts me!! So now,I need to solve two questions: what has happened to dns and why can't network managers connect the wifi card??? Am googling dns almost as we speak. Lisi
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-05 16:10 +0200 |
| Subject | Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRzd0-3Ok-23@gated-at.bofh.it> |
| In reply to | #169755 |
On Tuesday 05 July 2016 14:54:34 Lisi Reisz wrote: > On Tuesday 05 July 2016 09:26:00 Brian wrote: > > On Mon 04 Jul 2016 at 23:39:26 +0100, Lisi Reisz wrote: > > > > status 0 > > > > > > bssid=00:8e:f2:8f:58:58 > > > freq=0 > > > ssid=NETGEAR08 > > > id=0 > > > mode=station > > > pairwise_cipher=CCMP > > > group_cipher=CCMP > > > key_mgmt=WPA2-PSK > > > wpa_state=COMPLETED > > > address=xx:xx:xx:xx:xx > > > uuid=<string-of-numbers> > > > > You have a fully functional wireless card. It has authenticated and > > associated with the access point. Association can be confirmed with > > iwconfig. > > > > If you have physical access (and only if you have) to the machine > > bring down the wired connection with > > > > ifdown -v eth0 > > > > Check with > > > > route -n > > > > Now obtain an IP address for the wlan0 interface with > > > > dhclient -v wlan0 > > > > The wireless connection lasts as long as the machine is not powered > > off or rebooted. > > But the dns stops working if you plug the ethernet cable in. Just plug it > in. Don't do anything. But it must be recognised to have nay effect. It > is now unplugged again, but dns has still stopped working. :-( > > Still, this is great!!! Thank you, Brian. I have filed the method for > bringing up wireless manually separately in case my google foo deserts me!! > > So now,I need to solve two questions: what has happened to dns and why > can't network managers connect the wifi card??? Am googling dns almost as > we speak. Just started and found already thsi interesting (in teh circumstances) nugget of a symptom: "Only IPv6 resolution working when IPv4 resolution is not working, and visa versa" Now you have proved yourself and deloptes right, I'm going to try installing NM and giving it another chance, as suggested. I can always uninstall it again!! https://www.slightfuture.com/how-to/debian-dns-resolv Lisi
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-05 16:20 +0200 |
| Subject | Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRzmK-3UP-11@gated-at.bofh.it> |
| In reply to | #169756 |
On Tuesday 05 July 2016 15:05:37 Lisi Reisz wrote: > On Tuesday 05 July 2016 14:54:34 Lisi Reisz wrote: > > On Tuesday 05 July 2016 09:26:00 Brian wrote: > > > On Mon 04 Jul 2016 at 23:39:26 +0100, Lisi Reisz wrote: > > > > > status 0 > > > > > > > > bssid=00:8e:f2:8f:58:58 > > > > freq=0 > > > > ssid=NETGEAR08 > > > > id=0 > > > > mode=station > > > > pairwise_cipher=CCMP > > > > group_cipher=CCMP > > > > key_mgmt=WPA2-PSK > > > > wpa_state=COMPLETED > > > > address=xx:xx:xx:xx:xx > > > > uuid=<string-of-numbers> > > > > > > You have a fully functional wireless card. It has authenticated and > > > associated with the access point. Association can be confirmed with > > > iwconfig. > > > > > > If you have physical access (and only if you have) to the machine > > > bring down the wired connection with > > > > > > ifdown -v eth0 > > > > > > Check with > > > > > > route -n > > > > > > Now obtain an IP address for the wlan0 interface with > > > > > > dhclient -v wlan0 > > > > > > The wireless connection lasts as long as the machine is not powered > > > off or rebooted. > > > > But the dns stops working if you plug the ethernet cable in. Just plug > > it in. Don't do anything. But it must be recognised to have nay effect. > > It is now unplugged again, but dns has still stopped working. :-( > > > > Still, this is great!!! Thank you, Brian. I have filed the method for > > bringing up wireless manually separately in case my google foo deserts > > me!! > > > > So now,I need to solve two questions: what has happened to dns and why > > can't network managers connect the wifi card??? Am googling dns almost > > as we speak. > > Just started and found already thsi interesting (in teh circumstances) > nugget of a symptom: > > "Only IPv6 resolution working when IPv4 resolution is not working, and visa > versa" > > Now you have proved yourself and deloptes right, I'm going to try > installing NM and giving it another chance, as suggested. I can always > uninstall it again!! > https://www.slightfuture.com/how-to/debian-dns-resolv > > Lisi Footnote: Just tried to ssh in from my box and got this: lisi@Tux-II:~$ ssh sarah@debian-wheezy.local ssh: Could not resolve hostname debian-wheezy.local: Name or service not known lisi@Tux-II:~$ It's connected, but not. But the hardware seems fine. Lisi
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2016-07-05 17:20 +0200 |
| Subject | Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRAiK-4z1-15@gated-at.bofh.it> |
| In reply to | #169757 |
On Tue 05 Jul 2016 at 15:13:28 (+0100), Lisi Reisz wrote: > Footnote: > Just tried to ssh in from my box and got this: > > lisi@Tux-II:~$ ssh sarah@debian-wheezy.local > ssh: Could not resolve hostname debian-wheezy.local: Name or service not known > lisi@Tux-II:~$ > > It's connected, but not. But the hardware seems fine. Try with the IP#. Using .local will fail if avahi is not running properly at the other end. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-05 00:40 +0200 |
| Subject | Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRkGZ-2Z3-11@gated-at.bofh.it> |
| In reply to | #169679 |
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. 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? Trying again. > Reboot and first check firmware loading from 'journalctl'. root@debian-wheezy:/home/sarah# journalctl -b | grep 2200 Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection Jul 04 23:10:49 debian-wheezy kernel: ipw2200 0000:03:03.0: firmware: direct-loading firmware ipw2200-bss.fw Jul 04 23:10:49 debian-wheezy kernel: ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels) Jul 04 23:11:06 debian-wheezy NetworkManager[1239]: <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 23:11:07 debian-wheezy NetworkManager[1239]: <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. > > 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? I don't *believe* it! 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 > set_network 0 ssid "NETGEAR08" OK <3>CTRL-EVENT-SCAN-RESULTS > set_network psk "yyyyyyyyyyyyy" Invalid SET_NETWORK command: needs three arguments (network id, variable name, and value) <3>CTRL-EVENT-SCAN-RESULTS <3>CTRL-EVENT-SCAN-RESULTS <3>CTRL-EVENT-SCAN-RESULTS <3>CTRL-EVENT-SCAN-RESULTS > set_network 0 psk "yyyyyyyyyyyyy" OK <3>CTRL-EVENT-SCAN-RESULTS > enable network 0 OK <3>CTRL-EVENT-SCAN-RESULTS <3>Trying to associate with xx:xx:xx:xx:xx (SSID='NETGEAR08' freq=2437 MHz) <3>Association request to the driver failed <3>Associated with xx:xx:xx:xx:xx <3>WPA: Key negotiation completed with xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP] <3>CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx completed [id=0 id_str=] <3>CTRL-EVENT-SCAN-RESULTS > [1]+ Stopped wpa_cli root@debian-wheezy:/home/sarah# ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.475 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.491 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.483 ms 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.429 ms ^C --- 192.168.0.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 2999ms rtt min/avg/max/mdev = 0.429/0.469/0.491/0.032 ms root@debian-wheezy:/home/sarah# ping www.google.co.uk PING www.google.co.uk (216.58.213.163) 56(84) bytes of data. 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=1 ttl=57 time=12.5 ms 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=2 ttl=57 time=12.4 ms 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=3 ttl=57 time=13.2 ms 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=4 ttl=57 time=11.6 ms 64 bytes from lhr26s02-in-f3.1e100.net (216.58.213.163): icmp_seq=5 ttl=57 time=12.1 ms ^C --- www.google.co.uk ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4007ms rtt min/avg/max/mdev = 11.610/12.405/13.225/0.526 ms root@debian-wheezy:/home/sarah# Brilliant! \o/ \o/ But what next?? I stand rebuked for my lack of faith. :-( I hope that it is not permanent as i am about to change the passphrase - but I suppose that I could always call it network 1 in future. I really can't start dancing jigs around the house at this time of night at my age!!!! Lisi
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-05 01:40 +0200 |
| Subject | Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRlD4-3xx-21@gated-at.bofh.it> |
| In reply to | #169679 |
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. 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'. 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. > > 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? So I did it actually on the machine, and yes the card is partly alive - we have sadly known that all along. I can paste the file if anyone is interested, but it must have become boring. It was not an actual connection: ping did not work, although I had a network 0. Ping was obviously working previously over the ethernet that was connected so that I could ssh. Doh! I'm going to try that new card when it comes. I may, of course, be wasting £6, but I also may have a little hair left still, and it may not yet have gone grey. :-( Lisi
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-10 13:20 +0200 |
| Subject | FIXED - I hope!! Laptop wireless problem |
| Message-ID | <rTkWe-8it-3@gated-at.bofh.it> |
| In reply to | #169609 |
On Saturday 02 July 2016 01:15:27 Lisi Reisz wrote: > The built in wireless on the Dell Inspiron 9300 suddenly stopped working. > > Having poked around a bit with wicd and network-manager (not > simultaneously), I am checking whether the problem is sudden hardware > failure. I plugged in a USB network card. About half way through the saga I unplugged the external network card because it was muddying the waters. I cannot say which bit of the saga worked. Probably all of it, and I can only advise anyone with a similar intractable problem to follow the thread. I could not see how it could be software, but .... Deloptes and Brian both thought that it was software, so that had to count with me. They were, of course, right. They were likely to be right. Experience coupled with instinct counts. I have glossed over mentally the fact that the Debian network-install CD didn't succeed in connecting. I have, for now anyway, accepted that I don't know why that was: I have no experience of doing net-installs over wireless. I have always used a wired connection for installation. Ubuntu, as I feared when it was suggested, was a complete dead loss. Ubuntu-MATE after 4 HOURS had still not succeeded in booting, though it was still ploughing on. The last few things I did were: Change the SSID and password of my wireless router/connection point. Use Brian's method for manual connection, and go back to NM, which could suddenly consistently connect (though it still couldn't, before that particular manual connection). Give up trying to get NM to set DNS servers. Setting them manually worked, and that would probably have been where I left it if it had been for me. But I needed a consistent fully working automatic wireless connection with functioning DNS. So, for, I think the third time on the saga, I fully purged my network manager (at this point NM) and installed the other one (in this case wicd – which had been uninstalled in the first place because it wasn't working). I now have what appears to be a fully functional connection and shall be restoring the laptop to its owner. Thank you all for all your help, especially deloptes and Brian. Lisi
[toc] | [prev] | [standalone]
Page 4 of 4 — ← Prev page 1 2 3 [4]
Back to top | Article view | linux.debian.user
csiph-web