From: Martijn Lievaart <m@rtij.nl>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: Bridge netfilter defered hooks
Date: Thu, 08 Jun 2006 22:47:19 +0200 [thread overview]
Message-ID: <44888CD7.8090601@rtij.nl> (raw)
In-Reply-To: <4487CEA8.8060701@trash.net>
Patrick McHardy wrote:
>Carl-Daniel Hailfinger wrote:
>
>
>>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 ..
>
>
Something I've been thinking about. Currently it is impossible to write
any kind of generic tool that uses the mark and plays nice with other
generic tools. Maybe we need some kind of API that allocates bits in the
mark. Something like "give me two bits", that returns some handle to the
bits. That handle could then be used for identifying the bits in the mark.
As an added benefit, this encapsulates the operations on the mark,
making it trivial to switch to say 64 bits for the mark.
What do others think?
M4
next prev parent reply other threads:[~2006-06-08 20:47 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
2006-06-08 20:47 ` Martijn Lievaart [this message]
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=44888CD7.8090601@rtij.nl \
--to=m@rtij.nl \
--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.