linux-kernel - Re: [2.6 patch] the scheduled removal of the frame diverter

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: <8FCCCD3C-FA3D-4857-B76D-56087D1519A0@mac.com>
Date:	Mon, 13 Nov 2006 18:14:10 -0500
From:	Kyle Moffett <mrmacman_g4@....com>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Stephen Hemminger <shemminger@...l.org>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [2.6 patch] the scheduled removal of the frame diverter

On Nov 13, 2006, at 16:04:25, Adrian Bunk wrote:
> This patch contains the scheduled removal of the frame diverter.
>
> [snip]
>
> -config NET_DIVERT
> -	bool "Frame Diverter (EXPERIMENTAL)"
> -	depends on EXPERIMENTAL && BROKEN
> -	---help---
> -	  The Frame Diverter allows you to divert packets from the
> -	  network, that are not aimed at the interface receiving it (in
> -	  promisc. mode). Typically, a Linux box setup as an Ethernet bridge
> -	  with the Frames Diverter on, can do some *really* transparent www
> -	  caching using a Squid proxy for example.

 From my understanding of iptables/ebtables, identical functionality  
is already avaialble within that framework; and as such this patch is  
just removing broken experimental and redundant code.  The IPTables  
code also properly handles IPv6 and all the other old warts of the  
frame diverter as well.  I agree that this should go.

Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/