From: "Darrell Dieringer" <netfilter@darrelldieringer.com>
To: Big Daddy <bigdaddy@monster-solutions.net>, netfilter@lists.samba.org
Subject: RE: HTTP Port forwarding issues
Date: Mon, 8 Jul 2002 15:00:11 -0500 [thread overview]
Message-ID: <IMEDICLPAGAOCBLCCKLPGENCDLAA.netfilter@darrelldieringer.com> (raw)
In-Reply-To: <001f01c226b6$eb0a4f60$6702a8c0@internal.monstersolutions.net>
Hello,
Have you confirmed that the packets are leaving the firewall / router
(by using tcpdump, etc)? If they are, then it might be an IIS
configuration issue. I had some trouble forwarding http connections
to internal IIS machines (IIS4 on NT4 Server and IIS5 on Win2K Pro).
After much head pounding, I found the solution to my problem.
<begin offtopic>
If I remember correctly...
On the main property page for the web site in IIS, the "IP Address"
field should be set to "All Unassigned" and the port must be set to
the same one that is being forwarded. (ie, you must forward
$ext_ip:8080 to $int_ip:8080). Though there's nothing about http that
requires the ports to match, IIS has some trouble.
For instance, if your arrangement is $ext_ip:8080 to $int_ip:80, IIS
replies to the initial request for whatever page with an http redirect
(302, I think). Actually, it may only do this if the "IP Address"
field in the main propery page is set to something other than "All
Unassigned". That redirect tells the client to ask for the page on a
different port. If that port is blocked by your firewall or by your
ISP (as it is in my case), the client never receives the content
because the redirect was unsuccessful.
</offtopic>
It has been many months since I solved this problem for my own home
setup, so I don't remember all the details. After confirming that the
packets are indeed on the wire, examine both your firewall logs and
your IIS logs for a clue to what's going on.
I know I delved offtopic for netfilter, but hopefully it ends up being
helpful to a couple of people.
Darrell
-----Original Message-----
From: netfilter-admin@lists.samba.org
[mailto:netfilter-admin@lists.samba.org]On Behalf Of Big Daddy
Sent: Monday, July 08, 2002 2:38 PM
To: netfilter@lists.samba.org
Subject: HTTP Port forwarding issues
all,
for some reason i can get my smtp and pop3 to route from the
internet, but i cannot get http requests to forward correctly.
iptables -A FORWARD -p tcp -i eth0 -d $int_ip -p tcp --dport http -m
state --state NEW -j ACCEPT
iptables -A FORWARD -p tcp -i eth0 -d $int_ip -p tcp --dport smtp -m
state --state NEW -j ACCEPT (works)
iptables -A FORWARD -p tcp -i eth0 -d $int_ip -p tcp --dport pop3 -m
state --state NEW -j ACCEPT (works)
iptables -t nat -A PREROUTING -d $ext_ip -p tcp --dport smtp -j
DNAT --to-destination $int_smtp:25 (works)
iptables -t nat -A PREROUTING -d $ext_ip -p tcp --dport pop3 -j
DNAT --to-destination $int_pop3:110 (works)
iptables -t nat -A PREROUTING -d $ext_ip -p tcp --dport http -j
DNAT --to-destination $int_http:80
web server is running IIS5.
any help would be great!
Big D@ddy
next prev parent reply other threads:[~2002-07-08 20:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 19:37 HTTP Port forwarding issues Big Daddy
2002-07-08 19:44 ` Tom Eastep
2002-07-08 19:51 ` Big Daddy
2002-07-08 19:56 ` Tom Eastep
2002-07-08 19:57 ` Antony Stone
2002-07-08 20:03 ` Big Daddy
2002-07-08 20:07 ` Antony Stone
2002-07-08 20:11 ` Stewart Thompson
2002-07-08 20:39 ` Big Daddy
2002-07-08 20:42 ` Antony Stone
2002-07-08 19:49 ` Antony Stone
2002-07-08 19:50 ` Stewart Thompson
2002-07-08 20:00 ` Darrell Dieringer [this message]
2002-07-08 20:25 ` Nathan Cassano
2002-07-08 20:50 ` Antony Stone
2002-07-08 21:20 ` Adam D. Barratt
2002-07-08 21:35 ` Nathan Cassano
2002-07-09 9:52 ` Jan Humme
2002-07-09 14:15 ` tcp/udp ports (was: Re: HTTP Port forwarding issues) James Sneeringer
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=IMEDICLPAGAOCBLCCKLPGENCDLAA.netfilter@darrelldieringer.com \
--to=netfilter@darrelldieringer.com \
--cc=bigdaddy@monster-solutions.net \
--cc=netfilter@lists.samba.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