X

AirPort Extreme 5.7 firmware (#3): More on an issue with public IP addresses -- Apple routers not to blame

AirPort Extreme 5.7 firmware (#3): More on an issue with public IP addresses -- Apple routers not to blame

CNET staff
2 min read

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.

It now appears that in at least some cases, the problem may be the presence a third-party router that does not provide the ability to connect to servers behind the NAT by way of the public WAN IP address of the NAT box.

In fact, Apple specifically tests their AirPort Extreme and Express routers for this capability.

MacFixIt reader Scott Rose writes:

"Although the problem is still not solved, at least I now know WHY the problem is happening... and Apple's Firmware Update is not to blame.

"Through a series of coincidences, I was actually lucky enough to get in touch with the engineers in Apple's Airport firmware division, and they were helping me to nail down this problem.

"Turns out that Apple takes great pride in the fact that they are one of the very few manufacturers who make routers that behave properly in this regards.

"So what was causing the problem on my network, then?

"Something I hadn't thought about... the Vonage Linksys RTP300 router that we're using for our Vonage VoIP service. Turns out that this router does not support clients behind the NAT connecting to servers behind the NAT by way of the public WAN IP address.

"Linksys is to blame, not Apple!

"And apparently, this feature may have actually been working in an earlier firmware update, but apparently, Vonage automatically pushes firmware updates to RTP300's, apparently without user notification."

In the absence of third-party routers like the aforementioned Linksys device, the public IP address functionality works properly with the AirPort Extreme 5.7 firmware.

MacFixIt reader Joshua Ochs writes:

"I am not seeing this problem with a nearly identical setup. I have no problem accessing the public IP of my Airport Extreme (firmware 5.7) from the internal LAN, using a dyndns alias. Everything works just fine."

Feedback? Late-breakers@macfixit.com.

Previous coverage:

Resources

  • pushes firmware updates
  • Late-breakers@macfixit.com
  • AirPort Extreme 5.7 firmwa...
  • AirPort Extreme 5.7 firmwa...
  • More from Late-Breakers