On Friday 5 January 2007 16:53, Mick wrote: > > More about that here: > > > > "Why TCP over TCP is a Bad Idea" > > http://sites.inka.de/sites/bigred/devel/tcp-tcp.html > > Hmm, that explains why running VCN through ssh gets a bit ropy at > times?
Do you mean VNC? > So, is port forwarding for browsing and emails through ssh a > bad idea then? No, because with ssh port forwarding you just forward the data coming from/going to the application (eg, mailreader) without stacking additional protocols (as in, for example, ppp or ip over ssh), for which you need some way of forwarding IP-or-lower-level data between interfaces (for example, using tun/tap). Some programs (like openvpn) overcome the issue by using tcp-over-udp by default. And, anyway, tcp over tcp is a bad idea, but that does not necessarily mean that it won't work. It will most likely fail when the transport link is slow or error prone. -- [email protected] mailing list
