netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Rathouský" <jan.rathousky@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: port based routing for local generated connections
Date: Sun, 17 May 2009 01:28:03 +0200	[thread overview]
Message-ID: <a14f8c120905161628i6b129e87m17f6db647115315c@mail.gmail.com> (raw)

Hi everybody,
I'm looking for something that allows me routing based on destination
ports (for two OpenVPN tunnels).
First I found nice howto [1] but there is one problem – it works only
with LAN traffic and I want it for one computer with two ISPs. Because
router decision is done before writing marks for local generated
packets. So this howto is not for me :(
I was told that "iptables -j ROUTE" is what I'm looking for.
But I'm not able to compile POM with actual iptables version and my
Debian Squeeze kernel.
Than I found xtables-addon which is much more "fresh" than POM. But it
doesn't have support for ROUTE action.
Do you plan to add it to xtables-addon?
or
Do you know something else that can help me with this situation?

Thanks for answers and for your work.

Jan

PS: does anyone try to contact someone from netfilter team to add a
link to xtables-addon instead of POM? It's quite hard to find this
project.


[1] http://www.linuxhorizon.ro/iproute2.html
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2009-05-16 23:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-16 23:28 Jan Rathouský [this message]
2009-05-17  7:21 ` port based routing for local generated connections Jan Engelhardt
2009-05-17  8:15   ` Jan Rathouský
  -- strict thread matches above, loose matches on Subject: below --
2009-05-16 23:40 Jan Rathouský

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=a14f8c120905161628i6b129e87m17f6db647115315c@mail.gmail.com \
    --to=jan.rathousky@gmail.com \
    --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).