From: Mark Frazer <mark@somanetworks.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: root@chaos.analogic.com, "Perches,
Joe" <joe.perches@spirentcom.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Subject: Re: want opinions on possible glitch in 2.4 network error reporti ng
Date: Thu, 7 Feb 2002 17:29:26 -0500 [thread overview]
Message-ID: <20020207172926.A22693@somanetworks.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020207151325.10014A-100000@chaos.analogic.com> <3C62EC67.FCB9958A@nortelnetworks.com>
In-Reply-To: <3C62EC67.FCB9958A@nortelnetworks.com>; from cfriesen@nortelnetworks.com on Thu, Feb 07, 2002 at 04:06:47PM -0500
Chris Friesen <cfriesen@nortelnetworks.com> [02/02/07 16:04]:
> under our control. It seems to me to be logical to block the sender
> until the congestion goes away, or return with an error code if the
> sender is non-blocking. This may not play nice with the current kernel
> networking code (qdisc and all that) but doesn't it seem like a good
> idea in principle?
If not, it is then possible for a user on a fast machine to hammer the
network interfaces with UDP packets as some sort of denial of service
attack?
Blocking all senders when the qdisc is full and round-robin'ing among
the blocked would prevent this particular attack.
next prev parent reply other threads:[~2002-02-07 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 17:37 want opinions on possible glitch in 2.4 network error reporti ng Perches, Joe
2002-02-07 18:08 ` Richard B. Johnson
2002-02-07 18:44 ` Chris Friesen
2002-02-07 19:51 ` Jan Harkes
2002-02-07 20:10 ` Chris Friesen
2002-02-07 20:33 ` Richard B. Johnson
2002-02-07 21:06 ` Chris Friesen
2002-02-07 21:29 ` Richard B. Johnson
2002-02-07 22:29 ` Mark Frazer [this message]
2002-02-08 8:35 ` Ian Molton
-- strict thread matches above, loose matches on Subject: below --
2002-02-07 20:37 Perches, Joe
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=20020207172926.A22693@somanetworks.com \
--to=mark@somanetworks.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cfriesen@nortelnetworks.com \
--cc=joe.perches@spirentcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox