Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Nils Andreas Svee <me@lochnair.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Dave Taht" <dave.taht@gmail.com>
Cc: "Toke Høiland-Jørgensen via Cake" <cake@lists.bufferbloat.net>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>,
	"Simon Sundberg" <Simon.Sundberg@kau.se>
Subject: Re: [Cerowrt-devel] [Bloat] [Cake] Fwd: [Galene] Dave on bufferbloat and jitter at 8pm CET Tuesday 23
Date: Fri, 26 Feb 2021 01:32:39 +0100	[thread overview]
Message-ID: <86692246-90d3-4b5b-bcb3-5a67a29d67f7@lochnair.net> (raw)
In-Reply-To: <87wnuw1luc.fsf@toke.dk>

On 2/25/21 11:30 AM, Toke Høiland-Jørgensen wrote:

> Ah, wireguard doesn't have XDP support, so that's likely not going to
> work; and if you run it on the physical interface, even if you didn't
> get driver errors, the tool would just see the encrypted packets which
> is not terribly helpful (it parses TCP timestamps to match
> incoming/outgoing packets and compute the RTT).

I figured that might be the case. Yes I would've disabled the VPN if I 
didn't get driver errors.
I changed the network interface to use an emulated Intel E1000 tonight, 
and if I bypass the VPN it works as it should.

> I guess we should be more flexible about which hooks we support, so it
> can also be used on devices with no XDP support. Adding in Simon, who is
> writing the code; I think he is focused on getting a couple of other
> features done first, but this could go on the TODO list :)

It's not like I'm in a hurry, and I'd probably need some time to figure 
out how to tweak the CAKE parameters correctly with this anyway ;)

Speaking of, isn't one of the challenges with solutions like these that 
it's hard to tell when conditions have improved and allow for more 
throughput? At least that's what I remember being the issue when I 
tested CAKE's autorate-ingress back in the day.


- Nils

>> -Toke

  reply	other threads:[~2021-02-26  0:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874ki24ref.wl-jch@irif.fr>
2021-02-23 17:46 ` [Cerowrt-devel] " Dave Taht
2021-02-23 21:30   ` [Cerowrt-devel] [Cake] " Nils Andreas Svee
2021-02-24  1:14     ` Dave Taht
2021-02-24  1:29       ` [Cerowrt-devel] [Bloat] " Stephen Hemminger
2021-02-24 10:51       ` Toke Høiland-Jørgensen
2021-02-24 22:49         ` [Cerowrt-devel] " Nils Andreas Svee
2021-02-24 23:27           ` Toke Høiland-Jørgensen
2021-02-24 23:35             ` [Cerowrt-devel] " Nils Andreas Svee
2021-02-25 10:30               ` Toke Høiland-Jørgensen
2021-02-26  0:32                 ` Nils Andreas Svee [this message]
2021-02-26 11:47                   ` Toke Høiland-Jørgensen
2021-02-24 15:19     ` [Cerowrt-devel] " Taraldsen Erik
2021-02-24 16:11       ` Toke Høiland-Jørgensen
2021-02-24 18:43       ` [Cerowrt-devel] [Make-wifi-fast] " Jonathan Morton
2021-02-24 23:27       ` [Cerowrt-devel] " Nils Andreas Svee

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86692246-90d3-4b5b-bcb3-5a67a29d67f7@lochnair.net \
    --to=me@lochnair.net \
    --cc=Simon.Sundberg@kau.se \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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