3 ms·
I feel afraid to ask, but considering HTTP is transmitted over TCP, why would you tunnel TCP back again? Actually, nvm I don't need to know, you can keep your
by TZubiri 3y ago
I feel afraid to ask, but considering HTTP is transmitted over TCP, why would you tunnel TCP back again?
Actually, nvm I don't need to know, you can keep your cursed ourobouros protocol to yourself.
- mordechai9000 3y agoYes, it can cause a problem called TCP Meltdown where the inner TCP and the outer TCP both try resending data and the connection degrades significantly. I think you can work around it, somewhat, by tweaking the TCP timing. But generally it's best to use UDP for the outer protocol when you're tunneling TCP
- Thorrez 3y agoI don't think that's the case here. I think it's just tunneling the data, not the full TCP packets.
- mordechai9000 3y agoI was not aware, thanks.
- jpillora 3y agoCorrect, it’s equivalent to ssh tunneling except there’s some HTTP/websocket wrappers around it
- Thorrez 3y agoI don't think it's tunneling the full TCP packets. I think it's extracting the data stream from the incoming TCP stream, tunneling that data, and creating a new TCP stream to the destination on the other end of the tunnel. So basically the same as ssh -L or ssh -R .
- globular-toast 3y agoIt's for getting arbitrary traffic out of corporate firewalls by disguising it as regular HTTP traffic.
- remram 3y agoAfraid to ask but not afraid to insult?