|
From: | Bill Auerbach |
Subject: | [lwip-devel] [bug #31828] lwIP AUTOIP addresses accessed from a host with a non-AUTOIP |
Date: | Wed, 08 Dec 2010 20:53:04 +0000 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 ( .NET CLR 3.5.30729; .NET4.0E) |
URL: <http://savannah.nongnu.org/bugs/?31828> Summary: lwIP AUTOIP addresses accessed from a host with a non-AUTOIP Project: lwIP - A Lightweight TCP/IP stack Submitted by: billauerbach Submitted on: Wed 08 Dec 2010 03:53:03 PM EST Category: ARP Severity: 3 - Normal Item Group: Faulty Behaviour Status: None Privacy: Public Assigned to: None Open/Closed: Open Discussion Lock: Any Planned Release: lwIP version: CVS Head _______________________________________________________ Details: One cannot talk to an lwIP device with an AUTOIP address from a host that does not have an AUTOIP address. Test case: LWIP_DHCP and LWIP_AUTOIP are both 0. Set the device to have an AUTOIP (link-local) address. You cannot ping or connect to the device from an interface that does not have an AUTOIP address. If the interface has an AUTOIP address, it does work OK. There are RFC cases covering assigning AUTOIP addresses and for a device having an AUTOIP address. I'm pretty confident that the first part (assigning) is right. I thought maybe code is removed with LWIP_AUTOIP = 0 to cause this problem, but setting LWIP_AUTOIP to 1 does not change this behavior. _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?31828> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |