topic WLC 2504 Slow download speed on wireless after switching ISP in Wireless

WLC 2504 Slow download speed on wireless after switching ISP

dpp021189 — Mon, 05 Jul 2021 10:23:20 GMT

A client of mine recently switched to Comcast Business for their ISP. The wired connections work great, but ever since the switch over, the wireless seems to be terribly slow. I have uploaded the client detail information of the machine I am working on and wlan settings. This is across the wireless network, so it is not isolated to this one device. The speed seems to be very sporadic, but I never actually lose the connection, just the speed dwindles down to nothing during speed tests. I am not sure where to go from here.

do you have a real wireless

ali aqrabawi — Sun, 14 Jun 2015 17:33:19 GMT

do you have a real wireless throughput test ?

Iperf between a wireless client as iperf client , and wired client as iperf server is same vlan as the wireless client ,,

test for both tcp and udp .

the client RSSI and SNR is more than perfect , so you should get a good wireless throughput.

i have a concern why about the WLAN interface which is mapped to mgmt interface ,

can you confirm that the client got an ip from same vlan as mgmt vlan ?

client that operating in same vlan as mgmt vlan will have issues, as this vlan is filled with high priority traffic and multicast/broadcast traffics,

Just to add, you should not

Scott Fella — Sun, 14 Jun 2015 17:44:52 GMT

Just to add, you should not have WPA TKIP or WPA2 AES enabled together or a mix and match of both. You should just have WPA2 AES configured first of all. This would of been an issues in general and doesn't have to do with Internet access at all. Once you fix that piece, then follow what Ali posted and test locally on the lan.

-Scott

Here is the iperf output with

dpp021189 — Mon, 15 Jun 2015 17:06:31 GMT

Here is the iperf output with the Server being a wired device and the client is a wireless device.

TCP

C:\Users\tsp1admin\Desktop\iperf-2.0.5-3-win32\iperf-2.0.5-3-win32>iperf.exe -c
192.168.1.4
------------------------------------------------------------
Client connecting to 192.168.1.4, TCP port 5001
TCP window size: 63.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.1.98 port 56741 connected with 192.168.1.4 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.1 sec 36.1 MBytes 30.1 Mbits/sec

UDP
C:\Users\tsp1admin\Desktop\iperf-2.0.5-3-win32\iperf-2.0.5-3-win32>iperf.exe -c
192.168.1.4 -u
------------------------------------------------------------
Client connecting to 192.168.1.4, UDP port 5001
Sending 1470 byte datagrams
UDP buffer size: 63.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.1.98 port 60135 connected with 192.168.1.4 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec
[ 3] Sent 893 datagrams
[ 3] WARNING: did not receive ack of last datagram after 10 tries.

1Mbits/sec is not acceptable

ali aqrabawi — Mon, 15 Jun 2015 19:35:11 GMT

1Mbits/sec is not acceptable at all ,

are both clients (iperf server and client ) are in same vlan ?

do you see same results with all clients ?

please try to map the client to different vlan other than mgmt vlan , and check the iperf results ,

if same issue , i think you will need a TACcase .