DD-WRT v23 and WRT54GL router slowdown script problems I am hoping to get an answer to this, not just for myself, but also for ALL router noobs using DD-WRT v23 and the WRT54GL router without Linux experience but REALLY need to fix the router slowdown issues as shown in http://www.dd-wrt.com/wiki/index.php/Router_Slowdown#Solution_1 using solution 1, but are stumped because the second half of the solution doesnâ€™t work with DD-WRT v23 and higher. It would be good, and not just for myself, if people knew how to do this correctly, or at least how to set things back the way they were if they screw it up. So here is my setup: I have static IPâ€™s for two computers and a PS3. I am going to ignore the PS3, and call each of the two computers IP1 and IP2. I am running Windows XP Home Edition. I broke this fix into two parts. 1) I used Bittornado to test, because itâ€™s an easy way to test P2P connectivity for me. When I started out, both IP1 and IP2 both tested just fine. (Although you wouldnâ€™t know it from the way people talk, there are loads of legal files to get via P2P) 2) I went into Management, and then in IP Filter Settings I set Maximum ports to 4096, TCP Timeouts and UDP timeouts to 90. 3) Tested, both still worked fine!! 4) The second half of the instructions above is where things went south, real quick. a) The tutorial I linked to above only explains the command lines that work for DD-WRT *before* v23. It lists the files that can be populated on v23 to â€œget the same effectâ€, but says nothing at all about what commands you would use to do that. b) http://www.linksysinfo.org/forums/showthread.php?t=35939 suggests that the following lines could be used to create the same effect, but says nothing about what command lines to use: /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout_stream 5) So I wasnâ€™t able to figure out what values to assign to the above lines so I found a script that at least addressed the drop-out-every-hour issue for TCP (nothing for UDP) and followed the following: http://www.linksysinfo.org/forums/showthread.php?t=43031 6) I put the following script in the Administration then Commands tab, and wrote the following commands into the command shell, then chose Save FireWall echo 172800 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established echo 1 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts echo 1 > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses 7) I tested, and suddenly both computers werenâ€™t forwarding ports for Bittornado at all anymore! Nothing I tried fixed it. 8) I restored to factory defaults, and started over. But as I learned later that the script is stored as a rc_firewall variable in flash memory (a NVRAM variable). This doesn't get erased on startup, and will remain with every boot and will always execute. 9) When I had entered the commands the first time there had been a blank line in-between each line of code. I tried entering the commands again, this time with no spaces in between the lines. This time the first computer (IP1) was back to forwarding for Bittornado! YEAH! BUT the second one, IP2 still isnâ€™t passing any tests. 10) Iâ€™m very much stuck. If these lines will stop my router from dropping out every hour, then it would be REALLY good to get them to work. But at this point, Iâ€™d be just as happy to reset my rc_firewall variable to whatever the default was for now. I just want to get both computers forwarding the right ports and can deal with scripts like this some other day. If I can avoid re-flashing the DD-WRT back on again, that would be ideal. And probably unnecessary as Iâ€™m guessing thereâ€™s probably an easier way to reset the rc_firewall variable to what it was. Any kind souls willing to help with this issue? Perhaps the script only works with one computer, and not with two on a network?