netdev - Re: Proposed interface for per-packet mesh-ttl

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] [day] [month] [year] [list]

Message-ID: <8e8340660708161543l1b4de41at861fbb98463f39e8@mail.gmail.com>
Date:	Thu, 16 Aug 2007 15:43:16 -0700
From:	"Luis Carlos Cobo" <luisca@...ybit.com>
To:	"Stephen Hemminger" <shemminger@...ux-foundation.org>
Cc:	"Javier Cardona" <javier@...ybit.com>,
	"Dan Williams" <dcbw@...hat.com>,
	"Christoph Hellwig" <hch@...radead.org>, netdev@...r.kernel.org
Subject: Re: Proposed interface for per-packet mesh-ttl

On 8/16/07, Stephen Hemminger <shemminger@...ux-foundation.org> wrote:
> The problem with socket options is how does the application know
> the correct policy? Pushing configuration to application is just deferring
> the problem, not solving it.  You want some policy to be done by the
> infrastructure; that means kernel, libraries, daemons, etc. Doing it in
> the application is often inflexible and unusable.

The policy will usually be done by the kernel. If the flag is not set,
which will happen most of the time, the driver will use a sensible
default ttl. The socket option would only be used by applications that
are specifically interested in a configurable ttl (like an application
to plot neighbors within an specific diameter). A per-interface
setting is not good enough, since we do not want the neighbor-plotting
tool to affect the ttl of other connections (e.g. a ssh session) that
might be going on at the same time.

-- 
Luis Carlos Cobo Rus       GnuPG ID: 44019B60
cozybit Inc.
-
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