| 1 |
On Friday 5 January 2007 16:53, Mick wrote: |
| 2 |
|
| 3 |
> > More about that here: |
| 4 |
> > |
| 5 |
> > "Why TCP over TCP is a Bad Idea" |
| 6 |
> > http://sites.inka.de/sites/bigred/devel/tcp-tcp.html |
| 7 |
> |
| 8 |
> Hmm, that explains why running VCN through ssh gets a bit ropy at |
| 9 |
> times? |
| 10 |
|
| 11 |
Do you mean VNC? |
| 12 |
|
| 13 |
> So, is port forwarding for browsing and emails through ssh a |
| 14 |
> bad idea then? |
| 15 |
|
| 16 |
No, because with ssh port forwarding you just forward the data coming |
| 17 |
from/going to the application (eg, mailreader) without stacking |
| 18 |
additional protocols (as in, for example, ppp or ip over ssh), for which |
| 19 |
you need some way of forwarding IP-or-lower-level data between |
| 20 |
interfaces (for example, using tun/tap). |
| 21 |
Some programs (like openvpn) overcome the issue by using tcp-over-udp by |
| 22 |
default. |
| 23 |
And, anyway, tcp over tcp is a bad idea, but that does not necessarily |
| 24 |
mean that it won't work. It will most likely fail when the transport |
| 25 |
link is slow or error prone. |
| 26 |
-- |
| 27 |
gentoo-user@g.o mailing list |
Archives