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

Date:	Mon, 30 Jul 2007 13:37:20 -0700
From:	"Javier Cardona" <javier@...ybit.com>
To:	"Stephen Hemminger" <shemminger@...ux-foundation.org>
Cc:	"Dan Williams" <dcbw@...hat.com>,
	"Christoph Hellwig" <hch@...radead.org>, netdev@...r.kernel.org
Subject: Re: Proposed interface for per-packet mesh-ttl

Hi Stephen,

On 7/27/07, Stephen Hemminger <shemminger@...ux-foundation.org> wrote:
> In this case perhaps you can have a table that maps skb->priority to
> mesh ttl? priorty can already by handled by existing setsockopt calls,
> and modified by netfilter and QoS managements.

Thanks for the feedback.  IMHO overloading the [SOL_SOCKET]
SO_PRIORITY  sockoption for something as different as changing the
mesh-ttl is quite a stretch.   But I admit that it meets the driver
requirements of "never add sockopt" and "not [ab]use netfilter hooks".
 If that's acceptable to all, I'll modify the patch in that direction.

Cheers,

Javier
-
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