After Lion upgrade, having network issues after wake from sleep

You should try google the problem then. There's tons of people with network connectivity issues after a Lion install/upgrade. Even here on the apple forums, lots of threads with same problems.

Every single Mac I have been involved with, since the Lion release have these problems. Some of my friends even rolled back to SL, because it was to annoying. So there ARE problems. Have in mind that using an external drive, but always shut the system down or log out, would never encounter this network connectivity issue, the same for all those Macs running without anything externally connected. So we might be a minority group, but this doesn't change the fact, that I can fix the problem, by unplugging everything externally connected and reproduce the error in a heartbeat, if I want to.

After few (lot) tests I can say:

1. I have this bug with both ethernet and wifi connection.
   
2. Every change I do to network preferences that involves a network reset (i.e. turning off/on wifi; changing network preset; reboot; logout/login) fixes the problem for that session.
3. The bug happens only when I have an USB external drive plugged in (and my Time Machine is turned off).

Anyone having this bug without an external disk drive plugged?

Yes. I do not have any USB drives connected.

I've filled a bug with Apple. I'd suggest that fellow developers do the same. I can live with most of the other bugs in Lion, but this one is a nightmare. I don't want to see 10.7.1 come and go and for this issue to remain. 10.7.1 is days away, 10.7.2 will likely be months away...

William Kucharski wrote:

«many of them have, for example, their iTunes libraries on an external FW drive»

Any Mac with an USB drive plugged?

ctomer wrote:

Yes. I do not have any USB drives connected.

Aaaw... What a nightmare! 😟

Well, I'm not a developer... I filed a normal feedback... I think that's all I can do, atm...

I'll get a beer, maybe... 😝

No, all the systems I'm speaking of are regularly put to sleep for intervals of five minutes to days.

For example, my MBP had an external FW drive attached, and when I returned from four days away and woke it the Wi-Fi connection to the net was instantly active - the same as earlier today when I returned after ten minutes away.

Note also that neither AD nor Google are arbiters of an issue's prevalence; those experiencing an issue post, the millions that do not generally don't, and more than a few post-Lion network problems have been resolved by firmware updates to or replacement of associated routers.

Have people noticed a difference between lid sleeps for portables, system timeout sleeps or "Sleep" Apple menu sleeps?

William Kucharski wrote:

Have people noticed a difference between lid sleeps for portables, system timeout sleeps or "Sleep" Apple menu sleeps?

I tried after your advice and yes, I found a difference:

I've got the network bug only when I put the Mac manually to sleep.

If I set a timeout and the Mac goes to sleep, when I wake it up there's no bug, even with the USB drive plugged in.

I've just finished all the emails and files etc for Apple to check over with my system. The first lot were about my computer in it's working state. And then for the last batch I wanted to recreate the problem and was worried that I wouldn't be able to do it just when I needed it to happen most. But, set my computer to sleep, waited 2 minutes for drives to spin down or whatever sleep induced, and then tried to wake it up again - and low and behold, no internet connection. Emailed the details over and will wait for reply. Interesting you guys now able to recreate the bug with manually sleeping the computer and not with letting it go to sleep itself. Is that a definite?

I will try to recreate that as well.

I just set my computer to sleep itself after 1 min, waited for a minimum of 5 mintues to make sure fans and drives had spun down and everything was quiet. Tried to re-awaken and nothing, no internet connection. To even post this I had to go through the usual system prefs, network, location and change Home to Auto and back etc.

AshleyTarver wrote:

Interesting you guys now able to recreate the bug with manually sleeping the computer and not with letting it go to sleep itself. Is that a definite?

Yes, to me, at least by now.

I tried several times and was always the same:

Manual sleep:

USB plugged: no internet connection.

USB unplugged: internet connection.

Auto Sleep:

Always internet connection.

Both eternet and wifi, no Time Machine, Router Netgear, iMac 24 2.4.

Later this week I have to upgrade another iMac on a different network, so I'll do some few more tests.

My wifi appears to be working fine again. I had set system sleep for 2am, after returning home I woke the machine and had internet access. Then I manually put the iMac to sleep by pushing the power button. Tonight I will put it to sleep from the Apple menu as well and let it sleep for about 10 minutes or so.

Does anyone have any console messages they can share that may be relevant?

So people do not have to re-read my original post, I am quoting it here:

"I too was having this problem. After reading the console logs I noticed quite a few Little Snitch errors. Little Snitch was broken, the version was incompatible with Lion. I updated Little Snitch and now my WiFi is working after waking from sleep. I have tried it three times now after it always failing to connect before the update of LS.

Hopefully this helps someone else."

And later:

"I don't know what else to say, after updating Little Snitch I am able to connect to my wifi now, consistently.

I am using an Airport Extreme, 7.5.2.

I did not uninstall Little Snitch, I upgraded it. Whether or not there are files left behind by the Little Snitch installer that are still causing errors I do not know. I did notice however, that when I upgraded Little Snitch it did update my boot cache's. Could this be related? Or have I just been lucky these past few times that I have been connecting? I don't know. But if I still do not have the wifi connect problem after a day or so, I'll let you know.

I also do have a TIme Machine volume but have not had any problems that seem related to that volume.

To add to my previous post here if I leave my iMac switched off and Airport Extreme on there is no problem the latter works OK. I find that if I switch my MacBook on still with the iMac off then the problem appears and the Airport Utility prog keeps telling me there is a problem and my Airport Extreme does not work. Thus both iMac and MacBook both upgraded to Lion create problems that switch me out of the Internet. I have configured my BT Home Hub now as a wireless router in order to get access but if I configure the iMac or MacBook to connect to it they are not happy and keep buggering up the system preventing the Airport Extreme from working. I have yet to try unplugging all USB drives as that presents another problem, it's where my data is.

Apple need to make some changes to LIon, urgently.

This issue is a System problem, it can randomly appear after System Updates. If you have any media in the Optical Drive please remove it and put the computer to sleep and re-wake it. This is already a reported bug.

Sorry to report that no, my wifi did not work after waking from sleep. Either it is intermittent or I had woken it from a system initiated sleep. I turned wifi off/on and it reconnected.

Of greatest interest to me is this line

7/26/11 8:28:12.952 PM UserEventAgent: CaptiveNetworkSupport:CaptiveStartDetect:2343 Bypassing probe on Jim because it is protected and not on the exception list

Here are some console entries during the wifi problem:

7/26/11 8:28:09.000 PM kernel: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

7/26/11 8:28:10.032 PM UserEventAgent: CaptiveNetworkSupport:CaptivePublishState:1211 en1 - PreProbe

7/26/11 8:28:10.043 PM configd: network configuration changed.

7/26/11 8:28:12.000 PM kernel: Auth result for: 00:XX:xx:xx:xx:90 MAC AUTH succeeded

7/26/11 8:28:12.000 PM kernel: AirPort: Link Up on en1

7/26/11 8:28:12.000 PM kernel: en1: BSSID changed to 00:34:46:a4:16:90

7/26/11 8:28:12.000 PM kernel: AirPort: RSN handshake complete on en1

7/26/11 8:28:12.912 PM configd: network configuration changed.

7/26/11 8:28:12.952 PM UserEventAgent: CaptiveNetworkSupport:CaptivePublishState:1211 en1 - Probe

7/26/11 8:28:12.952 PM UserEventAgent: CaptiveNetworkSupport:CaptiveStartDetect:2343 Bypassing probe on Jim because it is protected and not on the exception list

7/26/11 8:28:12.953 PM UserEventAgent: CaptiveNetworkSupport:CaptivePublishState:1211 en1 - Unknown

7/26/11 8:28:12.956 PM configd: network configuration changed.

7/26/11 8:28:14.324 PM ntpd: bind(25) AF_INET6 fe60::216:f3ff:fe956:d14%5#123 flags 0x11 failed: Can't assign requested address

7/26/11 8:28:14.324 PM ntpd: unable to create socket on en1 (15) for fe60::216:f3ff:fe95:d14#123

7/26/11 8:28:22.000 PM kernel: IOSurface: buffer allocation size is zero

7/26/11 8:28:25.052 PM UserEventAgent: ServermgrdRegistration cannot load config data

7/26/11 8:28:25.052 PM UserEventAgent: ServermgrdRegistration oldConfig is nil during net changed notification

Unfortunately it's not readily reproducible on just any system; I know I and several others have tried without success, so the more information on affected systems and exact methodology to reproduce the issue is good.