i managed to solve my issue...
i had 7.5.2 running in bridge mode with this topology:
internet adsl router -> airport extreme 3rd gen (wan port)
gigaethernet switch -> airport lan port
various wired devices connected to eth switch (including imac)
various wireless devices connected on 2.4ghz to airport (apple tv among them)
time capsule expanding extreme wireless range
this network was running reliably for more than a year.
when the airport detected 7.6 was released by apple it went to orange blinking....
everything kept running with a single exception: wired to/from wireless were not handling dhcp requests as before
yes this happened without anybody touching anything on the net (it just stopped working)
first thing i did to troubleshoot it was updating the airport to 7.6 using the imac (airport tool 5.5.3 on lion).
after flash was complete... airport hanged and nothing worked (not even internet connectivity)
factory defaults restore by holding reset button on powerup....
tried again setting the aiport with initial values to allow simple internet connectevity.... no luck
every time i tried to save the settings the airport hanged and factory rest was required....
i thought it was 7.6 issue...... so rolled back to 7.5.2
tried again and again (factory reset with button and setting basic bridge to get internet.... no luck)
thought it was osx 5.5.3 airport tool... so downloaded (by connecting windows laptop directly to dsl router) the 5.5.3 airport tool for windows..... tried again all the process ... no luck
then i tried factory resetting again and configuring basic setting with ipad... and it worked.... i had basic internet thru airport...
so back to osx airport tool to configure the remaining settings not available on ipad simple tool (like enabling 5ghz etc)... and airport hanged.... rebooted and i noticed all changes were not saved (only the ones done from ipad were kept)... tried many times.. no luck...
so i thought it was 5.5.3 tool that was faulty.....(tried 5.5.2 on snow leopard)... same thing...
i then turned off airport extreme thinking it was hardware faulty and tried everything again on the timecapsule as main station... same results...
disconnected the lan cable from the airport (kept only the wan connection) and everything worked good over wireless (osx lion 5.5.3 with airport 7.6).. everything worked fine lastly...with one exception:
dhcp requests are still not relayed between wired and wireless segments...
it seems airport 7.5.2/7.6 and/or airport tool 5.5.2/5.5.3 has some kind of issues when having wired+wireless connectivity when configuring... if i connect the wired ethernet i can replicate the issue everytime...
too bad it took me 2 days of testing all possible combinations to find out what apple did not...
please apple fix this asap....
hope it helps somebody out there ....
It just occurred to me that I didn't even have Airport Utility open when my units started flashing-- and the option to monitor my Airport devices was not checked. In thinking about what others have written, I still think that some of the devices automatically recognize that there's an update and stop working properly until it's performed. I'll see if things change, now that I've un-checked the update option when opening AU. I hope this makes the difference. Thanks again.
yes i confirm this... my net started to work unreliably (no dhcp assignment to apple tv) as soon as the airport extreme detected the update was available...
i think there is one of two possibilities:
option 1 (unlikely): apple pushes something to airports over the net that forces users to update or have crippled networks
option 2 (most likely): firmware has bugs that appear when the "update available" flag is detected (probably apple never tries new firmware with another newer firmware also available)
I just relived my whole nightmare through your description, Juan. I had very similar experiences and seem to have a similar network design. As I'd mentione earlier, once I re-installed, from scratch, the Extreme base station and ethernet-connected Expresses, the wirelessly-connected Expresses didn't need to be re-set. They retained their settings and worked fine, but everything on the Ethernet part of my network had to be completely re-configured. This was an absolute mess! I can't even imagine what the Apple techs must be going through fielding requests for help. I sure hope it makes them sit up and take notice before ever again releasing an update before it's ready. I completely agree with you: with all the complaints of similar issues, I can't believe that some of these problems didn't show up during beta testing!
By the way, unless I missed it, you didn't mention ever re-setting your dsl modem. After re-installing my main Extreme base station, I disconnected my cable modem and disconnected everything from it. I then re-connected the co-ax cable and the power. This forced a new Internet signal and my entire network, wired to wireless, is working as perfectly as it was before this horrible update. If you haven't completely reset your DSL modem, that may just take care of your DHCP issues. Good luck.
hmmm i dont remember resetting the dsl router (as every time i wanted internet access i just connected a female-hemale rj45 adapter to bridge the eth switch to the dsl router and everything worked fine (of course with all wireless devices isolated from internet))
what i did as workaround a few minutes ago was setting the dsl router in bridge mode and changing airport to "share a single ip address" mode....
i now have to deal with the nat forwarding to airport itself.... but im happy to have all wireless/wired devices running happily again......
btw.... too bad airport requires reboot to make simple changes (like changing a password, or adding/editing/deleting a nat port)...... my very cheap dsl router does almost everything over a web without ever rebooting unless i want to change core services like type of dsl line encapsulation and such....)
hope we get TESTED 7.7 "dont reboot for everything" airport firmware sometime in the future
I completely agree about the more simple, "don't reboot for everything," update... only it had better be WELL-TESTED! I now have cable Internet, but had dsl for years & years. I remember setting up my last dsl modem, which had a router built in, in bridge mode and deactivating the router component, allowing just aiport, alone, to manage the routing-- just as you've now done. This was recommended by both Apple and my isp. Although I can't specifically remember what they'd said, I believe they thought I'd get faster speeds and less network interference that way. (With DSL you can certainly use all the speed you can get!) I also remember being told by my ISP that everytime the Airport was rebooted, the modem should be re-booted as well. At the very least, I'm pretty sure that if you haven't re-booted your modem, after going through all the re-configuring you've done, you should probably re-set it. However... if it "ain't broke," right? Now that you're completely happy with the way things are working, maybe you should just leave well enough alone. So long as your speeds are OK and your connectivity is stable, why bother? I'm a complete perfectionist and there have been too many times when I've messed things up by trying to make them more perfect. Just onemore thing for you to consider.... Glad you've got both wireless and wired working again! This was NOT the way I'd planned on spending my weekend, but at least everything's back to normal again!
I tried to go back to version 7.5, but my system is still broken even after a complete refresh. I've abandoned the Airport Extreme/Express combination in favor of my DSL wireless router, which to my surprise I am finding has better signal strength throughout the house. I wasted several hours this evening trying to fix a system that was working perfectly fine until Apple mucked it up. Why Apple? It just doesn't work!
Have you guy's tried switching the channel on the AP to make sure it's not an interference issue ?
For folks who are mentioning that 7.5.2 works better, note down the channel the wireless network is on 7.5.2.
Upgrade the AirPort Base Station and check what channel 7.6 pick's and if it's a different channel, then try going back to using the previous channel.
Also try physically unplugging and replugging the unit from the power supply if things don't go well after the upgrade.