Quote:
Originally Posted by s2scott
<back after a long absence...>
the one potential disadvantage of SSH is that it is over TCP, not over UDP. As the transmission (e.g. 802.11) degrades the encryption correction/recovery compounds with TCP correction/recovery. Extra CPU cycles and some packets are spent/wasted.
This is only a problem on dirty/poor sessions.
In two years of operating this way, I've "suffered" it maybe two three times. openVPN or IPSEC would have suffered it better.
/S
|
I dunno. I just set up OpenVPN for a local lumber company's sales force and we had to go to TCP because UDP wasn't stable enough. In this case I don't know how I would have implemented an ssh tunnel for them to access their desktop's without making it difficult for them. What would you guys have done in a situation like that?
-Tim