All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bas Verhoeven <netfilter@bserved.nl>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: iptables NAT routing issues
Date: Thu, 10 May 2007 22:06:00 +0200	[thread overview]
Message-ID: <46437B28.5000805@bserved.nl> (raw)
In-Reply-To: <464372FE.1070802@plouf.fr.eu.org>

Pascal Hambourg wrote:
> Which option did you choose ?
We still have the outbound server DNAT-ing connections to the 
webserver's ip, that worked fine.
On the webserver we now mark all outgoing web packets:

# iptables -t mangle -A OUTPUT -s <webserver_inner_ip> -p tcp --sport 80 
-j MARK --set-mark 2

And we use iproute2 to forward them back to the outbound server:

# ip rule add fwmark 2 pref 10 table web.out
# ip route add default via <outbound_box_ip> dev eth0 table web.out

Couldn't test with CONNMARK, as the box doesn't ship with that, but MARK 
works great for now.

I did test your last option too, but that just didn't work and sounded 
very hacky-ish, not something we could rely on, even if it worked.


  reply	other threads:[~2007-05-10 20:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 21:16 iptables NAT routing issues Bas Verhoeven
2007-05-08 22:25 ` Jan Engelhardt
2007-05-08 22:33   ` Pascal Hambourg
2007-05-08 22:37     ` Jan Engelhardt
2007-05-08 22:46       ` Bas Verhoeven
2007-05-08 22:48         ` Maximilian Wilhelm
2007-05-08 23:03         ` Pascal Hambourg
2007-05-10 14:21           ` Bas Verhoeven
2007-05-10 19:31             ` Pascal Hambourg
2007-05-10 20:06               ` Bas Verhoeven [this message]
2007-05-10 22:14                 ` Pascal Hambourg
2007-05-08 22:37 ` Maximilian Wilhelm

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=46437B28.5000805@bserved.nl \
    --to=netfilter@bserved.nl \
    --cc=netfilter@lists.netfilter.org \
    --cc=pascal.mail@plouf.fr.eu.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.