[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Wifi Can't Connect



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 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


Reply to: