[163684] in North American Network Operators' Group
Re: Blocking TCP flows?
daemon@ATHENA.MIT.EDU (Kenny Kant)
Fri Jun 14 02:51:31 2013
In-Reply-To: <CAGsuqq2c9+6fjzodGUqonGbK4Mg3bbgZwM+P92L46e-4Y1tgYg@mail.gmail.com>
From: Kenny Kant <akennykant@gmail.com>
Date: Fri, 14 Jun 2013 01:47:56 -0500
To: Eric Wustrow <ewust@umich.edu>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
+1 for Bro
http://www.bro.org
http://packetpushers.net/healthy-paranoia-show-11-bro-the-outer-limits-of-i=
ds/
Sent from my iPad
On Jun 13, 2013, at 2:32 PM, Eric Wustrow <ewust@umich.edu> wrote:
> Hi all,
>=20
> I'm looking for a way to block individual TCP flows (5-tuple) on a 1-10 gb=
ps
> link, with new blocked flows being dropped within a millisecond or so of
> being
> added. I've been looking into using OpenFlow on an HP Procurve, but I don'=
t
> know much in this area, so I'm looking for better alternatives.
>=20
> Ideally, such a device would add minimal latency (many/expandable CAM
> entries?), can handle many programatically added flows (hundreds per
> second),
> and would be deployable in a production network (fails in bypass mode). Ar=
e
> there any
> COTS devices I should be looking at? Or is the market for this all under
> the table to
> pro-censorship governments?
>=20
> Thanks,
>=20
> -Eric
