From: Dennis Jacobfeuerborn <dennisml@conversis.de>
To: Stig Thormodsrud <stig@ubnt.com>, netfilter@vger.kernel.org
Subject: Re: Recommended hardware for iptables based firewall/router
Date: Sun, 09 Nov 2014 15:05:41 +0100 [thread overview]
Message-ID: <545F74B5.3050401@conversis.de> (raw)
In-Reply-To: <CAL-yc88QPD5w8wLbm6u0skP-6DpMfsFdu0EvQi+6NY7ZYZGUow@mail.gmail.com>
On 09.11.2014 06:15, Stig Thormodsrud wrote:
> On 09.11.2014 01:49, Yucong Sun wrote:
>> Dennis Jacobfeuerborn <dennisml@conversis.de>
>>
>> The EdgeRouter 's asic couldn't handle all use cases , Having some
>> special rule will make it go to "offload" disabled mode. You should
>> research if that's the problem.
>
> I'm a developer on this product. I'd be interested in the test cases
> that it couldn't handle.
This isn't a test case the system is already in live use.
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.
Right at this moment on the wan interface I see 34.273 rx pps and 57.232
tx pps which is going to increase a bit in the coming hours but gives a
good picture about the the system has to handle right now.
Regards,
Dennis
next prev parent reply other threads:[~2014-11-09 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 5:15 Recommended hardware for iptables based firewall/router Stig Thormodsrud
2014-11-09 14:05 ` Dennis Jacobfeuerborn [this message]
2014-11-09 14:52 ` Dennis Jacobfeuerborn
-- strict thread matches above, loose matches on Subject: below --
2014-11-02 3:51 Dennis Jacobfeuerborn
2014-11-02 22:38 ` Neal Murphy
2014-11-09 0:40 ` Dennis Jacobfeuerborn
[not found] ` <CAJygYd07-y0bDSr8THXWjNEW-e1rK5ZhGiE8aeJ_jXYJpFiL2A@mail.gmail.com>
2014-11-09 0:49 ` Yucong Sun
2014-11-09 1:11 ` Dennis Jacobfeuerborn
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=545F74B5.3050401@conversis.de \
--to=dennisml@conversis.de \
--cc=netfilter@vger.kernel.org \
--cc=stig@ubnt.com \
/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.