Re: port forwarding -- nat/ipfw

Adrian Urquhart wrote:
Also, you won't be able to test this forwarding from inside your LAN due to "double NATing" - you can't go out from your LAN to your public IP and then back in to a port forwarded machine. You need to use a machine external to your LAN. So things may be working as you want them to, it's just that you're testing incorrectly.

Excuse me?
Maybe I'm reading this incorrectly, but I'm using a double NAT setup, and I'm perfectly able to access webservers on my LAN (the "inside") using their public address.
How does this work?
I have a dynamic IP address on my ADSL router, so I use dynamic dns to get a name to match the ip address.
I have several servers on my LAN, but my firewall can only forward http (port 80) to one internal ip address. I solve that problem by letting the webserver on that internal address be a proxy for the other servers.

So, whether I type (from inside my LAN) http://www.google.com/ or http://name-of-internal-webserver.dyndns.org/ I get the correct page.

Just my 2 eurocents.
--
Torfinn Ingolfsen,
Norway
.

Relevant Pages

  • Re: port forwarding -- nat/ipfw
    ... IP and then back in to a port forwarded machine. ... machine external to your LAN. ... the webserver on that internal address be a proxy for the other servers. ... ADSL router is doing something which my setup isn't? ...
    (comp.unix.bsd.freebsd.misc)
  • RE: Setting up a new Terminal Server farm with NLB and Session Dir
    ... On your first node have IP for LAN and have an IP that you want your "farm" ... of the terminal servers. ...
    (microsoft.public.windows.terminal_services)
  • Re: MTA on non-standard port
    ... just to give you some idea: my home LAN has a FreeBSD box used ... with his/her laptop, which happens to be infected and sends spam, etc. ... Eventually they stated that I could send mail through their mail servers ... I've had two separate incidents of me sending mail to individuals, ...
    (freebsd-questions)
  • Re: DNS for Idiots...
    ... > DNS: Primary DNS is pointing to a DNS server on your LAN? ... > those to private IPs running on servers on the LAN, web servers, not DNS ...
    (microsoft.public.win2000.dns)
  • Event ID: 5719 on Windows 2000 CLIENT
    ... After bootup, I could not see other computers on the lan using Network Neighborhood. ... I notice that other people on this newsgroup have had a similar problem with a network client booting up and the replies they get are for KB articles dealing with this error on Servers, which won't fix the problem if it's on one of your clients. ...
    (microsoft.public.win2000.networking)