|
|
Mochuelo <hola@xxxxxxx> writes:
>On Wed, 11 May 2005 14:21:44 GMT, Andrew Schulman
><andrex@xxxxxxxxxxxx> wrote:
>>As you said, your router maps 80.35.x.x:80 to 192.161.0.10:12000. What
>>it doesn't do is to map 127.0.0.1:80 to 192.161.0.10:12000, or
>>192.161.0.10:80 to 192.161.0.10:12000. I think this is your trouble.
>>Within your LAN, a DNS lookup to personal.test.com is being resolved to
>>either 127.0.0.1 or 192.161.0.10, not 80.35.x.x. So the router doesn't
>>do its mapping.
>>
>>From one or more of the hosts in your LAN, what does 'host
>>personal.test.com' say? If it isn't 80.35.x.x, then you need to do one
>>of several things:
>No, when I ping personal.test.com from inside my LAN, I read
>"80.35.x.x". That works ok. The problem, I guess (with my little
>knowledge of networks) is that the router, when it receives a request
>for 80.35.x.x, does different actions depending on whether the request
>is outside or inside my LAN. If it is outside my LAN, PAT mapping is
>applied, and my page is correctly shown. If the request for 80.35.x.x
>comes from inside the LAN, the router interprets I want to configure
>it, and it does not do any PAT mapping, and directly asks me for the
>user and password to access the router.
It is very possible that it does different actions from inside than from
outside. That will be entirely up to the router software inside teh router.
Note that sending to 80.35.x.x the router will ask the external DNS server
for the route to that address, and discover that it is itself. It will
never send out the packets, but will deal with them itself. Then the
question is how does it deal with them.
I am surprised that it regards its external IP from the internal lan
as a request for its internal setup . But it will be a function of the
router. Not all routers will behave the same way.
>I don't believe this has not been faced by thousands of people before
>me. I guess there must be an easy solution.
Why would it be faced by thousands? Not that many people have your
particular router and of those that do, probably very very few want to do
what you do (access an internal computer via its external IP)
|
|