netdev - Re: [PATCH] ipv4: add DiffServ priority based routing

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: <201001141250.27287.schmto@hrz.tu-chemnitz.de>
Date:	Thu, 14 Jan 2010 12:50:27 +0100
From:	Torsten Schmidt <torsten.schmidt@...06.tu-chemnitz.de>
To:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH] ipv4: add DiffServ priority based routing

On Tuesday 12 January 2010 21:16:07 you wrote:
> You can't do any of these things you are doing, I've basically been
> ignoring all of these crazy diffserv patches, they're nuts!
> 
> The TOS socket option has a meaning and behavior defined by the BSD
> sockets interface many years ago.  And you cannot and must not change
> the behavior of those system calls because applications are written to
> the current behavior and you will break them.  Protecting the new
> behavior with a kernel config option is a non-starter, it's pointless
> because no distribution is going to enable a kernel option that
> knowingly breaks applications.
> 
> And it is also possible to set the TOS field however you desire using
> what the kernel currently provides, we do not preclude proper diffserv
> support, the BSD socket interfaces allow that just fine.
okay, I noticed.

> And you can also do diffserv by classifying traffic and setting the
> TOS field using either the packet scheduler, or even netfilter.
Our company is more interested in IP DiffServ traffic accounting.
So we simply need a fast mechanism which generates IP DiffServ traffic
statistics, without setting the network interface in promiscuous mode,
(which softflowd ore tcpdump does).

So first idea was to implement a virtual file e.g. called /proc/net/ip_dscp.
If the main line peoples are not interested in, i will no longer send these
patches. 

Thanks,
Torsten

PS.: Maybe we could implement a more general mechanism to classify TOS/DiffServ 
traffic in the kernel (if needed) ?
--
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