Q: WiFi disconnects by it self Mavericks problems

Had issue with Firefox and Safari (not using airport). Will look around to see if can force wifi to stay awake! Thanks.

My disconnection problems have been solved using the "caffeinate" suggestion posted in this discussion. It is a bit of an inconvenience to open a terminal window whenever I log on, but I greatly appreciate that someone was kind enough to post that advice.

Obviously, I permanent fix is required, and I do hope (make that, "expect") that Apple will resolve this very vexing problem with a Mavericks patch ASAP.

I've been good all week without any further disconnection issues since performing the fix posted above "renew DHCP Lease, uncheck Keychain in iCloud, and then restart the computer".   (using a newish MacBook Air with Mavericks upgrade and an all-in-one cable company supplied modem / wireless router).  Doesn't make sense, but worked for me.  Have not turned Keychain back on in iCloud because I don't want to jinx it.

The thing about Safari I said earlier? Scracth that, it happens whetever it is open or not. My solution so far is a "useful" one for me: installed the Google Drive agent to keep the connection open. Since I use it anyway, it works far better.

I remember an option in Onyx or Cocktail that allows you to stop Mavericks from quitting unused apps. Haven't tried it yet, but when I do I will post the results.

Yes, this worked for me too.

I wrote a simple Apple Script on Automator to avoid having to do this manually.

You can save it as an Application and have it run on login.

No rocket science here, but beats having to specifically remember to run this.

on run {input, parameters}

          tell application "Terminal"

                    activate

                    do script with command "caffeinate"

          end tell

end run

Just to throw my hat into the ring...

I will be browsing and internet connection fails.  Only fix is to restart.  Apparently this is not a priority fix for Apple.  Sad.

Updates to Mac OSX are increasingly becoming painful.  Lack of support for MacPro--early Intel models--is also frustrating and the reason I am returning to Windows workstations.

That aside, I am having the internet connection issues after updating to Mavericks. 

I was having intermintent wifi connectivity problems on a MacBook Pro with Time Warner Cable Modem and an Apple Time Capsule 4GB as the router.

My solution was to turn off the option for IPv6. I set it to Automatic

In Airport Utility I went to Internet tab and then Internet Options and put IPv6 Configuration to Local-link.

It forces it to use IPv4 and all is well.

@ireadcharts - Making your suggested change to the airport config fixed the issue for me. thanks!

Here are some interesting observations, I'm not qualified to say what it means exactly but I believe that it does point to something in Mavericks causing wi-fi issues.

Like others on this formum, since upgrading, I have been having connection problems with frequent dropping of internet connection with wi-fi still showing as being connected and complete disconnections.  It got so bad I have been using an ethernet cable and a TP Link which at least gave me a reliable connection.  I have tried all the suggestions on all the forums (apart from fiddling round with files in terminal) caffeinating and so on without any improvement.

The genius bar had a look at my MBP and found no issues and the wi-fi worked fine in the store. They said that the problem was most likely due to the cheap and nasty BT router but I don't believe that this is true as all the other machines in the house work 100%. I have noticed that if I use the MBP very near to the router the connection works well.

I have had a new large disk installed and the original disk retained as a second disk.  I felt comfortable with re-installing Mountain Lion on the old disk and immediately the wi-fi worked again with many more hubs showing on the list of available networks.

The really strange thing is that when I rebooted with Mavericks there was a noticeable improvement in wi-fi.  It's still not as good as with Mountain Lion but definitely better than before. Why???

To my mind there is something in Mavericks that is the cause of this and the boffins at Apple have to put all our observations together to help them get to the bottom of the issues and provide a solution.  We have done our bit now it's down to Apple.

Model Name:          iMac

  Model Identifier:          iMac12,2

  Processor Name:          Intel Core i7

  Processor Speed:          3.4 GHz

  Number of Processors:          1

  Total Number of Cores:          4

  L2 Cache (per Core):          256 KB

  L3 Cache:          8 MB

  Memory:          12 GB

  Boot ROM Version:          IM121.0047.B1F

  SMC Version (system):          1.72f2

  Serial Number (system):          C0*******HJW

I have $10000 AUD worth of imac, air extreme, time machine, Ipads x2 and 2x iphone 5.

I think the least they could do is fix these issues.

I have spent hours trying to fix this problem presently i have air extreme and time machine linked with with ethernet cables to get them to link to the system if i wanted more cables i wouldnt have bought a wifi set up.

What really kills me is when you read the os manual for each and they tell you of the ease of wifi connectivity and set up.

Sorry i have spent valuable hours of my free time trying to fix this this problem and it grinds my grapes.

Apologies to those sensitive souls who might be offended by my rant.

<Edited by Host>

After spending far too long trying to resolve this, have rolled back to Snow Leopard, and Safari and wifi now working fine.  So clearly a Mavericks issue (not that I ever doubted).  Disappointed (to put it mildly) that Apple have't acknowledged this or provided a fix. 

Tried all above solutions and none of them worked. As final random try I push the reset button of my router (a Belkin N+) and that seems to solve my problem. I don't know why this works: maybe it is some sort of xmas magic

Here is what I have when issuing a PING.  27% packet loss from wi fi - Good Grief ! 

64 bytes from 10.222.48.1: icmp_seq=135 ttl=255 time=3.691 ms
64 bytes from 10.222.48.1: icmp_seq=136 ttl=255 time=3.667 ms
64 bytes from 10.222.48.1: icmp_seq=137 ttl=255 time=3.717 ms
Request timeout for icmp_seq 138
Request timeout for icmp_seq 139
Request timeout for icmp_seq 140
Request timeout for icmp_seq 141
Request timeout for icmp_seq 142
64 bytes from 10.222.48.1: icmp_seq=143 ttl=255 time=6.203 ms
64 bytes from 10.222.48.1: icmp_seq=144 ttl=255 time=4.899 ms
64 bytes from 10.222.48.1: icmp_seq=145 ttl=255 time=2.553 ms
64 bytes from 10.222.48.1: icmp_seq=146 ttl=255 time=3.641 ms
64 bytes from 10.222.48.1: icmp_seq=147 ttl=255 time=3.632 ms
64 bytes from 10.222.48.1: icmp_seq=148 ttl=255 time=3.636 ms
64 bytes from 10.222.48.1: icmp_seq=149 ttl=255 time=3.607 ms
64 bytes from 10.222.48.1: icmp_seq=150 ttl=255 time=5.789 ms
64 bytes from 10.222.48.1: icmp_seq=151 ttl=255 time=3.713 ms
64 bytes from 10.222.48.1: icmp_seq=152 ttl=255 time=3.928 ms
64 bytes from 10.222.48.1: icmp_seq=153 ttl=255 time=3.687 ms
64 bytes from 10.222.48.1: icmp_seq=154 ttl=255 time=3.715 ms
64 bytes from 10.222.48.1: icmp_seq=155 ttl=255 time=4.397 ms
64 bytes from 10.222.48.1: icmp_seq=156 ttl=255 time=3.628 ms
64 bytes from 10.222.48.1: icmp_seq=157 ttl=255 time=3.941 ms
64 bytes from 10.222.48.1: icmp_seq=158 ttl=255 time=2.639 ms
Request timeout for icmp_seq 159
Request timeout for icmp_seq 160
Request timeout for icmp_seq 161
Request timeout for icmp_seq 162
Request timeout for icmp_seq 163
64 bytes from 10.222.48.1: icmp_seq=164 ttl=255 time=1.908 ms
64 bytes from 10.222.48.1: icmp_seq=165 ttl=255 time=24.837 ms
64 bytes from 10.222.48.1: icmp_seq=166 ttl=255 time=4.694 ms
64 bytes from 10.222.48.1: icmp_seq=167 ttl=255 time=3.693 ms
64 bytes from 10.222.48.1: icmp_seq=168 ttl=255 time=5.076 ms
64 bytes from 10.222.48.1: icmp_seq=169 ttl=255 time=3.617 ms
64 bytes from 10.222.48.1: icmp_seq=170 ttl=255 time=3.795 ms
64 bytes from 10.222.48.1: icmp_seq=171 ttl=255 time=3.756 ms
64 bytes from 10.222.48.1: icmp_seq=172 ttl=255 time=3.592 ms
64 bytes from 10.222.48.1: icmp_seq=173 ttl=255 time=3.679 ms
64 bytes from 10.222.48.1: icmp_seq=174 ttl=255 time=3.625 ms
64 bytes from 10.222.48.1: icmp_seq=175 ttl=255 time=3.618 ms
64 bytes from 10.222.48.1: icmp_seq=176 ttl=255 time=1.984 ms
64 bytes from 10.222.48.1: icmp_seq=177 ttl=255 time=3.896 ms
64 bytes from 10.222.48.1: icmp_seq=178 ttl=255 time=3.609 ms
Request timeout for icmp_seq 179
Request timeout for icmp_seq 180
Request timeout for icmp_seq 181
Request timeout for icmp_seq 182
Request timeout for icmp_seq 183
Request timeout for icmp_seq 184
64 bytes from 10.222.48.1: icmp_seq=185 ttl=255 time=3.558 ms
64 bytes from 10.222.48.1: icmp_seq=186 ttl=255 time=3.625 ms
64 bytes from 10.222.48.1: icmp_seq=187 ttl=255 time=3.702 ms
^C
--- 10.222.48.1 ping statistics ---
188 packets transmitted, 137 packets received, 27.1% packet loss
round-trip min/avg/max/stddev = 1.637/4.000/50.429/4.491 ms

I have just tried the suggestion of configuring IPv6 to local-link and this has improved the situation even if it's still not as good as it was at picking up the router signal from any distance.

If this is a real observation and not just a temporary fluke then it should surely provide a pointer to what is wrong with Mavericks.  APPLE BOFFINS PLEASE NOTE!

Thanks MacManNYC

People have reported this with each and every OS update. At all times, <insert previous OS here> the the bestest, most stable OS ever. If you don't believe me, just search the old Mountain Lion, Lion, Snow Leopard, Leopard, etc. forums. APPLE SUPPORT COMMUNITIES MEMBERS PLEASE NOTE!