You are not logged in.

#1 2013-01-13 20:35:49

JMO
Member
From: Argentina
Registered: 2006-04-08
Posts: 98

NetworkManager, netcfg and pdnsd conflicts

I'll try to be brief and clear.
I installed Arch on a laptop which connects to a home wireless network.
I used wifi-menu to manually connect, but after enabling the netcfg@[homewireless] service, that wasn't necessary anymore.

Now, after installing Gnome Shell, I noticed no network applet, so I saw in the Arch wiki that the applet depends on NetworkManager.
The problem is that NetworkManager conflicts with netcfg in some way, because there is no way it connects when the NetworkManager service is enabled and running.

The message is always

 > WPA Authentication/Association Failed 

May it be wpa_supplicant insted of netcfg the reason of that?


Furthermore, NetworkManager seems to overwrite /etc/resolv.conf, making pdnsd useless.

I want autoconnect to the network and being able to select other networks if I'm not at home from a GUI (not wifi-menu)

Please, is there anything I'm missing?

Offline

#2 2013-01-13 20:51:44

Stebalien
Member
Registered: 2010-04-27
Posts: 1,237
Website

Re: NetworkManager, netcfg and pdnsd conflicts

You can only use one or the other (they serve the same purpose).

Both NetworkManager and netcfg manage network connections. nm-applet is a frontend for NetworkManager and thus requires NetworkManager (it will start it automatically using dbus if it isn't already running).


Steven [ web : git ]
GPG:  327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C
Do not email: honeypot@stebalien.com

Offline

#3 2013-01-13 20:54:55

dodo3773
Member
Registered: 2011-03-17
Posts: 801

Re: NetworkManager, netcfg and pdnsd conflicts

Try putting your nameserver in /etc/resolve.conf.head

$ cat /etc/resolv.conf.head 
nameserver 127.0.0.1
$ 

Make sure you specify wlan0 / eth0 in your /etc/pdnsd.conf if applicable (the "interface" variable):

cat /etc/pdnsd.conf
global {
	perm_cache=1024;
	cache_dir="/var/cache/pdnsd";
#	pid_file = /var/run/pdnsd.pid;
	run_as="pdnsd";
	server_ip = 127.0.0.1;  # Use eth0 here if you want to allow other
				# machines on your network to query pdnsd.
	status_ctl = on;
#	paranoid=on;       # This option reduces the chance of cache poisoning
	                   # but may make pdnsd less efficient, unfortunately.
	run_ipv4=on;                   
	query_method=udp_tcp;
        min_ttl=15m;       # Retain cached entries at least 15 minutes.
	max_ttl=1w;        # One week.
	timeout=3;        # Global timeout option (10 seconds).
	neg_domain_pol=on;
        neg_rrs_pol=on;
        par_queries=1;

}

# The following section is most appropriate if you have a fixed connection to
# the Internet and an ISP which provides good DNS servers.
server {
	label= "myisp";
	ip = 192.168.1.1;  # Put your ISP's DNS-server address(es) here.
#	proxy_only=on;     # Do not query any name servers beside your ISP's.
	                   # This may be necessary if you are behind some
	                   # kind of firewall and cannot receive replies
	                   # from outside name servers.
	timeout=30;         # Server timeout; this may be much shorter
			   # that the global timeout option.
	uptest=if;         # Test if the network interface is active.
	interface=eth0;    # The name of the interface to check.
	interval=10m;      # Check every 10 minutes.
	purge_cache=off;   # Keep stale cache entries in case the ISP's
			   # DNS servers go offline.
}


source {
	owner=localhost;
#	serve_aliases=on;
	file="/etc/hosts";
}

/*
include {file="/etc/pdnsd.include";}	# Read additional definitions from /etc/pdnsd.include.
*/

rr {
	name=localhost;
	reverse=on;
	a=127.0.0.1;
	owner=localhost;
	soa=localhost,root.localhost,42,86400,900,86400,86400;
}

You can edit / create /etc/dhclient.conf:

$ cat /etc/dhclient.conf
prepend domain-name-servers 127.0.0.1;
$ 

Also, you can define the nameserver in networkmanager under the edit connection tab for wireless and there is a networkmanager hook for pdnsd in the aur if that helps:
https://aur.archlinux.org/packages/netw … her-pdnsd/

Other than that do the obvious stuff like add pdnsd to your runlevel in systemd etc.. Hope any of that helps.

Edit: Don't forget to do all the permissions stuff too on the pdnsd wiki page.

Last edited by dodo3773 (2013-01-13 20:56:05)

Offline

#4 2013-01-13 21:36:59

JMO
Member
From: Argentina
Registered: 2006-04-08
Posts: 98

Re: NetworkManager, netcfg and pdnsd conflicts

Thanks both of you. I've removed netcfg from my system, since even after disabling netcfg service there was left a netcfg@ service which I couldn't disable. I've created a resolv.conf.head file too, pointing to localhost, and NetworkManager didn't touch it smile

Now everything works as I wanted to ^^
Thanks again!

Offline

Board footer

Powered by FluxBB