AirPort Extreme 5.7 firmware (#2): More on an issue with public IP addresses
AirPort Extreme 5.7 firmware (#2): More on an issue with public IP addresses
We previously reported on a change brought about in the AirPort Extreme 5.7 firmware update where the NAT implementation disallows access to public IPs from inside the private network on some configurations.
Several readers have now corroborated the issue.
MacFixIt reader Simon Leemann writes:
"I experienced the same Scott Rose reported. I used to be able to access one of my Macs (NAT and DCHP, necessary port forwarding on) behind the AirPort Express by using its public name like myMac.dyndns.org. Ever since the update, I have to use its private (Bonjour) name like myMac.local. Of course this work-around only works from inside the LAN. However to do the same (for example ssh login) from the outside I obviously have to use the global name. It's a pain to have to use two different names depending on where you are. Since I normally use a PowerBook, the machine is sometimes inside and sometimes outside the LAN. A login on the other machine has to be done differently depending on where I'm currently at. IIRC it wasn't always that way and I'd like to see Apple make it work the way it used to."
If you are experiencing a similar issue, please let us know.
Previous coverage:
Resources