Comcast download speed fix for Linksys eSeries

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 17:10, 4 January 2014 (edit)
JNavas (Talk | contribs)
m (Methodology - tweak)
← Previous diff
Current revision (18:15, 18 March 2018) (edit) (undo)
Ian5142 (Talk | contribs)
(Added Advanced tutorials category.)
 
(18 intermediate revisions not shown.)
Line 3: Line 3:
[Culled from DD-WRT Forum thread [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=176395 Critical DSCP bug Affecting WiFi Download Speeds on Comcast]] [Culled from DD-WRT Forum thread [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=176395 Critical DSCP bug Affecting WiFi Download Speeds on Comcast]]
-Unlike other service providers, IPv4 packets from the Comcast network are configured with [https://en.wikipedia.org/wiki/Differentiated_services DSCP] 8, Priority higher than Default/Routine (0).+There is an edge case interaction between Comcast IPv4 [https://en.wikipedia.org/wiki/Differentiated_services DSCP] and improper condition handling in the [https://en.wikipedia.org/wiki/Wireless_Multimedia_Extensions WMM] driver in certain '''Linksys/Cisco eSeries''' routers (and possibly others as well) which results in very low download speeds. This issue can appear in both stock and third-party (DD-WRT) firmware, although Cisco appears to have at some point released new WMM drivers that largely resolve the issue in current stock firmware.
 + 
 +The cause is that IPv4 packets from the Comcast network are configured with DSCP 8, which the driver handles improperly, whereas other providers typically use DSCP 0, which the driver handles properly. (Both are valid values.)
-There is an edge case interaction between this Comcast DSCP value and improper condition handling in the [https://en.wikipedia.org/wiki/Wireless_Multimedia_Extensions WMM] driver in certain '''Linksys/Cisco eSeries''' routers (and possibly others as well) which results in very low download speeds. This issue can appear in both stock and third-party (DD-WRT) firmware, although Cisco appears to have at some point released new WMM drivers that largely resolve the issue in current stock firmware. 
== Symptoms == == Symptoms ==
-Download speeds are normal with ''current'' stock firmware, and on ''wired'' connections with DD-WRT firmware, but are very low (less than 1 Mbps) on ''wireless'' connections with DD-WRT firmware.+Download speeds are normal with ''current'' stock firmware, and on ''wired'' connections with DD-WRT firmware, but are much lower (possibly even less than 1 Mbps) on ''wireless'' connections with DD-WRT firmware even with strong signal.
 + 
 +To see if you are getting the problematic DSCP, you can look at your downloaded IPv4 packets with [http://www.wireshark.org/ Wireshark], preferably directly connected to WAN, but you should see them even on Wi-Fi. (See [http://netspoon.wordpress.com/2012/09/08/add-dscp-column-in-wireshark/ Add DSCP Column in Wireshark])
-Because DSCP pertains to QoS, it's possible this problem might only exist ''when QoS is enabled'' (and go away when QoS is disabled), but this has not been confirmed. 
== Testing == == Testing ==
-To see if you are getting the bad DSCP, take a look at your downloaded IPv4 packets with [http://www.wireshark.org/ Wireshark], preferably directly connected to WAN, but you should see them even on Wi-Fi. (See [http://netspoon.wordpress.com/2012/09/08/add-dscp-column-in-wireshark/ Add DSCP Column in Wireshark]) 
-If you see the problem, open a Telnet or SSH connection to DD-WRT, and run the following commands:+To test this fix, open a Telnet or SSH connection to DD-WRT, and run the following commands (copy and paste to avoid typos):
insmod xt_DSCP.ko insmod xt_DSCP.ko
- iptables -t mangle -A PREROUTING -i vlan2 -j DSCP --set-dscp 0+ iptables -t mangle -A PREROUTING -i `nvram get wan_ifname` -j DSCP --set-dscp 0
Assuming there are no errors, check download speed on wireless. Assuming there are no errors, check download speed on wireless.
-You may need to change ''vlan2'' depending on your particular setup. 
== Configuration == == Configuration ==
-To save the fix so it survives reboots, first navigate to ''Administration'' > ''Commands''+To save the fix so it survives reboots, navigate to ''Administration'' > ''Commands''
-In Command Shell, enter Commands:+In Command Shell, enter Commands (copy and paste to avoid typos):
insmod xt_DSCP.ko insmod xt_DSCP.ko
and click ''Save Startup''. and click ''Save Startup''.
-In Command Shell, enter Commands:+In Command Shell, enter Commands (copy and paste to avoid typos):
- iptables -t mangle -A PREROUTING -i vlan2 -j DSCP --set-dscp 0+ iptables -t mangle -A PREROUTING -i `nvram get wan_ifname` -j DSCP --set-dscp 0
and click ''Save Firewall''. and click ''Save Firewall''.
-== Methodology == 
-This fix changes DSCP header information as soon as a packet hits the WAN interface on the router. 
-DSCP as received from Comcast's network is 8. This is actually higher than default priority, but the WMM driver interprets it incorrectly.+== Methodology ==
 +This fix changes DSCP header information in all packets to DSCP 0 when they arrive at the WAN interface of the router, which the WMM driver handles properly.
-The fix changes DSCP on all packets to 0 (Default priority), which the WMM driver handles properly. (This is how other ISPs set DSCP and is why the issue is specific to Comcast.) 
== References == == References ==
Line 53: Line 51:
[[Category:Tutorials| ]] [[Category:Tutorials| ]]
[[Category:Comcast| ]] [[Category:Comcast| ]]
 +[[Category:Linksys guides]]
 +[[Category:Linksys]]
 +[[Category:Advanced tutorials]]

Current revision

Contents

[edit] Introduction

[Culled from DD-WRT Forum thread Critical DSCP bug Affecting WiFi Download Speeds on Comcast]

There is an edge case interaction between Comcast IPv4 DSCP and improper condition handling in the WMM driver in certain Linksys/Cisco eSeries routers (and possibly others as well) which results in very low download speeds. This issue can appear in both stock and third-party (DD-WRT) firmware, although Cisco appears to have at some point released new WMM drivers that largely resolve the issue in current stock firmware.

The cause is that IPv4 packets from the Comcast network are configured with DSCP 8, which the driver handles improperly, whereas other providers typically use DSCP 0, which the driver handles properly. (Both are valid values.)


[edit] Symptoms

Download speeds are normal with current stock firmware, and on wired connections with DD-WRT firmware, but are much lower (possibly even less than 1 Mbps) on wireless connections with DD-WRT firmware even with strong signal.

To see if you are getting the problematic DSCP, you can look at your downloaded IPv4 packets with Wireshark, preferably directly connected to WAN, but you should see them even on Wi-Fi. (See Add DSCP Column in Wireshark)


[edit] Testing

To test this fix, open a Telnet or SSH connection to DD-WRT, and run the following commands (copy and paste to avoid typos):

insmod xt_DSCP.ko
iptables -t mangle -A PREROUTING -i `nvram get wan_ifname` -j DSCP --set-dscp 0

Assuming there are no errors, check download speed on wireless.


[edit] Configuration

To save the fix so it survives reboots, navigate to Administration > Commands

In Command Shell, enter Commands (copy and paste to avoid typos):

insmod xt_DSCP.ko

and click Save Startup.

In Command Shell, enter Commands (copy and paste to avoid typos):

iptables -t mangle -A PREROUTING -i `nvram get wan_ifname` -j DSCP --set-dscp 0

and click Save Firewall.


[edit] Methodology

This fix changes DSCP header information in all packets to DSCP 0 when they arrive at the WAN interface of the router, which the WMM driver handles properly.


[edit] References