From: Sven-Haegar Koch <haegar@sdinet.de>
To: Jan Kirchhoff <kirchy@gmx.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: Special routing for incoming pop3-requests
Date: Fri, 5 Sep 2003 21:24:34 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.56.0309052121450.4129@space.comunit.de> (raw)
In-Reply-To: <3F58BB42.20306@gmx.de>
On Fri, 5 Sep 2003, Jan Kirchhoff wrote:
> I am new to this List and I'm not really sure if this is really an
> iptables-issue, but I think iptables is the tool I need for this:
nope, you need policy routing
> How do I get to work (with iptables-rules on server1?), that all packets
> from server1 port 110 that have a destination other than the LAN go out
> on fw2 but all other traffic goes to fw1?
> I need a special route based on source-ip and source-port. I do not want
> to rewrite the destination ip (which would not help since its already
> right) but have influence on the routing to the next gateway.
have a look at http://lartc.org/howto/lartc.rpdb.html
c'ya
sven
--
The Internet treats censorship as a routing problem, and routes around it.
(John Gilmore on http://www.cygnus.com/~gnu/)
prev parent reply other threads:[~2003-09-05 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 16:35 Special routing for incoming pop3-requests Jan Kirchhoff
2003-09-05 19:24 ` Sven-Haegar Koch [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.56.0309052121450.4129@space.comunit.de \
--to=haegar@sdinet.de \
--cc=kirchy@gmx.de \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox