Currently Being ModeratedJan 31, 2012 9:00 AM (in response to lrogersinlv)
Since I've installed the update of Airport Configuration Ultility and I restart my MacBook I've no problems with WiFi dropping out (already 5 hours), normally WiFi drops every 10 minutes out. Maybe Apple has found the problem and fixed it?
Currently Being ModeratedJan 31, 2012 9:06 AM (in response to iRik1988)
I finaly found out what the problem is! it is a Router issue you need to make sure your router sends out only one signal like B or G only not both that proberly is conflicting with OSX 10.7.
This is also what fixed it in my case.
Connections were timing out while the WiFi icon still showed "connected".
Set my router to "G" speed only, no more connection loss on my 2 white Lion MacBooks
Currently Being ModeratedJan 31, 2012 9:17 AM (in response to Shootist007)
Yes, it's an OS X issue.
I suspect it's something about how Lion handles mixed-mode B/G/N networks.
Macbooks were working fine with Snow Leopard, but not with Lion, no other changes were made to the network.
Still, having a workaround beats waiting for Apple to fix it.
Currently Being ModeratedJan 31, 2012 9:21 AM (in response to BenHart67)
We've done that and other users were effected. What access point are you using? We have all Aruba...
I'm using a cheap TP-Link MR3220 3G Router.
How were the other users affected? Here the most notable change is the loss of 130MBit speed, but all our devices ( 2 Macbooks, iphone 3g, android phone ) keep working.
Currently Being ModeratedJan 31, 2012 9:25 AM (in response to max hampel)
Well, basically the vintages of machines we have on campus are all over the board. While many of them worked with broadcasting only "n", a few of them dropped off the network, had very slow speeds, etc.
I know I'll never have 100% customer satsifaction, but I'd like 99%.
Currently Being ModeratedJan 31, 2012 11:08 AM (in response to Carlo TD)
Carlo TD wrote:
I think you ment to say 10.0.1.1 anyway i dont know the difference between setups of 192.168.1.1 or 10.0.1.1 or 172.16.1.1 ....I think the Apple Extreme/ Time Capsule defults to 10.0.1.1 but i just checked my router, and i must have changed it a long time ago because my settings are 192.168.1.1 other than that i am not sure or dont understand.
Usually, most routers will use the 192.168.X.Y network as the default. But, if you chain some routers together, and the newly connected router sees 192.168.X.Y handed out to it as it's WAN address, it might either pick a different 'X' on the 192.168 network (your old router might use 192.168.1.Y, and your new router might then use 192.168.2.Y for example), or it might just switch to network 10.X.Y.Z.
It's not really important, for most people, what network it "uses", but it must be "routable" from both sides, or your internet access will be broken.
Currently Being ModeratedJan 31, 2012 11:27 AM (in response to renzofromroma)
My conclusion of this story is that there must be some kind of compatibility issue between lion and some routers (not all) located in the wireless protocoll, (maybe gphoney can tell us if it is at TCP level or around it). Most of the people are having no problem with lion, someone posted that apple has problem with linksys and many others have solved just replacing their router. In my home in italy I have no problem at all with the router there, I have problems here with this huawei, that's why I wanted to try to connect my MBP to a different router and, so far, it is working. I cannot simply replace my router because mine is a wi-max internet-connection.
So , gphoney, I don't think there is anything else we can test because, if it is a protocol problem, it must be solved either by apple or by those particular routers manufacturers updating their drivers, and here I don't know who should do it;
We all know, that there are a wide range of things, that seem to "fix" the problem. I, personally, still believe that there are a wide range of "normally occurring" cases of interference and bad wireless protocol behaviors, that create a common "link failure" in the WiFi part of the path. The issue is, that MACOS-X use to deal with those errors okay, and didn't drop connections, but rather silently, recovered and continued on.
I think that what is happening now, is that the link is being dropped, and the interface is losing it's IP address, and is thus not routable. Everyone keeps reporting that their "Airport is up", meaning to me, that they see the wireless icon in the tool bar at the top left of the screen showing that wireless is still connected. Some people have reported that when it fails, that if they open a terminal window, and type "ifconfig -a", and/or "netstat -rn", that there is not an assigned IP address, and/or assigned default route.
What you should see, is something like the following, note the line with the ==>.
gphonei$ ifconfig -a
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::21b:63ff:fea1:fddb%en0 prefixlen 64 scopeid 0x4
==> inet 192.168.1.91 netmask 0xffffff00 broadcast 192.168.1.255
media: autoselect (1000baseT <full-duplex,flow-control>)
That line says that an IPV4 address is assigned to the interface, and shows it to be 126.96.36.199. The output of netstat -rn should be something like the following:
gphonei$ netstat -rn
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 4 6046 en0
That last line, that begins with "default" is the important bit that tells your computer, how to get to the internet. It says that the "gateway" or "default" path out of your local network is through the 192.168.1.1 gateway machine.
The third piece of information that migh be "telling" of what the configuration of the network really is, is the domain name server that your router is telling your computer to use to convert hostnames into their IP addresses.
gphonei$ cat /etc/resolv.conf
# Mac OS X Notice
# This file is not used by the host name and address resolution
# or the DNS query routing mechanisms used by most processes on
# this Mac OS X system.
# This file is automatically generated.
This information also comes from the DHCP response that your computer receives when it has sent out a DHCP request, when the interface is (re)initialized.
So, when your network stops working, you might try these commands real quick, before it fixes itself, or at least before you reset your airport connection, and see what it tells you about the state of your network.
I'm still really believing that the "network interference drops" are just no longer telling the "link management" code that they've actually reset the interface and removed the address allocation/assigment, so that a new DHCP request will be sent back out. Thus, the "wireless" indicates things are up, but there is no address assigned, so it looks like you are not connected, and nobody knows that there is a problem that needs to be fixed.
Currently Being ModeratedJan 31, 2012 11:48 AM (in response to jvant)
Are you in NL and perhaps on an XS4ALL Frtitz!Box by AVM? I have trouble connecting to N-band with the same described problems as anyone else (1.5 mo old iMac 21'' with Lion, straight from the box). Brand new modems by leading provider in NL. Oh yes: they are aware! I just installed the update, need to finish work and shall test asap.
Currently Being ModeratedJan 31, 2012 12:30 PM (in response to jvant)
Jip, they did not. Switched to the AVM Frtitz on BG, on N, with separate network names: a full Windows like freeze up after 6 minutes! Switching to my Timecapsule as had been for 1.5 mo: no problems again. AVM uses WPA + WPA2 mixed mode, Time Capsule uses either WPA or WPA2. I had no problems at all on Time Capsule 5 GHz and WPA2. For a month. To me this seems like a security implementation issue as it differs from router to router, band to band, in combination with both iMacs and MBPs alike. The only difference now being Lion update and security settings. I am working on Time Capsule, and will eventually see the update coming. Good luck all.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points