From: grenville armitage <garmitage@swin.edu.au>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Dealing with P2P traffic in modern networks - measurement, identification, and control
Date: Tue, 17 Apr 2012 13:23:15 +1000 [thread overview]
Message-ID: <4F8CE223.6090807@swin.edu.au> (raw)
In-Reply-To: <4E8388EE.7000106@swin.edu.au>
Apologies for re-animating an old thread, but please see
below for something possibly of tangential interest to
the list.
On 09/29/2011 06:51, grenville armitage wrote:
>
>
> On 09/29/2011 03:40, Jesper Dangaard Brouer wrote:
>>
>> Thanks Dave,
>>
>> I have always had the dream of implementing a behavioural based traffic
>> classification Netfilter module. But I have been unable to find some
>> good research in this area, this might be the answer :-)
>>
>> If anybody else on the list have links/articles relating to behavioral
>> traffic classification, I'm interested! :-)
>
> If by "behavior" you're referring to the statistical patterns within flows
> (packet length variations, inter arrival times, etc) you might be interested
> in our DIFFUSE (http://caia.swin.edu.au/urp/diffuse) work. We've extended
> FreeBSD's ipfw firewall code so that it can recognise traffic based on statistical
> characteristics, and use this (rather than direct packet inspection) to trigger
> e.g. rate shaping, etc. Although our prototype code was initially developed
> for FreeBSD, we've got a preliminary Linux port too. The website contains an
> overview description, docs and patch files against FreeBSD and Linux source.
After some poking, prodding and hair-pulling over the past few months
we've released a prototype implementation of our DIFFUSE system ported
to OpenWRT -- http://caia.swin.edu.au/urp/diffuse/openwrt/
We have specifically implemented and tested DIFFUSE running on a
TP-Link WR1043ND using OpenWRT, and documented the work in tech report
(http://caia.swin.edu.au/reports/120412A/CAIA-TR-120412A.pdf)
In particular, we demonstrated the ability of a DIFFUSE-enabled WR1043ND
to detect & protect certain online game traffic (without knowing ports and
addresses a priori) from queuing delays usually induced by bulk TCP cross
traffic, and do so at line rates quite suitable for typical ADSL2+ environments.
This is prototype work, not rigorously debugged nor read for prime time. But
we hope it is nevertheless of some interest!
cheers,
gja
prev parent reply other threads:[~2012-04-17 3:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 15:56 Dave Taht
2011-09-28 17:40 ` Jesper Dangaard Brouer
2011-09-28 18:03 ` Jesper Louis Andersen
2011-10-03 12:03 ` David Täht
2011-09-28 20:51 ` grenville armitage
2011-09-29 21:58 ` Jesper Dangaard Brouer
2011-10-01 1:02 ` grenville armitage
2012-04-17 3:23 ` grenville armitage [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F8CE223.6090807@swin.edu.au \
--to=garmitage@swin.edu.au \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox