|To:||"David S. Miller" <davem@xxxxxxxxxxxxx>|
|Subject:||Re: [PATCH 2/2] ipv4 routing: multipath with cache support, 2.6.10-rc3|
|From:||Einar Lück <lkml@xxxxxxxxxxxxxx>|
|Date:||Wed, 09 Feb 2005 21:42:39 +0100|
|References:||<41C6B54F.2020604@xxxxxxxxxxxxxx> <20050202172333.4d0ad5f0.davem@xxxxxxxxxxxxx> <420A1011.1030602@xxxxxxxxxxxxxx> <20050209120157.18dc75c1.davem@xxxxxxxxxxxxx> <420A715D.7050106@xxxxxxxxxxxxxx> <20050209123004.2d65e1cf.davem@xxxxxxxxxxxxx>|
|User-agent:||Mozilla Thunderbird 1.0 (Windows/20041206)|
David S. Miller wrote:
This was brought up before. It's the case where the system is acting as a router, you have to consider that case and not just the one where the local system is where the connections are originating from. Your trick only works because of how routes are cached per-socket. Once you get into the realm of traffic going through the machine as a router, the trick stops to work.
We considered the routing case: in the routing case ip_route_input is called. In this case we just select the first route in the cache which is always the same (we ensure that). Consequently, the routing behaviour is not changed in this case and remains in the way you like it.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH 2/2] ipv4 routing: multipath with cache support, 2.6.10-rc3, David S. Miller|
|Next by Date:||Re: PROBLEM: 2.6.11-rc2 hangs on bridge shutdown (br0), Andre Tomt|
|Previous by Thread:||Re: [PATCH 2/2] ipv4 routing: multipath with cache support, 2.6.10-rc3, David S. Miller|
|Next by Thread:||Re: [PATCH 2/2] ipv4 routing: multipath with cache support, 2.6.10-rc3, David S. Miller|
|Indexes:||[Date] [Thread] [Top] [All Lists]|