<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>Yeah, we're gonna have to set up an alarm for when we get these so we can go back and clear them. I'd rather have a ip address conflict logged than to have an actual ip address conflict occur.<br><br><span><br><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Robert Kulagowski" <rkulagow@gmail.com><br><b>To: </b>"cisco-voip (cisco-voip@puck.nether.net)" <cisco-voip@puck.nether.net><br><b>Sent: </b>Tuesday, May 10, 2011 11:23:59 AM<br><b>Subject: </b>Re: [cisco-voip] suggested/best practices for DHCP settings on routers<br><br>On Mon, May 9, 2011 at 3:16 PM, Ryan Ratliff <rratliff@cisco.com> wrote:<br>> An address conflict occurs when two hosts use the same IP address. During<br>> address assignment, DHCP checks for conflicts using ping and gratuitous<br>> Address Resolution Protocol (ARP). If a conflict is detected, the address is<br>> removed from the pool. The address will not be assigned until the<br>> administrator resolves the conflict.<br>><br>> Yes it does.<br>> -Ryan<br><br>We ended up adding:<br><br>no ip dhcp conflict logging<br><br>to our router configuration so that we wouldn't end up with _all_<br>addresses unassignable.<br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div></body></html>