Issues with PacePlc+WIFI+OSX

[Guest]

Any progresses being made with this issue?

I've been having a similar issue where the WiFi connection drops for 10~50 seconds every 2 or 3 minutes on my MacBook Pro and my MacBookAir - both mid-2013 (see ping trace below)

I just got a new 4111N-030 from SONIC and it's still happening.

64 bytes from 192.168.42.1: icmp_seq=2148 ttl=255 time=1.440 ms
64 bytes from 192.168.42.1: icmp_seq=2149 ttl=255 time=5.504 ms
Request timeout for icmp_seq 2150
Request timeout for icmp_seq 2151
Request timeout for icmp_seq 2152
Request timeout for icmp_seq 2153
Request timeout for icmp_seq 2154
Request timeout for icmp_seq 2155
Request timeout for icmp_seq 2156
Request timeout for icmp_seq 2157
Request timeout for icmp_seq 2158
Request timeout for icmp_seq 2159
Request timeout for icmp_seq 2160
Request timeout for icmp_seq 2161
Request timeout for icmp_seq 2162
Request timeout for icmp_seq 2163
Request timeout for icmp_seq 2164
Request timeout for icmp_seq 2165
Request timeout for icmp_seq 2166
Request timeout for icmp_seq 2167
Request timeout for icmp_seq 2168
Request timeout for icmp_seq 2169
Request timeout for icmp_seq 2170
Request timeout for icmp_seq 2171
Request timeout for icmp_seq 2172
Request timeout for icmp_seq 2173
Request timeout for icmp_seq 2174
Request timeout for icmp_seq 2175
Request timeout for icmp_seq 2176
Request timeout for icmp_seq 2177
Request timeout for icmp_seq 2178
Request timeout for icmp_seq 2179
Request timeout for icmp_seq 2180
Request timeout for icmp_seq 2181
Request timeout for icmp_seq 2182
64 bytes from 192.168.42.1: icmp_seq=2183 ttl=255 time=1.885 ms
64 bytes from 192.168.42.1: icmp_seq=2184 ttl=255 time=3.223 ms
64 bytes from 192.168.42.1: icmp_seq=2185 ttl=255 time=2.460 ms
64 bytes from 192.168.42.1: icmp_seq=2186 ttl=255 time=2.048 ms

[jmwade32]

I'm having a similar issue with my MacBook (2008 model). It works fine at work or on any other Wifi connection but at home, the whole computer freezes after 5 minutes. Took it to the Apple Store and they made me look stupid because there were no issues while at the store and on their connection. I have no trouble with any other devices that are connected to my home network. Would love to hear of some type of fix.

[lbrooke]

I'm having a similar issue with my MacBook (2008 model). It works fine at work or on any other Wifi connection but at home, the whole computer freezes after 5 minutes. Took it to the Apple Store and they made me look stupid because there were no issues while at the store and on their connection. I have no trouble with any other devices that are connected to my home network. Would love to hear of some type of fix.

I took a look at your account and I see that you have the FTTN service. We have run across a few customers who have had similar issues as you (I'm assuming this didn't start happening until the FTTN was installed?) and we have discovered that disabling IPv6 has helped with this problem. To disable this on your Mac go to System Preferences > Network > Airport > Click on Advanced then on the TCP/IP tab, click on Configure IPv6 and set it OFF.

Please let us know if this helps or if you continue to experience further issues. You can also give Support a call so that we can do some additional troubleshooting with you, we can be reached at 1.888.766.4233 and are available 7 days a week from 8am-10pm.

[lbrooke]

Any progresses being made with this issue?

I've been having a similar issue where the WiFi connection drops for 10~50 seconds every 2 or 3 minutes on my MacBook Pro and my MacBookAir - both mid-2013 (see ping trace below)

I just got a new 4111N-030 from SONIC and it's still happening.

64 bytes from 192.168.42.1: icmp_seq=2148 ttl=255 time=1.440 ms
64 bytes from 192.168.42.1: icmp_seq=2149 ttl=255 time=5.504 ms
Request timeout for icmp_seq 2150
Request timeout for icmp_seq 2151
Request timeout for icmp_seq 2152
Request timeout for icmp_seq 2153
Request timeout for icmp_seq 2154
Request timeout for icmp_seq 2155
Request timeout for icmp_seq 2156
Request timeout for icmp_seq 2157
Request timeout for icmp_seq 2158
Request timeout for icmp_seq 2159
Request timeout for icmp_seq 2160
Request timeout for icmp_seq 2161
Request timeout for icmp_seq 2162
Request timeout for icmp_seq 2163
Request timeout for icmp_seq 2164
Request timeout for icmp_seq 2165
Request timeout for icmp_seq 2166
Request timeout for icmp_seq 2167
Request timeout for icmp_seq 2168
Request timeout for icmp_seq 2169
Request timeout for icmp_seq 2170
Request timeout for icmp_seq 2171
Request timeout for icmp_seq 2172
Request timeout for icmp_seq 2173
Request timeout for icmp_seq 2174
Request timeout for icmp_seq 2175
Request timeout for icmp_seq 2176
Request timeout for icmp_seq 2177
Request timeout for icmp_seq 2178
Request timeout for icmp_seq 2179
Request timeout for icmp_seq 2180
Request timeout for icmp_seq 2181
Request timeout for icmp_seq 2182
64 bytes from 192.168.42.1: icmp_seq=2183 ttl=255 time=1.885 ms
64 bytes from 192.168.42.1: icmp_seq=2184 ttl=255 time=3.223 ms
64 bytes from 192.168.42.1: icmp_seq=2185 ttl=255 time=2.460 ms
64 bytes from 192.168.42.1: icmp_seq=2186 ttl=255 time=2.048 ms

I'm sorry to hear you're still experiencing issues even after getting a new modem. If you could send us your account information we'd more than happy to take a look to see what might be going on

[kevinmcm]

Isn't 300 seconds (5 minutes) the typical WPA-PSK key rotation interval? The system log on the laptop probably has more info. There may be SSID collisions or WiFi client bugs slowing down renewal. It normally takes a second or two to complete.

[adame]

I agree with Kevin that this sounds like a key issue. If you're using Mountain Lion or later, I'd recommend launching the Wireless Diagnostics Utility (more info here: https://support.apple.com/en-us/HT202663) and selecting the option to "Monitor my Wi-Fi connection." This should generate a report when it's finished, including logs that I would love to take a look at.

[Guest]

I'm experiencing the same symptoms. Any solution?

[adame]

What issue is it exactly? What hardware are you using? Have you had a chance to run the wireless diagnostic utility? If you have a Sonic account, I'd be happy to troubleshoot this with you one-on-one.

[cariesaxton]

I have this same problem. I've called Sonic support 3 times and no one has been able to help. Has anyone found a solution???

[thomas_l]

I have this same problem. I've called Sonic support 3 times and no one has been able to help. Has anyone found a solution???

Hi - something we've sometimes seen cause an issue wherein wireless is not working on a specific device (but is working on others) is when a wireless access point is broadcasting the same wireless network name on both the 2.4GHz and 5GHz frequencies. If you are using a Sonic-provided Pace 4111N for your wireless, this would not apply as it doesn't have 2.4GHz capabilities, but if you are using a Pace 5268AC or your own wireless access point that has 5GHz capabilities, it may be worth making sure the 2.4GHz and 5GHz networks are broadcasting with different SSID name information (I usually just add a -5 to the end of the 5GHz network name, for example changing "Sonic-001" to "Sonic-001-5"), and then attempting to see if you are able to successfully connect the device in question.

Please note that any devices that were previously connected to the network whose name was changed will have to manually reconnect.