From: Patrick McHardy <kaber@trash.net>
To: Martijn Lievaart <m@rtij.nl>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: Bridge netfilter defered hooks
Date: Tue, 20 Jun 2006 23:44:18 +0200 [thread overview]
Message-ID: <44986C32.60105@trash.net> (raw)
In-Reply-To: <449867EE.5080808@rtij.nl>
Martijn Lievaart wrote:
> Patrick McHardy wrote:
>
>> It can see that it would be useful for complex setups, but I can't think
>> of an efficient implementation of this. You would have to carry a table
>> of handle identifiers -> mark ranges with every packet, wouldn't you?
>>
>>
>
> No, no! Just an API (which doesn't need to be coupled to iptables kernel
> part at all) where one can "reserve" some bits in the nfmark. That
> handle would refer to the same bit(s) everywhere, but you don't need to
> know which bits in the mark you are exactly using. So this implies
> ANDing as well. Something along these lines (error handling simplified):
>
> # reserve 1 bit
> MYMARK=`iptables-mark --reserve mybits:1`
> # This would return some 'handle' (most probably the offset in the mark,
> prefixed with something)
>
> # Use MYMARK to set just one bit in the mark
> iptables -A ..... -j MARK --set $MYMARK
It seems I misunderstood you, I thought you were talking about dynamic
reservations :) Sure, something like /etc/iproute/rt_realms would make
life easier for users. But it doesn't really solve the problem that its
sometimes really hard to get along with 32 bits.
prev parent reply other threads:[~2006-06-20 21:44 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
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 [this message]
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=44986C32.60105@trash.net \
--to=kaber@trash.net \
--cc=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.