10 Replies Latest reply: Feb 4, 2013 11:57 PM by sibroller2
defecta Level 1 Level 1 (0 points)

Hi folks,

 

I have found a consistent and duplicatable bug with the current Aiport Extreme firmware version 7.6.1 where if I try and create a custom port forward and do not specify UDP ports, only TCP ports, when I save the new rule and hit Update, the Airport Extreme forgets the TCP ports I specified. The only way I have been able to get it to accept the custom rule is by specifying the UDP port as well. And If I remove the UDP port after a successfull update, it forgets the TCP port as well.

 

I have on one occasion managed to get a custom rule without a UDP specified to successfully save and update when I a added a predefined rule at the same time but I been unable to duplicate this behaviour since.

 

I have the first Gigabit dual band 802.11n Airport Extreme (the one where you can choose between 2.4Ghz and 5Ghz Wifi but you cant have both at the same time) and I am using version 6.1 (610.31) of the Airport Utility.

 

Is anyone else having the same problems?


Airport Extreme