Arch Linux

Schrauber

Member

Registered: 2007-02-01

Posts: 7

Re: Problems with KNetworkManager

Hi,

same problem to me. I already changed my rc.conf as suggested. But no result.

Here my rc.conf:

...
MODULES=(mii via-rhine agpgart via-agp drm powernow-k7 pcmcia ndiswrapper)
...
lo="lo 127.0.0.1"
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(lo !eth0 !wlan0)

gateway="default gw 192.168.178.1"
ROUTES=(!gateway)
...
DAEMONS=(syslog-ng !network dbus hal !netfs crond dhcdbd networkmanager alsa cpufreq)

Output of ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:40:D0:5F:8F:1D
          inet addr:192.168.178.20  Bcast:192.168.178.255  Mask:255.255.255.0
          inet6 addr: fe80::240:d0ff:fe5f:8f1d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:440 errors:0 dropped:0 overruns:0 frame:0
          TX packets:431 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:268122 (261.8 Kb)  TX bytes:54678 (53.3 Kb)
          Interrupt:10 Base address:0xe300

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:174 errors:0 dropped:0 overruns:0 frame:0
          TX packets:174 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:13380 (13.0 Kb)  TX bytes:13380 (13.0 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:0F:B5:84:81:A8
          inet6 addr: fe80::20f:b5ff:fe84:81a8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:6 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:452 (452.0 b)  TX bytes:0 (0.0 b)
          Interrupt:7 Memory:22010000-22020000

Output of iwconfig:

wlan0     IEEE 802.11b  ESSID:"Axohzgftv&mwg"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:04:0E:A6:9A:D6
          Bit Rate=54 Mb/s   Sensitivity=-200 dBm
          RTS thr=2346 B   Fragment thr=2346 B
          Power Management:off
          Link Quality:50/100  Signal level:-64 dBm  Noise level:-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Messages.log:

Feb  1 20:25:50 laptop NetworkManager: <information>    Deactivating device wlan0.
Feb  1 20:25:50 laptop NetworkManager: <WARNING>         nm_device_802_11_wireless_set_essid (): error setting ESSID to '' for device wlan0: Invalid argument
Feb  1 20:26:36 laptop NetworkManager: <information>    wlan0: Device is fully-supported using driver 'ndiswrapper'.
Feb  1 20:26:36 laptop NetworkManager: <information>    Now managing wireless (802.11) device 'wlan0'.
Feb  1 20:26:36 laptop NetworkManager: <information>    Deactivating device wlan0.
Feb  1 20:26:38 laptop NetworkManager: <WARNING>         nm_device_802_11_wireless_set_essid (): error setting ESSID to '' for device wlan0: Invalid argument
Feb  1 20:28:36 laptop NetworkManager: <information>    User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / Axohzgftv&mwg
Feb  1 20:28:36 laptop NetworkManager: <information>    Deactivating device wlan0.
Feb  1 20:28:36 laptop NetworkManager: <WARNING>         nm_device_802_11_wireless_set_essid (): error setting ESSID to '' for device wlan0: Invalid argument
Feb  1 20:28:36 laptop NetworkManager: <information>    Device wlan0 activation scheduled...
Feb  1 20:28:36 laptop NetworkManager: <information>    Activation (wlan0) started...
Feb  1 20:28:36 laptop NetworkManager: <information>    Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb  1 20:28:36 laptop NetworkManager: <information>    Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb  1 20:28:36 laptop NetworkManager: <information>    Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb  1 20:28:36 laptop NetworkManager: <information>    Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb  1 20:28:36 laptop NetworkManager: <information>    Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb  1 20:28:36 laptop NetworkManager: <information>    Activation (wlan0/wireless): access point 'Axohzgftv&mwg' is encrypted, and a key exists.  No new key needed.
Feb  1 20:28:36 laptop NetworkManager: <information>    SUP: sending command 'INTERFACE_ADD wlan0               wext    /var/run/wpa_supplicant '
Feb  1 20:28:38 laptop NetworkManager: <WARNING>         real_act_stage2_config (): Activation (wlan0/wireless): couldn't monitor the supplicant.
Feb  1 20:28:38 laptop NetworkManager: <information>    Activation (wlan0) failure scheduled...
Feb  1 20:28:38 laptop NetworkManager: <information>    Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb  1 20:28:38 laptop NetworkManager: <information>    Activation (wlan0) failed for access point (Axohzgftv&mwg)
Feb  1 20:28:38 laptop NetworkManager: <information>    Activation (wlan0) failed.
Feb  1 20:28:38 laptop NetworkManager: <information>    Deactivating device wlan0.
Feb  1 20:28:38 laptop NetworkManager: <WARNING>         nm_device_802_11_wireless_set_essid (): error setting ESSID to '' for device wlan0: Invalid argument

I can not see a problem in config. Connection through wired network works fine with Knetworkmanager.
Only thing are the messages in message.log. But I not sure about what they mean.
And yes, the network is encrypted. With wpa_supplicant it worked fine. But I wanted the comfort of Knetworkmanager.

mutlu_inek

Member

From: all over the place

Registered: 2006-11-18

Posts: 683

Re: Problems with KNetworkManager

Schrauber, your /etc/rc.conf looks fine.

It seems that NetworkManager cannot correctly (or at all) use wpa_supplicant.

1. Does NM work for unencrypted networks?

2. Does wpa_supplicant actually run as a process?

3. Is SSID broadcasting turned off on your router? If yes, you have to adjust the settings in /etc/wpa_supplicant.conf.

# AP scanning/selection
# By default, wpa_supplicant requests driver to perform AP scanning and then
# uses the scan results to select a suitable AP. Another alternative is to
# allow the driver to take care of AP scanning and selection and use
# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
# information from the driver.
# 1: wpa_supplicant initiates scanning and AP selection
# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
#    parameters (e.g., WPA IE generation); this mode can also be used with
#    non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
#    APs (i.e., external program needs to control association). This mode must
#    also be used when using wired Ethernet drivers.
# 2: like 0, but associate with APs using security policy and SSID (but not
#    BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
#    enable operation with hidden SSIDs and optimized roaming; in this mode,
#    the network blocks in the configuration file are tried one by one until
#    the driver reports successful association; each network block should have
#    explicit security policy (i.e., only one option in the lists) for
#    key_mgmt, pairwise, group, proto variables
ap_scan=1

Therefore, if essid is not broadcast, change it to ap_scan=2.

4. If you tried that and it does not work, try getting more information from NetworkManager by doing this in a console:

sudo killall NetworkManager
sudo NetworkManager --no-daemon

Please post the complete output generated while trying to connect.

Schrauber

Member

Registered: 2007-02-01

Posts: 7

Re: Problems with KNetworkManager

I will try out without encryption this evening. But with only wpa_supplicant it worked fine.

And my ESSID is broadcasted.

Schrauber

Member

Registered: 2007-02-01

Posts: 7

Re: Problems with KNetworkManager

Your tip with wpa_supplicant.conf was right. Thank you very much. Now it works fine.

damjan

Member

Registered: 2006-05-30

Posts: 452

Re: Problems with KNetworkManager

I did not know, you did not tell that before. I am not absolutely sure about what to do in this case, but if it does not work I would make an entry for it in rc.conf anyway.

I tried that also INTERFACES=(lo !ath0 !eth0) but there was no change.

Just out of curiosity, why is pcmcia explicitly not started in rc.conf?

It's not needed since kernel 2.6.16 (I think, maybe it was another version), and even before pcmcia was not needed for CardBus cards (so actually it's a CardBus).

I'm a bit confused about what you are saying... in my rc.conf NetworkManager is started *after* dhcdbd.

Well, does it work? If not, why don't you do what I advised? Please post what you did and if you do not understand something about what I wrote, please describe exactly what you do not understand about it.

Holding back information and making other people guess will not help you all that much.

Well, I didn't do anything first ... I thought NetworkManager „should just work"™ .. but obviously not.

What I do is ... starting from an unconfigured wifi interface (pcmcia card just inserted, driver loads automatically, the interface is down). Then I start /etc/rc.d/dhcdbd, start /etc/rc.d/networkmanager and knetworkmanager. Then I click on the ssid in knetworkmanager's menu .. Nothing happens. I then repeat, and check with 'iwconfig ath0' and I can see it scans for the wifi network but can't find it .. or it can't associate ... I don't know why. I see wpa_supplicant is running (even if my wifi doesn't use any security nor is the essid hidden). I've now tried seting wpa_supplicant to ap_scan=0, 1 and 2 .. but it didn't help.

As I said, if I stop networkmanager, I can connect to my wifi AP very easily with iwconfig.

mutlu_inek

Member

From: all over the place

Registered: 2006-11-18

Posts: 683

Re: Problems with KNetworkManager

Did you change "network" to "!network" in the DAEMONS section of your rc.conf as I suggested?

Please post your current rc.conf.

Master One

Member

From: Europe

Registered: 2007-01-21

Posts: 249

Re: Problems with KNetworkManager

Anybody running network-manager + avahi? I found out, that network-manager is the reason, why avahi-dnsconfd can not be started on boot or resume. Please have a look at this thread for details.

damjan

Member

Registered: 2006-05-30

Posts: 452

Re: Problems with KNetworkManager

Did you change "network" to "!network" in the DAEMONS section of your rc.conf as I suggested?

Yes

Please post your current rc.conf.

here it is stripped of comments:

LOCALE="mk_MK.utf8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Skopje"
KEYMAP="us"
CONSOLEFONT="cyr-sun16"
CONSOLEMAP=
USECOLOR="yes"

MOD_AUTOLOAD="yes"
MOD_BLACKLIST=()
MODULES=(e100 psmouse fuse button fan battery ac processor thermal video)
USELVM="no"

HOSTNAME="archaeopteryx"
lo="lo 127.0.0.1"
INTERFACES=(lo !ath0 !eth0)
ROUTES=()

DAEMONS=(syslog-ng !hotplug !pcmcia @gensplash !network netfs alsa dbus @hal @avahi-daemon @avahi-dnsconfd kdm @bluetooth @smartd @crond @gpm @sshd dhcdbd @networkmanager)

VERBOSEONFAIL="yes"

mutlu_inek

Member

From: all over the place

Registered: 2006-11-18

Posts: 683

Re: Problems with KNetworkManager

Try this:

...
HOSTNAME="archaeopteryx"
lo="lo 127.0.0.1"
ath0="dhcp"
eth0="dhcp"
INTERFACES=(lo !ath0 !eth0)
gateway="default gw 192.168.178.1"
ROUTES=(!gateway)
...

damjan

Member

Registered: 2006-05-30

Posts: 452

Re: Problems with KNetworkManager

No change... BTW are you sure networkmanages cares about what's in rc.conf ... since I don't see where he checks those values.

mutlu_inek

Member

From: all over the place

Registered: 2006-11-18

Posts: 683

Re: Problems with KNetworkManager

are you sure networkmanages cares about what's in rc.conf

Definitely.

After system boot do the following and report the output that is given in the console when you try to connect with either Gnome or KDE system tray applet.

sudo killall NetworkManager
sudo NetworkManager --no-daemon

damjan

Member

Registered: 2006-05-30

Posts: 452

Re: Problems with KNetworkManager

SOLVED AT LAST

Ok, the sollution was to have this in /etc/wpa_supplicant.conf:

network={
   ssid=""
   key_mgmt=NONE
}

I've also reverted /etc/rc.conf to :

HOSTNAME="archaeopteryx"
lo="lo 127.0.0.1"
INTERFACES=(lo)

ROUTES=()

and all is good. KnetworkManager works even then.

Thank you everybody.

tim

Member

From: Sweden

Registered: 2006-10-29

Posts: 98

Re: Problems with KNetworkManager

OK so I have a really weird problem to add to the network manager woes. If I use networkmanager I can connect to wireless access points etc and cruise the net blah blah. BUT (and yes I have tested this extensively) if I use networkmanager I cannot send or receive email via imap using any email client (kmail, thunderbird, sylpheed, evolution etc etc) and when I go to print (i have a wireless printer) the print dialog freezes for about a minute or more and then once that dialog disapears, the actual document sits in a queue for about another minute before actually being sent to the printer.

None of these problems happen if I do not use network manager and yes I've set everything up with network manager exactly as has been explained in this post several times

p.s. I'm using 0.8 voodoo

tim

tafsen

Member

Registered: 2006-05-03

Posts: 141

Re: Problems with KNetworkManager

What applet is the KNetworkManager shown by?

mutlu_inek

Member

From: all over the place

Registered: 2006-11-18

Posts: 683

Re: Problems with KNetworkManager

What applet is the KNetworkManager shown by?

I do not quite understand.

KNetworkManager is the KDE frontend (including system tray applet) for NetworkManager. Is that helpful?

tafsen

Member

Registered: 2006-05-03

Posts: 141

Re: Problems with KNetworkManager

Well, I got KNW to work last time, but now I have a fresh install of Arch and I can't make a connection with KNW.  The program says that it's connected, but I don't get an ipadress.  It sets ESSID but I don't get an ip.

knogi

Member

Registered: 2007-03-22

Posts: 3

Re: Problems with KNetworkManager

Hello!
I have a problem to get my wlan running with knetworkmanager. My normal lan is running well with it.
For testing I have an Access Point running without any encryption.

/etc/rc.conf

lo="lo 127.0.0.1"
#eth0="eth0 10.150.96.128 netmask 255.255.255.0"
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo !eth0 !eth1)

gateway="default gw 192.168.0.1"
#stusta="default gw 10.150.96.254"
ROUTES=( !gateway)

DAEMONS=(syslog-ng dbus hal !network crond netfs dhcdbd networkmanager bluetooth samba cups)

/etc/conf.d/wireless

wlan_eth1="eth1 mode managed essid lrz"
WLAN_INTERFACES=(eth1)

ifconfig

eth0      Link encap:Ethernet  HWaddr 00:C0:9F:BF:5E:C8
          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::2c0:9fff:febf:5ec8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15896 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11019 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8742183 (8.3 Mb)  TX bytes:1671007 (1.5 Mb)
          Interrupt:16

eth1      Link encap:Ethernet  HWaddr 00:12:F0:DE:40:8C
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:548 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6205 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:17 Memory:b0218000-b0218fff

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:740 errors:0 dropped:0 overruns:0 frame:0
          TX packets:740 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:58115 (56.7 Kb)  TX bytes:58115 (56.7 Kb)

iwconfig

lo        no wireless extensions.

eth0      no wireless extensions.

eth1      unassociated  ESSID:""
          Mode:Managed  Channel=0  Access Point: Not-Associated
          Bit Rate:0 kb/s   Tx-Power=20 dBm   Sensitivity=8/0
          Retry limit:7   RTS thr:off   Fragment thr:off
          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

eth2      no wireless extensions.

if I run NetworkManager --no-daemon

NetworkManager: <information>   starting...
NetworkManager: <information>   eth1: Device is fully-supported using driver 'ipw2200'.
NetworkManager: <information>   nm_device_init(): waiting for device's worker thread to start
NetworkManager: <information>   nm_device_init(): device's worker thread started, continuing.
NetworkManager: <information>   Now managing wireless (802.11) device 'eth1'.
NetworkManager: <information>   Deactivating device eth1.
NetworkManager: <information>   eth0: Device is fully-supported using driver 'tg3'.
NetworkManager: <information>   nm_device_init(): waiting for device's worker thread to start
NetworkManager: <information>   nm_device_init(): device's worker thread started, continuing.
NetworkManager: <information>   Now managing wired Ethernet (802.3) device 'eth0'.
NetworkManager: <information>   Deactivating device eth0.
NetworkManager: <information>   Updating allowed wireless network lists.
NetworkManager: <WARNING>        nm_dbus_get_networks_cb (): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - org.freedesktop.NetworkManagerInfo.NoNetworks.
NetworkManager: <debug info>    [1174567728.803703] nm_device_802_11_wireless_get_activation_ap (): Forcing AP 'knet'
NetworkManager: <information>   User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / knet
NetworkManager: <information>   Deactivating device eth1.
NetworkManager: <information>   Device eth1 activation scheduled...
NetworkManager: <information>   Activation (eth1) started...
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <information>   Activation (eth1/wireless): access point 'knet' is unencrypted, no key needed.
NetworkManager: <information>   SUP: sending command 'INTERFACE_ADD eth1                wext  /var/run/wpa_supplicant  '
/usr/sbin/wpa_supplicant: symbol lookup error: /usr/sbin/wpa_supplicant: undefined symbol: SSL_CTX_set_info_callback
NetworkManager: <information>   SUP: response was '@Dѷ@Dѷedesktop/NetworkManager/Devices/eth1/Networks/knet'
NetworkManager: <WARNING>        nm_utils_supplicant_request_with_check (): supplicant_interface_init: supplicant error for 'INTERFACE_ADD eth1                wext    /var/run/wpa_supplicant'.  Response: '@Dѷ@Dѷedesktop/NetworkManager/Devices/eth1/Networks/knet'
NetworkManager: <WARNING>        real_act_stage2_config (): Activation (eth1/wireless): couldn't connect to the supplicant.
NetworkManager: <information>   Activation (eth1) failure scheduled...
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <information>   Activation (eth1) failed for access point (knet)
NetworkManager: <information>   Activation (eth1) failed.
NetworkManager: <information>   Deactivating device eth1.
NetworkManager: <WARNING>        nm_signal_handler (): Caught signal 2, shutting down normally.
NetworkManager: <information>   Caught terminiation signal
NetworkManager: <debug info>    [1174567735.627023] nm_print_open_socks (): Open Sockets List:
NetworkManager: <debug info>    [1174567735.627049] nm_print_open_socks (): Open Sockets List Done.
NetworkManager: <information>   Deactivating device eth1.
NetworkManager: <information>   Deactivating device eth0.

Everytime I want to connect to my ap it cancels at 28% (device configuration or so).
knogi

Last edited by knogi (2007-03-22 12:56:33)

Back2Cali

Member

From: Germany

Registered: 2006-02-26

Posts: 223

Re: Problems with KNetworkManager

I also have a problem with (k)networkmanager. If I want to get an IP for the WLan device using dhcp nothing happens but it works fine for the LAN adapter. But switching from WLan to Lan and back will work using a static IP in rc.conf instead of using dhcp. Since this bothered me a lot I tried the gnome network manager on another laptop and the same thing happened. I can only get an IP on my LAN adapter. So I guess this is nothing caused by knetworkmanager or gnome-network-manager. I think this problem is caused by networkmanager itself.
Maybe somebody should write a bug report. Since I don't know much more than the things I wrote above maybe the bug should be reported by somebody who has a little more detailed information than mine.

bboozzoo

Member

From: Poland

Registered: 2006-08-01

Posts: 125

Re: Problems with KNetworkManager

the point is that networkmanager can support only one active link right now, though support for more links is part of google summer of code projects

mutlu_inek

Member

From: all over the place

Registered: 2006-11-18

Posts: 683

Re: Problems with KNetworkManager

/etc/conf.d/wireless

wlan_eth1="eth1 mode managed essid lrz"
WLAN_INTERFACES=(eth1)

What happens if you comment out everything you have in /etc/conf.d/wireless?

knogi

Member

Registered: 2007-03-22

Posts: 3

Re: Problems with KNetworkManager

If I comment out everything in /etc/conf.d/wireless and start NetworkManager --no-daemon I get following output:

NetworkManager: <information>   starting...
NetworkManager: <information>   eth1: Device is fully-supported using driver 'ipw2200'.
NetworkManager: <information>   nm_device_init(): waiting for device's worker thread to start
NetworkManager: <information>   nm_device_init(): device's worker thread started, continuing.
NetworkManager: <information>   Now managing wireless (802.11) device 'eth1'.
NetworkManager: <information>   Deactivating device eth1.
NetworkManager: <information>   eth0: Device is fully-supported using driver 'tg3'.
NetworkManager: <information>   nm_device_init(): waiting for device's worker thread to start
NetworkManager: <information>   nm_device_init(): device's worker thread started, continuing.
NetworkManager: <information>   Now managing wired Ethernet (802.3) device 'eth0'.
NetworkManager: <information>   Deactivating device eth0.
NetworkManager: <information>   Updating allowed wireless network lists.
NetworkManager: <WARNING>        nm_dbus_get_networks_cb (): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - org.freedesktop.NetworkManagerInfo.NoNetworks.
NetworkManager: <debug info>    [1174638809.166279] nm_device_802_11_wireless_get_activation_ap (): Forcing AP 'knet'
NetworkManager: <information>   User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / knet
NetworkManager: <information>   Deactivating device eth1.
NetworkManager: <information>   Device eth1 activation scheduled...
NetworkManager: <information>   Activation (eth1) started...
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <information>   Activation (eth1/wireless): access point 'knet' is unencrypted, no key needed.
NetworkManager: <information>   SUP: sending command 'INTERFACE_ADD eth1       wext     /var/run/wpa_supplicant '
/usr/sbin/wpa_supplicant: symbol lookup error: /usr/sbin/wpa_supplicant: undefined symbol: SSL_CTX_set_info_callback
NetworkManager: <information>   SUP: response was 'X$߷X$߷P!߷
                                                           edesktop/NetworkManager/h'
NetworkManager: <WARNING>        nm_utils_supplicant_request_with_check (): supplicant_interface_init: supplicant error for 'INTERFACE_ADD eth1         wext   /var/run/wpa_supplicant  '.  Response: 'X$߷X$߷P!߷
                                               edesktop/NetworkManager/h'
NetworkManager: <WARNING>        real_act_stage2_config (): Activation (eth1/wireless): couldn't connect to the supplicant.
NetworkManager: <information>   Activation (eth1) failure scheduled...
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <information>   Activation (eth1) failed for access point (knet)
NetworkManager: <information>   Activation (eth1) failed.
NetworkManager: <information>   Deactivating device eth1.

As you can see I still can't connect.
knogi

knogi

Member

Registered: 2007-03-22

Posts: 3

Re: Problems with KNetworkManager

Ok, finally I got it to work. :-)

I searched for "wpa_supplicant: undefined symbol: SSL_CTX_set_info_callback" from my "NetworkManager --no-daemon" output and I found that it seems to be a part of ssl. So I installed openssl and now everything works fine. Thanks for the help.
knogi