All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amin Azez <azez@ufomechanic.net>
To: Patrick McHardy <kaber@trash.net>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	Netfilter Developer Mailing List
	<netfilter-devel@lists.netfilter.org>
Subject: RE: xt_gateway 20070605 (kernel)
Date: Sat, 16 Jun 2007 08:34:30 +0100	[thread overview]
Message-ID: <200706160857.l5G8vhv24743@server1.secure-linux-server.com> (raw)

From: "Patrick McHardy" <kaber@trash.net>
Sent: 15/06/07 18:27
Subject: Re: xt_gateway 20070605 (kernel)

=So far I don't intend to merge it, but I'm also not very opposed
=to it (only reason against it is that its another file to take
=care of when changing say function signatures and it doesn't
=offer anything that we can't already do). Its up to you to
convince me :)

It does one thing well and simply.
For most iptables users, realms is more complicated than replicating route information in the nat table.

Realms are perhaps suitable with a large routing infrastructure under one administration.

Xt_gateway removes the need for the more advanced explanations of the SNAT target that are required from time to time.

Xt_gateway is simple to manage snat when the gateways are out of administrative control.

Xt_gateway is persisted solely with iptables-save.
There is no iproute-save (actually there is, I posted it to the relevant list a few months back but no-one noticed).

I'm not going to try to convince you harder than this. Some directors and shareholders (if they were aware) would probably prefer that you did NOT merge it to the mainline kernel and I also have a duty to them.

However I thank you (and more particularly Jan) for the time you have spent on this.

Sam

             reply	other threads:[~2007-06-16  7:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16  7:34 Amin Azez [this message]
2007-06-16  7:59 ` xt_gateway 20070605 (kernel) Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2007-06-16  9:29 Amin Azez
2007-06-16 12:00 ` Jan Engelhardt
2007-06-16 12:14   ` Amin Azex
2007-06-16 16:31     ` Amin Azex
2007-06-15 17:20 Amin Azez
2007-06-15 17:27 ` Patrick McHardy
2007-06-15 19:21   ` Jan Engelhardt
2007-06-06 15:58 Amin Azez
2007-06-06 16:06 ` Patrick McHardy
2007-06-06  7:01 Amin Azez
2007-06-05 11:17 xt_gateway 20070605 Jan Engelhardt
2007-06-05 11:17 ` xt_gateway 20070605 (kernel) Jan Engelhardt
2007-06-05 12:08   ` Jan Engelhardt
2007-06-05 15:15     ` Patrick McHardy
2007-06-05 15:20       ` Jan Engelhardt
2007-06-06 11:31         ` Patrick McHardy
     [not found]       ` <46727873.20503@ufomechanic.net>
2007-06-15 16:11         ` Jan Engelhardt
2007-06-15 16:15           ` Patrick McHardy
2007-06-05 22:24   ` Phil Oester

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=200706160857.l5G8vhv24743@server1.secure-linux-server.com \
    --to=azez@ufomechanic.net \
    --cc=jengelh@computergmbh.de \
    --cc=kaber@trash.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.