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 23 Mar 2010 00:40 On 3/22/10 11:03 PM, Jack Schneider wrote: > Hi, Mark > Have you got wpa-supplicant /installed/loaded ? > You need that for wpa access, I believe... > > FWIW > Jack > Good question, Jack. I had not remembered that there was actually a wpasupplicant package. I did have it installed. I just upgraded it, rebooted. No change: still no wifi. I think in my first post about this I gave a slightly mixed up account of what happens when I start KWiFiManager. It alternates every few seconds between "Ultimate Signal Strength" (full bars) and "Out of Range" (no bars). When it has full bars, The "Status of Active Connection" box says "Connected to network: [MY_SSID]". When it has no bars, it says "Searching for network: any". It persistently shows "Local IP: unavailable." If I click on the "Scan for Networks..." button, it sees my SSID (and my neighbor's). But the odd thing is that, in the "Status of Active Connection" box, the "Access point" address shows a mac address that is the same as my broadband router's address, except for the last digit: the last digit of my router's mac address is 5, but KWiFiManager says it's connecting to an Access point address that ends in B. When I run KNetworkManager, And click on the "Scan" button next to the SSID textbox, it sees no SSIDs at all -- neither in the map nor the details view. This is killing me. The computer's networking is handshaking my router but not getting an IP. Can anyone help me figure this out? Below is the rest of my original post, for reference. - - - - - - - - - - - - - - - - - - - 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 PERhttp://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
From: Freeman on 23 Mar 2010 00:50 On Tue, Mar 23, 2010 at 12:30:42AM -0400, Mark wrote: .. . . > >> } > 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 PERhttp://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! Not much, but have you always had wpa in your network/interfaces? My non-KDE network managers have always used wpa as a backend. My network/interfaces just has the two lines. -- Kind Regards, Freeman http://bugs.debian.org/release-critical/ -- 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/20100323044851.GA4539(a)Europa.office
From: Alexander Samad on 23 Mar 2010 02:30 On Tue, Mar 23, 2010 at 9:44 AM, Mark <HerrPoetry(a)hailmail.net> wrote: > On Monday 22 March 2010 04:32:08 pm Andrei Popescu wrote: >> Please post the output of: [snip] > ~# /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 this tells me you have connected, which says to me it might not be a wireless probem, can you assign yourself an ip and ping the gateway ? I don't see any invalid packets - even after the dhcp request have gone out :) [snip] -- 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/836a6dcf1003222325q3260effasdccb0ca17d0c1385(a)mail.gmail.com
From: Jack Schneider on 23 Mar 2010 09:10 On Tue, 23 Mar 2010 00:30:42 -0400 Mark <HerrPoetry(a)HailMail.net> wrote: > On 3/22/10 11:03 PM, Jack Schneider wrote: > > Hi, Mark > > Have you got wpa-supplicant /installed/loaded ? > > You need that for wpa access, I believe... > > > > FWIW > > Jack > > > > Good question, Jack. I had not remembered that there was actually a > wpasupplicant package. I did have it installed. I just upgraded it, > rebooted. No change: still no wifi. > > I think in my first post about this I gave a slightly mixed up > account of what happens when I start KWiFiManager. It alternates > every few seconds between "Ultimate Signal Strength" (full bars) and > "Out of Range" (no bars). When it has full bars, The "Status of > Active Connection" box says "Connected to network: [MY_SSID]". When > it has no bars, it says "Searching for network: any". It persistently > shows "Local IP: unavailable." If I click on the "Scan for > Networks..." button, it sees my SSID (and my neighbor's). > But the odd thing is that, in the "Status of Active Connection" > box, the "Access point" address shows a mac address that is the same > as my broadband router's address, except for the last digit: the last > digit of my router's mac address is 5, but KWiFiManager says it's > connecting to an Access point address that ends in B. > > When I run KNetworkManager, And click on the "Scan" button next to > the SSID textbox, it sees no SSIDs at all -- neither in the map nor > the details view. > > This is killing me. The computer's networking is handshaking my > router but not getting an IP. Can anyone help me figure this out? > Below is the rest of my original post, for reference. > > - - - - - - - - - - - - - - - - - - - > > 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 > > > PERhttp://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 I have had a similar problem on a old laptop. My difficulty was that I lost the routing setup. sudo route command gave no gateway address. For no good technical reason I restarted dbus (/etc/init.d/dbus restart) and issued a (sudo route add default gw (ip of gw) wlan0 command and it connected. I don't know or undestand why it worked...IANAG 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/20100323074326.445d7ef3(a)Speeduke.volunteerwireless.net
From: godo on 23 Mar 2010 13:20
> 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 > > I think that KNetworkManager (or some other package) have some problem. For example my router have WPA2 encryption. With IBM Squeeze laptop (Intel WiFi) I can connect only if router broadcast SSID. So I was first turn on broadcast SSID, scan, enter password and then he connect, turn off broadcast SSID. On same router Lenovo Sid with Broadcom WiFi and also KNetworkManager can't connect. My friend HP laptop Squeeze and Broadcom WiFi can't connect. Both Broadcom WiFi laptops can't remember password and constantly asking again and again. Does anybody know which package would be responsible for that and how to track bug? -- Bye, Goran Dobosevic Hrvatski: www.dobosevic.com English: www.dobosevic.com/en/ Registered Linux User #503414 -- 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/4BA8F70F.6060907(a)dobosevic.com |