4/20 Airport Bug?

OK, I've had 3 different clients call me today, all of whom use the new Airport Extreme 802.11n router, all of whom had their internet/airport stop working sometime last night or this morning. They all have different internet providers (some on cable, some on DSL), and all have had the same symptoms, airport shows green status light, but there is no wireless network to be found, and no connection to the internet can be had even when using an ethernet cable from the airport. Connecting straight to the modem works fine, but the airport, despite all settings being correct and the green status light, is completely oblivious and unable to broadcast it's network.
Anyone know of anything that expires, updates or anything else that would make 4/20 or 4/21 a day where airport extremes would stop working?

We've had this same issue since 4/15, exactly when I was transmitting my tax return. Everything "works" (internet connection found, my computer and the airport communicate, green light, etc) but we just can't connect to the internet. It all started when an auto update in Aiport Utility downloaded. I re-downloaded the update. I am currently connected straight to my cable modem. This is driving us nuts! We have 2 brand new macbooks in our house and they can't even get on the internet. Kevin McK--Please post any resolution you find when you go to your clients.

Similar Messages

  • Airport bug, lost wifi...

    Hello,
    I have a macbook pro 15 inch (mid 2009) with snow leopard and for several days, sometimes the airport bug. Wireless internet is cut, it is impossible to reconnect to the network. I can not restart AIRPORT, sometimes it is marked "no card installed". I need to restart the computer, sometimes at least 3 times to find the wifi signal.
    I made no program installation, no modification system and I tried five different important wireless network. I tried to delete AIRPORT preferences and then put it back but it did not work. I do not know what to do. I have a problem since "Security Update 2011-005".
    The wifi working fine on my bootcamp partition.....so it's not an hardware issue;
    thank you

    Having the exactly same issue. At least once a day, Airport drops the connection and deactivates itself. Impossible to re-activate it, so I need to reboot the computer (sometimes 3 to 5 times in a row) in order to have Aiport reactivated.
    I'm using a MacBook Pro 13" (mid 2010). The problem appeared with an update. It was so annoying that I installed Linux (Ubuntu) and it works just fine, which makes me think the issue is not hardware-related but strictly softare-related.
    I don't know if Grégoire found a solution to the problem, but I would be very interested in any clue that might help me out. I've tried every suggestion found on the Apple website, but nothing helped so far. It's been more than a year now... Having a very bad experience with my MacBook Pro...

  • 10.6.6 - Major Airport Bug?

    Hi Folks,
    Recently upgraded to 10.6.6 (MacBook Pro) and I've noticed an odd Airport bug. The sequence is like this:
    Cold Boot > Connect to Wifi > Surf Net > Close Lid & Sleep > Open Lid and Connect to Wifi
    At this stage I cannot connect to the internet. I have a valid IP and its the same network. AirPort is showing connected. The only way to be able to surf again is to completely reboot (And it might take more that one reboot)
    Its happened on two entirely separate networks. One is a open college network that worked flawlessly on 10.6.5. The other is a simple home network that again worked perfectly under 10.6.5.
    The only thing I've been able to ascertain is I can't get a new IP. I constantly get the same one even when I cycle Airport. Eventually on a reboot I get a new IP (DCHP is on etc). On the packet side of things, lots of received packets but no many sent.

    I feel 99.9% confident in saying this is not a bug in the update. If it were, we'd be seeing a lot of reports, and we're not. I sleep and wake my MacBook Pro many times per day every day and never have trouble with wireless access.
    So, the question is, what's wrong with your machine? Try some of the recommendations in my post here:
    http://discussions.apple.com/message.jspa?messageID=12952906#12952906
    Hopefully, something there will lead you to a resolution of your problem.

  • Another Airport Bug

    <div style="-webkit-border-radius: 15px; border: 1px solid grey; background: #eee; padding: 5px;"
    I've been searching all over both Apple's knowledge base and the rest of the internet because of this problem. My Macbook Pro's built-in airport is totally unusable,
    The menubar item displays the "airport on" image, but the only two options are "turn airport on," which does nothing, and the "Open Internet Connect..." item. Internetc Connect says the Airport is on, and the status is
    "Status not availible"
    "Status not availible"
    "Status not availible".
    The Airport will automatically connect to open wireless networks, but does not inform the user. The Airport menu bar remains the same.
    Has anyone encountered this problem, or have a suggestion?
    17" Macbook Pro Core 2, 2GB Ram, Bootcamp'd   Mac OS X (10.4.8)  

    More info: these people seem to have the same bug::
    http://discussions.apple.com/thread.jspa?messageID=4176858
    This is another instance -- but the helpful responder confuzed the built-in airport with a base station.
    http://discussions.apple.com/thread.jspa?messageID=4004411
    Another thread; this seems to be a fairly common bug:
    http://discussions.apple.com/thread.jspa?messageID=4087082&
    I submitted a bug report on this, so hopefully Apple will get back to us (affected users).
    Also: I don't seem to be able to edit my first message - that is REALLY annoying

  • Airport BUG

    Whenever my computer wakes up from sleep it is incapable of detecting wifi networks!
    Solutions attempted:
    clearing stored preferred networks - does nothing
    turning airport off and then on again - does nothing
    restarting the airport extension (kext via command line) - results in failure of the airport card until reboot (can't reload it)
    reboot - after reboot everything is fine again and wifi function works perfectly.
    Despite reboot fixing the problem temporarily, this is frustrating enough to make me move to linux if I can't fix it soon. I'm guessing this is a bug in the most recent airport software update, because I haven't had this problem until recently and don't think I've modified any settings that would affect this.
    Any assistance would be much appreciated.
    PowerBook G4   Mac OS X (10.4.8)  

    Appears that quite a few folks are having this problem with OS X 10.4.8 using WPA2 security...
    (ref: http://www.macfixit.com/article.php?story=20061004074201292 &
    http://docs.info.apple.com/article.html?artnum=304482)
    Try the following, in order, (sorry if there's any redundancy to what you may have already tried) until resolved:
    1a. Delete Preferred Network(s)
    - System Preferences > Network > AirPort > Configure
    - In the "By default, join:" pull-down menu, select "Preferred networks"
    - Delete the network(s) you regularly use from the list
    1b. Delete AirPort Keychain Entries
    - Launch the "Keychain Access" application located in Applications/Utilties.
    - Click on the "Kind" filter at the top, and look for any "AirPort network password" entries...and delete them.
    - Restart, or log out then back in.
    1c. Add Preferred Network(s)
    - System Preferences > Network > AirPort > Configure
    - In the "By default, join:" pull-down menu, select "Preferred networks"
    - Add the preferred network(s) using the "+" button.
    - Restart or log out then back in.
    2. Run the Disk Utility to repair Disk Permissions.
    3. Turn off the Mac OS X Firewall
    - System Preferences > Sharing > Firewall
    - Click the "Stop" button.
    4. Move System Configuration Files
    (Note: You will have to reestablish your network connections settings.)
    - Go to /Library/Preferences
    - Move the SystemConfiguration folder and com.apple.networkConfig.plist file to the desktop.
    - Restart your Mac. (Note: OS X will rebuild the files that are now sitting on your desktop. If this doesn't resolve the issue, you can move the folder & .plist file back to it's original location.)

  • Airport Dying....

    I have 10.6.2 - all the updates. So I'll be online, and my signal will just drop. I have an airport extreme router but I know that's not the problem because this problem has happened on 3 different networks, including a linksys and dlink. So my connection drops... sometimes it comes back, sometimes it doesn't. Sometimes airport still shows as connected but it just doesn't work... in any case if I turn airport off, it won't let me turn it back on - when I hit turn airport on nothing happens.
    I know there's a really long thread here on dropping wi-fi signals, but I dont even know where to start with that one. It's my understanding there are a ton of airport bugs in that latest update they made.
    Is there anything I can do now or should I just put up with it until another update comes out?

    HI,
    Try a different Airport Channel.
    Open AirPort Utility, located in the Utilities folder in the Applications folder on a computer using Mac OS X.
    Select the device you’re setting up, and then click Manual Setup. Enter the base station password if necessary
    Click AirPort in the toolbar, and then click Wireless.
    Choose a new channel from the Channel pop-up menu.
    Carolyn

  • Airport problems with 10.5.3

    I bought a macbook for the first time in october last year after the release of leopard after using windows for 10 years. I can honestly say that this thing is the biggest piece of junk i ever purchased.
    I have had internet problems since day one. It took me buying 3 different routers to finally get one that worked with the macbook. Then 10.5.2 came out and my internet drop outs started again. I switched back to 10.5.1 and it worked agian. Once i accidentally downloaded 10.5.2 again and guess what? Yep Drop out problems.
    Now since 10.5.3 came out to supposedly fix the airport bug, i install it just for my internet not to work at all. I'm so freaking sick of this i'm about to go back to windows and never take apple serious again. I have read post after post of people experiencing the same problems.
    I really want to give apple a fair shake and try to get this resolved so i can enjoy this laptop. I have to have 10.5.3 to run protools as its not compatible with previous leopard releases.
    what the heck do i do? Take it in to a genius bar and demand a new aiport card?
    Please advise, i'm at my wits end.

    You are right that there are a lot of reports about dropped wireless connections regarding the Macbook. I am not very versant technically (especially regarding wireless) but I have a few observations.... Do you use Bootcamp XP? XP has brilliant wireless software. My Macbook is the first Apple I have purchased also. Prior I always relied on XP to find and keep signals wherever I went and at home. I used NetGear DLink routers at home (various strengths of each). I always ran into trouble when I tried secured or encrypted signals - so number one I always leave them unconfigured (I just plug them in right out of the box.) Secured wireless is way too much work and too much of a mystery to bother with. Second, I must say I never notice dropped signals unless I am downloading something that takes a long time (updates). I guess if you are playing games online, a dropped signal is unacceptable, but I don't do games, so again - not bothered. In any case, with my Macbook I got to compare Apple to MS by using Bootcamp and I think XP is better than Tiger. This is fun because it is the same hardware - the software is an issue somehow - BUT - a big "but" - the routers are more often the problem. (Have you ever noticed how many new firmware updates some routers need? - that is never a good sign...) I too, purchased more and more routers (always "on sale") to improve speed and connectivity, but was never happy. Over time I finally upgraded from Tiger to Leopard and with it I also decided to "go Apple" by actually getting Airport Express (my first "N" router). That was a month ago and now I have speed and tremendous connectivity. Success. One last tip. I have noticed with Apple that if you have a fresh install of OS X - and if it works well without updates then just LEAVE it! On more than one occassion I loaded the updates and saw a performance drop. My answer was to Erase/re-install and leave it. Never mess with a working setup. Don't be afraid to use your warranty and get satisfaction. In spite of what you feel and read in forums, most Macs work really well.

  • IMac and Macbook can't see each other via Airp

    Except sometimes.
    Using Leopard on both new machines, I can share Internet connections and printers fine. The problem is in trying to mount volumes or share files.
    I create a network on the iMac, connect to it on the Macbook, and use the appropriate password on both machines. I've set file sharing preferences perfectly and confirmed that at the store.
    Sometimes, from the Go menu I can find one machine from the other. Sometimes I can't. When I find them, file sharing and accessing work fine--although for some reason, the volumes do not mount on my desktop! I have to use the Go Network menu item.
    But other times they just don't see each other. I only get this to work by REPEATEDLY logging out of networks, turning Airport on and off, creating new network names, and so forth.
    The worst results come from creating a familiar network with a name and password I've used before. The best results come from creating a brand new network, new name and pswd. And creating the using 128-bit WEP is the worst, but I think that sometimes that works, too.
    My question is, am I doing something wrong, or is this another Leopard/Airport bug?
    Also, if I can access the other computer in Go Network, how come the volume doesn't mount on my desktop??
    Thanks.

    Don't know if this will help - but if you're using an Extreme base station go to the Airport Utility and look at the list of DHCP Clients. I had the same problem only I had an iMac and a Macbook running OS 10.4.11. Turns out that my printer and my iMac were sharing the same IP address. When I assigned a permanent address to the printer (out of the normal distribution range used for the other computers) the problems all went away. So, for instance, if the router was assigning IP addresses ending in 10.0.1.199, 198, 197, etc., and the primary computer ended witih 200, I named the printer 10.0.1.201
    Hope that helps.

  • Macbook Wireless Authentication Problem

    I am having a strange issue that I haven't seen much information in either the Leopard forum or the Snow Leopard forums. This issue started with the 10.5.8 upgrade. When I migrated to 10.5.8 the campus network wireless stopped working. The Campus Network runs on WPA Enterprise. I have no issues connecting to my WPA Personal network at home. Neither network broadcasts the SSID and both require authentication to access. The home network requires just a password to connect while the campus network requires both Username and Password authenticated via Active Directory. When connecting to the campus network opening the Network preferences pane shows Airport flashing Authenticating then Authenticated repeatedly. Eventually after 10-20 minutes of flashing the wireless will finally connect to the network. Console shows the following:
    Sep 14 07:35:31 ***** eapolclient[324]: PEAP: successfully authenticated
    Sep 14 07:35:32 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
    Sep 14 07:35:32 ***** eapolclient[324]: PEAP: successfully authenticated
    Sep 14 07:35:32 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
    Sep 14 07:35:32 ***** eapolclient[324]: PEAP: successfully authenticated
    Sep 14 07:35:33 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
    Sep 14 07:35:33 ***** eapolclient[324]: PEAP: successfully authenticated
    Sep 14 07:35:33 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
    Sep 14 07:35:33 ***** eapolclient[324]: PEAP: successfully authenticated
    Sep 14 07:35:33 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
    Sep 14 07:35:33 ***** eapolclient[324]: PEAP: successfully authenticated
    Sep 14 07:35:34 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
    Sep 14 07:35:34 ***** eapolclient[324]: PEAP: successfully authenticated
    Sep 14 07:35:34 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
    Sep 14 07:35:34 ***** eapolclient[324]: PEAP: successfully authenticated
    Sep 14 07:35:35 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
    Sep 14 07:35:35 ***** eapolclient[324]: PEAP: successfully authenticated
    Sep 14 07:35:36 ***** configd[15]: network configuration changed.
    Following the instructions here:
    http://www.viewfromthedock.com/2009/08/temp-fix-for-10-5-8-airport-bug/
    Which has you replace the following 2 files fixes the issue:
    AppleAirport.kext
    IO80211Family.kext
    Now that I have upgraded to Snow Leopard the problem is back again. This is a completely fresh loaded laptop. I erased and formatted the hard drive before installing Snow Leopard. I'm running an older Macbook that uses the Atheros card. A guy I work with has a slightly newer Macbook running a Broadcom card that doesn't have this issue.
    I do have a log file I generated from this post:
    http://discussions.apple.com/messageview.jspa?messageID=10123194
    If that would be helpful in getting the problem resolved.
    Thanks in advance.

    Here:
    Card Type: AirPort Extreme (0x14E4, 0x8D)
    Firmware Version: Broadcom BCM43xx 1.0 (5.10.91.19)
    Locale: ETSI
    Country Code: TW
    Supported PHY Modes: 802.11 a/b/g/n
    Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 149, 153, 157, 161, 165
    Country code may vary, according to base stations in the vicinity. When I'm at home in the UK, code is TW. At work in the UK, code is US. Verbose startup of the OS reveals variety long before authentication, so I guess that the country code sometimes reflects the characteristics of a nearest capable base station.
    I have different issues in different environments. One of the issues is summarised at <http://discussions.apple.com/thread.jspa?messageID=10159356&#10159356> and in this area of Apple Discussions, I watch just a few other threads.

  • BUG FOUND!! in Airport Disk programming

    I'm betting this is having a bigger issue then most poeple realize as it effects reconnecting to the Airport disk.
    Ok after lots of testing I've figured out a major bug in the Airport Disk Programming for Security.
    This has only been verified with the following settings:
    1. Airport Disk is configured with Accounts for access
    2. Formatted with HFS+ USB drive.
    Discription:
    1. When connecting to the Airport Disk you get the error:
    "Connection Failed
    Unknown user, incorrect password, or login is disabled. Please retype the login information or contact the disk's administrator."
    2. You retype the password and user name and it still says the same thing over and over and over.
    The Cause of problem:
    You connect to your Airport Disk the first time with no problem using your login and password. If you cause your connection to be interrupted for a small amount of time and you get that Warning about server disconnect and it shows your airport disk and personal disk with the disconnect button, and they disconnect!! Then you cannot reconnect to the Airport Disk till you reset the Airport Extreme.
    To get this Disconnect dialog, it can be caused by a number of common uses, here are a few of the common ones:
    1. you VPN into work (with Airport Disk shares mounted)
    2. you change from wireless to Hardwired connection (with Airport Disk shares mounted)
    3. You let your computer go to sleep when its on a wireless connection but are connected through another wireless access point hardwired to the network (with Airport Disk shares mounted)
    When getting your Airport Disk volumes disconnected in this way, The Airport Extreme I'm guessing is deactivating the account and not properly disconnecting the connection. So at this point you have to Reboot the Airport Extreme to let you use your account again on the Airport Disk.
    I hope some poeple from Apple actually read these. I've had to reset my Airport extreme about 24 times a day between my wife's 15" MBP and my 17" SR MBP getting this disconnect problem.
    And for those poeple out there who keep having Airport Disk connection problems, Lets make sure your not having this problem. To test, simply reboot the airport extreme router & see if you can connect to your Airport Disk Volumes, then once your volumes are mounted turn off your Airport wireless (on your MAC) or unplug your Hardwire till you get the disconnect message. Then try to reconnect to your Airport Volumes after restoring your network connection.
    This issue needs to be fixed ASAP!!!!
    Please reply to this message with your nominations to try and get this issues raised to a P1 or lvl 1 priority so it's in the next firmware upgrade as it's not an issue with OS x programming side, as a rebot of the computer still doesn't restore the connectivity with the AirPort Disk.

    HERES A SOLUTION I POSTED IN ANOTHER THREAD!
    Hi,
    I've been trying to work out the Hard Drive problems with the Airport Extreme for a few days and have had some success, so I'll share the info if its any use!
    First of all, your printer and both hard drives all run off their own power supply, therefore, you don't need to have a powered usb hub, or just take the plug out and keep using the hub, save yourself a plug!
    More importantly, I have had the same thing with the hard drive appearing in the Airport Utility yet whenever I try to connect, it comes up with an error and can't mount, although when I go to network and connect it appears but then goes wrong at the last part mounting, this is what I found...
    the first time I plugged hard drive in all worked nicely, however, any time I have unplugged the power to the Aiport Extreme and connected again it'll show but never connect. When I went to make a few partitions I realised that if you unplug the router and repower, whatever HD name its seen before doesn't work until the HD name was changed again. For example....
    I called my first HD to connect 'wifiHD', was working fine, next time i unplugged router was still showing in network but I couldn't mount it, I then plugged it to the mac and renamed it 'wifiDISK' for example and plugged it back into the router and it worked fine! Its very strange cos when I needed to unplug it last time I then had the same trouble and just renamed it back to 'wifiHD' it worked fine! Its a little flaw which is a right bugger to find so the bottom line is...
    RENAME THE HARD DRIVE EVERY TIME YOU UNPLUG THE ROUTER AND YOU CAN MOUNT IT AGAIN
    Another tip is format your HD in 'Mas OSX Extended' as it can be read by both mac and PC over the network. Then as windows isn't the best when you go to 'My Network Places' and 'Add Network Place' if you can't find the HD or even the router then enter
    \\routername\\hardrivename\
    in this format into the box, it'll take a mo but it'll then ask for the password! I personally have my hard drive guest access read + write so I entered
    user: guest
    password: base station password (or disk password as selected in airport utility)
    and it all worked!
    Sorry for the long explanation, hope this has helped!

  • A bug in AirPort Extreme 802.11n

    I'm posting this on behalf of a colleague who has found a bug within the settings of the AirPort Extreme router both to make Apple aware as well as to see if anyone else is coming across this.
    He notes:
    "The bug is that the AirPort Extreme advertises the attached drive (USB) to the wan port via Bonjour even when you have that option disabled in the routers settings.
    ot=out
    The packets in question come exactly every 12 minutes (720 seconds) and are broadcast to 169.254.255.255 from 169.254.232.51 and appear to be smb packets containing the string "MAILSLOT/BROWSE"
    I assume that the from address (169.254.232.51) may change from Airport to Airport (not sure how it picked that address out of the ZeroConf range)"
    Ultimately it seems as though even when Bonjour is turned of in the router it still continues to broad cast across the sub-net. We are just curious as to Who, What, Where, How, and Why?
    Should it be committed as a bug so that this traffic can be completely disabled in the future?
    Is any one else seeing this? If so is it the same IP Address range?
    G3, G4, G5, iMac G5, Xserve G5, XRaid, PowerBook, iBook, MacBook Pro, Mac Mini   Mac OS X (10.4.6)   Have used every Mac OS since version 8 to date.

    Wil,
    Have you learned any more about this? I stumbled upon it because I had a setting on my SonicWall firewall that caused me to get "IP Spoof" Alerts on a regular basis. I started investigating it and finally got enough information to find your post.
    I am rather curious about this problem, why it exists and any work arounds, should they exist. In my case, I found a way to stop the alerts but not stop the "offending" packets. FYI, my thread is over here, but I don't think it adds much to your topic:
    http://discussions.apple.com/thread.jspa?threadID=881394&tstart=0
    Regards,
    Chip

  • Airport problems (bug report)

    To put "the bottom-line up front", I'd like to know if anyone can put me in contact with Apple's Airport software engineers (or can forward this to them so a bug fix can be released). I have composed as detailed of a description of the bug as possible and all my attempted fixes.
    I've been having problems (for some time now) with my airport connection dying at seemingly random times, but most often within 5 minutes of re-booting. The indicator on the menu bar will show full signal, but I will not be able to even ping my router.
    This was not an issue until I installed Airport Update 4.2 (back in September). Shortly thereafter, I suspected the update was the problem, and did a complete re-install minus that update (and the ones reliant on it). Things then worked with no problems. I got brave and installed the update (in November) and since then the problems returned. I so far have not been willing to undertake another complete re-install.
    This is not an issue on my Jaguar partition, nor is it on a G4 that has a wired connection to the router, nor is it one on my brother's Powerbook G4, (running Tiger on a wireless connection). Running Fix Permissions and Fix Disk from Disk Utility has no effect, (including single-user boot with fsck). Resetting the router (and cable modem) has no effect.
    3rd-party software is ruled out. None was installed during my initial Panther installation when I first noticed the problem. Upgrading to Tiger is currently beyond my monetary means.
    For information, my router is a Linksys (802.11b) model BEFW11S4.

    hi there--
    your best bet for wanting your information to be shared is to call apple technical support at 1-800-275-2273. you can give a detailed report to a tech support agent, who will pass it along to the powers that be. you could also request to speak to an upper tier agent. then the report will be more likely to be handed over to apple engineering.

  • New Base Airport Extreme 802.11n .....bugs

    Well,
    I have just read tens of posts in many forums, included this one.
    It seems that the Base Airport Extreme 802.11n has severe problems of connections to internet.
    That's is also my case.
    This is my config.
    1. Modem NetGear DM111P <--> WAN Base Airport Extreme 802.11n
    2. LAN Base Airport Extreme 802.1n <--> Ethernet iMac 24"
    3. LAN iMac as DHCP auto IP
    4. Base Airport set for PPPoE
    There is no way to get into Internet.
    If I connect the Modem DM111P directly to the iMac 24" LAN the Internet is on, fast, fluid.
    With the Airport in betwwen....no way...
    Any help ?
    I am seriously thinking Apple has distributed a product full of bugs.
    Read other forums with same problem.
    Beppe
    iMac 24"   Mac OS X (10.4.8)   Base Airprt Extreme + 2 x Airport Express

    James,
    Confirmed: the NetGear <--> AEBS <--> iMac does not work.
    I have set the Bridge Mode as you suggest, but nothing, no internet !
    Othe 3 hours of tests in setting tens of conigurations. No one works.
    All the leds of the NetGear Modem as the one in the AEBS are solid green.
    I will return back the NetGear modem to the retailer.
    I am now running with my old Pirelli Modem from Alice Service (Telecom Italia Net) that - even if slower - at least it works.
    I am concluding that the Airport Extreme has seriuos problems of compatibility with the open market modems.
    Apple should check the SW+HW before selling such difficult items as the the Airport Extreme base.
    Just a question: which model/type of modem(s) is(are) effectively compatible with the AEBS ?
    If the retailer will permit me this, I will replace the NetGear (a very good modem...what a pity) with a compatible one with this strange base.
    Thaks for your help.
    Beppe

  • Airport Self-assigned bug

    Hello,
    I have a MBP 2.4 running OSX 10.5.6, and I have for a least the last 6 months have the problem that it won't re-connect after restart/sleep/airport-on-off.
    Well, that's not entirely correct, because it does find my network and tries to connect with the comment "Self-assigned IP". That fails. I then have to select the network myself, without further problems.
    PS: I also had the keychain update 1.0 password bug, where it would ask for the password everytime. I got that fixed by booting up in safe mode (holding shift at boot time), and just re-starting.
    I really hope I can fix this last problem.
    Regards

    Seems like I posted in the wrong forum (should have been in the old MBP forum). Sorry.

  • Airport Extreme IPv6 firewall bug

    I've been experimenting with IPv6 support in the Airport Extreme, and I think I found a bug.
    If a host on the WAN side has a smaller MTU, as might be the case if it is being tunneled, then attempting to run a bunch of data through a TCP connection will naturally result in the remote host returning an ICMPv6 packet too big notification. Those don't seem to be making it through the IPv6 firewall in the AEBS back to the originating host. This locks up the TCP connection. Reducing the MTU of the local host's interface is a workaround, but it's annoying.

    This magically fixed itself some time ago.

Maybe you are looking for