public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: peter.mueller@ipfire.org
To: development@lists.ipfire.org
Subject: Re: [Oisf-users] Suricata causes massive packet loss
Date: Sat, 07 Sep 2019 17:29:00 +0000	[thread overview]
Message-ID: <30f4eabc-d362-fb20-528e-aaaa17c7755a@ipfire.org> (raw)
In-Reply-To: <ea5d6ed6cf97e022f4d212a6bc6959f744192dbd.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]

Hello Stefan, hello Peter, hello Eric, hello *,

sorry for the late reply.

@Peter: Thank you for the "max-pending-packets" hint. Changing the value
from 1024 (default) to 2048, 4096 and 8192 unfortunately did not made
things better - OpenVPN throughput stays the same.

@Stefan: Thank you for building and packaging! I will install it on
my testing machine and report back within the next days.

Since I was unable to reproduce the OpenVPN bandwidth issue on another
(productive) system running on Core Update 134, I guessed Core 135
(https://blog.ipfire.org/post/ipfire-2-23-core-update-135-released)
introduced that problem. This is wrong, I have updated the system meanwhile,
performed a reboot, and everything stays the same.

@Eric: It is good to know that the DNS problem can be tracked down
to a Netfilter bug. There are some iptables/Netfilter/... packages which
we are not shipping the latest version, I will update them. Do you happen
to have a bugtracker ID or link for that problem?

@All: Meanwhile, the domain "suricata-ids.org" was listed at URIBL
(http://uribl.com/), so some mails got rejected at our mail server. I
guess that was a false positive and removed hard reject action for URIBL.
Anyway: Is anyone aware of a compromise or security issues at "suricata-ids.org"?

Thanks, and best regards,
Peter Müller

  reply	other threads:[~2019-09-07 17:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-07 12:19 Stefan Schantl
2019-09-07 17:29 ` peter.mueller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-07 12:26 Stefan Schantl
2019-09-05 18:56 peter.mueller

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

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

  git send-email \
    --in-reply-to=30f4eabc-d362-fb20-528e-aaaa17c7755a@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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