Problems with KNetworkManager

tafsen · 2007-01-23 20:58:56

I find both my Wireless and my wired network with KNetworkManager, but I can't connect to the network. Not even with dhclient, as long as NetworkManager is running. But if I stop NetworkManager, I have no problem to get connection with dhclient. How do I fix this?

mutlu_inek · 2007-01-23 23:18:00

Could you please post the relevant parts of /etc/rc.conf?

Could you post the output from ifconfig and iwconfig?

Do you actually see your wireless network's essid in KNetworkManager?

Does your router/AP use MAC filtering or encryption?

joshuaheretic · 2007-01-25 16:27:22

I had a similar problem once with NetworkManager. My problem ended up being that the DBus connection policies were too restrictive. I edited my /etc/dbus-1/system.d/NetworkManager.conf file, added "allow own" lines to all of the user sections, and remove all of the "deny" lines. I should say that while it got it to work for me as a quick fix, I'm sure it is not recommended, and I can't vouch for the safety or stability of doing it this way. Also, you may have to do something similar for the dhcdbd.conf and nm-applet.conf in the same directory.

Snarkout · 2007-01-25 18:29:04

I needed to have dhcdbd in my daemons array, needed to remove "network" from the daemons, and needed to comment out any interfaces I wanted handled by networkmanager for things to work correctly for me.

tafsen · 2007-01-25 19:15:39

I did what Snarkout said, removed 'network' drom deamons and comment out the interfaces's (exept lo). And then made a restart. Started dhcpcd and NetworkManager, but still the same problem =

Snarkout · 2007-01-26 14:00:50

What does happen? Please answer all of mutlu_inek's questions. "cannot connect to the network" could mean pretty much anything - we need to narrow it down some.

tafsen · 2007-01-28 17:47:42

wrong post...

Last edited by tafsen (2007-01-28 17:57:54)

damjan · 2007-01-29 06:09:37

I have a problem with networkmanger too. I'm using an atheros card (a+b, no g) with the latest madwifi driver and 2.6.18.5 kernel.

First of all, if I manually configure everything all works. I setup the essid with iwconfig, and start dhcpcd and I'm connected. But if I start networkmanger and dhcdbd daemons, knetworkmanager will show my home wifi network. However, clicking on it, a progress bar is shown, but it stucks at 20%. Manually checking with 'iwconfig ath0' I can see that it won't associate with the AP. The essid is correct, but it just won't associate, it continously changes channels.

When I disable NM and set the essid with iwconfig it connects in a matter of seconds. The only thing I can see wrong is that in dmesg I get this: ADDRCONF(NETDEV_UP): ath0: link is not ready

mutlu_inek · 2007-01-29 06:44:50

mutlu_inek wrote:

Could you please post the relevant parts of /etc/rc.conf?
Could you post the output from ifconfig and iwconfig?

Also, could you do the following and report NetworkManager's messages?

sudo killall NetworkManager
sudo NetworkManager --no-daemon

tafsen · 2007-01-29 11:19:38

What damjan says goes for me aswell.

I'll check on the other stuff soon

tafsen · 2007-01-29 23:48:56

lo="lo 127.0.0.1"
#eth0=""
INTERFACES=(lo eth0)

DAEMONS=(syslog-ng netfs crond hal dhcdbd kdm)

Do you want me to put the output of ifconfig and iwconfig just after I've booted up?

mutlu_inek · 2007-01-30 01:47:56

tafsen, try this (I am assuming you wlan card is eth0, is that correct?):

lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo !eth0)
[...]
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
[...]
DAEMONS=(syslog-ng dbus hal !network crond netfs dhcdbd networkmanager kdm)

Don't you have a wifi module in /etc/rc.conf?

Btw. you should do the same (see first two lines) for your wired device. NetworkManager manages both.

And yes, please post the output of iwconfig and ifconfig after applying these changes (please follow the correct order for the daemons!!!), reebooting, logging in to KDE and then trying to connect to your wireless network.

Last edited by mutlu_inek (2007-01-30 01:49:26)

tafsen · 2007-01-30 12:47:31

It's random witch card that's Eth0 and Eth1, how do I fix this? And why do I get eth2 aswell? Could that be my modem?

Snarkout · 2007-01-30 15:41:38

Check out /etc/mtab for persistent network device naming. As for eth2, do you have a firewire port? See if eth1394 is being loaded.

tafsen · 2007-01-30 15:45:51

Now it's working after I rearanged my rc.conf file Thank you very much!

But is there a way that I can decide whitch of the two networkcards to start first?

Master One · 2007-01-30 17:11:24

mutlu_inek wrote:

lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo !eth0)
[...]
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
[...]
DAEMONS=(syslog-ng dbus hal !network crond netfs dhcdbd networkmanager kdm)

(please follow the correct order for the daemons!!!)

Well, I just installed knetwork-manager and followed your instructions. It seems to be working as expected, except one thing:

NetworkManager does not set my /etc/resolv.conf correctly. This is what I get after a boot:

$ cat /etc/resolv.conf
# generated by NetworkManager, do not edit!
search chaos.lan
nameserver 127.0.0.1
nameserver 192.168.1.10

The "search" line should be something else, which is given by my local dhcp-server, and I have no idea, where that "chaos" comes from.

I already searched for configs of dhcdbd, but there seems to be none.

Any hint?

damjan · 2007-01-30 23:19:20

This is from my rc.conf:

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

Do I explicitly need "!ath0 !eth0" in INTERFACES? What exactly the ! does?
BTW I've also tried to remove dhcpcd and reinstall dhclient.. but that didn't help - normally since for some reason the wifi card doesn't associate with the AP when using NetworkManager.

mutlu_inek · 2007-01-31 00:39:40

damjan wrote:

This is from my rc.conf:
lo="lo 127.0.0.1"
INTERFACES=(lo)
ROUTES=()
DAEMONS=(syslog-ng !hotplug !pcmcia @gensplash network netfs alsa dbus @hal @avahi-daemon @avahi-dnsconfd kdm @bluetooth @smartd @crond @gpm @sshd dhcdbd @networkmanager)
Do I explicitly need "!ath0 !eth0" in INTERFACES? What exactly the ! does?
BTW I've also tried to remove dhcpcd and reinstall dhclient.. but that didn't help - normally since for some reason the wifi card doesn't associate with the AP when using NetworkManager.

No wireless cards at all? Where are the entries? And where are routes and gateway? Yes, you need to put them in there.

Also, there is a reason to reordering the daemon start order. You should adapt according to what I posted above.

NetworkManager needs dhcdbd. Also, network needs to be commented out with an exclamation mark. That is what it does for other settings, too.

@ tafsen: AFAIK no. NetworkManager handles the devices automatically. If you plug the wire into a router/whatever, it should switch to that automatically. If you do not like the choice, you need to select the card from the system tray applet.

@ Master One: NetworkManager on Arch does that. Do not ask me why. You can safely ignore it.

Last edited by mutlu_inek (2007-01-31 00:42:59)

Master One · 2007-01-31 08:49:19

mutlu_inek wrote:

@ Master One: NetworkManager on Arch does that. Do not ask me why. You can safely ignore it.

I would safely ignore it, if it wouldn't mess up my lan DNS search possibility. I am running dnsmasq in my local server, which is a dhcp server + dns cache, and I am used to use the hostname only when connecting to other local machines by rdesktop or ssh, instead of using the FQDN, so I need my lan domain, which is assigned by the dhcp server, to be put in /etc/resolv.conf (so it has to be "search localnet.lan" instead of "search chaos.lan".

So is there a solution for this problem?

mutlu_inek · 2007-01-31 13:26:48

Master One, you can configure it in /etc/dhclient.conf.

Master One · 2007-01-31 16:36:55

mutlu_inek, thanks a lot, that was exectly what I was looking for, and it works now

Master One · 2007-01-31 21:53:43

BTW Can somebody tell me, why to start /etc/rc.d/networkmanager, and not /etc/rc.d/networkmanager-dispatcher, and what the difference is (what the latter is for)?

mutlu_inek · 2007-02-01 01:18:42

If running, NetworkManagerDispatcher runs the scripts in /etc/NetworkManager/dispatcher.d every time the network status changes either way between offline and online. The scripts are run alphabetically. Internally, the scripts can use two variables ($1 and $2) the values of which change in regard to the network status. Therefore, with extremely simple script syntax you can execute any commands, e.g. run network time protocol daemons.

damjan · 2007-02-01 02:23:23

mutlu_inek wrote:

No wireless cards at all? Where are the entries? And where are routes and gateway? Yes, you need to put them in there.

My wifi card is a PCMCIA card ... so until I plug it in I don't have a wifi interface, I don't have an IP address nor do I have any routes. How would I have them?!?

mutlu_inek wrote:

Also, there is a reason to reordering the daemon start order. You should adapt according to what I posted above.
NetworkManager needs dhcdbd.

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

mutlu_inek · 2007-02-01 03:43:00

damjan wrote:

My wifi card is a PCMCIA card ... so until I plug it in I don't have a wifi interface, I don't have an IP address nor do I have any routes. How would I have them?!?

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.

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

damjan wrote:

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.

Last edited by mutlu_inek (2007-02-01 03:56:46)

Arch Linux

#1 2007-01-23 20:58:56

Problems with KNetworkManager

#2 2007-01-23 23:18:00

Re: Problems with KNetworkManager

#3 2007-01-25 16:27:22

Re: Problems with KNetworkManager

#4 2007-01-25 18:29:04

Re: Problems with KNetworkManager

#5 2007-01-25 19:15:39

Re: Problems with KNetworkManager

#6 2007-01-26 14:00:50

Re: Problems with KNetworkManager

#7 2007-01-28 17:47:42

Re: Problems with KNetworkManager

#8 2007-01-29 06:09:37

Re: Problems with KNetworkManager

#9 2007-01-29 06:44:50

Re: Problems with KNetworkManager

#10 2007-01-29 11:19:38

Re: Problems with KNetworkManager

#11 2007-01-29 23:48:56

Re: Problems with KNetworkManager

#12 2007-01-30 01:47:56

Re: Problems with KNetworkManager

#13 2007-01-30 12:47:31

Re: Problems with KNetworkManager

#14 2007-01-30 15:41:38

Re: Problems with KNetworkManager

#15 2007-01-30 15:45:51

Re: Problems with KNetworkManager

#16 2007-01-30 17:11:24

Re: Problems with KNetworkManager

#17 2007-01-30 23:19:20

Re: Problems with KNetworkManager

#18 2007-01-31 00:39:40

Re: Problems with KNetworkManager

#19 2007-01-31 08:49:19

Re: Problems with KNetworkManager

#20 2007-01-31 13:26:48

Re: Problems with KNetworkManager

#21 2007-01-31 16:36:55

Re: Problems with KNetworkManager

#22 2007-01-31 21:53:43

Re: Problems with KNetworkManager

#23 2007-02-01 01:18:42

Re: Problems with KNetworkManager

#24 2007-02-01 02:23:23

Re: Problems with KNetworkManager

#25 2007-02-01 03:43:00

Re: Problems with KNetworkManager

Board footer