netdev - Re: [PATCH] Update function names in /proc/net/tcp documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071016104636.7d633bad@hyperion.delvare>
Date:	Tue, 16 Oct 2007 10:46:36 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	rick.jones2@...com, netdev@...r.kernel.org
Subject: Re: [PATCH] Update function names in /proc/net/tcp documentation

Hi Herbert,

On Sun, 14 Oct 2007 18:09:12 +0800, Herbert Xu wrote:
> Jean Delvare <khali@...ux-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
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html