Err, not really. The underlying TCP protocol takes care of re-transmissions and stuff, so your TCP session "inside" the SSH tunnel sees a lossless connection.
The overhead is due to the double-encapsulation and headers. If you're going to do TCP over UDP tunnels there's a good name for that: IPSEC. Haven't tried IPSEC over 3G but it works over Smart Bro. Doing things like SSH tunnelling or GRE are non-standard technologies at best. On 6/12/07, Gideon Guillen <[EMAIL PROTECTED]> wrote: .. > The reason why running tunnelling protocols over SSH can be slow is > that running tunnelling TCP over another TCP implementation is that > over time, the error correction or retransmission for each TCP layer > (for handling timeouts or if the packet was corrupted) would conflict > with each other, and might cause retransmission multiple times instead > of just one. > > The better way to do it is to tunnel your TCP protocol on a UDP > protocol. Something like OpenVPN over UDP is preferred over OpenVPN > over TCP or SSH tunnelling. _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
