|
From: Mario Spinthiras on 20 Jun 2008 14:40 Greetings, I recently setup a server which I had originally assigned a DHCP address from the interfaces file using the line "iface eth0 inet dhcp" .. After I had put the machine on the rack I simply changed the addressing to static and restarted the networking. This all went well for a while. Today the machine had lost its power feed and as a result the machine was offline for a while. When the machine came back up (power) , it got an address by DHCP though the settings in the interfaces file said static with all relevant addressing. This is not something new to me , I have dealt with Linux machines for almost 10 years now. I just cannot seem to understand why it did this. Checking the interfaces file again , the only thing I had seemed to forget is the broadcast 192.168.100.0 directive which denotes the network number and nothing more. I have played with the way ifup parses this file and cannot seem to derive a bug of somekind. Here is a thought though. I believe the previously retrieved address from DHCP is cached somewhere (though Ive searched high and low for it) and when "something" triggers the parsing error , it goes back to that DHCP previously assigned address. Can I have your thoughts on this? Its extremely strange behavior and I cannot understand how a broadcast directive that was missing would cause this problem. Note that the addressing that is static and the DHCP assigned address are both in the same subnet. Is there a force feature of somekind that tells it to go DHCP in a certain "case" ? Possible ifupdown bug? -- Warm Regards, Mario A. Spinthiras Blog: http://www.spinthiras.net Mail: mspinthiras(a)gmail.com Skype: smario125 -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: x_debian-user_x on 21 Jun 2008 02:10 On Fri, Jun 20, 2008 at 09:35:39PM +0300, Mario Spinthiras wrote: > Possible ifupdown bug? Yes it doesn't sound right to me either. If you do not receive any further replies then I suggest to file a bug report against ifupdown. Otherwise post your entire /etc/network/interfaces verbatim in case someone can spot an error. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Andrei Popescu on 21 Jun 2008 17:30 On Fri, Jun 20, 2008 at 09:35:39PM +0300, Mario Spinthiras wrote: [...] > Possible ifupdown bug? Do you have network-manager installed? Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein)
|
Pages: 1 Prev: Balsa's "Gnome editor?" Next: How do I find my local sub-net, to broadcast NTP |