Hi all,
Regarding this problem , what i did was i did these steps to delibrately make the conflict with an NT machine on the same network:-
#ifdown eth0 #ifconfig eth0 10.3.2.33 netmask 255.255.0.0 ( 10.3.2.33 is the IP of the NT machine ) This worked fine , it didn;t give me any error stating that 10.3.2.33 is already allocated, though it gave error to NT machine (IP for it was taken from DHCP ) saying IP conflict.
So i feel that if we say that IP is static then the eth0 of linux machine should come up without any problem , whether conflict or no conflict....
but then donno how to solve kavita's problem.
--Tapesh
--- Philip S Tellis philip@konark.ncst.ernet.in wrote:
On Thu, 30 Jan 2003, Tapeshwar Nath wrote:
if i have configured my network as static , then
while booting does
Linux search for dhcp server... and if not, then
that interface should
come up properly without any issues....
assume eth0 has static IP 192.168.0.10
assume rest of network is on DHCP with dhcp pool 192.168.0.*
it is very likely that while linux:eth0 is down, some other machine comes up and gets IP address 192.168.0.10.
After that, if eth0 comes up, it gets an IP conflict.
It seems that this is not the case here since the dhcp pool does not include the linux machine's IP address.
Philip
-- The meta-Turing test counts a thing as intelligent if it seeks to devise and apply Turing tests to objects of its own creation. -- Lew Mammel, Jr.
-- _______________________________________________
__________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com