Can connect but can't surf - Belkin F5D8235-4

I have a dual boot Dell Latitude D610 with XP/Suse 11.1 and my issue is very specific. Only the suse partition can connect to my router, but can’t reach any network addresses. I can’t so much as ping the router or any network devices. I have a few unsecured wireless networks in the area which allow me to connect to the internet without issue and my XP partition also works just fine.

I have all the latest updates/patches including the most recent pae kernel. Any advice would be appreciated.

speretz wrote:
> I have a dual boot Dell Latitude D610 with XP/Suse 11.1 and my issue is
> very specific. Only the suse partition can connect to my router, but
> can’t reach any network addresses. I can’t so much as ping the router
> or any network devices. I have a few unsecured wireless networks in the
> area which allow me to connect to the internet without issue and my XP
> partition also works just fine.
>
> I have all the latest updates/patches including the most recent pae
> kernel. Any advice would be appreciated.

You have a problem with encryption. Have you installed wpa_supplicant?

If you are using WEP, are you using the Hex key, or are you trying to use a
passphrase? The latter is likely to fail.

If using NetworkManager, send part of the log from /var/log/NetworkManager.

Larry

I have found that this works fine with a 64 bit hex key, but the passphrase does not work. I did not know to install the wpa_supplicant but have found that I already have it.

Hopefully this is the correct segment of the log file:

Mar 14 09:15:26 linux-elx0 NetworkManager: <info> eth1: link timed out.
Mar 14 09:15:27 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> associated
Mar 14 09:15:27 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: associated -> disconnected
Mar 14 09:15:31 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> associated
Mar 14 09:15:31 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: associated -> disconnected
Mar 14 09:15:34 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> associated
Mar 14 09:15:34 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: associated -> disconnected
Mar 14 09:15:37 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> associated
Mar 14 09:15:37 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: associated -> disconnected
Mar 14 09:15:40 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> associated
Mar 14 09:15:40 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: associated -> disconnected
Mar 14 09:15:42 linux-elx0 NetworkManager: <info> eth1: link timed out.
Mar 14 09:15:43 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> associated
Mar 14 09:15:43 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: associated -> disconnected
Mar 14 09:15:46 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> associated
Mar 14 09:15:46 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: associated -> disconnected
Mar 14 09:15:50 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> associated
Mar 14 09:15:50 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: associated -> disconnected
Mar 14 09:15:53 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> associated
Mar 14 09:15:53 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: associated -> disconnected
Mar 14 09:15:56 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> associated
Mar 14 09:15:56 linux-elx0 NetworkManager: <info> (eth1): supplicant connection state: associated -> disconnected
Mar 14 09:15:58 linux-elx0 NetworkManager: <WARN> get_secrets_cb(): Couldn’t get connection secrets: applet-device-wifi.c.1542 (get_secrets_dialog_response_cb): canceled.
Mar 14 09:15:58 linux-elx0 NetworkManager: <info> (eth1): device state change: 6 -> 9
Mar 14 09:15:58 linux-elx0 NetworkManager: <info> Activation (eth1) failed for access point (Belkin_N_Wireless_114F7B)
Mar 14 09:15:58 linux-elx0 NetworkManager: <info> Marking connection ‘Auto Belkin_N_Wireless_114F7B’ invalid.
Mar 14 09:15:58 linux-elx0 NetworkManager: <info> Activation (eth1) failed.
Mar 14 09:15:58 linux-elx0 NetworkManager: <info> (eth1): device state change: 9 -> 3
Mar 14 09:15:58 linux-elx0 NetworkManager: <info> (eth1): deactivating device (reason: 0).

If you are using WEP, failure of the passphrase is common. The reason is that
the “standard” does not have a standard method of converting from a phrase to
the key. If your AP and the client use different methods, it fails.

If you are using WPA, I have never heard of a failure of passphrase conversion
as there is a standard method for conversion.

Larry