Issues with PacePlc+WIFI+OSX

[Igor]

Hi,

I have DSL service from Sonic and my configuration is:

Router:
Pace Plc (4111N-030)
Hardware Version: 2701-000816-003
Software Version: 9.5.1.53.1
DSL Modem: A2pD037f.d23c

Laptop:
MacBook Pro Retina 2013 (OSX 10.9.2)

Issue:

When I'm on wifi, every 5-10 minutes I'm loosing connectivity for 10-40 seconds. (Interval the same for days, and periodically increased or decreased). If I'm pinging something picture looks like:

-----
64 bytes from 8.8.8.8: icmp_seq=3077 ttl=46 time=42.046 ms
Request timeout for icmp_seq 68614
....ANOTHER ~30 timeouts....
Request timeout for icmp_seq 68641
64 bytes from 8.8.8.8: icmp_seq=3106 ttl=46 time=41.430 ms
-----

If I plug in into router via wire, everything is good. Also there is no issues on other devices (Ipad, Windows laptop).
During this blackout, if in OSX I'll renew DHCP lease, connectivity is back instantly.

P.S. I'm seeing this issue ONLY on my home internet (with sonic.net router), never seen such issues on any other wifi hotspot I've ever used on my laptop.

What I've tried and it didn't help:

1. New sonic router (the same model)
2. Turn off wifi on sonic router and plug in AirportExpress.

Additional info:
- This started to happen 5-6 months ago. When I've just started to use sonic (Year ago) everything was fine.
- I'm assuming that this issue related to router DHCP, because this is ONLY thing that I didn't touch in configuration.

Any help will be appreciated.

Regards,
Igor

[adame]

Hi Igor,

Thanks for the detailed information. Just to clarify the last part of your post, when you disabled wireless on the Pace and connected via the Airport Express' wireless, you were able to successfully surf, but your connection still dropped out every 5-10 minutes? Can you confirm the IP address you're getting in this configuration is from the airport router? When you lose connectivity behind the airport, are you still able to ping the default gateway given to you by the Airport?

[Igor]

Airport configured in Bridge mode, so I'm always getting IP from sonic router DHCP. When I'm loosing connectivity (with or without airport) nothing is pingable (internet and local router IP).

[dane]

When you plug an Airport in behind a Pace, it automatically extends the current network by bridging, and even allows you to configure it to match the SSID and WPA key. I believe that this allows for proper seamless roaming within the home between the Airport and the Pace unit. It's a great way to extend your WiFi network reach.

But with regards to the occasional issues experienced by the poster, I'd guess DHCP on the Mac or Pace. Does the Mac have any firewall software running on it by chance?

[Igor]

There is no firewalls or any other specific software. I'm seeing this issues only with sonic router. At work or when I;m joining wifi of my neighbors everything is good.

Regards,
Igor

[dane]

There is no firewalls or any other specific software. I'm seeing this issues only with sonic router. At work or when I;m joining wifi of my neighbors everything is good.

Regards,
Igor

Understood, Adam will need to look further into that.

[adame]

I'd like to take a more in depth in look at the circuit. Can you email or private message me your Sonic.net username? My email address is just my username @corp.sonic.net.

[Igor]

Hi Adam,

Thanks a lot for quick response. I've sent email to you with some details.

Regards,
Igor

[dennish00a]

I have exactly this same problem and it is infuriating. I use my laptop all over the world and have ZERO problems with the built-in WiFi--except in my own house! Same deal: periodically I can't ping the router over WiFi, but everything is always fine when plugging in via Ethernet. Just this morning, for example:

64 bytes from 192.168.42.1: icmp_seq=4654 ttl=255 time=1.984 ms
64 bytes from 192.168.42.1: icmp_seq=4655 ttl=255 time=1.345 ms
64 bytes from 192.168.42.1: icmp_seq=4656 ttl=255 time=3.854 ms
Request timeout for icmp_seq 4657
Request timeout for icmp_seq 4658
Request timeout for icmp_seq 4659
Request timeout for icmp_seq 4660
Request timeout for icmp_seq 4661
Request timeout for icmp_seq 4662
Request timeout for icmp_seq 4663
Request timeout for icmp_seq 4664
Request timeout for icmp_seq 4665
Request timeout for icmp_seq 4666
Request timeout for icmp_seq 4667
Request timeout for icmp_seq 4668
Request timeout for icmp_seq 4669
Request timeout for icmp_seq 4670
Request timeout for icmp_seq 4671
Request timeout for icmp_seq 4672
Request timeout for icmp_seq 4673
Request timeout for icmp_seq 4674
Request timeout for icmp_seq 4675
Request timeout for icmp_seq 4676
Request timeout for icmp_seq 4677
Request timeout for icmp_seq 4678
Request timeout for icmp_seq 4679
Request timeout for icmp_seq 4680
Request timeout for icmp_seq 4681
Request timeout for icmp_seq 4682
Request timeout for icmp_seq 4683
Request timeout for icmp_seq 4684
Request timeout for icmp_seq 4685
Request timeout for icmp_seq 4686
Request timeout for icmp_seq 4687
Request timeout for icmp_seq 4688
Request timeout for icmp_seq 4689
Request timeout for icmp_seq 4690
Request timeout for icmp_seq 4691
Request timeout for icmp_seq 4692
64 bytes from 192.168.42.1: icmp_seq=4693 ttl=255 time=3.663 ms
64 bytes from 192.168.42.1: icmp_seq=4694 ttl=255 time=2.030 ms
64 bytes from 192.168.42.1: icmp_seq=4695 ttl=255 time=2.187 ms
64 bytes from 192.168.42.1: icmp_seq=4696 ttl=255 time=2.202 ms
64 bytes from 192.168.42.1: icmp_seq=4697 ttl=255 time=1.823 ms
64 bytes from 192.168.42.1: icmp_seq=4698 ttl=255 time=2.565 ms
64 bytes from 192.168.42.1: icmp_seq=4699 ttl=255 time=3.104 ms
64 bytes from 192.168.42.1: icmp_seq=4700 ttl=255 time=2.176 ms
64 bytes from 192.168.42.1: icmp_seq=4701 ttl=255 time=4.317 ms
64 bytes from 192.168.42.1: icmp_seq=4702 ttl=255 time=38.909 ms
64 bytes from 192.168.42.1: icmp_seq=4703 ttl=255 time=44.077 ms
64 bytes from 192.168.42.1: icmp_seq=4704 ttl=255 time=43.941 ms
Request timeout for icmp_seq 4705
64 bytes from 192.168.42.1: icmp_seq=4706 ttl=255 time=3.588 ms
64 bytes from 192.168.42.1: icmp_seq=4707 ttl=255 time=2.111 ms

This happens every 5-10 minutes. Connection via Ethernet cable is always fine.

[adame]

Hi Dennis,

We'd like to work with you on this problem to see if we can find a common element between your and Igor's set-up. I see you use your Sonic address, so we'll drop you an email there this morning.