On 6/26/2007 9:03 PM, Mohan Sundaram wrote:
The caching would be per destination IP - so it is likely all clients will use the same route and thus interface.
This could be a problem. I was taking the caching to be remembering which route was chosen and believing it to be associated with a specific source IP address. I can see this being a very large issue when trying to do load balancing.
In light of this information, I think that better could be done in Netfilter. However if there ever was a way to have route selection per source IP in the kernel, I would be more interested in that.
I wonder if route selection caching would be different in different routing tables. In other words use a different routing table for a different (set of) clients. Thus one cached routing decision per routing table which could differ per routing table.
Grant. . . . _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
