From: Aaron Wood <woody77@gmail.com>
To: "Dave Täht" <dave@taht.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] doing better videoconferencing and voip emulation and analysis?
Date: Fri, 12 Feb 2016 12:17:51 -0800 [thread overview]
Message-ID: <CALQXh-NUa2NMTjFz3j6pcw=n6DRVoU7QyGu3fcFGHQUO-zXswg@mail.gmail.com> (raw)
In-Reply-To: <56BE28D0.8050009@taht.net>
[-- Attachment #1: Type: text/plain, Size: 1812 bytes --]
scapy (python) should be able to keep up with a voip or video stream. I've
been using it to parse packets and do some other manipulations. It's
certainly not C, performance-wise, but it's incredibly flexible at the
protocol manipulation level.
The performance issues that I'm running into with it have me tempted to
look for something similar in Go. I'm unencapsulating packets (think
stripping packets out of a GRE tunnel), and only able to get about
1000-1200 packets/sec on modest hardware (running in a linux VM hosted on
windows on an i5 processor...)
-Aaron
On Fri, Feb 12, 2016 at 10:47 AM, Dave Täht <dave@taht.net> wrote:
>
> A *long* while ago I had started at an attempt to do some better voip
> and videoconferencing emulation. I stopped primarily due to:
>
> A) wanting a *good* three way UDP handshake to kick off the protocol
> (thus avoiding the DDOS possibilities)
>
> B) No money
>
> C) Not wanting to write it in C (and the low level features needed like
> sendmmsg and manipulating low level ip header constructs like qos and
> ecn seem hard to get at in many other languages)
>
> D) hoping that some other protocol (like QUIC) could be used for it
> instead.
>
> Anyway, my first attempt at describing what I wanted to do ended up
> here, before I realized how much work it would be.
>
> https://github.com/dtaht/twd/blob/master/rfc/middle.mkd
>
> And I'm really tempted to go write something new in go or rust (Not C!
> Need a break from C!), or leverage some other rtp/sip benchmarking tool.
> Has any other libraries or benchmarks shown up worth leveraging to
> tackle these problems?
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2462 bytes --]
next prev parent reply other threads:[~2016-02-12 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 18:47 Dave Täht
2016-02-12 20:17 ` Aaron Wood [this message]
2016-02-13 22:56 ` Michael Richardson
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='CALQXh-NUa2NMTjFz3j6pcw=n6DRVoU7QyGu3fcFGHQUO-zXswg@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave@taht.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