Wifi Constantly Dropping in Lion

gphonei wrote:

Wireshark, will show you where everyone is at, and help with signal level analysis.

Other people have reported problems with channel switching causing loss of service often enough to create problems like yours. They've switched to a fixed channel to keep the radio from hopping around.

Great ideas. I will try a fixed channel.

I experimented with running wireshark in monitor mode to capture the 802.11 protocol messages. It automatically parses the radiotap header so I can see S/N's. What I need to learn how to do is filter for only my SSID (I see mine plus all my neighbors) and somehow dump the S/N values somewhere to plot, saving the chore of having to scroll through thousands of messages. I am not a network engineer but this tool helps me appreciate those that are.

I do not think I have experienced the radio dropout while using WEP. The problem appears with WPA and appears to get worse in WPA2. Is there merit to decreasing the MTU lower than 1480? Making conclusions based on these observations after only a few days of testing is a recipe for error so I will continue to test. More later.

I feel obligated to post some of my other failed attempts (not suggested by gphonei btw)

Some have posted solutions such as writing an applescript to periodically ping an IP address (local router or 8.8.8.8). I tried this and other solutions a few days ago. While I was happy to learn how to automatically execute an applescript upon boot, these did not seem to help in my case, nor did resetting the macbook's NVRAM, nor did resetting the SMC. Under osx's system preferences, system, network, adding 8.8.8.8 to the DNS seems to have only caused problems when I tried to wirelessly access my campus home page this morning and local library home page. Without an active connection, there was no getting to 8.8.8.8 so deleting it automatically put the default local router's IP as the DNS server and I was back where I started. I only post this so perhaps someone will learn from my mistakes 🙂

I had been similar problems to many people on this thread with my iMac (running ML 10.8.2) dropping its wifi connection all the time. It began after I upgraded my wireless router (Linksys X3000). And as part of the upgrade I finally shifted from WEP to WPA2, changed passwords etc. I tried fixing channels, reducing MTU size, creating a new location but nothing seemed to work.

I then came across a thread which suggested cleaning out my keychain of all the passwords to any router at 192.168.1.1. When I opened Keychain I was amazed to find half a dozen entries, collected over the years as I've migrated from each old mac to the new one.

I deleted all over them. Then re-connected to my wifi network, entering all the details afresh. Since then, no problems at all.

I would suggest trying it if you've tried everything else. If it does work for you, let people know on this thread (and/or others).

I gave up and got a Atheros based airport card from ebay. Put it in my macbook two weeks ago, no wifi problems since.

GO TO YOUR NETWORK PREFERENCES.....

for some reason i have had weird wifi issues when i shouldn't particularly in my Dad's house. i was being connected to a weird IP Address that none of the other computers were on...

the airport in my Macbook Pro 13" mid 2011 started DROPPING WIFI at my other house with an Airport Extreme that ive never had problems with. power cycled everything, you know, normal troubleshooting procedures.

nothing was working besides, turning the airport off (at the top of the menu bar (wifi symbol)) and then back on.

that seemed to work for about 30-60 seconds then drop again like some other users were describing.

bottom line

AT MY DADS HOUSE:

my Mac was connecting to 192.1.10.73 or something that started with a 192

the devices that were actually getting internet were on 10.1.10.***

in other words something starting with a 10.

so at my dads house i had to MANUALLY configure the IP Address in order to even get connected...

at my other house. i went into SYSTEM PREFERENCES > NETWORK PREFERENCES >

you can add and subtract diiferent networks like you would through mail by + and - at the bottom left of the window...

i just added another WIFI conncetion... named it WIFI 2.....check your IP Addresses on the devices that are staying connected. you may need to add it manually...

to manually add IP Address go to advanced at the bottom right of the NETWORKS window > TCP/IP > and then change the CONFIGURE IPv6 to MANUALLY.... then youll be able to type in your IP Address and not have the mac self assign something it will never work on.....

you may also want to try Renew DHCP Lease for a quick fix SOMETIMES........it doesn't always work



I have the same problem of wi-fi dropping. I have mid 2012 MacBook Pro with Lion. Sometimes the wifi drops after a minute and sometimes it holds for 30mins. But keeps dropping unless i have a transfer going and often even then.

It seem my wifi hotspot (named Andromeda) is on channel 6 and there are many other wireless connections in my building on the same channel. Could this be the real problem instead of the problem being the Os or the MacBook Pro hardware?

Software Versions:

CoreWLAN: 2.1.3 (213.1)

CoreWLANKit: 1.0.3 (103.2)

Menu Extra: 7.2 (720.1)

configd plug-in: 7.4.1 (741.1)

System Profiler: 7.0 (700.3)

IO80211 Family: 4.2 (420.3)

WiFi Diagnostics: 1.0.2 (102)

AirPort Utility: 6.1 (610.31)

Interfaces:

en1:

Card Type: AirPort Extreme (0x14E4, 0xF5)

Firmware Version: Broadcom BCM43xx 1.0 (5.106.198.19.22)

MAC Address: 10:40:f3:ed:9a:6c

Locale: ETSI

Country Code: DE

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

Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140

Wake On Wireless: Supported

AirDrop: Supported

Status: Connected

Current Network Information:

Andromeda:

PHY Mode: 802.11n

BSSID: 50:cc:f8:66:0e:87

Channel: 6

Country Code: DE

Network Type: Infrastructure

Security: WPA2 Personal

Signal / Noise: -28 dBm / -87 dBm

Transmit Rate: 65

MCS Index: 7

Other Local Wi-Fi Networks:

SoneraGateway00-26-44-A5-CB-26:

PHY Mode: 802.11n

BSSID: 00:26:44:a5:cb:26

Channel: 6

Network Type: Infrastructure

Security: WPA2 Personal

Signal / Noise: -71 dBm / -88 dBm

SoneraGateway08-76-FF-48-5E-64:

PHY Mode: 802.11n

BSSID: 08:76:ff:48:5e:64

Channel: 6

Network Type: Infrastructure

Security: WPA2 Personal

Signal / Noise: -64 dBm / -88 dBm

SoneraGatewayB4-82-FE-BF-31-55:

PHY Mode: 802.11n

BSSID: b4:82:fe:bf:31:55

Channel: 6

Network Type: Infrastructure

Security: WPA2 Personal

Signal / Noise: -72 dBm / -88 dBm

ZyXEL_5493:

PHY Mode: 802.11n

BSSID: c8:6c:87:aa:1e:22

Channel: 11

Network Type: Infrastructure

Security: WPA2 Personal

Signal / Noise: -72 dBm / -84 dBm

norkko:

PHY Mode: 802.11g

BSSID: 00:18:f8:f5:cd:16

Channel: 13

Country Code: DE

Network Type: Infrastructure

Security: WPA2 Personal

Signal / Noise: -80 dBm / -88 dBm

I´ve found a solution. It seems that most of the Wi-fi routers and mobile phones default wireless channel is 6. Also seems that channel 11 is also one of the most used default channels. I´m on the move a lot so I have used Samsung Galaxy Notes Mobile Hotspot. The hotspots default channel is again 6. I couldn´t change the setting of my Notes hotspot, but I found an app in googles Play-store called Wifi Tether in which you can choose the channel and the application can also keep the connection up by pinging websites (theres default sites but you can name any sites you like). I chose channel 7 and since no one in my neighbourhood has channel 7 the connection keeps with no problem.

Wifi Tether for Android. You need to Root your Android handset to use this.

https://play.google.com/store/apps/details?id=com.googlecode.android.wifi.tether &hl=fi

I guess the problem is in some way in the way Lion treats wireless connections, but i tested my connection with my old MacBook Pro with Snow Leopard and had the same problem.

Go to About this Mac > More Info > System Report > Network > Wi-Fi and check your neighbourhoods Wi-Fi Channels then change your Wi-Fi routers/mobile hotspots channel to a free/least used channel.

Go read up on how Wi-Fi works. Channel 7 interferes with both channel 6 channel 11.

Yeah I know. Just checked and channel 1 works well for me.

Allnuts wrote:

Yeah I know. Just checked and channel 1 works well for me.

The used bandwidth by each of 802.11b, 802.11g and 802.11n is different. That's an important part of where in the list of channels you might find a more usable environment. And, because people can change their channels, it can change over time, requiring you to revisit it.

Your othe post showed many 802.11n on channel 6. Try channel 1 and 11. If that still doesn't work for you, there could be something else happening with other 2.4ghz devices such as phones or remote audio monitors o wireless video extenders, etc on channel 1 and up. The Signal / Noise: figures in that list show that several of those signals can be heard fairly well by your router (noise is at -87dbm). That's where the interferening signals drop out of "view". Most are being received above -75dbm, and one is as loud as -64dbm. So, they will definately be a problem for you.

If switching to channel 1 or 11 doesn't improve things for you, you might not have much choice other than to try 5ghz to see if that solves your problem.

Hi guys,

QUESTION - what is the latest official remedy from the drivers / oreferences perspective to make 2010-aged MBP with BroadCom WLAN NIC & Driver particulars work as in my case work in a mixed G/N environment?

Beforehand in this thread, I've googled some suggestions to downgrade the driver, or disable the power-saving. What's the status quo?

Let me add some details here. I'm an owner of a mid-2010 MacBook Pro (

MacBookPro6,2) running Mac OS X 10.7.5 (11G63), if anyone from Apple Resellers screens this - S/N is W8013BPNAGV

I concur to some posts in a middle of this thread that say it's Apple's side of the house that drops Wireless-N connectivity. Switching from IEEE802.11n to 802.11g helps and secures stable connection. No, let me state it - it's definitely Apple & Broadcom issue. I put total responsibility on untested interop to Apple as they are releasing the OS and drivers that do not support IEEE802.11n.

ifconfig en1

en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

ether 58:b0:35:62:7e:0e

inet6 fe80::5ab0:35ff:fe62:7e0e%en1 prefixlen 64 scopeid 0x5

inet 192.168.0.173 netmask 0xffffff00 broadcast 192.168.0.255

media: autoselect

status: active

FYI, my iface is

en1:

Card Type: AirPort Extreme (0x14E4, 0x93)

Firmware Version: Broadcom BCM43xx 1.0 (5.106.198.19.22)

MAC Address: 58:b0:35:62:7e:0e

Locale: ETSI

Country Code: SG

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

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

Wake On Wireless: Supported

AirDrop: Supported

Status: Connected

Current Network Information:

That is the only network, whole spectrum is free and I have other devices (802.11g and 802.11n) on the same SSID working in mixed G/N mode without interruptions. It's only this particular MacBook that fails to work on N.

Please update this thread

Hello DRW9,

Can you advise the way that you made Mac OS X Lion work with Snow Leopard drivers please?..

Thanks!

Hello moskovit,

I'm curious whether you're still in OS X 10.7.x and using the downgraded driver in a mixed B/G environment. Can you advise whether it's your case still?

Thanks!

arsenyspb wrote:

Hi guys,

QUESTION - what is the latest official remedy from the drivers / oreferences perspective to make 2010-aged MBP with BroadCom WLAN NIC & Driver particulars work as in my case work in a mixed G/N environment?

Beforehand in this thread, I've googled some suggestions to downgrade the driver, or disable the power-saving. What's the status quo?

Let me add some details here. I'm an owner of a mid-2010 MacBook Pro (

MacBookPro6,2) running Mac OS X 10.7.5 (11G63), if anyone from Apple Resellers screens this - S/N is W8013BPNAGV

I concur to some posts in a middle of this thread that say it's Apple's side of the house that drops Wireless-N connectivity. Switching from IEEE802.11n to 802.11g helps and secures stable connection. No, let me state it - it's definitely Apple & Broadcom issue. I put total responsibility on untested interop to Apple as they are releasing the OS and drivers that do not support IEEE802.11n.

ifconfig en1

en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

ether 58:b0:35:62:7e:0e

inet6 fe80::5ab0:35ff:fe62:7e0e%en1 prefixlen 64 scopeid 0x5

inet 192.168.0.173 netmask 0xffffff00 broadcast 192.168.0.255

media: autoselect

status: active

FYI, my iface is

en1:

Card Type: AirPort Extreme (0x14E4, 0x93)

Firmware Version: Broadcom BCM43xx 1.0 (5.106.198.19.22)

MAC Address: 58:b0:35:62:7e:0e

Locale: ETSI

Country Code: SG

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

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

Wake On Wireless: Supported

AirDrop: Supported

Status: Connected

Current Network Information:

That is the only network, whole spectrum is free and I have other devices (802.11g and 802.11n) on the same SSID working in mixed G/N mode without interruptions. It's only this particular MacBook that fails to work on N.

Please update this thread

My airport interface is shown as:

en1:

Card Type: AirPort Extreme (0x14E4, 0x8D)

Firmware Version: Broadcom BCM43xx 1.0 (5.106.98.81.22)

MAC Address: 00:23:6c:9a:14:ec

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, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 149, 153, 157, 161, 165

Wake On Wireless: Supported

AirDrop: Supported

Status: Connected

I've never had this problem on my Macbook pro. It's always worked fine. Mine is a little older than yours by version number. I did buy this in spring of 2009.

I use 5ghz for all my wireless on my devices which support it. I have 2.4ghz for devices which don't have 5ghz radios. I've used netgear radios for quite some time. I also have a TimeCapsule that I use some times when I need my netgear router at some other event/location. I also have radios from http://ubnt.com that I use, and I've not had problems with those either.

The number one thing that I will stress over and over, is make sure you have the latest firmware installed for your wireless router. The manufactures are shipping new products before the firmware is finished, and expecting their users to use the web interface to the router to set it up, and that interface usually tries to automatically update the firmware in the router.

What WiFi router are you using? Have tried to check and make sure you have the latest firmware update?

Hi gponei,

5 Ghz spectrum is not possible where I'm.

I'm using Cisco DPC3925 yes latest firmware of course, that supports 802.11bgn, bg or G only modes.

As said, I'm only observing the above said behavior on MBP with Wireless-N. I also have few other laptops with Windows 7 on them working excellent on full 802.11n connection.

I've plugged in the kext as per http://rys.sommefeldt.com/2012/05/13/backup-and-restore-os-x-lion-wi-fi-kext.htm l but after this mod for the two last hours 802.11n connection of MacBook Pro experiences enormous latency. Same host from nearby Windows 7 laptop pings with stable 320...350 ms, while MBP kext/driver introduces stack latency up to 1100...1200 ms.

After observing this for 1+ hours, I've downgraded Wireless radio mode on AP to 802.11b/g (not N) mode.

I hate it ((

Any other ideas on any other kexts to drop in?

arsenyspb wrote:

Hi gponei,

5 Ghz spectrum is not possible where I'm.

I'm using Cisco DPC3925 yes latest firmware of course, that supports 802.11bgn, bg or G only modes.

What security mode are you using? Can you try WPA2-AES? It might not be supported on all of your devices, but if you can try it on your Mac, it would be interesting to see if it changes what you are experiencing. I looked at the manual for your router at http://www.cisco.com/en/US/docs/video/at_home/Cable_Modems/3900_Series/4021192_B .pdf and I am look at pages 38-50 or so. It seems like you might also turn off WPS so that it's not trying to auto register anything at the router, as described on page 38. I've never used WPS on routers because I know how to set things up manually. Turning it off might disable some code in the router which is creating this problem. The manual says that WPA-TKIP can not be used for 802.11n, so I guess you've already been using AES. Have you been using WPA or WPA2?