This may be more related to a setting on the wireless access point. If the wireless AP is not set to a fixed mode such as "g" or "n", and it "hears" the presence of a "b" device associated or not, it will go into a compatibility mode and effectively run at the lower "b" rate. In my SOHO environment, I fix my wireless mode to "g" as that is compatible with all the devices I want to have connected, but if a guest brings in a "b" mode device, they cannot connect, but they don't downgrade the throughput of my existing network. Your 6-9 Mbps throughput is more typical of what I would expect in a "b" environment.
We have been investigating what seems to be an obscure issue with regards to Comcast speeds wired vs. wireless "G" speeds on a 30/5 circuit. Here are the symptoms: Wired (directly to modem): Speeds are what one would expect - 25-30 Mbps down and 4-5 Mbps up. Wireless: Speeds are in the 6-9 Mbps. We have tried a variety of consumer and higher end APs/Wireless routers. All with the same basic results - the speeds are significantly slower.
In order to dig deeper, I captured wireshark traces for both wired/wireless on Comcast and Optimum Online circuits. The biggest difference I could find is that on the Comcast circuit both wired and wireless, there were many: TCP Dup ACK packets (see below for an example)
Has anyone seen this before? Is there a solution without changing the client laptop? We would like to have a solution that is hardware based (router or firmware) rather than telling users they must all make registry changes which makes us nervous (liability) and end-users irritated that "it works on other networks without a problem" Any insight on this would be greatly appreciated. Will Howard___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe |
- Follow-Ups:
- Re: [Wireshark-users] TCP Dup Ack Issues with Comcast vs.Cablevision
- From: William Howard
- Re: [Wireshark-users] TCP Dup Ack Issues with Comcast vs.Cablevision
- References:
- [Wireshark-users] TCP Dup Ack Issues with Comcast vs. Cablevision
- From: William Howard
- [Wireshark-users] TCP Dup Ack Issues with Comcast vs. Cablevision
- Prev by Date: Re: [Wireshark-users] Names in display filter ip address specs
- Next by Date: Re: [Wireshark-users] tshark conversatons
- Previous by thread: [Wireshark-users] TCP Dup Ack Issues with Comcast vs. Cablevision
- Next by thread: Re: [Wireshark-users] TCP Dup Ack Issues with Comcast vs.Cablevision
- Index(es):