From: Dmitry Butskoy <buc@odusz.so-cdu.ru>
To: netdev@vger.kernel.org
Subject: Re: Traceroute and "ping" sockets: some questions
Date: Fri, 19 Aug 2011 17:56:26 +0400 [thread overview]
Message-ID: <4E4E6B8A.1030707@odu.neva.ru> (raw)
In-Reply-To: <20110819.062249.2234872106788628654.davem@davemloft.net>
David Miller wrote:
>>> Why limit? He can spam with UDP socket just as easily at any rate
>>> he pleases,
>>>
>> Yes, but most cases such UDP is "one-way" spam (until services like
>> "echo 7/udp" are enabled).
>> For icmp echo, we normally receive icmp replies, hence it is
>> bidirectional crap. Which was not present before.
>>
> Well, replace UDP with TCP syn flood.
>
Well.
Why then there is "net/ipv4/ping_group_range" restrictions, with default
values (low=1, high=0) which denies this way even for root?
Regards,
Dmitry
next prev parent reply other threads:[~2011-08-19 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 11:19 Traceroute and "ping" sockets: some questions Dmitry Butskoy
2011-08-19 11:38 ` David Miller
2011-08-19 12:22 ` Dmitry Butskoy
[not found] ` <4E4E4DF6.2020509@odu.neva.ru>
[not found] ` <20110819.062249.2234872106788628654.davem@davemloft.net>
2011-08-19 13:56 ` Dmitry Butskoy [this message]
2011-08-19 14:00 ` David Miller
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=4E4E6B8A.1030707@odu.neva.ru \
--to=buc@odusz.so-cdu.ru \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox