From: Jean Delvare <khali@linux-fr.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: rick.jones2@hp.com, netdev@vger.kernel.org
Subject: Re: [PATCH] Update function names in /proc/net/tcp documentation
Date: Tue, 16 Oct 2007 10:46:36 +0200 [thread overview]
Message-ID: <20071016104636.7d633bad@hyperion.delvare> (raw)
In-Reply-To: <E1Ih0PI-0003TX-00@gondolin.me.apana.org.au>
Hi Herbert,
On Sun, 14 Oct 2007 18:09:12 +0800, Herbert Xu wrote:
> Jean Delvare <khali@linux-fr.org> wrote:
> >
> >> inet_diag is the preferred interface.
> >
> > How does it work? Is there some documentation available? I see
> > net/ipv4/inet_diag.c but I have no idea how to use it.
>
> Have a look at the iproute package. It contains the ss command
> which provides a command-line interface to it.
>
> Of course it's also a good example of how you can access it from
> C. The Debian pidentd package has also been patched to use this
> interface.
Thanks for the information. Now I'm worried that most people use
netstat and not ss, while it seems that netstat doesn't have tcp_diag
support. Would it make sense to add tcp_diag support to netstat? Or
should we simply invite system admins to switch from netstat to ss
(maybe by adding a netstat-like formatting option)?
Not that I am skilled enough in this area to do either myself anyway
(let alone the lack of time), but I'm curious what the correct approach
would be.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2007-10-16 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 20:54 [PATCH] Update function names in /proc/net/tcp documentation Jean Delvare
2007-10-12 23:13 ` Rick Jones
2007-10-13 12:43 ` Jean Delvare
2007-10-13 12:49 ` Herbert Xu
2007-10-14 9:59 ` Jean Delvare
2007-10-14 10:09 ` Herbert Xu
2007-10-16 8:46 ` Jean Delvare [this message]
2007-10-16 10:34 ` Herbert Xu
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=20071016104636.7d633bad@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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;
as well as URLs for NNTP newsgroup(s).