From: Dmitry Butskoy <buc@odusz.so-cdu.ru>
To: netdev@vger.kernel.org
Subject: Traceroute and "ping" sockets: some questions
Date: Fri, 19 Aug 2011 15:19:16 +0400 [thread overview]
Message-ID: <4E4E46B4.9010909@odu.neva.ru> (raw)
Hi
I've released new version of the Linux traceroute 2.0.18, which supports
new (SOCK_DGRAM, IPPROTO_ICMP) sockets, appeared in the kernel 3.0 .
This way users might perform icmp tracerouting (`-I') without setuid bit
or cap_net_raw settings of the executable.
(See it at
http://sourceforge.net/projects/traceroute/files/traceroute/traceroute-2.0.18/)
I would like to ask some questions:
- Currently such "ping" sockets implemented for IPv4 only. Are there any
plans to implement it for IPv6 as well?
The traceroute-2.0.18 is ready for IPv6 anyway -- just wait for
appearing it in the kernel without recompile (I hope :) ) -- but I would
prefer to test it as soon as possible.
- Are there any plans to implement some "rate control" (maybe
sysctl-configurable too), to restrict unprivileged users to send icmp
echoes too fast (ie. faster than 200 ms -- the current ping(8) restriction)?
Regards,
Dmitry Butskoy
http://www.fedoraproject.org/wiki/DmitryButskoy
next reply other threads:[~2011-08-19 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 11:19 Dmitry Butskoy [this message]
2011-08-19 11:38 ` Traceroute and "ping" sockets: some questions 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
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=4E4E46B4.9010909@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