Prev: switching to console and zapping
Next: Unable to use wifi
From: Zhang Weiwu on 25 Jun 2010 23:20
Hello. In case IP address conflict is detected, different system behave
differently. I recall in my campus days FreeBSD would ignore it as if IP
address conflict never happened, while Windows system would disable
eithernet interface for a while and try it later. Having used Debian for
a few years I wonder if this behavior is configurable in Debian? And the
reconfigurability is related to networkmanager (which doesn't exist in
my campus days) or not?

Thanks.

Best.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C256A92.2040904(a)realss.com
From: Camaleón on 26 Jun 2010 11:20
On Sat, 26 Jun 2010 10:48:50 +0800, Zhang Weiwu wrote:

> Hello. In case IP address conflict is detected, different system behave
> differently. I recall in my campus days FreeBSD would ignore it as if IP
> address conflict never happened, while Windows system would disable
> eithernet interface for a while and try it later. Having used Debian for
> a few years I wonder if this behavior is configurable in Debian? And the
> reconfigurability is related to networkmanager (which doesn't exist in
> my campus days) or not?

I am unaware of any specific configuration to prevent this, at least when
using no DHCP server and you manually define the IP address of the network
devices.

It also should be nice that "network manager" could handle this.

Anyway, there are some tips for discovering duplicated IP addresses:

***
How to: Detect Duplicate IP Address With arping command under Linux
http://www.cyberciti.biz/faq/linux-duplicate-address-detection-with-arping/
***

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/pan.2010.06.26.15.16.30(a)gmail.com
From: Zhang Weiwu on 27 Jun 2010 20:30
On 2010年06月26日 23:16, Camaleón wrote:
> I am unaware of any specific configuration to prevent this, at least when
> using no DHCP server and you manually define the IP address of the network
> devices.
>
Just for your information I heard a solution. IPwatchD is a userland
tool (in debian) that can configure a script to run when IP address
conflict detected. That should server the need. I need to try it later.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C27ECCB.3030407(a)realss.com
 | 
Pages: 1
Prev: switching to console and zapping
Next: Unable to use wifi