Re: Masqed client cannot access masqed server
Artom wrote:
> I have a small home LAN with all internal machines - including the
> webserver this post is about - SNATed to the single (dynamic) IP address
> my ISP gives me. Note that my NAT router and my server are different
> machines. I'm using the TLPD IP-Masq HOWTO's stronger iptables ruleset,
> with some small PORTFW modifications for a file sharing app and the
> aforementionned webserver.
>
> I can access my webserver internally on the 192.168.0.0 network, and
> people outside can access it using my public IP address (thanks dynamic
> DNS!), but I can't access it from the inside using my public IP address,
> i.e. I can't go out and then back in again. I can ping my public IP
> address from the inside, and I can ssh to it from the inside too, but
> port 80 connections time out.
>
> This isn't a real problem, but out of curiosity, what would be the
> solution?
Think again.
I've seen this problem, accompanied by the answers, around for a while
by now.
May I ask You a personal favour (only because I am too lazy to do it
myself):
Please make a picture of how a connection between an inside web browser
request to Your public IP would look like. From the beginning over all
MASQ'ing and everything to Your server and back. And step-by-step.
Make it look cute, and You'll be the author of the "Local-MASQ-HowTo",
which will be read worldwide.
Sorry for being brute, Jack.
--
----------------------------------------------------------------------
My personal reading of the string "MicroSoft" expands to "NanoWeak"...
|