From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Fun with the mangle table + LARTC
Date: Mon, 01 Aug 2005 08:01:38 -0500 [thread overview]
Message-ID: <42EE1D32.8010308@gmx.co.uk> (raw)
In-Reply-To: <200508010916.37911.gdh@acentral.co.uk>
Gavin Hamill wrote:
> Hi - this is one of those "not sure if it's netfilter or LARTC" issues,
I'm not sure either, but here's a guess.
> -A POSTROUTING -s 10.0.0.0/255.255.255.0 -o eth1 -j MASQUERADE
> -A POSTROUTING -s 10.0.0.0/255.255.255.0 -o eth2 -j MASQUERADE
Why MASQUERADE? Try using SNAT rules.
> using tcpdump I can see the outgoing and reply packets on eth2 with the
> correct source address (i.e. the one the ISP on eth2 gives me) set, but
> tcpdump on eth0 shows only the packets from the MASQ'd host - the replies
> from the Internet host are not passed through.
Is there anything dropping the packets in FORWARD? Try tracking with
iptables LOG rules rather than tcpdump.
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
next prev parent reply other threads:[~2005-08-01 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 8:16 Fun with the mangle table + LARTC Gavin Hamill
2005-08-01 13:01 ` /dev/rob0 [this message]
2005-08-01 15:41 ` Gavin Hamill
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=42EE1D32.8010308@gmx.co.uk \
--to=rob0@gmx.co.uk \
--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