All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Ray Leach <spoons@rchq.co.za>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: Multi ISP router/firewall ...
Date: Wed, 28 Mar 2007 08:18:26 +0200 (MEST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0703280816500.32661@yvahk01.tjqt.qr> (raw)
In-Reply-To: <1175061118.21066.34.camel@rayw.internal>


On Mar 28 2007 07:51, Ray Leach wrote:
>
>I tried both methods - iptables using the ROUTE target as well as using
>iptables to mark the packets, then using iproute2 to lookup and route
>using a table with an ip fwmark rule.
>
>In both cases, the traffic is routed out and return traffic comes back
>in the correct interface, but it does not get NATed backed to the
>client.
>
>iptables -A FORWARD -i eth0 -p tcp --dport 80 -s 10.0.0.3 -j ACCEPT
>iptables -A FORWARD -i eth4 -p tcp --sport 80 -d 10.0.0.3 -j ACCEPT
>
>iptables -A FORWARD -t mangle -p tcp --dport 80 -s 10.0.0.3 -j MARK
>--set-mark 0x4

The routing decision is done before the FORWARDing chain is entered.
Try moving the MARK to INPUT.

>iptables -A POSTROUTING -t nat -o eth4 -p tcp --dport 80 -s 10.0.0.3 -j
>SNAT --to 10.1.0.2
>
>ip rule del fwmark 4 table 4 priority 32000
>ip route flush table 4
>ip route add table 4 default via 10.1.0.1
>ip rule add fwmark 4 table 4 priority 32000
>ip route flush cache
>
>
>What am I doing wrong?
>
>Looking in /proc/net/ip_conntrack I can find an entry for http traffic
>from machine at ip 10.0.0.3 created by the SNAT rule above. When the
>traffic returns back in eth4 it seems to disappear on the firewall ...

Jan
-- 


  reply	other threads:[~2007-03-28  6:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 15:32 Multi ISP router/firewall Pierre JUHEN
2007-03-28  5:51 ` Ray Leach
2007-03-28  6:18   ` Jan Engelhardt [this message]
2007-03-28  6:43     ` Ray Leach
2007-03-28 11:42       ` Raymond Leach
2007-03-28 12:21       ` Ray Leach
2007-03-28 17:15         ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2007-03-27 12:52 Ray Leach

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.61.0703280816500.32661@yvahk01.tjqt.qr \
    --to=jengelh@linux01.gwdg.de \
    --cc=netfilter@lists.netfilter.org \
    --cc=spoons@rchq.co.za \
    /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.