Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?

[Philip Homburg <[e-mail]>]

In your letter dated Wed, 16 Mar 2011 10:47:45 +0100 you wrote:
>On 2011-03-16, at 10:08 , Mohacsi Janos wrote:
>
>> Yes. DAD can fail, and you system log you will see.
>
>How will this help a network admin, when the system log says, that a server th
>at is supposed to have a certain fixed IP or a DHCP client, that is also suppo
>sed to have a certain fixed IP (however, one assigned by DHCP) cannot obtain t
>his IP, because some other host with privacy extension enabled is currently us
>ing this IP by plain coincident? How can you resolve that problem? Running aro
>und the building and asking all people with non-DHCP devices to please tempora
>rily disconnect of the network? 

You look up the MAC address for that IPv6 address and then block the MAC
address on your switches. Problem solved.

You can slightly better than that. For wired connections, you can look up
to which port the offending system is connected, and with an up-to-date cable
plan you can also find it.

For wireless, you want EAP anyhow, so you can just look up which user account
was used and then contact that user.