The prevention of hijacking ip (DHCP and Ubuntu Server)


Warning: count(): Parameter must be an array or an object that implements Countable in /home/styllloz/public_html/qa-theme/donut-theme/qa-donut-layer.php on line 274
0 like 0 dislike
10 views
The question is simple, but I unfortunately do not Linuxoid.

After restarting the server grabs someone else's ip address (10.1.8.44)

If you write:
sudo /etc/init.d/networking restart
then everything falls into place: the server picks a free ip

in /etc/network/interfaces is just this:

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp


Where what to add to the server immediately took free ip address?
by | 10 views

7 Answers

0 like 0 dislike
On the client, the files /var/lib/dhcp3/dhclient.eth?.leases that? There is just stores the address, which is "given before" and which may be requested from the server again (there is a possibility in the DHCP Protocol). Maybe Ubuntu is trying to do and does it wrong or the server is not standard and not understand it.
\r
If anything, these files can be safely deleted.
by
0 like 0 dislike
It's a strange problem and I'm not quite sure what to blame ubuntu.
Alternatively, list the permanent address of the machine to DHCP.
by
0 like 0 dislike
Read section 3.2 of RFC 2131 about how DHCP works. There, in the end, the client is required before final mounting configuration to verify that there are no conflicts (send ARP request). If he puts himself in the end, the conflict address — then blame the customer.
\r
Ubuntu uses dhclient. It may be worthwhile to read about him more. If you want to try alternatives — it is udhcpc, dhcpcd; how to put them into Ubuntu — you have no idea.
by
0 like 0 dislike
where do You run dhcp?
by
0 like 0 dislike
Thank you!
by
0 like 0 dislike
And what name will be? Medindex? Damgage?
by
0 like 0 dislike
I think I figured out who is to blame:
This conflicted address (10.1.8.44) now has a large format plotter that most of the time asleep (he can sleep, given the weekend 3-4 days), waking up, he is not likely to bother to ask the dhcp server, and gave his address to someone... and he fine print can not and others me to believe... But I'm over it (and a couple of his colleagues) still watch, we have a network of regularly this happens, networkers dismiss ("it happens, just disable and enable the connection"), I think we require statics for all network printers, so the same questionable components which are "turned off" in hibernation.
by

Related questions

0 like 0 dislike
3 answers
0 like 0 dislike
5 answers
0 like 0 dislike
2 answers
0 like 0 dislike
1 answer
110,608 questions
257,186 answers
0 comments
28,000 users