NATPMP

With an update to Airport Base Station 5.7 I got a new addon that makes me very curious. If you open up the config window and go to 'Options for this Basestation' a new window pops up. There I can mark a new field called 'activate NATPMP' under this it says 'only for Macs with OS 10.4 or newer'. Can anyone tell me what this is? I tried google, without any result.
sorry for the system is actually in German

The English version renders this as NAT Port Mapping Protocol. I tried Googling for this, and came up with this explanation:
http://www.rogueamoeba.com/utm/posts/Article/PMP-2006-01-01-17-00

Similar Messages

  • How to disable back to my mac with Windows airport utility?

    Setup is as follows:
    Modem > AEBS (latest version) > Windows 8.1 machine running IPSEC VPN server
    ..I cannot get the outside world to talk to the VPN server despite forwarding the required ports (500,4500,1701) so I enable debug logging on the AEBS and see a bunch of these.
    Mar  7 19:49:26 airport-extreme natpmp: Binding added for udp, 109.155.226.110:32771 to 10.0.1.2:4500 with lifetime 7200
    Mar  7 19:49:26 airport-extreme natpmp: Binding added for udp, 109.155.226.110:32769 to 10.0.1.32:4500 with lifetime 7200
    In AEBS I'm forwarding 4500 to IP .99
    4500 is BTMM right?
    So I'm thinking I'll disable BTMM on the AEBS and test again however the Windows airport utility won't let me disable/enable BTMM and I dont have another OSX machine on the network currently to use to check/change the setting.
    Any suggestions on how I can disable BTMM from the Windows tool?  Or without a tool at all?
    Thanks!!

    I strongly recommend whenever a router is seeming to cause issues.. you actually bypass it.. plug the computer directly into the modem and see if the vpn works. You need to get the simple easy to work before you attempt the much harder job of vpn passthrough on a known problematic device.
    If the vpn doesn't work still you have the vpn server or local firewall setup wrongly.
    If it works ok and the airport continues to give you grief.
    My advice is simple.. get another router. Bridge the AE and use it for Wireless. A cheap normal router (particularly if you purchase wisely one that has possible 3rd party firmware) is going to save you years of aging, worry, pain, and all round trouble. Particularly when you try to get things working Apple to Windows with their different upnp vs NATPMP protocols, it is just too hard.
    however I'm still seeing those binding messages in the log, as if it's still going somewhere.
    Some interaction with Apple is built into every Mac with iCloud ID at least. Turn off all the other clients in the network.. reboot the AE.. but I doubt it will make any difference. It might not be BTMM it might simply be the security protection of the username and password. 

  • Transmission web interface does not load until I restart daemon

    I'm prefer using the transmission web interface to manage my torrents, when I run the daemon and connect to kiwi:9091, it works fine (kiwi=localhost). However when I restart and try to connect to the web interface I am unable to connect.
    Google Chrome reports:
    Oops! Google Chrome could not connect to kiwi:9091
    and Firefox says:
    Unable to connect
    Firefox can't establish a connection to the server at kiwi:9091.
    Even though I've enabled the transmission service:
    # systemctrl enable transmission.service
    and the service is running after a fresh boot:
    $ systemctl status transmission.service
    transmission.service - Transmission Bit Torrent Daemon
    Loaded: loaded (/usr/lib/systemd/system/transmission.service; enabled)
    Active: active (running) since Wed 2013-03-06 12:10:05 GMT
    Process: 398 ExecStart=/usr/bin/transmission-daemon --pid-file /run/transmission/transmission.pid (code=exited, status=0/SUCCESS)
    Main PID: 444 (transmission-da)
    CGroup: name=systemd:/system/transmission.service
    └─444 /usr/bin/transmission-daemon --pid-file /run/transmission/transmission.pid
    When I restart the service, the web interface works fine.
    # systemctl restart transmission.service
    # systemctl status transmission.service
    transmission.service - Transmission Bit Torrent Daemon
    Loaded: loaded (/usr/lib/systemd/system/transmission.service; enabled)
    Active: active (running) since Wed 2013-03-06 11:20:48 GMT; 35s ago
    Process: 1313 ExecStart=/usr/bin/transmission-daemon --pid-file /run/transmission/transmission.pid (code=exited, status=0/SUCCESS)
    Main PID: 1314 (transmission-da)
    CGroup: name=systemd:/system/transmission.service
    └─1314 /usr/bin/transmission-daemon --pid-file /run/transmission/transmission.pid
    Mar 06 11:20:49 kiwi transmission-daemon[1314]: Loaded 2 torrents (session.c:1943)
    Mar 06 11:20:49 kiwi transmission-daemon[1314]: Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:72)
    Mar 06 11:20:49 kiwi transmission-daemon[1314]: Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:72)
    Mar 06 11:20:51 kiwi transmission-daemon[1314]: Port Forwarding (UPnP) Found Internet Gateway Device "http://192.168.1.254:8000/jd877ogd4w2/IG...p.c:200)
    Mar 06 11:20:51 kiwi transmission-daemon[1314]: Port Forwarding (UPnP) Local Address is "192.168.1.79" (upnp.c:202)
    Mar 06 11:20:53 kiwi transmission-daemon[1314]: Port Forwarding (UPnP) Port forwarding through "http://192.168.1.254:8000/jd877ogd4w2/IGD/upnp...p.c:277)
    Mar 06 11:20:53 kiwi transmission-daemon[1314]: Port Forwarding (UPnP) Port forwarding successful! (upnp.c:280)
    Mar 06 11:20:53 kiwi transmission-daemon[1314]: Port Forwarding State changed from "Not forwarded" to "Forwarded" (port-forwarding.c:93)
    wat?

    I too had the same problem as you. And then I found this:
    https://bugs.archlinux.org/task/31478

Maybe you are looking for