-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of William Bohannan
Sent: 20 December 2006 16:33
To: [EMAIL PROTECTED]
Cc: lartc@mailman.ds9a.nl
Subject: RE: [LARTC] blocking traffic on the FORWARD chain using physdev
Still can't seem to block on the FORWARD chain in one directio
lliam
-Original Message-
From: Oscar Mechanic [mailto:[EMAIL PROTECTED]
Sent: 14 December 2006 12:41
To: William Bohannan
Cc: lartc@mailman.ds9a.nl
Subject: RE: [LARTC] blocking traffic on the FORWARD chain using physdev
Are you sure you want to block ICMP how about PMTU
ebtables -I FORW
:[EMAIL PROTECTED]
> Sent: 14 December 2006 12:27
> To: William Bohannan
> Cc: lartc@mailman.ds9a.nl
> Subject: Re: [LARTC] blocking traffic on the FORWARD chain using physdev
>
> Hi
>
>Physdev may no longer be supported soon something to do with hooks
> and how this is
--Original Message-
From: Oscar Mechanic [mailto:[EMAIL PROTECTED]
Sent: 14 December 2006 12:27
To: William Bohannan
Cc: lartc@mailman.ds9a.nl
Subject: Re: [LARTC] blocking traffic on the FORWARD chain using physdev
Hi
Physdev may no longer be supported soon something to do with hooks
and h
Hi
Physdev may no longer be supported soon something to do with hooks
and how this is difficult to support. I have stopped using it cause I
found some odd behavior in physdev-in, out seemed fine I remember. I use
ebtables and marks for this now.
On Thu, 2006-12-14 at 20:55 +0900, William Boha
Currently using physdev on a bridge to try and isolate certain paths
across and to the bridge. It all works except when trying to stop the
flow in one direction on the FORWARD chain?? Can someone please help??
Below is the testing done so far.
eth1 <---> BRIDGE <---> eth0
# Block (eth0 ---> eth