This is the scenario: Inet Inet | | A(gw) B(gw) \ / \___ ___/ \/ Other nodes | | C A, B and the "other nodes" form an ad-hoc network and use the 10.x.x.x private class. A and B are nodes sharing their Inet connection. The node C has to create an IPIP tunnel to one of the two gw to be sure that all the packets routed to the Internet use the same gw. The node C might decide to use both A and B to implement a simple load sharing, in this way, the traffic load will be split between the two gateway: - it creates an IPIP tunnel to A and B, - adds in the routing table the default route using the tunnels which lead to A and B as multipath gateways. The question is: will an established connection use the same gw for all its future packets? If the answer is yes, then it's all fine, otherwise how is it possible to implement it? Keep in mind that since this is a setup done automatically by a routing software, it isn't possible to depend on a unofficial patch, the users wouldn't like it ;0 Note also that this is not the same setup of the "multiple internet connection" HOWTOs, in fact, in that situation there is a single router which NATs the connections. The multipath code creates new cached routes. Since after connect the socket is "connected", i.e. saddr and daddr are known and they are always provided when resolving route So, the connected socket should not experience any outage when the route is resolved after cache entry expiration assuming the routing rules do not change. (That is snip of the Julian Anastasov's reply in a lartc thread: http://mailman.ds9a.nl/pipermail/lartc/2002q2/003780.html) Does it mean that it should work? Wouldn't be useful a multipath algorithm which selects nexthops considering the devices' bandwidth usage (f.e. by monitoring /proc/net/dev)? Thanks in advance PS: for more information about the routing software see: http://netsukuku.freaknet.org and http://lab.dyne.org/Ntk_IGS -- :wq! "I don't know nothing" The One Who reached the Thinking Matter '.' [ Alpt --- Freaknet Medialab ] [ GPG Key ID 441CF0EE ] [ Key fingerprint = 8B02 26E8 831A 7BB9 81A9 5277 BFF8 037E 441C F0EE ] - : send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html