In fact, the standard implies that if you want to determine whether a port is already mapped, you must send another map request. For example, you previously mapped private port 60000 to public port 50000, but lost state. Now you want to know what public port the server assigned previously for private port 60000. In this case, if you send a request to map private port 60000 to arbitrary port N, then you will receive a response containing the current public port mapping for that port, namely, 50000. If it wasn’t mapped, you’d receive the actual mapping you requested, namely N. After that, you can destroy the mapping by sending a request with lifetime 0 and external port 0.

If you want to know what the server’s *public* port 50000 is mapped to, then it doesn’t look like there is an operation for that query in the protocol. If you find a way in the RFC, I’m happy to add a method or take a patch.

If i have a application which will add NAT-PMP port automatically, i want to check whether this port is added or not? How i can do this?

If it fails to automatically get_gateway_addr() it throws an exception, even if you specify the gateway on the command line.

It should not call get_gateway_addr() if -g is passed on the command line.

Thanks for the regex. I’ve integrated it.

I noticed the get_gateway_addr for nt systems is still TODO.
I think the following pattern would work, the rest of the code should be exactly the same as the posix code. it works fine here.

>pattern = re.compile(“.*?Default Gateway:[ ]+(.*?)\n”)

Thanks for the suggest/bug report. The mutex was left over from when I tried to do a simple thread-safe queue for requests, as per the spec. I decided to leave it for 0.0.2, and forgot to remove the half-baked attempt.

I’ve removed it for now until the exception raising and handling code gets cleaned up a bit.

I really needed this one
I’m sure it would be useful for many python applications.
Thanks again.