'A discussion with Vint Cerf, Van Jacobson, Nick Weaver, and Jim Gettys' -- the big guns! Great discussion (via Tony Finch)

'Tcprstat is a free, open-source TCP analysis tool that watches network traffic and computes the delay between requests and responses. From this it derives response-time statistics and prints them out.' Computes percentiles, too

'When amount of sockets is enough large, netstat or even plain cat /proc/net/tcp/ cause nothing but pains and curses. In linux-2.4 the desease [sic] became worse: even if amount of sockets is small reading /proc/net/tcp/ is slow enough. This utility presents a new approach, which is supposed to scale well.' via scanlan

hey, I know a few of those! 'I need more help on a project I’m driving at Amazon where we continue to make big changes in our datacenter network to improve customer experience and drive down costs while, at the same time, deploying more gear into production each day than all of Amazon.com used back in 2000. It’s an exciting time and we have big changes happening in networking. If you enjoy and have experience in operating systems, networking protocol stacks, or embedded systems and you would like to work on one of the biggest networks in the world, [get in touch].' -- James Hamilton

'a network proxy that terminates TLS/SSL connections and forwards the unencrypted traffic to some backend. It's designed to handle 10s of thousands of connections efficiently on multicore machines.'

Gunnar Kreitz' paper on its innards! 'Spotify is a music streaming service offering lowlatency access to a library of over 8 million music tracks.
Streaming is performed by a combination of client-server access
and a peer-to-peer protocol. In this paper, we give an overview
of the protocol and peer-to-peer architecture used and provide
measurements of service performance and user behavior.
The service currently has a user base of over 7 million and
has been available in six European countries since October 2008.
Data collected indicates that the combination of the client-server
and peer-to-peer paradigms can be applied to music streaming
with good results. In particular, 8.8% of music data played comes
from Spotify’s servers while the median playback latency is only
265 ms (including cached tracks). We also discuss the user access
patterns observed and how the peer-to-peer network affects the
access patterns as they reach the server.'

'Connected to TELEHACK port 13 / It is 8:16 am on Saturday, April 30, 2011 in Mountain View, California, USA. There are 10 local users. There are 24139 hosts on the network.' via Waxy

the innards of Spotify's client, server fleet, and P2P layer, from the dev team themselves. good stuff

a success story from JSConf. great tips, I'm sure some will be practical at smaller scales ;)

a very hairy hack to perform a block-level rsync-like "send just the changes" algorithm between two very large files (think /dev/sda block devices).  Crazy, but it'd work alright!

'Any TCP session you initiate to one of the proxied IP addresses [specified on the command line] will be captured by sshuttle and sent over an ssh session to the remote copy of sshuttle, which will then regenerate the connection on that end, and funnel the data back and forth through ssh. Fun, right? A poor man's instant VPN, and you don't even have to have admin access on the server.'

'It is alleged that some ex-developers (and the company<br />
they worked for) accepted US government money to put backdoors into [the OpenBSD] network stack, in particular the IPSEC stack. Around 2000-2001'

used by UPC for deep packet inspection, according to the EMI v UPC judgement

"benchmarks disprove common wisdom" shocker

wonderful; our world's economies are now more networked than ever, and vulnerable to the attacks which that enables. Have we learned nothing from the last few years?

SMB setup details

'a proxy server that works behind a NAT, even when the client is behind a NAT, without any 3rd party'. nifty, by Samy "MySpace worm" Kamkar

GFS, warts and all

so, it seems the wireless ISPs don't have sufficient IPv4 space for their customers, and are filtering access to the internet via NAT; unfortunate side effect is that this breaks data retention as defined in the UK. wonder if the same applies here?

another serialization format, binary, no IDL, no code generation, from GitHub

'File-based, rather than tuple-based processing'; based around UNIX command-line toolset; good UNIXish UI; lots of caching of intermediate results; low setup overhead -- although it does require a shared POSIX filesystem, e.g. NFS, for synchronization