From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Babic Date: Wed, 25 Jan 2012 11:27:44 +0100 Subject: [U-Boot] [PATCH 00/28] Add link-local addressing support In-Reply-To: <1327020811-1538-1-git-send-email-joe.hershberger@ni.com> References: <1327020811-1538-1-git-send-email-joe.hershberger@ni.com> Message-ID: <4F1FD920.3060400@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 20/01/2012 01:53, Joe Hershberger wrote: > Link-local support allows the bootloader to get a usable network address > regardless of network environment. Given that bootloaders may not always > have access to a DHCP server, this functionality makes accessing it in > those environments easier. It is also referred to as zero-configuration IP. > Hi Joe, I have a basic question about your patchset. RFC3927 requires that addresses are continuosly checked to avoid conflicts - this is a strict requirement. However, it is clear we cannot comply with this requirement. The protocol runs once and there is not a background process to check for conflicts. I can imagine we can get conflicts, when several targets are running at the same time in u_boot and they are attached to a network where local-link addressing is active. Then we can have two or more system using the same ip address, making the network unreliable. Which are the limitations of this implementation ? They should also described in your patchset, maybe with a README file. Is is thought to connect the target directly to a PC ? Best regards, Stefano Babic -- ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de =====================================================================