LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   cannot connect to secure wireless network with Fedora 3 (https://www.linuxquestions.org/questions/linux-wireless-networking-41/cannot-connect-to-secure-wireless-network-with-fedora-3-a-363418/)

raindogs 09-14-2005 04:55 PM

cannot connect to secure wireless network with Fedora 3
 
I'm using Fedora 3 on a Thinkpad 600x with an Aironet 4800 Wireless card. I can connect to a wireless network when it's totally open and insecure, but as soon as I need to deal with any sort of WEP security or even an SSID, I can't get an IP address. I'm currently trying to connect to a network that is password-protected and has the SSID "house", but the same problems persist. I have tested out the network on another machine and everything works fine, so I'm sure that the network is up and I have the right password. I've pasted all of the relevant info below and would really appreciate any suggestions.

Thanks,
Alex
***************************************************************************
settings in Fedora's network wirless configuration tool:

mode: Managed
network name (SSID): specified, house
channel: 1
transmit rate: 11Mb/s
key: <correct key> (yes, I'm sure it's right and I'm sure it's not hex)

***************************************************************************
output of iwconifg:
sit0 no wireless extensions.

eth0 IEEE 802.11-DS ESSID:"house"
Mode:Managed Frequency:2.442 GHz Access Point: FF:FF:FF:FF:FF:FF
Bit Rate=11 Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thr:off Fragment thr:off
Encryption key:****-****-****-****-****-****-** Security mode:open
Power Management:off
Link Quality=0/100 Signal level=-106 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

wifi0 IEEE 802.11-DS ESSID:"house"
Mode:Managed Frequency:2.442 GHz Access Point: FF:FF:FF:FF:FF:FF
Bit Rate=11 Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thr:off Fragment thr:off
Encryption key:****-****-****-****-****-****-** Security mode:open
Power Management:off
Link Quality=0/100 Signal level=-106 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

***************************************************************************
output after running �ifup eth0�:

Determining IP information for eth0...PING 192.168.99.1 (192.168.99.1) from 192.168.99.72 eth0: 56(84) bytes of data.

--- 192.168.99.1 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
, pipe 4
failed.


output of `tail -30 /var/log/messages`

Sep 14 14:35:10 localhost dhclient: No DHCPOFFERS received.
Sep 14 14:35:10 localhost dhclient: Trying recorded lease 192.168.99.72
Sep 14 14:35:13 localhost kernel: airo: cmd= 2
Sep 14 14:35:13 localhost kernel: airo: status= 7f02
Sep 14 14:35:13 localhost kernel: airo: Rsp0= 0
Sep 14 14:35:13 localhost kernel: airo: Rsp1= ff10
Sep 14 14:35:13 localhost kernel: airo: Rsp2= 10
Sep 14 14:36:54 localhost kernel: Setting key 0
Sep 14 14:36:55 localhost kernel: airo: cmd= 1
Sep 14 14:36:55 localhost kernel: airo: status= 7f01
Sep 14 14:36:55 localhost kernel: airo: Rsp0= 85
Sep 14 14:36:55 localhost kernel: airo: Rsp1= ff10
Sep 14 14:36:55 localhost kernel: airo: Rsp2= 10
Sep 14 14:36:55 localhost dhclient: wifi0: unknown hardware address type 801
Sep 14 14:36:55 localhost dhclient: wifi0: unknown hardware address type 801
Sep 14 14:36:55 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Sep 14 14:37:03 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Sep 14 14:37:12 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Sep 14 14:37:20 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Sep 14 14:37:35 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Sep 14 14:37:43 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Sep 14 14:37:53 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Sep 14 14:38:07 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Sep 14 14:38:13 localhost dhclient: No DHCPOFFERS received.
Sep 14 14:38:13 localhost dhclient: Trying recorded lease 192.168.99.72
Sep 14 14:38:16 localhost kernel: airo: cmd= 2
Sep 14 14:38:16 localhost kernel: airo: status= 7f02
Sep 14 14:38:16 localhost kernel: airo: Rsp0= 0
Sep 14 14:38:16 localhost kernel: airo: Rsp1= ff10
Sep 14 14:38:16 localhost kernel: airo: Rsp2= 10

Matir 09-14-2005 05:11 PM

If you are using an ascii key, you must prepend it with "s:".

raindogs 09-14-2005 07:19 PM

Thanks for the reply. I did enter the "s:" before the key, but the same errors happen. I should also note that I had this same problem on a network at a cafe that had an SSID but no encryption. It seems that I have something incorrect on some deeper level, but I'm left scracthing my head as to what that might be.




Quote:

Originally posted by Matir
If you are using an ascii key, you must prepend it with "s:".

Matir 09-14-2005 10:34 PM

Well, all networks have an SSID. Are you sure you have the right/proper driver?

raindogs 09-15-2005 10:08 AM

I'm pretty sure I do, as it has worked before on networks that are open and insecure. Of course it's possible that I'm inadvertantly changed something, is there a way I can double check this? The selection in the GUI device setup does claim to be detecting the correct device.


Quote:

Originally posted by Matir
Well, all networks have an SSID. Are you sure you have the right/proper driver?

Matir 09-15-2005 10:30 AM

Just checking. Are eth0 and wifi0 the same device on your system?


All times are GMT -5. The time now is 08:53 PM.