[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
[lwip-devel] [bug #36403] ip4_input() and ip6_input() always pass inp to higher layers
Fri, 13 Feb 2015 19:43:07 +0000
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.111 Safari/537.36
Follow-up Comment #4, bug #36403 (project lwip):
Well, my point was there *is* no input netif in ip_route(): the input netif is
only available during the recv callback. Given that, passing up inp leads to
different results when sending to inp from the recv callback than sending the
same packet via routing (as routing should select the 'accept' netif).
Given that, your routing problems should not depend on the change I made
yesterday, do they?
What's your IP setup in this situation anyway? Would it make sense to use
source-address-based-routing in this case?
Reply to this item at:
Nachricht gesendet von/durch Savannah