Currently Being ModeratedJun 30, 2012 8:07 PM (in response to defecta)
Further testing shows that selecting a predefined rule and changing the ports to suit my purpose allows for a successful save and update of the port forwarding rules. There is definitely something broken on this thing. I would feel better about it if I wasn't the only one. Meaning its probably just a firmware issue.
Currently Being ModeratedJul 5, 2012 1:30 PM (in response to defecta)
I experience similar problems mapping only UDP ports. Unless I specify TCP and UDP ports at the same time the destination ports are left out / forgotten when saving and updating the configuration.
Currently Being ModeratedJul 7, 2012 11:07 PM (in response to defecta)
I too have found the disappearing TCP port to be an issue in the same version of Airport Utility. I tested entering and saving the settings using the Airport Utility version 5.6 and it keeps the settings.
Currently Being ModeratedOct 3, 2012 8:51 AM (in response to defecta)
Ah, good to see others have this problem too. I spent hours last night isolating it. Unlike defecta, I can't just edit it to get it work and have to enter a number for both UDP and TCP to get it to stick. However, if I select something in the pull down meny like Personal Web Sharing, the selection sticks without entering the extra UDP number. That only applies to a few of my items though.
Currently Being ModeratedOct 3, 2012 9:07 AM (in response to Vinoh)
I just found out that if I use the Airport Utility on my iPhone to change the port settings, it works fine. So it seems to be a bug in Airport Utility on the Mac.
Currently Being ModeratedNov 28, 2012 6:13 AM (in response to defecta)
Airport Utility 6.1 on Mac, when adding an IPv4 Port Mapping will silently throw away TCP ports if you don't enter UDP ports also.
After clicking Update, my AirPort Extreme 802.11n (3rd Generation) restarts, the port mapping entry is added but the ports are all empty.
The iPhone client lets you edit existing entries but won't let you tap Done unless you fill all UDP and TCP port fields. Once the 'Done' button becomes active, you can clear the UDP ports, tap Done and it will save correctly with TCP ports only (and will show up as such in Mac Airport Utility).
- Very poor QA by Apple - wanting to add a TCP port only without UDP ports is the common case, not the exception.
- It seems to be impossible to map a different public port to a given private port number?
- Why does the AirPort have to restart just for changing the port forward config?
Other modern routers with web interfaces don't need to.
Currently Being ModeratedNov 29, 2012 5:24 AM (in response to Hubert7)
Thanks guys, and Hubert in particular!
Really helped me out, there!
I fully agree with with you on your thoughs - this is poorly done by Apple.
Message was edited by: Binker__nor
Currently Being ModeratedNov 30, 2012 7:20 PM (in response to defecta)
Same for me. I've reported this to bugreport.apple.com and the bug ID issued is 12791528
Currently Being ModeratedFeb 4, 2013 11:57 PM (in response to defecta)
I have Time Capsule 2nd gen and OS X Server admin.
I've seen Server admin can put only TCP ports in TC config and it apparently didn't work thru Airport Utility.
So just a moment ago I guessed it requires at least something to be in the UDP fields.
I tryed to save port mapping with a space for UDP and it worked.
Although this is still a bug but at least this allows you to regain manual control over port mapping.
Hope this "space" port redirect won't break anything.