Patrick McHardy <[EMAIL PROTECTED]> wrote:
>
> Thats what I meant, expressed slightly more misunderstandable :)
Now that I read it again indeed you were right all along :)
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apan
Herbert Xu wrote:
> On Thu, Jan 26, 2006 at 03:25:17PM +0100, Patrick McHardy wrote:
>
>>[IPV4]: Always set fl.proto in ip_route_newports
>>
>>ip_route_newports uses the struct flowi from the struct rtable returned
>>by ip_route_connect for the new route loo
On Thu, Jan 26, 2006 at 03:25:17PM +0100, Patrick McHardy wrote:
>
> [IPV4]: Always set fl.proto in ip_route_newports
>
> ip_route_newports uses the struct flowi from the struct rtable returned
> by ip_route_connect for the new route lookup and just replaces the port
> nu
Patrick McHardy wrote:
> [IPV4]: Always set fl.proto in ip_route_newports
>
> ip_route_newports uses the struct flowi from the struct rtable returned
> by ip_route_connect for the new route lookup and just replaces the port
> numbers if they have changed. If an IPsec policy exist
Fix xfrm lookup in ip_route_newports for a very special case.
IPv6 needs a similar fix, it doesn't reroute at all after
selecting new ports, I'll send a patch for that soon.
[IPV4]: Always set fl.proto in ip_route_newports
ip_route_newports uses the struct flowi from the struct rtabl
