Erik Mundall wrote:
In practice, here is what happens: eth0 -- receives sporadic traffic, mostly due to incoming http requests eth1 -- averages a few Kbps in/out eth4 -- averages a Mbps or more, outgoing; incoming fluctuates widely It seems that in spite of the 'balance', the buck always stops at the last route in the list.
You are running an ancient version of Ubuntu that probably has a kernel built with CONFIG_IP_ROUTE_MULTIPATH_CACHED=y. This was common in older distribution kernels.
I am confused, from what I understand, on one point of theory--namelythis:1) The load is supposed to be balanced on a per-connection basis such that each client computer will have its traffic directed through a single interface.
No. Each CONNECTION will have its traffic directed through a single interface. And the traffic is not guaranteed to be balanced at all -- only that connections will be assigned to interfaces in round-robin fashion with weights applied.
2) The traffic can be directed to a particular interface based upon its type (e.g. icmp, http, p2p)
It can be directed to a particular interface by information in the IP and protocol headers. It cannot be directed by heuristics like ipp2p.
It seems that one could not have it both ways. ??
Of course not. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
