Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Maciej Sołtysiak" <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Revising the synflood limit
Date: Mon, 23 Sep 2019 09:37:55 +0000	[thread overview]
Message-ID: <7s3IIz5xdCFBZa7qezeDJsrz5I5m0eFbzp-4LiCUsXk3gVt7Y8FXCf6ATGu3ZvRawzFQQH5snU8TRZaGnR4hlRQvgg3CbGgYw3BTE-b3AQQ=@soltysiak.com> (raw)
In-Reply-To: <CAA93jw7LxQ7StpMvosDTwwOtZFjvHKwHNWXCdpaCGg+jwzrUkA@mail.gmail.com>

> I'm not sure if it is a "nice catch" or not yet. It's merely me (now
> us) tying two anomalies together that might be connected. Can you
> convert that -j drop to a -j log to see where they come from?
So, I must say I got rusty with my iptables.
When I said I have the same, I had positive packet counters on the limit rule, not the drop rule (or the log rule I added)

So, sorry to jump the gun, but I'm not experiencing it.

Maciej


  reply	other threads:[~2019-09-23  9:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03  0:47 [Cerowrt-devel] talking at linux plumbers in portugal next week Dave Taht
2019-09-03 12:23 ` [Cerowrt-devel] [Bloat] " Mikael Abrahamsson
2019-09-03 14:21   ` Dave Taht
2019-09-03 14:35     ` [Cerowrt-devel] Revising the synflood limit Dave Taht
2019-09-10 18:08       ` Maciej Sołtysiak
2019-09-10 22:35         ` Dave Taht
2019-09-23  9:37           ` Maciej Sołtysiak [this message]
2019-09-03 14:45     ` [Cerowrt-devel] [Bloat] talking at linux plumbers in portugal next week Toke Høiland-Jørgensen
2019-09-03 14:47       ` Dave Taht
2019-09-03 15:10         ` Toke Høiland-Jørgensen
2019-09-03 15:21           ` Dave Taht
2019-09-03 15:22     ` Sebastian Moeller

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='7s3IIz5xdCFBZa7qezeDJsrz5I5m0eFbzp-4LiCUsXk3gVt7Y8FXCf6ATGu3ZvRawzFQQH5snU8TRZaGnR4hlRQvgg3CbGgYw3BTE-b3AQQ=@soltysiak.com' \
    --to=maciej@soltysiak.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=swmike@swm.pp.se \
    /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