So, I decided to give curvetun a try, since tcp-in-tcp has been hell... 1/N
libnacl has a "creative" build system that's a giant shell script with hard-coded LD_LIBRARY_PATHS for ancient proprietary unices. WTF. 3/N
-
-
Eventually I found libsodium, which is a portable fork of nacl that's actually possible to build, and convinced curvetun to link to it. 4/N
-
But curvetun had some bogus stuff using stdout/stderr as lvalues to overwrite them I had to rip out.... 5/N
-
And after all that, it doesn't seem to work. TCP mode rapidly connects and drops, with no output indicating why. UDP nothing. 6/N
-
Guessing it's weird glibcisms or something going on. Anyone used curvetun linked to musl? 7/N
-
On the bright side, managed to make tcp-in-tcp less hellish using netem. 8/N
-
tc qdisc add dev wlan0 root netem delay 5ms # 9/N
-
Apparently most/all of the wifi collisions stemmed from receipt of a pkt on one wlan interface immediately generating pkts on another? 10/N
End of conversation
New conversation -
-
-
He got bored with messing users up with non-licensing, and went for atrociously-bad build systems instead.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
DJB build process foils another!
-
Seriously, how much time did he spend writing that awful script, just to make users' lives hell?
-
Lots of time but spread out over decades. That's an evolution of the qmail build scripts.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.