DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is it stacking resolv.conf's? If so, the running resolv.conf should contain the details of (the last program) that has stacked it.
Alternatively, are you running dhcpd/avahi or something?
Quote:
no overlapping between its DHCP range and your static IP?
I'm guessing, but I don't think that would do this; it would go wrong if/when two devices got the same ip, but I don't see how the router on its own can change your computer's IP (unless you are running some program which expects to pick up an ip from dhcp, of course).
@JosipBroz the ip addresses are not overlapping. The router is giving out addresses starting at 10.0.0.11 and my static ip is 10.0.0.10 (Which gets changed by dhcp all the time to 10.0.0.11)
Its interesting if I stop dhcdb which I understand is the client side DHCP demon:
Quote:
/etc/init.d/dhcdbd stop
When I reboot the router eth0 doesnt have ANY ip!
@salasi
I think that I have left all the networking configuration standard. I am not sure what you mean by stacking resolv.con but here are the contents of my resolv.conf
Quote:
debby:/home/adam# cat /etc/resolv.conf
### BEGIN INFO
#
# Modified_by: NetworkManager
# Process: /usr/bin/NetworkManager
# Process_id: 3696
#
### END INFO
@salasi
I think that I have left all the networking configuration standard. I am not sure what you mean by stacking resolv.con but here are the contents of my resolv.conf
Quote:
debby:/home/adam# cat /etc/resolv.conf
### BEGIN INFO
#
# Modified_by: NetworkManager
# Process: /usr/bin/NetworkManager
# Process_id: 3696
#
### END INFO
nameserver 10.0.0.1
this is exactly what I mean: whatever you set up as resolv.conf (prior to NM running), NetworkManager has been at it, via the OS call to do exactly this, pushed the pre-network-manager version onto the stack and run its own version for the duration. if you look at mine under similar circumstances (running kde and NM active):
Quote:
### BEGIN INFO
#
# Modified_by: NetworkManager
# Process: /usr/bin/NetworkManager
# Process_id: 2900
#
### END INFO
nameserver 192.168.1.34
nameserver 192.168.1.1
but is otherwise similar. However, if you open NM, you'll see it also takes control of IP, Netmask, broadcast address (err, and MAC address).
I think if you you want to run NM, you can set the static address in there and it'll work (until the next time you have a non-clean shutdown, and then you might have to re-write resolv.conf, so you might need want to take a backup copy when NM isn't running).
Thanks for your help, it seems to be behaving its self now. I went into the network manager and even though it was already set to static IP I configured it again and applied the settings.
I have restarted my router and still have my static ip. I guess it could be some sort of a bug with the NM if you manually edit the settings and put a static IP.
This is going back some years, but back in Sarge, if you allowed DHCP to set an address during install, then tried to configure a static afterwards, you would see exactly the problem you described. The installation would set up dhcp-client which would run on reboot even though you had set static. Since dhcp would run at boot, you'd lose your static.
The solution was to uninstall what was then dhcp-client, and now appears to be called dhclient3 on unstable. If you need the dhclient, then you need to edit your startup and make sure nothing uses dhclient.
@tredegar thanks for the info although it seems to be behaving its self since I re-configured eth0 with the KDE NM.
@JimBass I did read something about what your describing but when I saw the dates (at least 2 years ago) I figured this issue must have been fixed. Anyway its keeping the static now
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.