3 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Mario Schmidt commented  ·  June 28, 2010 1:05 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Hello Hagen, as suggested, it should be detected that there is an IP address conflict. Nothing more or less.

  This could be displayed at several places like WebAdmin Dashboard (if login is still possible because the conflict is at another interface) or console login for example.

• Mario Schmidt commented  ·  May 18, 2009 2:04 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Currently, the ASG just does not detect IP address conflicts when an ASG-IP is used somewhere else in the LAN - it will just not work and you won' t get a notification or LOG entry.

  Debugging IP address conflicts in Linux is somewhat awful because you only notice your communication does not work properly, but instead of a popup/message (like in Windows e.g.) you get nothing.

• Hagen von Eitzen commented  ·  May 12, 2009 7:52 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Actually, the gateway to the internet is somewhat late a place to detect IP address conflicts.
  What should be detected?
  IP packets with sender IP and MAC not matching a current ARP entry? This fails for non-local nets and relies on a good notion of perfect ARP enty survival time ...