From: Jim Laurino <nfcan.x.jimlaur@dfgh.net>
To: netfilter@lists.netfilter.org
Subject: Re: Forwarding while on same subnet...confusions (nfcan: addressed to exclusive sender for this address)
Date: Thu, 25 Nov 2004 10:07:11 -0500 [thread overview]
Message-ID: <20041125150711.GA27717@salty> (raw)
In-Reply-To: <dc56727e041123110948cb3a14@mail.gmail.com> (from +nfcan+jimlaur+77cd5e9588.mismith356#gmail.com@spamgourmet.com on Tue, Nov 23, 2004 at 14:09:12 -0500)
On 2004.11.23 14:09, Mike Smith - mismith356@gmail.com wrote:
> Hello All,
>
.......
> and then, after some google'ing and reading:
>
> iptables -t nat -A POSTROUTING -s 138.1.89.6 -p tcp --dport 80 -j SNAT
> --to 138.1.88.246
>
One more observation.
The postrouting is looking for packets with a *destination* port 80.
I think this rule is meant to deal with packets from the apache server
returning to the client. I think apache will have a well known
*source* port of 80 in this case, the destination port is random.
You could look with a sniffer to check.
Or look at the packet counters to see if it is matching.
........
prev parent reply other threads:[~2004-11-25 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 19:09 Forwarding while on same subnet...confusions Mike Smith
2004-11-24 16:06 ` Jason Opperisano
2004-11-25 15:07 ` Jim Laurino [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=20041125150711.GA27717@salty \
--to=nfcan.x.jimlaur@dfgh.net \
--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