[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #36403] ip4_input() and ip6_input() always pass inp to

From: Simon Goldschmidt
Subject: [lwip-devel] [bug #36403] ip4_input() and ip6_input() always pass inp to higher layers
Date: Mon, 13 Aug 2012 20:04:11 +0000
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20100101 Firefox/14.0.1

Follow-up Comment #1, bug #36403 (project lwip):

> Intuitively I think we should be passing the accepted netif

For "simple" applications, I think so, too.

> but keeping a reference to inp means we can send response packets on the
same netif that we received data

I think you can argue about that: from testing at work, I know that at least
Windows XP sends out packets to the normal route, no matter where a packet has
been received (yes, also ICMP responses).

So while the logical thing to do would be to respond on 'inp', I think that
responding on the accepting netif would be just as good: if the caller delays
its response, the accepting netif would be used anyway!


Reply to this item at:


  Nachricht gesendet von/durch Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]