All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@lists.netfilter.org
Subject: Re: iptables NAT routing issues
Date: Fri, 11 May 2007 00:14:07 +0200	[thread overview]
Message-ID: <4643992F.4050001@plouf.fr.eu.org> (raw)
In-Reply-To: <46437B28.5000805@bserved.nl>

Bas Verhoeven a écrit :
> 
>> Which option did you choose ?
[...]
> On the webserver we now mark all outgoing web packets:
[...]
> And we use iproute2 to forward them back to the outbound server:
[...]

Ok. You seem to know how to use advanced routing, I am a bit surprised 
you said you "weren't aware of that option".

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

The 'CONNMARK' target and the 'connmark' match were included in the 
kernel 2.6.10. Earlier kernel versions had to be patched with the 
patch-o-matic-ng.

> 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.

Huh, what last option ? I don't know what you're talking about. ;-)


  reply	other threads:[~2007-05-10 22:14 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
2007-05-10 22:14                 ` Pascal Hambourg [this message]
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=4643992F.4050001@plouf.fr.eu.org \
    --to=pascal.mail@plouf.fr.eu.org \
    --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 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.