All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Bart De Schuymer <bdschuym@pandora.be>
Subject: Re: Bridge netfilter defered hooks
Date: Thu, 08 Jun 2006 09:15:52 +0200	[thread overview]
Message-ID: <4487CEA8.8060701@trash.net> (raw)
In-Reply-To: <44809B1C.2010907@gmx.net>

Carl-Daniel Hailfinger wrote:
> Patrick McHardy wrote:
> 
>>Thats what I meant by "iptables+mark". You can combine iptables
>>specific matches by marking matching packets, then match on the
>>mark with ebtables (or the other way around for incoming packets).
> 
> 
> IIRC the mark has only 32 bits. Not so long ago, I was using 30 bits
> of that in my firewalling rules on a bridge-router. I might have
> squeezed the physdev match in the remaining 2 bits, but I'm not
> sure. I do admit the setup was fairly uncommon (bridging and
> double nat with only one machine).

Yes, its getting a bit tight in there, but so far in all setups I've
seen it was possible to get along with the 32 bits using masks or
reusing bits after they are no longer needed. I guess we'll have to
wait and see ..

  reply	other threads:[~2006-06-08  7:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-02 14:57 Bridge netfilter defered hooks Patrick McHardy
2006-06-02 17:00 ` Bart De Schuymer
2006-06-02 17:18   ` Patrick McHardy
2006-06-02 20:10     ` Carl-Daniel Hailfinger
2006-06-08  7:15       ` Patrick McHardy [this message]
2006-06-08 20:47         ` Martijn Lievaart
2006-06-08 21:40           ` Simon Lodal
2006-06-08 22:17             ` Martijn Lievaart
2006-06-08 23:43               ` Philip Craig
2006-06-19 16:01                 ` Patrick McHardy
2006-06-19 15:59           ` Patrick McHardy
2006-06-20 21:26             ` Martijn Lievaart
2006-06-20 21:44               ` Patrick McHardy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4487CEA8.8060701@trash.net \
    --to=kaber@trash.net \
    --cc=bdschuym@pandora.be \
    --cc=c-d.hailfinger.devel.2006@gmx.net \
    --cc=netfilter-devel@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.