Cannot connect to secured wireless

four20 · 04-18-2009, 05:26 PM

Here's my situation. Using Wicd I can connect to a wired network, I can connect to a unsecured wireless network, but I cannot connect to a secure wireless network and my pass phrase is correct.

Wicd resets IP, verifies authentication. and tries to obtain a IP address and times out after 60 sec..

My router is a NetGear WPN311, Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01), and running Slackware-12.2.

I have googled, and searched these forums with no luck in finding a solution.

lspci

Code:

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
03:01.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
03:01.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
0b:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)

iwconfig

Code:

lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"NETGEAR1"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated   
          Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ifconfig

Code:

eth0      Link encap:Ethernet  HWaddr 00:15:c5:ae:9f:7d  
          inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::215:c5ff:feae:9f7d/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2822 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2926 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1847003 (1.7 MiB)  TX bytes:529003 (516.6 KiB)
          Interrupt:17 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:18:f3:3b:d5:0c  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1753 (1.7 KiB)  TX bytes:3451 (3.3 KiB)

wmaster0  Link encap:UNSPEC  HWaddr 00-18-F3-3B-D5-0C-65-74-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wicd log

Code:

2009/04/18 15:54:53 :: ---------------------------
2009/04/18 15:54:53 :: wicd initializing...
2009/04/18 15:54:53 :: ---------------------------
2009/04/18 15:54:53 :: Automatically detected wireless interface wlan0
2009/04/18 15:54:53 :: found wireless_interface in configuration wlan0
2009/04/18 15:54:53 :: setting wireless interface wlan0
2009/04/18 15:54:53 :: automatically detected wired interface eth0
2009/04/18 15:54:53 :: found wired_interface in configuration eth0
2009/04/18 15:54:53 :: setting wired interface eth0
2009/04/18 15:54:53 :: found wpa_driver in configuration wext
2009/04/18 15:54:53 :: setting wpa driver wext
2009/04/18 15:54:53 :: found always_show_wired_interface in configuration False
2009/04/18 15:54:53 :: found use_global_dns in configuration False
2009/04/18 15:54:53 :: setting use global dns to False
2009/04/18 15:54:53 :: setting use global dns to boolean False
2009/04/18 15:54:53 :: found global_dns_1 in configuration None
2009/04/18 15:54:53 :: found global_dns_2 in configuration None
2009/04/18 15:54:53 :: found global_dns_3 in configuration None
2009/04/18 15:54:53 :: setting global dns
2009/04/18 15:54:53 :: global dns servers are None None None
2009/04/18 15:54:53 :: found auto_reconnect in configuration True
2009/04/18 15:54:53 :: setting automatically reconnect when connection drops
2009/04/18 15:54:53 :: found debug_mode in configuration 0
2009/04/18 15:54:53 :: found wired_connect_mode in configuration 1
2009/04/18 15:54:53 :: found signal_display_type in configuration 0
2009/04/18 15:54:53 :: found dhcp_client in configuration 2
2009/04/18 15:54:53 :: Setting dhcp client to 2
2009/04/18 15:54:53 :: found link_detect_tool in configuration 0
2009/04/18 15:54:53 :: found flush_tool in configuration 0
2009/04/18 15:54:53 :: Wireless configuration file found...
2009/04/18 15:54:53 :: Wired configuration file found...
2009/04/18 15:54:53 :: chmoding configuration files 0600...
2009/04/18 15:54:53 :: chowning configuration files root:root...
2009/04/18 15:54:53 :: Using wired interface...eth0
2009/04/18 15:54:53 :: Using wireless interface...wlan0
2009/04/18 15:54:53 :: autoconnecting... wlan0
2009/04/18 15:55:02 :: No wired connection present, attempting to autoconnect to wireless network
2009/04/18 15:55:02 :: Unable to autoconnect, you'll have to manually connect
2009/04/18 15:55:08 :: Attempting to autoconnect with wired interface...Putting interface down
2009/04/18 15:55:08 :: 
2009/04/18 15:55:08 :: Releasing DHCP leases...
2009/04/18 15:55:08 :: Setting false IP...
2009/04/18 15:55:08 :: Stopping wpa_supplicant and any DHCP clients
2009/04/18 15:55:08 :: Flushing the routing table...
2009/04/18 15:55:08 :: Putting interface up...
2009/04/18 15:55:08 :: Running DHCP
2009/04/18 15:55:13 :: Broadcasting DHCP_DISCOVER
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: broadcastAddr option is missing in DHCP server response. Assuming 192.168.1.255
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpIPaddrLeaseTime=86400 in DHCP server response.
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: DHCP_OFFER received from  (192.168.1.1)
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: Broadcasting DHCP_REQUEST for 192.168.1.4
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpIPaddrLeaseTime=86400 in DHCP server response.
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: DHCP_ACK received from  (192.168.1.1)
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: Broadcasting ARPOP_REQUEST for 192.168.1.4
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: Broadcasting DHCP_DISCOVER
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: broadcastAddr option is missing in DHCP server response. Assuming 192.168.1.255
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpIPaddrLeaseTime=86400 in DHCP server response.
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: DHCP_OFFER received from  (192.168.1.1)
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: Broadcasting DHCP_REQUEST for 192.168.1.4
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpIPaddrLeaseTime=86400 in DHCP server response.
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: DHCP_ACK received from  (192.168.1.1)
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: Broadcasting ARPOP_REQUEST for 192.168.1.4
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: 
2009/04/18 15:55:13 :: DHCP connection successful
2009/04/18 15:55:13 :: Connecting thread exiting.
2009/04/18 15:56:28 :: Connecting to wireless network NETGEAR1
2009/04/18 15:56:28 :: Putting interface down
2009/04/18 15:56:28 :: Releasing DHCP leases...
2009/04/18 15:56:28 :: Setting false IP...
2009/04/18 15:56:29 :: Stopping wpa_supplicant and any DHCP clients
2009/04/18 15:56:29 :: Flushing the routing table...
2009/04/18 15:56:29 :: Generating psk...
2009/04/18 15:56:29 :: Attempting to authenticate...
2009/04/18 15:56:29 :: Putting interface up...
2009/04/18 15:56:30 :: Running DHCP
2009/04/18 15:57:30 :: Broadcasting DHCP_DISCOVER
2009/04/18 15:57:30 :: 
2009/04/18 15:57:30 :: timed out waiting for a valid DHCP server response
2009/04/18 15:57:30 :: 
2009/04/18 15:57:30 :: 
2009/04/18 15:57:30 :: DHCP connection successful
2009/04/18 15:57:30 :: Connecting thread exiting.
2009/04/18 15:57:32 :: Attempting to autoconnect with wired interface...Putting interface down
2009/04/18 15:57:32 :: 
2009/04/18 15:57:32 :: Releasing DHCP leases...
2009/04/18 15:57:32 :: Setting false IP...
2009/04/18 15:57:32 :: Stopping wpa_supplicant and any DHCP clients
2009/04/18 15:57:32 :: Flushing the routing table...
2009/04/18 15:57:32 :: Putting interface up...
2009/04/18 15:57:32 :: Running DHCP
2009/04/18 15:57:37 :: Broadcasting DHCP_DISCOVER
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: broadcastAddr option is missing in DHCP server response. Assuming 192.168.1.255
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpIPaddrLeaseTime=86400 in DHCP server response.
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: DHCP_OFFER received from  (192.168.1.1)
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: Broadcasting DHCP_REQUEST for 192.168.1.4
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpIPaddrLeaseTime=86400 in DHCP server response.
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: DHCP_ACK received from  (192.168.1.1)
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: Broadcasting ARPOP_REQUEST for 192.168.1.4
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: Broadcasting DHCP_DISCOVER
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: broadcastAddr option is missing in DHCP server response. Assuming 192.168.1.255
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpIPaddrLeaseTime=86400 in DHCP server response.
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: DHCP_OFFER received from  (192.168.1.1)
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: Broadcasting DHCP_REQUEST for 192.168.1.4
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpIPaddrLeaseTime=86400 in DHCP server response.
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: DHCP_ACK received from  (192.168.1.1)
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: Broadcasting ARPOP_REQUEST for 192.168.1.4
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: 
2009/04/18 15:57:37 :: DHCP connection successful
2009/04/18 15:57:37 :: Connecting thread exiting.

It worked before. Had to do a fresh install (don't ask, stupidity) and now no secured wireless connection. Totally stumped. any suggestions would be great.

TIA

onebuck · 04-18-2009, 09:24 PM

Hi,

You can look at 'Configuring your network in Slackware' to assist you in your network setup.

This link and others are available from 'Slackware-Links'. More than just Slackware® links!

four20 · 04-18-2009, 09:44 PM

There's a couple links you listed that I haven't looked at yet. I'll give them a try.
Thanks very much.

Don

wheelsg · 04-20-2009, 03:14 PM

I'll take a look at the links also, but in the meantime what's worked for me (Linksys WPC100N card->WPA2 wifi router) has been to stop wicd, invoke wpa_supplicant with driver and .conf, then ivoke dhcpcd on the interface. Clunky, but it works. I can get onto unprotected nets with wicd as well.

My original thought was that I'd need to re-install wicd since my madwifi and wpa_supplicant builds came after the initial install.

Talk to you later,
Geoff.

boler · 04-22-2009, 09:43 AM

Hi, I don't know anything about Wicd but I'll tell you how I connect to an encrypted wifi network.

The first thing that I noticed is that "ENCRYPTION KEY = OFF" in the iwconfig output. Encryption key should be on and the key stated.

First of all read the slackbook page on networking if you haven't already: http://www.slackbook.org/html/networ...-hardware.html.

run netconfig if you haven't already.

As for the setup. This is what I do as root: (NOTE: ath0 for my card, you need to use wlan0 etc.)

ifconfig ath0 up
iwconfig ath0 essid LINKSYS_WIFI
iwconfig ath0 ap 08:09:AA:BB:CC
iwconfig ath0 key 1234-5678-9ABC-DEF0-1234-66
iwconfig ath0 key on
iwconfig (to check settings)
dhcpcd ath0 (uses dhcp to find an ip address)

The point is you need to specify using "iwconfig ath0 essid" the name of the wireless network. I also specify the access point hardware address which you can find by typing:

iwlist scan

and copying the number of your wifi network.

If your network is not encrypted use:

iwconfig ath0 key off

I pull all this in a little script which runs at boot time so the machine is internet ready when I log in.

Does this work?

wheelsg · 04-22-2009, 10:54 AM

That's pretty much what wpa_supplicant does. Set up a wpa_supplicant.conf file with the ESSID and a plain-english passphrase. There's a sample file that will guide you. The syntax for invoking wpa_supplicant is:

Code:

wpa_supplicant -Bw -c/etc/wpa_supplicant.conf -Dwext -iwlan0

'-Bw' runs it as a daemon, waiting for insertion of the wifi card.

'-c'specifies the full path & filename of the configuration file mentioned above.

'-Dwext' loads the 'Wireless EXTensions' driver, since it seems that that is what you're using. You can confirm that in the wicd preferences.

'-iwlan0' tells it the interface name created by invoking the driver (from your 'iwconfig' output, wmaster0 doesn't seem to be set up).

You can use '-d' instead of '-Bw' to see the activity on stdout to give you confidence it works, then Ctrl-C and reinvoke it with '-Bw' when you know it's right. Using '-dd' makes it a bit more verbose, showing you the actual passing of the passphrase (in hex).

Wicd uses wpa_supplicant as well, but it seems to stall after the negotiation. That's why your dhcpcd can't get through. When you don't use wicd, you can use wpa_cli, the command-line interface to wpa_supplicant, to get the status of the connection. Once you're connected, invoke dhcpcd (with the -d option, to daemonize it with your interface) and you should get an address in short order.

Good luck,
Geoff.

(Aside to AlienBob: how'd I do?)

okos · 04-22-2009, 06:02 PM

Did you make sure your router works properly.
I had a dell true mobile router with wpa encryption. I fiddled and fiddled with my computer trying to make it work to no avail. I then tried on my wife's computer and discovered it did not work either. When I bought a new router and it worked like a charm. I used both wicd and the stock /etc/rc.d/inetd.conf successfully with the new router.

See how I did things here.

BobNutfield · 04-22-2009, 06:29 PM

Quote:

wlan0 IEEE 802.11bg ESSID:"NETGEAR1"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated

Hello, I don't use wicd, so this response may not be relevant, but I have a post just tonight on this forum seeking help for a similar issue with wpa_supplicant. I noticed that your wireless is not associated with the hardware address and when I did that, it cured by connection problems because I was having the same issue with being able to connect to an unesecured network but not a secured one.

You might try running:

Quote:

iwconfig wlan0 ap 00:18:f3:3b:d5:0c

May not be the answer, but worth a shot.

Bob

EDIT: Sorry, I just noticed that boler had already suggested this.