Ubuntu

knetworkmanager activating, won't change

Asked by maxsx

Hallo,

i'm trying to setup a connection to Linksys AP with "dd-wrt" firmware via Knetworkmanager.
Sometimes it is possible to connect, but mostly not. The wireless connection is working with public access points in this location.
The ap is hidden.

release:
System:
Distributor ID: Ubuntu
Description: Ubuntu 8.04.1
Release: 8.04.1
Codename: hardy

controller:
Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)

syslog:

Jun 12 11:34:19 maxsx-laptop NetworkManager: <info> Activation (eth1) started...
Jun 12 11:34:19 maxsx-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jun 12 11:34:19 maxsx-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jun 12 11:34:19 maxsx-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jun 12 11:34:19 maxsx-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jun 12 11:34:19 maxsx-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jun 12 11:34:19 maxsx-laptop NetworkManager: <info> Activation (eth1/wireless): access point 'NSN-Wimax' is encrypted, and a key exists. No new key needed.
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant0^I'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: response was '0'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 4e534e2d57696d6178'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 12 11:34:20 maxsx-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jun 12 11:34:22 maxsx-laptop NetworkManager: <info> Old device 'eth1' activating, won't change.

thank You

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Bhavani Shankar (bhavi) said : 		#1

Hello

Try wicd (http://wicd.sourceforge.net/) is a wireless network manager for Linux. Instructions for its installation on Ubuntu can be found here (http://wicd.sourceforge.net/wiki/doku.php?id=faq). It's pretty simple but you'll need a way to get the computer temporary internet access (i.e. via wire) or transfer the packages via an usb disk or something.

Works for hardy too.. Have a try...

Regards

Bhavani Shankar.

Revision history for this message
Alecz20 (alexguzu) said : 		#2

I had the same problem. I also tried wicd, but it didn't help, it still didn't connect.

It seems that sometimes a restart or persistence on trying to connect works sometimes.

There is also a bug report for this issue:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/138922

Can you help with this problem?

Provide an answer of your own, or ask maxsx for more information if necessary.

To post a message you must log in.