Issues with WiFi signal

  • 1
  • Question
  • Updated 2 years ago
Below is some information I have regarding my surroundings, I initially tried using an airport extreme to get WiFi at my dads new house however there was some inconsistencies in the performance of the network so I brought over my Aerohive to get some additional information about the surrounding areas.
I've tried migrating between channels 1/6/11 or putting it on auto and I still will experience sporadic spikes and inconsistent transfer speeds.

For example my MBP connected works just fine however a TV watching netflix in the other room will play on standard definition for about 2 minutes, buffer for a minute and repeat.

Ping response times to the gateway of the network look something like this from the AP itself however from my MBP to the gateway over wireless connection looks something like this, Note I'm about 30ft from AP right now clear line of sight.

ping 10.10.0.1

PING 10.10.0.1 (10.10.0.1): 56 data bytes

64 bytes from 10.10.0.1: icmp_seq=0 ttl=64 time=4.177 ms

64 bytes from 10.10.0.1: icmp_seq=1 ttl=64 time=9.424 ms

64 bytes from 10.10.0.1: icmp_seq=2 ttl=64 time=9.276 ms

64 bytes from 10.10.0.1: icmp_seq=3 ttl=64 time=1.683 ms

64 bytes from 10.10.0.1: icmp_seq=4 ttl=64 time=3.740 ms

64 bytes from 10.10.0.1: icmp_seq=5 ttl=64 time=4.125 ms

64 bytes from 10.10.0.1: icmp_seq=6 ttl=64 time=1.623 ms

64 bytes from 10.10.0.1: icmp_seq=7 ttl=64 time=1.588 ms

64 bytes from 10.10.0.1: icmp_seq=8 ttl=64 time=1.522 ms

64 bytes from 10.10.0.1: icmp_seq=9 ttl=64 time=1.849 ms

64 bytes from 10.10.0.1: icmp_seq=10 ttl=64 time=3.941 ms

64 bytes from 10.10.0.1: icmp_seq=11 ttl=64 time=1.195 ms

64 bytes from 10.10.0.1: icmp_seq=12 ttl=64 time=4.011 ms

64 bytes from 10.10.0.1: icmp_seq=13 ttl=64 time=7.741 ms

64 bytes from 10.10.0.1: icmp_seq=14 ttl=64 time=3.939 ms

64 bytes from 10.10.0.1: icmp_seq=15 ttl=64 time=3.946 ms

64 bytes from 10.10.0.1: icmp_seq=16 ttl=64 time=4.044 ms

64 bytes from 10.10.0.1: icmp_seq=17 ttl=64 time=1.602 ms

64 bytes from 10.10.0.1: icmp_seq=18 ttl=64 time=1.607 ms

--- 10.10.0.1 ping statistics ---

19 packets transmitted, 19 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 1.195/3.739/9.424/2.482 ms

 And from time to time it spikes to 20/400/1000ms 
interference summary throws this out

wifi0: High collision; wifi1: Fair;




AH-2d07c0#show acsp                                                            
Interface Channel select state  Primary channel  Channel width Power ctrl state      Tx power(dbm) 
--------- --------------------- ---------------- ------------- --------------------- -------------
Wifi0     Enable                11               20            Enable                20            
Wifi1     Enable                44               80            Enable                20            


AH-2d07c0#show acsp neighbor 
wifi0(8) ACSP neighbor list: 
Bssid               Mode     Ssid/Hive           Chan  Rssi(dBm)  Aerohive AP  CU CRC STA Channel-width  
0895:2ac1:8bdd      Access   TC8717TD7           1    -43         no           -- --  --  20             
6894:2355:ff89      Access   DVW3201B0C          1    -71         no           -- --  --  20             
2837:3746:e2da      Access   Extreme             1    -88         no           -- --  --  20             
6c70:9fdd:3ffc      Access   Extreme             1    -82         no           -- --  --  20             
f835:dd3a:4f3d      Access   snoopy1             1    -87         no           -- --  --  20             
f88e:858b:4cbf      Access   sanderson           3    -83         no           -- --  --  20             
dcef:099a:b62f      Access   Karr                3    -80         no           -- --  --  20             
deef:099a:b620      Access   NETGEAR-Guest       3    -79         no           -- --  --  20             
74d0:2bd0:f9e8      Access   Sparks home         6    -72         no           -- --  --  20             
f87b:8c5c:b5f6      Access   Amped_RTA1750_2.4   6    -60         no           -- --  --  40+            
001d:7e4e:a8d8      Access   linksys             6    -84         no           -- --  --  20             
687f:742e:0100      Access   snoopy              6    -71         no           -- --  --  20             
4494:fc44:f091      Access   NETGEAR75           7    -56         no           -- --  --  20             
48f8:b3ab:4d07      Access   Boxer               10   -84         no           -- --  --  40-            
4ef8:b3ab:4d07      Access   Boxer-guest         10   -85         no           -- --  --  40-            
48f8:b333:cac7      Access   FindAHobby2016      11   -84         no           -- --  --  20             
a01b:2900:27cb      Access   WIN_27cc            11   -82         no           -- --  --  20             
0cf8:93ea:7100      Access   TG862G02            11   -84         no           -- --  --  20             
f88e:8592:0d2b      Access   WIN_0d29            11   -81         no           -- --  --  20             
e0b7:0a05:36f0      Access   WIN_3786            11   -84         no           -- --  --  20             
841b:5ef5:aec2      Access   aaa                 11   -85         no           -- --  --  20             
28c6:8e8b:ef4a      Access   NETGEAR89           1    -84         no           -- --  --  20             
b83e:59e0:5419      Access   DIRECT-roku-4F68A8  11   -78         no           -- --  --  20             
          
          
wifi1(9) ACSP neighbor list: 
Bssid               Mode     Ssid/Hive           Chan  Rssi(dBm)  Aerohive AP  CU CRC STA Channel-width  
0895:2ac1:8bde      Access   TC8717TD7-5G        153  -51         no           -- --  --  80             
4494:fc44:f090      Access   NETGEAR75-5G        153  -70         no           -- --  --  40-            
74d0:2bd0:f9ec      Access   Sparks home         153  -83         no           -- --  --  40-            
f87b:8c5c:b5f7      Access   Amped_RTA1750_5.0   36   -84         no           -- --  --  80             
eab7:0a05:36f3      Access   WIN5_3786           40   -78         no           -- --  --  80             
e0b7:0a05:36f3      Access                       40   -78         no           -- --  --  80             
e6b7:0a05:36f3      Access                       40   -78         no           -- --  --  80             
6c70:9fdd:3ffd      Access   Extreme             149  -89         no           -- --  --  80             
dcef:099a:b62e      Access   NETGEAR94-5G        153  -87         no           -- --  --  80             
          
          
AH-2d07c0#
AH-2d07c0#
AH-2d07c0#
                                                                                                                                                                                                                                                                                                                                AH-2d07c0#show acsp channel-info detail | inc channel                          
CU=channel utilization; TxU=Tx utilization; IU=interference utilization
Lowest cost channel: 11, lowest-cost: 6
Scanned channels: 11
Interference alert triggered channel re-evaluation: 0
Channel 1 Cost:12 
Channel deduction: 6 (CU: 15%, TxU: 1%, IU: 8%, CRC: 1%)
Penalty on channel: 0
Wide channel penalty: 0
Overlapping channel adjustments: 0
Channel 2 Cost:32767 (overlap)
Channel deduction: 6 (CU: 10%, TxU: 0%, IU: 5%, CRC: 0%)
Penalty on channel: 0
Wide channel penalty: 0
Overlapping channel adjustments: 40
Channel 3 Cost:32767 (overlap)
Channel deduction: 0 (CU: 8%, TxU: 0%, IU: 3%, CRC: 1%)
Penalty on channel: 0
Wide channel penalty: 0
Overlapping channel adjustments: 40
Channel 4 Cost:32767 (overlap)
Channel deduction: 0 (CU: 4%, TxU: 0%, IU: 3%, CRC: 0%)
Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 40
Channel 5 Cost:32767 (overlap)
                Channel deduction: 12 (CU: 22%, TxU: 2%, IU: 11%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 40
Channel 6 Cost:12 
                Channel deduction: 6 (CU: 17%, TxU: 0%, IU: 8%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 0
Channel 7 Cost:32767 (overlap)
                Channel deduction: 6 (CU: 12%, TxU: 0%, IU: 6%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 40
Channel 8 Cost:32767 (overlap)
                Channel deduction: 0 (CU: 7%, TxU: 0%, IU: 3%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 40
Channel 9 Cost:32767 (overlap)
                Channel deduction: 20 (CU: 21%, TxU: 0%, IU: 21%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 40
Channel 10 Cost:32767 (overlap)
                Channel deduction: 10 (CU: 18%, TxU: 0%, IU: 14%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 40
Channel 11 Cost:6 
                Channel deduction: 6 (CU: 19%, TxU: 0%, IU: 7%, CRC: 2%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 0
Lowest cost channel: 44, lowest-cost: 0
Scanned channels: 9
Interference alert triggered channel re-evaluation: 0
Channel 36 Cost:0 
                Channel deduction: 0 (CU: 9%, TxU: 3%, IU: 2%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 0
Channel 40 Cost:32767 (offset)
                Channel deduction: 4 (CU: 9%, TxU: 1%, IU: 5%, CRC: 1%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 0
Channel 44 Cost:0 
                Channel deduction: 0 (CU: 1%, TxU: 0%, IU: 1%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 0
Channel 48 Cost:32767 (offset)
                Channel deduction: 0 (CU: 1%, TxU: 0%, IU: 1%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 0
Channel 149 Cost:0 
                Channel deduction: 0 (CU: 2%, TxU: 0%, IU: 1%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 0
Channel 153 Cost:32767 (offset)
                Channel deduction: 0 (CU: 3%, TxU: 0%, IU: 1%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 0
Channel 157 Cost:0 
                Channel deduction: 0 (CU: 1%, TxU: 0%, IU: 1%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 0
Channel 161 Cost:32767 (offset)
                Channel deduction: 0 (CU: 1%, TxU: 0%, IU: 1%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 0
Channel 165 Cost:32767 (offset)
                Channel deduction: 0 (CU: 1%, TxU: 0%, IU: 1%, CRC: 0%)
                Penalty on channel: 0
                Wide channel penalty: 0
        Overlapping channel adjustments: 0
AH-2d07c0#

Any tips or suggestions on what I can do to improve the performance of the network would be much appreciated.

The amount of experience I have on more in depth troubleshooting of wireless networks when it comes to spectral analysis and reading of signal levels is limited.
Photo of CaptainWTF

CaptainWTF

  • 4 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of BJ

BJ, Champ

  • 374 Posts
  • 45 Reply Likes
Do you have the ap associated with hive manager or just stand-alone, using cli commands? If it's reporting to hivemanager, I would run client monitor to see what the TV is doing first. I would also take a look at the tv radio spec. I would assume it's using 2.4 GHz which, as you can see, has plenty of contention.

Best,
BJ
Photo of kamalesh babu Vutukuri

kamalesh babu Vutukuri

  • 2 Posts
  • 0 Reply Likes
you should try reset the modem and reconfigure it. 
Photo of CaptainWTF

CaptainWTF

  • 4 Posts
  • 0 Reply Likes
Has nothing to do with it. Modem is in passthrough mode to a sonicwall. Wired network works just fine.

Issues with congestion over the WiFi and I'm not sure how to address the issue.
Photo of kamalesh babu Vutukuri

kamalesh babu Vutukuri

  • 2 Posts
  • 0 Reply Likes
You might have to switch to 5ghz band or get a bigger radio and see how it works since it has  more than 3 channels . you can try adding AP but that is the last option i assume.i dont see any overlap in the logs.Hope this helps.
Photo of Pekka Halonen

Pekka Halonen

  • 4 Posts
  • 0 Reply Likes
Well IMHO your log quotes explain the situation well.

wifi0 = 2.4 Ghz
wifi1 = 5.2 Ghz

You have your 2.4 set on channel 11. It cleary is the best choise for this environment.
There are  7 low level interefers on that channel and 1 bit higher ( -78db) DIRECT-roku-4F....
Then there are few retards  on channel 10 creating all that noise/low SNR on channel 11. yes happily they are not that loud, unber -80db.
incomes the "channel 7"  and NETGEAR75 with heafty -56 db. It allso gives overlap till ch9.

48f8:b333:cac7      Access   FindAHobby2016      11   -84         no           -- --  --  20           
a01b:2900:27cb      Access   WIN_27cc            11   -82         no           -- --  --  20             
0cf8:93ea:7100      Access   TG862G02            11   -84         no           -- --  --  20             
f88e:8592:0d2b      Access   WIN_0d29            11   -81         no           -- --  --  20             
e0b7:0a05:36f0      Access   WIN_3786            11   -84         no           -- --  --  20             
841b:5ef5:aec2      Access   aaa                 11   -85         no           -- --  --  20             
28c6:8e8b:ef4a      Access   NETGEAR89           1    -84         no           -- --  --  20             
b83e:59e0:5419      Access   DIRECT-roku-4F68A8  11   -78         no           -- --  --  20       


If your devices can reach to -50db on 2.4 Ghz.. then SNR will be some 50% of payload over interrefers. Remember that wifi is halfduplex so it actually cuts down the air time to 25% of optimal. And that is not much. I might need to stand corrected with my math but this gives you the clue, why wifi0 says "high collision". All of the 7 overlappers are sharing that 25% of timewindow and there is not much to share. I Assume it seems alike bad to other 11ch ssid holders as well.

In that specific case Karr, NETGEAR-Guest and sanderson should have their fair share of information and change from ch 3 to ch1 or ch6 or ch 11. Rather fully overlapping than one/two aside which makes it all noise.
Allso should that NETGEAR75, Boxer and Boxer-guest get their share of whoopin' and  find their spot on channels 1, 6 or 11. Rather than flooding airtime of everyone. 
All in all, 2.4 seems like misery to me in your case.

On 5.2Ghz you have your channel set on 44. No overlappers. Which is good. Best audible neighbour is on channel 153 with -51db. I assume it is in same space as you are.
 You have these channels to choose from in US: 36, 40, 44, 48, 149, 153, 157, 161. (according to: http://bradsfavorite.com/avoid-interference-5-ghz-wifi-5-8-ghz-cordless-phones/)
All free channels are 44(only you, tough) 48, 157, 161.
Which gives you a good idea why this one is diagnosed as "wifi1: fair". Only source of collision are your own devices. Remember wifi is halfduplex and one at the time traffic. So the more clients, the more alikely you get collisions.

0895:2ac1:8bde      Access   TC8717TD7-5G        153  -51         no           -- --  --  80             
4494:fc44:f090      Access   NETGEAR75-5G        153  -70         no           -- --  --  40-            
74d0:2bd0:f9ec      Access   Sparks home         153  -83         no           -- --  --  40-          
f87b:8c5c:b5f7      Access   Amped_RTA1750_5.0   36   -84         no           -- --  --  80             
eab7:0a05:36f3      Access   WIN5_3786           40   -78         no           -- --  --  80             
e0b7:0a05:36f3      Access                       40   -78         no           -- --  --  80             
e6b7:0a05:36f3      Access                       40   -78         no           -- --  --  80             
6c70:9fdd:3ffd      Access   Extreme             149  -89         no           -- --  --  80             
dcef:099a:b62e      Access   NETGEAR94-5G        153  -87         no           -- --  --  80   

[quote]
wifi0: High collision; wifi1: Fair;




AH-2d07c0#show acsp                                                            
Interface Channel select state  Primary channel  Channel width Power ctrl state      Tx power(dbm) 
--------- --------------------- ---------------- ------------- --------------------- -------------
Wifi0     Enable                11               20            Enable                20            
Wifi1     Enable                44               80            Enable                20            


AH-2d07c0#show acsp neighbor 
wifi0(8) ACSP neighbor list: 
--     
          
          
wifi1(9) ACSP neighbor list: 
--         
[/quote]
Photo of Pekka Halonen

Pekka Halonen

  • 4 Posts
  • 0 Reply Likes
Well I had to double post, cause more of my typing would not have fit in the response box. sorry for long ansver.

Considering video the most airtime consuming way to use wifi, it is only logical that you will see issues on 2.4 ghz band. Because of so low signal to noise ratio dropping your actual troughtput and sharing available airtime with that many other users as well.

Watching video over wifi in bad performance environment is not that simple. Consider it as continuous stream of airtime needed.

what could help you, that would be to increase the buffer size on your playback device. Lift it up atleast to 5min or rather to 10minutes. It could help, but only for limited time of playback. Say for an 1hour 30minutes, it could not cope with that. Buffer would runout at some point and then you would have that 10minutes of waiting a head..
Photo of CaptainWTF

CaptainWTF

  • 4 Posts
  • 0 Reply Likes
I appreciate the input.

I will be using 5 wherever possible however most devices in the environment are 2.4 such as the televisions and laptops. Only the newer iPads and iPhones there are capable of utilizing the AC
Photo of CaptainWTF

CaptainWTF

  • 4 Posts
  • 0 Reply Likes
It may be a deal where I just need to leave the 2.4 on auto and have them suck it up. 

You could try to take all the siding off the house & put RF shielding paint in lmao
Photo of Andrew Garcia

Andrew Garcia, Official Rep

  • 368 Posts
  • 120 Reply Likes
Since you are stuck on 2.4, there is always a chance that someone's microwave or cordless phone is screwing with you. Probably worth look at the spectrum analyzer for awhile.
Photo of BJ

BJ, Champ

  • 374 Posts
  • 45 Reply Likes
Is it an older TV with an Ethernet port?

Best,
BJ
Photo of Arison Mercado

Arison Mercado

  • 113 Posts
  • 8 Reply Likes
I recommend having the 5Ghz power settings higher than the 2.4 and adjusting the data rates on both 2.4 and 5ghz.