From: cc <cc@ns.kdtc.net>
To: netfilter@lists.netfilter.org
Subject: local forwarding(?)
Date: Fri, 17 Jan 2003 19:15:19 +0800 (HKT) [thread overview]
Message-ID: <200301171115.h0HBFJZC013763@ns.kdtc.net> (raw)
Hi,
I finally got the bridge working and so far,
things look ok.
From the outside, I can goto the website. That's
no problem. The problem is for local machines
going to http://www.mydomain.com/, the firewall
doesn't seem to be redirecting it properly.
LAN users have to use http://192.168.11.10/ to
access the website instead of the www.mydomain.com.
I understand that the actual ip address skips
the firewall and goes directly to the machine.
From my boss' point of view(totally ignorant
that 192.168.11.10 = www.mydomain.com), he
doesn't like that. So I'm hoping that he
can access (locally) www.mydomain.com.
So far my firewall script (the lines pertaining
to the www port) is as follows:
$IPTABLES -t nat -A PREROUTING -p tcp -i eth0 x.x.x.x \
--dport 80 -j DNAT --to 192.168.10.11
$IPTABLES -A FORWARD -p tcp -i eth0 -d 192.168.10.11 \
--dport 80 -j ACCEPT
$IPTABLES -A FORWARD -p tcp -i eth0 --dport 80 -j DROP
(I'm not entirely sure about that last item. It looks
strangely invalid...but I could be wrong. I don't
even think I should have that there.. am I right?)
If all my LAN ips are of the 192.168.10.0 host,
and the web server is 192.168.10.11, how do I
get the LAN clients to go to www.mydomain.com and
have the firewall redirect the packets to 192.168.10.11?
As you probably can figure out, I'm a little confused.
Any help appreciated
next reply other threads:[~2003-01-17 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 11:15 cc [this message]
2003-01-17 11:38 ` local forwarding(?) Raymond Leach
2003-01-17 11:50 ` Narendra Prabhu. B
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=200301171115.h0HBFJZC013763@ns.kdtc.net \
--to=cc@ns.kdtc.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