kf wrote:
> On Fri, 8 Sep 2000 [EMAIL PROTECTED] wrote:
>
> =
> =
> = --------------------------------------------------------------------------------
> = On Wed, 6 Sep 2000 [EMAIL PROTECTED] wrote:
> =
> = =it seems that RH 6.2 Linux doesn't complaint if there are 2 machines of
> = the
> = =same IP addess sitting in the same segment.
> = =why is that so? (i have checked the /var/log/messages)
> = =
> = =I have installed Solaris and Windows before with the same scenerio but in
> = =both cases I will know of any conflicting IP addresses during installation
> =
> = Having the same IP address for two different machines in some, albeit
> = obscure, situations. So, yes, you can do this. But normally it isn't
> = done.
> =
> = hth,
> = kf
> = --------------------------------------------------------------------------------
> = yes, but i don't want to do this...waht i want is that linux has the
> = capability to detect conflict IP.
> =
>
> Get on each machine and run "ifconfig". This will provide the name of
> each interface on that machine and information about it, part of which is
> its IP address. Do this on each machine and, using this information,
> create a database about your network. (If you have a large network, you
> should have this anyway.) You'd think that there would be a script
> already written which would do this, but I've never encountered one.
>
> If ping is available, you could get some of this information easier by
> doing a ping -c 1 [subnet-broadcast-address] and then analyse the
> information you get back.
I think what he is refering to is the windows "feature" that will at least warn the
user (I forget exactly what happens ) when it brings up an interface with an ip
address that is already in use. I too wish that this could be checked before the
interface is brought up so that someone couldn't bring up an box with the same IP
address of say, my intranet server and screw up everything. I got bit by this
setting up a test box about six months ago and is what prompted me to set up dhcp.
We are a small envrionment and this is not that big of a deal but in a large
hetrogenous environment I can see how this would be a real pain.
perhaps you are right about the broadcast ping and then grep for multiple returns of
the ip address of the box running the command. I am just supprised that this is not
an isuue on networks and ben addressed at the kernel level. especially with every IT
dept in the country playing with linux and not everyine having a clue.
Bret
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list