Q: Lion WiFi Connection Problem

Since Wednesday 12.October, 10.7.2 my iMac (2011) does not disconnect from WiFi during operation. But I still have the problem after hibernation.

If you're having trouble with a connection to a network (at a school, for example) which requires an authentication window, try the workaround in this thread http://att.macrumors.com/showthread.php?p=13625027#post13625027

Interesting fix, but I'd be weary of turning off a certificate revocation list. It's what your computer's programs look at to see whether a certificate they get from a website or online service is bad and fradulent.

When Diginotar was hacked during the summer, the security updates that the browser and OS makers issued were actually new CRLs with Diginotar's certificates added to it that told any web browser or other app that would have to use certificates to not accept those revoked certificates as legit. A revoked certificate is why your browser gives those huge untrusted connection warnings.

Hmmm... Both of those are "off" by default in Snow Leopard and in all earlier versions of Lion. 

Hmm. That's quite strange. Maybe it's only for certificates for captive portals?

If that's the case and they were off by default in the earlier versions, it's probably OK to turn them off in 10.7.2.

Ciao, Roberto!

Io non riesco proprio a sostituire i driver....però mi è venuta un'idea:  se io  prendo un'Airport express e configuro un'altra rete?....se è colpa dei driver non dovrei avere problema, no?

...magari qualcuno ha già provato!

A presto!

This seems to have worked for me. Hope it continues and works for you.

https://discussions.apple.com/thread/3196661?start=165&tstart=0

It IS a bit strange, hormelmeatcompany, I agree.  There probably is some small security disadvantage in that workaround, but people might (at their own risk!) be OK doing it at least until there is more information from Apple.  (Or from Aruba).

Just found another potential fix for others to try. As with the others, you'll have to look at Console.app and see what your logs say to narrow it down.

This is for the reconnect on wake-from-sleep problem specifically. After upgrading to 10.7.2, I started having it.

These are from my logs:

10/14/11 1:06:36.643 PM ntpd: unable to create socket on en1 (27) for fe80::e2f8:47ff:fe33:4e74#123

10/14/11 1:07:31.811 PM configd: subnet_route: write routing socket failed, Network is unreachable

10/14/11 1:07:59.641 PM ntpd: unable to create socket on en1 (30) for fe80::e2f8:47ff:fe33:4e74#123

10/14/11 1:08:22.810 PM configd: subnet_route: write routing socket failed, Network is unreachable

10/14/11 1:13:20.404 PM configd: subnet_route: write routing socket failed, Network is unreachable

10/14/11 1:33:04.517 PM applepushserviced: <APSCourier: 0x7f8fd591b5e0>: Stream error occurred for <APSTCPStream: 0x10ee23900>: The operation couldn’t be completed. Socket is not connected

10/14/11 1:33:22.054 PM configd: subnet_route: write routing socket failed, Network is unreachable

10/14/11 1:34:31.389 PM applepushserviced: <APSCourier: 0x7f8fd591b5e0>: Stream error occurred for <APSTCPStream: 0x10ee23900>: The operation couldn’t be completed. Socket is not connected

10/14/11 1:34:39.592 PM ntpd: unable to create socket on en1 (41) for fe80::e2f8:47ff:fe33:4e74#123

10/14/11 1:35:04.060 PM configd: subnet_route: write routing socket failed, Network is unreachable

10/14/11 1:52:01.560 PM ntpd: unable to create socket on en1 (46) for fe80::e2f8:47ff:fe33:4e74#123

10/14/11 1:53:00.558 PM ntpd: unable to create socket on en1 (47) for fe80::e2f8:47ff:fe33:4e74#123

10/14/11 7:42:44.625 PM applepushserviced: <APSCourier: 0x7f8fd591b5e0>: Stream error occurred for <APSTCPStream: 0x10ee23900>: The operation couldn’t be completed. Socket is not connected

10/14/11 7:43:12.239 PM configd: subnet_route: write routing socket failed, Network is unreachable

10/14/11 7:45:45.949 PM applepushserviced: <APSCourier: 0x7f8fd591b5e0>: Stream error occurred for <APSTCPStream: 0x7f8fd3d27c10>: The operation couldn’t be completed. Socket is not connected

10/14/11 10:11:17.257 PM ntpd: unable to create socket on en1 (53) for fe80::e2f8:47ff:fe33:4e74#123

The fe80::e2f8:47ff:fe33:4e74 clued me into it potentially being an IPv6 problem. I was puzzled about it though, as I had turned mine to Local link only.

However, you can disable it completely by going to Terminal.app and typing:

networksetup -listallservices

This lists what you'll need for the next command. The output for me was:

Bluetooth DUN

Wi-Fi

For some reason, ethernet wasn't listed. The next command you'll want to type is networksetup -setv6off Wi-Fi

In my case, Wi-Fi is what it called the wi-fi card but yours might be something else, which is why you should run networksetup -listallservices first to find out.

This only applies to the currently loaded network profile. If you switch to another, IPv6 will be turned to whatever setting it was at on that profile before, but if you switch back to the one it was turned off for again, it'll be off.. To verify it is turned off, you can to to the TCP/IP section of the window after clicking "Advanced..." at the bottom of the Network prefpane.

I haven't tested this extensively yet.

I didn't read through all 74 pages of posts, but it seems that I have a similar problem to everyone else. Since installing Lion on my macbook the wifi ONLY connects to certain networks gives me a "connection timeout" message for others.

... one of these networks happens to be my apartment building, to which I do not have access to the router since it is for the entire building. It says there are 5 bars, but it will not connect and almost immediately give me the "connection timeout" message.

Some networks, like my university wifi works perfectly. But no matter what I do, I cannot connect to my apartment's wifi. I've tried deleting the system config files and resetting my location, but neither worked. I was hoping 10.7.2 would fix it, but no luck. Here's some additional info on the networks and my card:

  Software Versions:

  CoreWLAN:          2.1.1 (211.3)

  CoreWLANKit:          1.0.1 (101.1)

  Menu Extra:          7.0.1 (701.2)

  configd plug-in:          7.1.1 (711.1)

  System Profiler:          7.0 (700.3)

  IO80211 Family:          4.1.1 (411.1)

  WiFi Diagnostics:          1.0.1 (101.1)

  AirPort Utility:          5.5.3 (553.20)

  Interfaces:

en1:

  Card Type:          AirPort Extreme  (0x168C, 0x87)

  Firmware Version:          Atheros 5416: 2.1.14.9

  MAC Address:          00:1b:63:c6:4d:ee

  Locale:          FCC

  Country Code:          US

  Supported PHY Modes:          802.11 a/b/g/n

  Supported Channels:          1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 149, 153, 157, 161, 165

  Status:          Connected

This network CONNECTS:

UWNet:

  PHY Mode:          802.11n

  BSSID:          00:24:6c:cc:0e:c0

  Channel:          1

  Network Type:          Infrastructure

  Security:          None

  Signal / Noise:          -78 dBm / -96 dBm

This network does NOT connect:

Orpheum:

  PHY Mode:          802.11g

  BSSID:                  00:18:01:d6:1a:e2

  Channel:             9

  Network Type:    Infrastructure

  Security:              None

  Signal /Noise:        -54 dBm / -96 dBm

If anyone could help me I would REALLY appreciate it. It's not fun going to the library every time I need to use the internet.

Naughds wrote:

 

This network does NOT connect:

Orpheum:

  PHY Mode:          802.11g

  BSSID:                  00:18:01:d6:1a:e2

  Channel:             9

  Network Type:    Infrastructure

  Security:              None

  Signal /Noise:        -54 dBm / -96 dBm

Hello,

Your home network is 802.11g 2.4GHz with a good signal and a good SNR of 42db. On that you should have a good connection.

Unfortunately, as you wrote, the wireless is for the whole apartment complex and this could be the reason for your connecting problems.

All participants in a wireless share the available bandwidth equally for up- and download.

That means if you have a 54MBit/s bandwidth in your 802.11g you may calculate for your own how many stations can use the wireless with a reliable speed, regardless of the radio signals quality.

In your case, I'm afraid the wireless is overloaded and therefore you got a connection time out.

You can check that by connecting on unusual times; e.g. if most of the inhabitants are out or sleeping.

Lupunus

Now I send my mac back today, 14 days money back guarantee ... shame... But after trying so many ... and the downgrade is from lion 10.7.X no longer possible for SL

Apple does not want that people work with the older operating systems

Thanks for your reply. I've tried to connect for about the past 3 weeks at all hours of the day. I'm not an expert at networking, but I have noticed that it always comes back with a "connection timeout" for networks with BSSID's that start with 00. I'm not really sure if that means anything, but it has been consistent with the error. That, and that I cannot connect with unprotected networks. The university is technically unprotected, but passwords are required when the browser is opened.

Hey @pple_Unknow,

The problem is fixed by allowing unauthenticated users to access the Online Certificate Status Protocol server mentioned in the certificate used by the authentication page (in our case, http://ocsp.godaddy.com/). Once this

access is granted, the page loads the first time on a Lion 10.7.2 Mac. Godaddy has info about their OCSP here:

http://community.godaddy.com/help/article/6723

Hope that helps!