News for hackers. Stuff that matters.
Re:Why TCP Over TCP Is A Bad Idea by ivank on Monday April 04, 2011 @08:31PM (#2409184)
If someone really wanted to do TCP over TCP (say, because UDP packets are blocked), couldn't they build something just like TCP but without retransmits? Does this already exist in some pile of code somewhere?
Re:Why TCP Over TCP Is A Bad Idea by xtacy on Monday April 04, 2011 @08:37PM (#2409201)
TCP does congestion control + reliable delivery. Retransmits help reliable delivery. So, TCP without retransmits is basically a datagram protocol that does only congestion control. DCCP does precisely this and its congestion control is TCP friendly. It's available in Linux afaik.

    http://en.wikipedia.org/wiki/Datagram_Congestion_Control_Protocol

    http://read.cs.ucla.edu/dccp/
Re:Why TCP Over TCP Is A Bad Idea by bostonvaulter2 on Tuesday April 05, 2011 @12:20AM (#2409695)
Re:Why TCP Over TCP Is A Bad Idea by dfox on Monday April 04, 2011 @09:50PM (#2409347)
Yes you certainly can, see sshuttle (on the frontpage just now) for example. But you will not get transparent end-to-end connection (which hardly matters). Idea is to reconstruct something similar to kernel socket calls from actual TCP packets and send those calls to the other side (with retransmission handled only by outer reliable transport).

It's similar idea as "User"/"NAT-only"/"Outgoing only" networking option offered by various virtualization systems and emulators. Probably original historical implementation of this hack is slirp, which is unix tool that works as NATing SLIP endpoint without needing root access (or anything OS-specific), that was often used in early '90s to get "full" IP connectivity from UNIX account on internet-connected modem-accessible system (usually without official approval to do so).

Re:Why TCP Over TCP Is A Bad Idea by ay on Tuesday April 05, 2011 @04:48PM (#2412647)
See my comment above about the TCP minions.