You are not logged in.
fixed in testing.
Freedom is what i love
Offline
jordz wrote:I also can't connect with networkmanager.
When i try to restart it i get this error::: Starting NetworkManager [BUSY]
/opt/gnome/sbin/NetworkManager: error while loading shared libraries:
libiw.so.28: cannot open shared object file: No such file or directory [FAIL]Somebody fixed it yet ?
rebuild it, wireless tools was updated to 0.29
thx i fixed it.
I now know why i can't connect anymore dhcdbd isn't running.
Is there yet a daemon script for?
edit: I found the script in this thread ![]()
Offline
hey guys, having some problems over here.
i don't have the network daemon running at all. i have eth0="dhcp" and ra0="dhcp" in my rc.conf. i started the dhcpcd daemon, and ran NetworkManager --no-daemon to show output.
here's what i get when i try to connect:
NetworkManager: <information> ra0: Device is fully-supported using driver 'rt2500'.
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 'ra0'.
-------------------
NetworkManager: <information> SUP: sending command 'INTERFACE_ADD ra0 wext /usr/var/run/wpa_supplicant '
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
there's a lot of operation not supported things. anyone got a clue how to debug this? or perhaps even more output?
Offline
Hi,
I'm having troubles connecting to my WPA network with NetworkManager (v0.6.3) from testing using bcm43xx driver on kernel26-2.6.17.4-2.
Here is the last line of log:
Jul 7 15:53:17 ****** NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jul 7 15:53:17 ****** NetworkManager: <information> Activation (eth1/wireless): access point '******************************' is encrypted, but NO valid key exists. New key needed.
Jul 7 15:53:17 ****** NetworkManager: <information> Activation (eth1) New wireless user key requested for network '******************************'.
Jul 7 15:53:17 ****** NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jul 7 15:53:17 ****** NetworkManager: <information> Activation (eth1) New wireless user key for network '******************************' received.
Jul 7 15:53:17 ****** NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jul 7 15:53:17 ****** NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jul 7 15:53:17 ****** NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jul 7 15:53:17 ****** NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jul 7 15:53:17 ****** NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jul 7 15:53:17 ****** NetworkManager: <information> Activation (eth1/wireless): access point '******************************' is encrypted, and a key exists. No new key needed.
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: sending command 'INTERFACE_ADD eth1 wext /usr/var/run/wpa_supplicant '
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: response was 'OK'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: sending command 'AP_SCAN 1'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: response was 'OK'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: sending command 'ADD_NETWORK'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: response was '0'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 ssid ************************************************************'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: response was 'OK'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 proto WPA'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: response was 'OK'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: response was 'OK'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 psk <key>'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: response was 'OK'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: sending command 'ENABLE_NETWORK 0'
Jul 7 15:53:18 ****** NetworkManager: <information> SUP: response was 'OK'
Jul 7 15:53:18 ****** NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jul 7 15:53:38 ****** NetworkManager: <information> Activation (eth1/wireless): association took too long (>20s), failing activation.
Jul 7 15:53:38 ****** NetworkManager: <information> Activation (eth1) failure scheduled...
Jul 7 15:53:38 ****** NetworkManager: <information> Activation (eth1) failed for access point (******************************)
Jul 7 15:53:38 ****** NetworkManager: <information> Activation (eth1) failed.
Jul 7 15:53:38 ****** NetworkManager: <information> Deactivating device eth1.
Anyone having a clue why it gets timeout?!
Thanx.
Offline
hypermegachi: the rt2500 isn't supported
http://live.gnome.org/NetworkManagerHardware
try it with the ndiswrapper.
big_gie: it seems your driver is still somewhat buggy
http://live.gnome.org/NetworkManagerHardware
Freedom is what i love
Offline
ndiswrapper works like a charm.
and maybe to clear up some confusion, the network daemon has to be started for it to work (with lo as the only interface)
Offline
big_gie: it seems your driver is still somewhat buggy
http://live.gnome.org/NetworkManagerHardware
Maybe thats the reason. I am now able to connect by trying many times. After 2 or 3 times, it connect.
I'm a bit disapointed at NetworkManager. Not that I have to manually try many times. Why does it have to ask me for the keyring password to access the wpa key? If I don't want to boot in X and stay in console, theres no way to control it (or am I missing something?).
I think I'll try the native arch wireless thing. At least it should connect at bootup, and not at the end of Gnome's loading.
Offline
I'm a bit disapointed at NetworkManager. Not that I have to manually try many times. Why does it have to ask me for the keyring password to access the wpa key? If I don't want to boot in X and stay in console, theres no way to control it (or am I missing something?).
System wide configuration is planned for the 0.7 branch ;-) http://live.gnome.org/NetworkManagerToDo
Offline
System wide configuration is planned for the 0.7 branch ;-) http://live.gnome.org/NetworkManagerToDo
This is great news ![]()
Offline
Have we got VPN support included yet?
Offline
Have we got VPN support included yet?
VPN is not in the releases yet but only in CVS. I have made PKGBUILDS for them however:
Offline
oooooookay....... has anyone had this problem?
When I go to the terminal and type
nm-applet (or nm-applet &)
I get this error....(which repeats for quite a while...)
(nm-applet:4517): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
I have a fresh Arch install. and I installed gnome-network-manager from testing.
In this land of the pain the sane lose not knowing they were part of the game.
~LP
Offline
nevermind...
I uninstalled gnome-network-manager networkmanager dhcdbd and dhclient and then I build networkmanager and dhcdbd from the aur and reinstalled the rest, this time from Gandulf's repo, (thanks Gandaulf) and then restarted and Network-Manger is online...
FYI I have a WUSB54g wifi card using ndiswrapper, if you have those specs, I would be glad to help you with your wifi problems.
In this land of the pain the sane lose not knowing they were part of the game.
~LP
Offline
Hmm, network manager worked perfectly for me ~2 weeks ago. Now I upgraded and with the latest networkmanager + gnomenetworkmanager from 'community' I'm getting:
** (nm-applet:6827): WARNING **: <WARNING> nma_dbus_init (): nma_dbus_init() could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.19" is not allowed to own the service "org.freedesktop.NetworkManagerInfo" due to security policies in the configuration file'Looks like a permission problem mentioned before. I can use NM as root, but that's not handy. My versions:
local/gnome-network-manager 0.6.4-1
Gnome frontend to NetworkManager
local/libnetworkmanager 0.6.4-2
The Network Manager Library
local/networkmanager 0.6.4-2
A Network ManagerAny hints/clues?
thanks in advance,
MDK
Open Source Software Operations/Nokia
michael.kostrzewa (at) nokia.com
Offline
mdk: It seems like gnome-network-manager from testing is actually broken. It has its d-bus policies wrong. (Further more there seems to be some glib(related) problems as well. I have filed a bug on the d-bus issue, http://bugs.archlinux.org/task/5280.
Im actually not quite sure who is responsible for the package in question. I have talked to Blaasvis about it but he hadn't time atm. So one should probably talk to JGC. I am unfortunately also quite busy atm.
Offline
go to /etc/dbus-1/system.d
edit NetworkManager.conf and nm-applet.conf and change "deny" to "allow" for the default policy.
Offline
hypermegachi: dont do that. Then you will allow anyone to access that interface. Change the policy at_console to read group="users" instead. At least that give a _little_ higher security.
So change the line reading:
<policy at_console="true">to
<policy group="users">This is actually exactly what the missing policy.patch does.
Offline