[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #38803] Source address in broadcast ping reply
From: |
Jens Nielsen |
Subject: |
[lwip-devel] [bug #38803] Source address in broadcast ping reply |
Date: |
Sun, 27 Oct 2013 12:12:57 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Firefox/24.0 |
Follow-up Comment #5, bug #38803 (project lwip):
On the other hand, I did some more reading in RFC 1122. This is from 3.2.1.3,
which defines the "specific-destination address" mentioned in the section I
quoted in my original post.
"The specific-destination address is defined to be the destination address in
the IP header unless the header contains a broadcast or multicast address, in
which case the specific-destination is an IP address assigned to the physical
interface on which the datagram arrived."
The behaviour seems odd, but the requirements are clear as far as I can tell..
In the case of broadcast ping we should use the address from "inp" regardless
of which interface the destination address matched. Direct ping should still
use the destination address from the request.
The ip_addr_isbroadcast() check is still done on the wrong interface though.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?38803>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/