Wily raconteur

Isn't SSH everyone's favorite quick and dirty VPN? Get Putty, setup browser to use the SSH connection as a proxy and you're good to go. Not long after DARPA released ESP, IPsec emerged as the de facto standard for creating encrypted tunnels to move data over the Internet between two geographically separate networks. It works at Layer 3, it's application agnostic and built right in to TCP with tighter integration in IPv6. It's adoption outside of corporate endpoints remains less than stellar, and for good reason. A typical conversation between a young developer Alice, wanting to secure her fledgling application's communication with her Network Engineer mate Bob, who works at a multi-homed Tier 4 datacenter in VRF hell. Alice : Hey mate, I'm deploying my application via Docker and would like to use a VPN to communicate between my Docker hosts. My M2M devices use 6LoWPAN and IPsec seems perfect. Bob :  Uhh, 6LoWPAN? Not my area of expertise but ...

#!/bin/sh # # Simple script to start TF2 server # Sat Dec  8 17:43:19 IST 2012 # # NOTE: This expects the TF2 server to be run as user "tf2server" # # Ensure this script is run as tf2server (EUID 500 in our case) only. if [[ $EUID -ne 500 ]]; then    echo "This script can ONLY be run as user: tf2server"    echo `/bin/grep tf2server /etc/passwd`    echo "Perhaps you're root? Your EUID seems to be $EUID"    exit 1 fi # User specified game vars MAP="jump_4starters_a9" MAXPLAYERS="24" GAMEIP="192.168.1.113" GAMEPORT="27015" GAMEPID="/home/tf2server/pids/tf2d.pid" GAMEDIR="/home/tf2server/hlds/gameserver/orangebox" GAMEBIN="./srcds_run" STEAMBIN="/home/tf2server/hlds/steam" GAMEOPTS="-game tf -autoupdate -steambin $STEAMBIN -maxplayers $MAXPLAYERS +map $MAP +ip $GAMEIP -port $GAMEPORT -pidfile $GAMEPID" # Nothing beyond this needs editing...