From: borg@uu3.net
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Patch using ipset match in policy routing.
Date: Wed, 5 Dec 2012 13:33:10 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.1212051326330.1837@cube> (raw)
In-Reply-To: <alpine.DEB.2.00.1212050926200.27565@blackhole.kfki.hu>
> As far as I see, it's a chicken and egg problem: the kernel must lookup
> the routing table first to select a source address and that can't be
> changed later by policy routing.
You are correct.
> In the bugzilla thread Ambroz Bizjak suggested using SNAT. Why doens't it
> a good solution?
SNAT is not supposed to be used that way.. better would be NETMAP.
But still I feel it is not right aproach.
Okey, lets cut it. I know that this patch is for very specific setups
that are used very rary. I rather wanted to have tech talk here about
how I've done certain things.
Lets it leave it as is. Patch is working fine (both SMP and non SMP hosts).
If someone will be interested in it, can pick it up and mail me directly.
Regards,
Borg
prev parent reply other threads:[~2012-12-05 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 21:49 Patch using ipset match in policy routing borg
2012-12-04 20:22 ` Jozsef Kadlecsik
2012-12-04 21:46 ` borg
2012-12-05 10:01 ` Jozsef Kadlecsik
2012-12-05 12:33 ` borg [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=Pine.LNX.4.64.1212051326330.1837@cube \
--to=borg@uu3.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.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 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).