From: Mike Fedyk <mfedyk@matchmail.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: pjd@fred001.dynip.com, robert@schwebel.de,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Networking with slow CPUs
Date: Fri, 29 Mar 2002 10:27:07 -0800 [thread overview]
Message-ID: <20020329182707.GG8627@matchmail.com> (raw)
In-Reply-To: <200203291133.g2TBXsi10506@fred.cambridge.ma.us> <Pine.LNX.3.96.1020329104533.22866C-100000@gatekeeper.tmr.com>
On Fri, Mar 29, 2002 at 10:47:55AM -0500, Bill Davidsen wrote:
> On Fri, 29 Mar 2002 pjd@fred001.dynip.com wrote:
>
> > Robert Schwebel wrote:
> > >
> > > Is there a possibility to "harden" a small machine (33 MHz embedded
> > > device) against e.g. flood pings from the outside world?
> >
> > It *is* bleeding edge, as someone else pointed out, but you should
> > really investigate NAPI. It's designed to make Linux resiliant against
> > non-flow-controlled network loads like routing, which sounds like
> > just the ticket.
>
> There is rate limiting in recent iptables, as well. I don't regard
> iptable as bleeding edge, so that may have a higher comfort level.
>
Yes, but it won't keep the interrupts from all of those packets from
overloading, and DoSing it or possibly crashing the system.
next prev parent reply other threads:[~2002-03-29 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 18:46 Networking with slow CPUs Robert Schwebel
2002-03-28 10:59 ` Peter Wächtler
2002-03-29 11:33 ` pjd
2002-03-29 15:47 ` Bill Davidsen
2002-03-29 18:27 ` Mike Fedyk [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-28 15:38 Samium Gromoff
2002-03-28 13:31 ` Richard B. Johnson
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=20020329182707.GG8627@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjd@fred001.dynip.com \
--cc=robert@schwebel.de \
/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.