[opensuse] NetworkManager and dhclient
Hi, I've recently got some device which is connected through rndis to my laptop (SynCE actually). That leads to some unexpected bad behaviour of my network configuration which is usually done by NetworkManager alone. So the story is that when I connect the device, udev is creating a network interface (usually eth2 but it could change if some other devices would create another eth device) and synce brings a hal script doing the actual connection using dccm (whatever that does exactly) but also is starting dhclient on the network device which is the base of the problem for me. By default now dhclient modifies /etc/resolv.conf (even if there are no nameservers returned by the device/dhcp-server but I've already opened a bug about that behaviour). So I had to resolve that issue by modifying /etc/sysconfig/network/dhcp to not update resolv.conf automatically. But now when changing WiFi networks I found out that NetworkManager is following that and for normal network connections the nameserver is not set up correctly. So I'm wondering if other people have similar setups and had a good idea to modify the configuration w/o fiddling manually with the setup all the time? Any hints? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 16 October 2008 03:57:12 am Wolfgang Rosenauer wrote:
Hi,
I've recently got some device which is connected through rndis to my laptop (SynCE actually). That leads to some unexpected bad behaviour of my network configuration which is usually done by NetworkManager alone.
So the story is that when I connect the device, udev is creating a network interface (usually eth2 but it could change if some other devices would create another eth device) and synce brings a hal script doing the actual connection using dccm (whatever that does exactly) but also is starting dhclient on the network device which is the base of the problem for me. By default now dhclient modifies /etc/resolv.conf (even if there are no nameservers returned by the device/dhcp-server but I've already opened a bug about that behaviour). So I had to resolve that issue by modifying /etc/sysconfig/network/dhcp to not update resolv.conf automatically. But now when changing WiFi networks I found out that NetworkManager is following that and for normal network connections the nameserver is not set up correctly.
So I'm wondering if other people have similar setups and had a good idea to modify the configuration w/o fiddling manually with the setup all the time?
Any hints?
Thanks, Wolfgang
What distribution are you on? More importantly what version of NetworkManager? NetworkManager _SHOULDN'T_ use anything in /etc/sysconfig/network (which I found out because it wasn't using /etc/sysconfig/network/config for netconfig). I had a similar problem. I actually had to remove resolv.conf, do sudo service network restart, allow the correct resolv.conf to be written, then configure my static search lists. Ben -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ben Kevan schrieb:
On Thursday 16 October 2008 03:57:12 am Wolfgang Rosenauer wrote:
Hi,
I've recently got some device which is connected through rndis to my laptop (SynCE actually). That leads to some unexpected bad behaviour of my network configuration which is usually done by NetworkManager alone.
So the story is that when I connect the device, udev is creating a network interface (usually eth2 but it could change if some other devices would create another eth device) and synce brings a hal script doing the actual connection using dccm (whatever that does exactly) but also is starting dhclient on the network device which is the base of the problem for me. By default now dhclient modifies /etc/resolv.conf (even if there are no nameservers returned by the device/dhcp-server but I've already opened a bug about that behaviour). So I had to resolve that issue by modifying /etc/sysconfig/network/dhcp to not update resolv.conf automatically. But now when changing WiFi networks I found out that NetworkManager is following that and for normal network connections the nameserver is not set up correctly.
So I'm wondering if other people have similar setups and had a good idea to modify the configuration w/o fiddling manually with the setup all the time?
What distribution are you on? More importantly what version of NetworkManager?
oh, yeah, actually that is openSUSE 11.0 with the original NetworkManager (including updates).
NetworkManager _SHOULDN'T_ use anything in /etc/sysconfig/network (which I found out because it wasn't using /etc/sysconfig/network/config for netconfig).
I wouldn't have expected it to use it too but I got the following in the NetworkManager log: Oct 16 11:21:56 tvp NetworkManager: <info> DHCP returned name servers but system has disabled dynamic modification! Actually I don't know _why_ system has disabled dynamic modification. I could swear it worked yesterday with the same setting on another WiFi network. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Ben Kevan -
Wolfgang Rosenauer