FCC outs upcoming refresh of Apple's AirPort Extreme

A new filing with the U.S. Federal Communications Commission has revealed an updated AirPort Extreme wireless base station from Apple is forthcoming.

The new hardware was outed this week by the FCC and discovered by Engadget. The filing, made by Apple on June 16, shows a 3x3 802.11n access point, dubbed model A1408.

The label includes mention of AirPort IDs in both the 2.4GHz and 5GHz range, as well as an Ethernet ID. The hardware carries an FCC ID of BCGA1408.

The documents do not reveal what may have changed in the new hardware model, but it's likely the new hardware is set for imminent release given the timing of the FCC filing.

In 2009, Apple's then-unannounced Magic Mouse was revealed by the FCC, just after AppleInsider revealed it would be a multi-touch device. A few weeks later, the Magic Mouse was made available by Apple.

Last week, Apple updated its AirPort Utility, and the software contains references to a new fourth-generation Time Capsule and fifth-generation AirPort Extreme. No mention of a new Time Capsule was made in the latest FCC filings, but given that stock of the hardware has run dry along with AirPort base stations, it's a likely candidate for a refresh as well.

Various rumors have claimed that Apple may shift its base stations to run iOS. This transition could allow for more robust features, like print and media streaming services, integration with iCloud, and cached wireless software updates.

The implementation of dual networks - an internal (private /encrypted), and an external (unencrypted / guest network) was an excellent idea (and made me buy the basestation for that sole feature).
The current implementation however is flawed: it assumes you do not have any dns servers inside your internal network. I hope this will finally be corrected.

In the current Apple design, both networks (internal and guest) share the same DNS configuration (how stupid) as configured in DHCP.
If you do have a private DNS inside your network, and you do not allow the guest network to connect to internal addresses (which is exactly why you would have dual networks), then the guests can't reach your internal DNS and need to configure manually an external DNS server, which is too much hassle or too complex for most "visitors".

I have submitted bug reports and service requests, but after more then 3 years Apple still hasn't found this setup important enough to provide a solution.

Apple should open-source the firmware or at least provide details on how to configure the airport over snmp v3 as the current administration and logging options are really too limited.
--
Peter
(somewhere in Switzerland)

now suppose the new airport extreme runs on ios
given the fact that apple's airprint feature in ios is not supported on many printers
would it not be very logical to make the airport extreme a "airprint print server"?

Yes, the Airport Extreme has been updated. This has a model number of MD031AM/A, while the previous model was MC340AM/A, which I ordered, then returned, a few weeks ago. They've also dropped the price by $20, as noted by Jackberger.

Various rumors have claimed that Apple may shift its base stations to run iOS. This transition could allow for more robust features, like print and media streaming services, integration with iCloud, and cached wireless software updates...

...and AppleTV !!!

Why does somebody ask me a question, I can never understand, I can never provide the answer, but believe I can.

Airport base stations may be targeted at schools and small business. My setup is no high-end requirement - I used cheaper devices before that offerd site-to-site VPN and more configuration options on the firewall.

Example: Imagine a small hotel where administrative staff wants to access the internal servers and where an internal dns is configured. Visitors are on the public network.

The correct solution for apple would be to have separate nameserver fields for the guest and internal dhcp configurations.
and
Allow DHCP to be activated independently on both networks. Currently DHCP is either on or off on BOTH networks. That again makes no sense.

I have an internal DHCP ( open source: dnsmask) which allows much finer control over the settings that Apple offers, but it can't be used because airport base station needing DHCP on its external network.