From: josh Reynolds <josh@kyneticwifi.com>
To: lartc@vger.kernel.org
Subject: Re: Best qdisc for interfaces of a firewall?
Date: Sun, 09 Nov 2014 15:01:25 +0000 [thread overview]
Message-ID: <545F81C5.80300@kyneticwifi.com> (raw)
In-Reply-To: <545EBBDE.3040200@conversis.de>
I would suggest talking to stig and an-cheng via either the ubnt forum,
or contact them in ##ubnt on freenode irc.
Rebooting like that is not normal behavior.
The only thing I can think of is maybe you have some very inefficient
firewall rules that could be cleaned up a bit? Do you have any
"external" packages installed that aren't natively on the router?
On 11/09/2014 04:58 AM, Dennis Jacobfeuerborn wrote:
> The firmware is the current 1.5 release (well current before the very
> recent 1.6 one) so it's not really old.
>
> fq_codel is not in use and all interface use a noqueue qdisc.
>
> We are only using zone based firewalling, NAT and network/port groups so
> basically just iptables+ipset and a couple of vlan interfaces.
>
> In its default configuration both cpus are pegged at 95% soft-irq usage.
> Enabling vlan offloading reduces that quite a bit...but apparently make
> the system reboot itself about once every two days.
>
> On 09.11.2014 07:29, josh Reynolds wrote:
>> There is an issue on older firmware with edgerouterand fq_codel, Dave
>> would be the one to talk about that.. it's a codel/kernel thing though.
>>
>> I know wisps running full line rate and thousands of customers through
>> edgerouter pros with no problems. What are you having issues with?
>>
>> On 11/08/2014 03:57 PM, Dennis Jacobfeuerborn wrote:
>>> Hi,
>>> I just looked at the interfaces of our EdgeRouter Pro appliance that we
>>> plan to replace (due to it apparently being overloaded at 150Mbit) and
>>> see that they all have a qdisc of "noqueue".
>>>
>>> What is the best qdisc to select for a pure firewall system? I can't
>>> find any decent information about the various qdiscs and which to chose
>>> in specific situations. For example there seems to exist a multiq
>>> scheduler but I cannot find a lot of information about its
>>> characteristics plus I already assigned the irq of each queue of the nic
>>> to individual cores so I wonder if something like multiq is even
>>> necessary.
>>>
>>> I'm also wondering about fairness and if that might be a legitimate
>>> reason to chose somehting like noqueue so one flooding flow cannot hog
>>> the queue and penalize all other flows.
>>>
>>> Any ideas what would be a well performing yet fair choice here?
>>>
>>> Regards,
>>> Dennis
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe lartc" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
next prev parent reply other threads:[~2014-11-09 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 0:57 Best qdisc for interfaces of a firewall? Dennis Jacobfeuerborn
2014-11-09 13:58 ` Dennis Jacobfeuerborn
2014-11-09 14:01 ` Alan Goodman
2014-11-09 15:01 ` josh Reynolds [this message]
2014-11-10 16:20 ` Rick Jones
2014-11-10 18:04 ` Dave Taht
2014-11-11 1:17 ` Dennis Jacobfeuerborn
2014-11-11 1:59 ` Stig Thormodsrud
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=545F81C5.80300@kyneticwifi.com \
--to=josh@kyneticwifi.com \
--cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.