From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: Chris Frederick <cdf123@cdf123.com>
Cc: Ramin Dousti <ramin@cannon.eng.us.uu.net>, netfilter@lists.netfilter.org
Subject: Re: iptables port forwarding not working
Date: Fri, 27 Jun 2003 16:07:45 -0400 [thread overview]
Message-ID: <20030627200745.GF11167@cannon.eng.us.uu.net> (raw)
In-Reply-To: <3EFC9618.5070706@cdf123.com>
On Fri, Jun 27, 2003 at 02:08:08PM -0500, Chris Frederick wrote:
> I'm running SuperScan 3.00 on a Windows 2000 box and scanning all ports
> 1-1000 to test the firewall.
>
> Are you saying to change the:
> $IPTABLES -A FORWARD -p tcp -i $INET_IFACE -d $INET_IP --dport 80 -j ACCEPT
> to:
> $IPTABLES -A FORWARD -p tcp -d 2.2.2.3 --dport 80 -j ACCEPT
> $IPTABLES -A FORWARD -p tcp -s 2.2.2.3 --sport 80 -j ACCEPT
> or do both? Or did I miss the point?
The first one.
The second one is not needed if you already have ESTABLISHED rule.
>
> If a packet was forwarded to the new destination correctly, but the
> reply couldn't get through (due to the error you pointed out), would
> that show up as a closed port on the scanner? That would explain why
> it's not showing as open. When I get home I'll test it again with
> tcpdump and nmap.
>
> And for the https, couldn't I use a cert made for the router(2.2.2.2) on
> ther apache server(2.2.2.3), and fool the client browsers to think that
> they're the same machine? This is only for a test environment, so if
> the cleints testing it get invalid cert errors it's no big deal.
Certs are based on DNS.
Ramin
>
> Thanks for the info, I'm gona read up on the FORWARD rules a bit more.
> I think I misunderstood how they worked.
>
> Chris Frederick
>
prev parent reply other threads:[~2003-06-27 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 18:06 iptables port forwarding not working Chris Frederick
2003-06-27 18:32 ` Ramin Dousti
2003-06-27 19:08 ` Chris Frederick
2003-06-27 20:07 ` Ramin Dousti [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=20030627200745.GF11167@cannon.eng.us.uu.net \
--to=ramin@cannon.eng.us.uu.net \
--cc=cdf123@cdf123.com \
--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.