[163644] in North American Network Operators' Group
Re: Blocking TCP flows?
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Thu Jun 13 16:04:46 2013
In-Reply-To: <CAGsuqq2c9+6fjzodGUqonGbK4Mg3bbgZwM+P92L46e-4Y1tgYg@mail.gmail.com>
Date: Thu, 13 Jun 2013 16:03:15 -0400
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Eric Wustrow <ewust@umich.edu>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Thu, Jun 13, 2013 at 3:32 PM, Eric Wustrow <ewust@umich.edu> wrote:
> Hi all,
>
> I'm looking for a way to block individual TCP flows (5-tuple) on a 1-10 gbps
> 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.
>
this sounds like a job for the arista box with the FGPA onboard, no?
> 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). Are
> there any
> COTS devices I should be looking at? Or is the market for this all under
> the table to
> pro-censorship governments?
>
> Thanks,
>
> -Eric
