Wifi Can't Connect
in [Debian]
|
Prev: VMWare Player as debian package
Next: Debian squeeze on Samsung N220: almost working very well but no control of brightness
From: Mark on 22 Mar 2010 16:30 I had wifi, now I don't. I just upgraded my kernel (using aptitude) from 2.6.26-686 to 2.6.32-3-686 and followed that with "aptitude full-upgrade", which removed a number of packages (that I wasn't using anyway) because I had previously always used apt-get (and I understand the consequences of this). I also installed kde-minimal (version 4). I know that the wifi was working for at least one session on the new kernel. But after a reboot, it stopped being able to connect. Alas, I do not know what I did in between. I was messing with aptitude without really knowing the consequences of my actions. SYMPTOMS Both when booting up and when trying things like "ifup wlan0" and "dhclient wlan0", I get the following response: > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 > No DHCPOFFERS received. > No working leases in persistent database - sleeping. When I open KWiFiManager, most of the time it sees my SSID and alternates between appearing connected -- i.e. green bars, good signal strength -- but with no Local IP, and an "Unavailable" Access Point; -- it stays like that for maybe 10-15 seconds, and then shows no connection. CONFIGURATION Basics: Dell Inspiron E1505, 2GB RAM. Running Lenny. Using repositories: lenny, testing, lenny-backports, lenny/updates (security), and debian-volatile. I have a Verizon (Westell) wireless modem/router. My MacBook Pro is connected to it wirelessly with no problem. I use WPA authentication. My /etc/wpa_supplicant.conf file reads (actual values not given here): > network={ > ssid="MY_SSID" > psk="MY_PSK" > } My /etc/network/interfaces files reads: > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface -- This section commented-out on > 12/31/09, and got wifi working in the first place. > #allow-hotplug eth0 > #iface eth0 inet static > # address 192.168.1.24 > # netmask 255.255.255.0 > # network 192.168.1.0 > # broadcast 192.168.1.255 > # gateway 192.168.1.1 > # # dns-* options are implemented by the resolvconf package, if installed > # dns-nameservers 192.168.1.1 > > # New DHCP Setup [WORKED UNTIL YESTERDAY] > iface eth0 inet dhcp > allow-hotplug eth0 > > > > iface wlan0 inet dhcp > wpa-driver wext > wpa-key-mgmt WPA-PSK > wpa-proto WPA > wpa-ssid MY_SSID > > auto wlan0 Trying something I found on the web, I edited my /etc/dhcp3/dhclient.conf file by uncommenting the timeout line: > #timeout 60; > # NEXT LINE ADDED AS PER http://forums.debian.net/viewtopic.php?t=21520 > timeout 100; I've installed KNetworkManager, but I don't understand how it works, and adding my wifi network in the WiFi tab seems to do nothing at all. I would appreciate any help anyone can offer! - Mark -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/201003221623.23239.HerrPoetry(a)hailmail.net
From: Florian Kulzer on 22 Mar 2010 17:40 On Mon, Mar 22, 2010 at 16:23:23 -0400, Mark wrote: > I had wifi, now I don't. > > I just upgraded my kernel (using aptitude) from 2.6.26-686 to > 2.6.32-3-686 and followed that with "aptitude full-upgrade", which > removed a number of packages (that I wasn't using anyway) because I > had previously always used apt-get (and I understand the consequences > of this). I also installed kde-minimal (version 4). > > I know that the wifi was working for at least one session on the new > kernel. But after a reboot, it stopped being able to connect. Alas, I > do not know what I did in between. I was messing with aptitude without > really knowing the consequences of my actions. > > SYMPTOMS > > Both when booting up and when trying things like "ifup wlan0" and "dhclient wlan0", I get the following response: > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 [...] > > No DHCPOFFERS received. > > No working leases in persistent database - sleeping. [...] > Basics: Dell Inspiron E1505, 2GB RAM. Running Lenny. Using > repositories: lenny, testing, lenny-backports, lenny/updates > (security), and debian-volatile. > > I have a Verizon (Westell) wireless modem/router. My MacBook Pro is > connected to it wirelessly with no problem. I use WPA authentication. > My /etc/wpa_supplicant.conf file reads (actual values not given here): > > network={ > > ssid="MY_SSID" > > psk="MY_PSK" > > } > > My /etc/network/interfaces files reads: [...] > > iface wlan0 inet dhcp > > wpa-driver wext > > wpa-key-mgmt WPA-PSK > > wpa-proto WPA > > wpa-ssid MY_SSID > > > > auto wlan0 Your configuration looks OK to me. The first thing to check is if your wireless device associates with the access point. Please post the output of: lspci -nn | grep -Ei 'net|wire' /sbin/iwconfig wlan0 -- Regards, | Florian | -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100322212233.GA5053(a)isar.localhost
From: Andrei Popescu on 22 Mar 2010 18:20 On Mon,22.Mar.10, 16:23:23, Mark wrote: > I had wifi, now I don't. Please post the output of: lspci | grep -i wireless (or whatever lspci line is relevant for you wireless interface) Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
From: Mark on 22 Mar 2010 18:50 On Monday 22 March 2010 04:32:08 pm Andrei Popescu wrote: > Please post the output of: > > lspci | grep -i wireless ~# lspci | grep -i wireless 0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) On Monday 22 March 2010 05:22:33 pm Florian Kulzer wrote: > Please post the output of: > > lspci -nn | grep -Ei 'net|wire' > /sbin/iwconfig wlan0 ~# lspci -nn | grep -Ei 'net|wire' 03:00.0 Ethernet controller [0200]: Broadcom Corporation BCM4401-B0 100Base-TX [14e4:170c] (rev 02) 03:01.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] 0b:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] (rev 02) ~# /sbin/iwconfig wlan0 wlan0 IEEE 802.11abg ESSID:"Radio Free Universe" Mode:Managed Frequency:2.437 GHz Access Point: 00:23:97:77:14:0B Bit Rate=54 Mb/s Tx-Power=15 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=70/70 Signal level=-35 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/201003221844.03376.HerrPoetry(a)hailmail.net
From: Jack Schneider on 22 Mar 2010 23:30
On Mon, 22 Mar 2010 16:23:23 -0400 Mark <HerrPoetry(a)hailmail.net> wrote: > I had wifi, now I don't. > > I just upgraded my kernel (using aptitude) from 2.6.26-686 to > 2.6.32-3-686 and followed that with "aptitude full-upgrade", which > removed a number of packages (that I wasn't using anyway) because I > had previously always used apt-get (and I understand the consequences > of this). I also installed kde-minimal (version 4). > > I know that the wifi was working for at least one session on the new > kernel. But after a reboot, it stopped being able to connect. Alas, I > do not know what I did in between. I was messing with aptitude > without really knowing the consequences of my actions. > > SYMPTOMS > > Both when booting up and when trying things like "ifup wlan0" and > "dhclient wlan0", I get the following response: > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6 > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19 > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9 > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9 > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 > > No DHCPOFFERS received. > > No working leases in persistent database - sleeping. > > When I open KWiFiManager, most of the time it sees my SSID and > alternates between appearing connected -- i.e. green bars, good > signal strength -- but with no Local IP, and an "Unavailable" Access > Point; -- it stays like that for maybe 10-15 seconds, and then shows > no connection. > > CONFIGURATION > > Basics: Dell Inspiron E1505, 2GB RAM. Running Lenny. Using > repositories: lenny, testing, lenny-backports, lenny/updates > (security), and debian-volatile. > > I have a Verizon (Westell) wireless modem/router. My MacBook Pro is > connected to it wirelessly with no problem. I use WPA authentication. > My /etc/wpa_supplicant.conf file reads (actual values not given here): > > network={ > > ssid="MY_SSID" > > psk="MY_PSK" > > } > > My /etc/network/interfaces files reads: > > # This file describes the network interfaces available on your > > system # and how to activate them. For more information, see > > interfaces(5). > > > > # The loopback network interface > > auto lo > > iface lo inet loopback > > > > # The primary network interface -- This section commented-out on > > 12/31/09, and got wifi working in the first place. > > #allow-hotplug eth0 > > #iface eth0 inet static > > # address 192.168.1.24 > > # netmask 255.255.255.0 > > # network 192.168.1.0 > > # broadcast 192.168.1.255 > > # gateway 192.168.1.1 > > # # dns-* options are implemented by the resolvconf package, > > if installed # dns-nameservers 192.168.1.1 > > > > # New DHCP Setup [WORKED UNTIL YESTERDAY] > > iface eth0 inet dhcp > > allow-hotplug eth0 > > > > > > > > iface wlan0 inet dhcp > > wpa-driver wext > > wpa-key-mgmt WPA-PSK > > wpa-proto WPA > > wpa-ssid MY_SSID > > > > auto wlan0 > > Trying something I found on the web, I edited > my /etc/dhcp3/dhclient.conf file by uncommenting the timeout line: > > #timeout 60; > > # NEXT LINE ADDED AS PER > > http://forums.debian.net/viewtopic.php?t=21520 timeout 100; > > I've installed KNetworkManager, but I don't understand how it works, > and adding my wifi network in the WiFi tab seems to do nothing at all. > > I would appreciate any help anyone can offer! > > - Mark > > Hi, Mark Have you got wpa-supplicant /installed/loaded ? You need that for wpa access, I believe... FWIW Jack -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100322220305.428c3f95(a)Speeduke.volunteerwireless.net |