>> Hi, I have a question about nat functionality.
>> The problem is that I opened a port to access my private network. I put a
>> server to listen on port 10000 and then I get my public ip address (using
>> a
>> service such as whatismyip.com) The problem is that when I telnet to this
>> public ip and port, the server in my machine doesn't get anything, but if
>> I
>> try this from "outside", then the server receives the conection! How can
>> this be? Why putting the public ip inside my private network doesn't
>> work?
>> Shouldn't this be treated as any other conection? (Of course, if I
>> connect
>> to the loopback or private ip, the server receives ok)
>
> Most NAT routers only recognize the public IP when they receive packets
> on the outside. When you're on your LAN, you have to use the private IP.
>
> There are some routers that will forward the public IP on either side,
> I've heard that D-Link does.

Hi, thanks both for your answers. The router I use is a ziyxel which seems
to be a bit weird.
So according to this, my question would be, why is the conection not done?
In what part does the packet get lost?
If I do a telnet to my own public address, this should pass the nat as a
usual outgoing conection, right? Or does the nat somehow realizes that I'm
trying to simulate a conection from the outside? If that weren't the case,
then I presume the packet is received by some outside router which sends it
back to the nat again, is this correct?
I'm certainly missing something, because I don't see why shouldn't the
packet be received by the nat, given that the dst port is opened.
I appreciate in advnace any .