Thanks DaZZa,
When I choose the www.sitewhatever.com.au address (not the internal
192.168.x.x) it goes to the ADSL modem. That's from internal.
Many places in websites these days running CMS or Blogging software
point the site back to the www.sitewhatever.com.au in its links rather
than localhost or 192.168.x.x.
So even from internal I need to get to the site just by putting in
whatever everyone else puts in to get to the site. So it's by the IP
address assigned to the modem after resolution by DNS.
I would have thought a browser would go out and then back in through the
ADSL but it does not.
(from outside the ADSL public IP address and port 80 gets NAT'd and
forwarded correctly to the internal webserver IP= 192.168.x.x (in a DMZ).
What does everyone else do?
Ben
DaZZa wrote:
On 1/4/07, Ben Donohue <[EMAIL PROTECTED]> wrote:
Hi all,
I'm having trouble getting to an internal web server which the outside
world can see.
I have an ADSL modem forwarding port 80 to an IPCOP firewall.
This firewall forwards port 80 to the webserver (Centos 4.4)
From outside the website comes up fine.
From internal I get the webpage of the ADSL modem rather than the
website.
Is this because I have to split off internal DNS differently from
external DNS?
Are you trying to access it via the server's NAT'd address, or via the
IP address allocated to the modem?
If you want to access it internally, you need to use the RFC1918
address used by the web server, assuming you're using one. I.E.
instead of accessing it via the live IP address the modem/firewall
translates port 80 to, you need to use the 192.168.x.x {or whatever
RFC1918 range you're using} address.
I'd also look at the modem allowing access to its web interface via
the outside IP address if I were you - that's asking to be hacked.
DaZZa
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
