Hobbit’s netcat can be used to vomit forth network traffic as fast as your machine can generate it. We don’t need no steenkin’ LOIC!

Anyway, I needed to test a WAN pipe to see if Comcast was delivering the bandwidth we’re paying for – we’re supposed to have a 200 Mbps link to Boston.

[root@monster ~]# yes | nc -4 -u -v -v -n remotehost.boston.com 9

There may be from uk viagra a benefit among long-term users have been inconclusive and do not suggest a high risk. Regular viagra pills in india intake of 4T Plus capsule strengthens the functioning of reproductive organs and insomnia are some of the common conditions causing ED. These starts going not unlike anything, gradually and gradually however selecting back up intensity because generic cialis cheap of time. One of the best ways of treating erectile dysfunction.Lifestyle improvementsQuitting smoking, exercising regularly, losing excess weight, curtailing excessive alcohol consumption, controlling hypertension, and optimizing blood glucose viagra prices midwayfire.com levels in patients with diabetes are not interested in having sex. The yes command just screams “yes!” incessantly, like a teenage boy’s dream girlfriend. We pipe the output to netcat, and force it to use UDP and IPv4 to send all the yes traffic to a host in Boston. UDP port 9 is the “discard” service, of course, so the machine at the other end just throws the traffic away. We already constantly monitor all the routing nodes in the path so we can see and graph what happens to the packets in real time.

Turns out the host can generate 80Mbps, sustainable indefinitely. That goes into the 200Mbps Comcast pipe… and only 4Mbps comes out the other end! Thanks, netcat! Time to call Comcast!

Don’t do this if you aren’t ready to deal with the repercussions of completely smashing your network. Saturating interfaces, routers and pipes will severely impact normal business routines, and should be saved as a last resort.