From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Laszlo Attila Toth <panther@balabit.hu>, netfilter-devel@vger.kernel.org
Subject: Re: [resend net-next] socket: Added 'transparent' option
Date: Thu, 04 Jun 2009 18:08:09 +0200 [thread overview]
Message-ID: <4A27F169.9090003@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0906041759320.20094@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Thursday 2009-06-04 17:27, Laszlo Attila Toth wrote:
> Also, if possible, try combining all the TBF implementations; limit
> and hashlimit are so close to each other, the latter would only need
> a "--hashlimit-mode notuple" (from a userspace pov) , and xt_limit
> could be obsoleted.
If we're going to touch the ABI and add a new revision, we should
at the same time try to get rid of the resolution problems so we
don't need yet another reversion when someone finally fixes this.
next prev parent reply other threads:[~2009-06-04 16:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 13:26 [resend net-next] socket: Added 'transparent' option Laszlo Attila Toth
2009-06-04 13:26 ` [resend iptables] " Laszlo Attila Toth
2009-06-04 13:34 ` [resend net-next] " Patrick McHardy
2009-06-04 14:55 ` Jan Engelhardt
2009-06-04 15:27 ` Laszlo Attila Toth
2009-06-04 16:03 ` Jan Engelhardt
2009-06-04 16:08 ` Patrick McHardy [this message]
2009-06-05 13:06 ` Laszlo Attila Toth
2009-06-08 12:30 ` [resend2] Socket match with transparent option, take 2 Laszlo Attila Toth
2009-06-08 12:30 ` [resend2 net-next] socket: added mtinfo with 'transparent' flag Laszlo Attila Toth
2009-06-08 12:30 ` [resend2 iptables] socket match: new revision, match transparent sockets Laszlo Attila Toth
2009-06-09 12:50 ` [resend2 net-next] socket: added mtinfo with 'transparent' flag Patrick McHardy
2009-06-09 13:11 ` [net-next] " Laszlo Attila Toth
2009-06-09 13:18 ` 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=4A27F169.9090003@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=panther@balabit.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).