The wireless issues with the E1200v2 are very real and even make dd-wrt unusable on this router for certain things. Since you brought this up I'll tell you what I know without going into any techy details. Certain wireless protocol will completely confuse this router. I have seen the same issues on the E2500 and the WNDR3700v3 but was very rare and only in a couple dd-wrt builds and no I don't remember which.
I have not found a dd-wrt build, including the 18946 for the E1200v2 suitable for me to use as my main router.
Example: Using E1200v2 as router / WAP or whatever...
FTP download will be at 1 mbps at best. Upload not affected and is always scary fast.
Tried different FTP cleints on android phone, Galaxy S3 tab, laptops. Filezilla won't even work and it does a good job on most anything.
The dd-wrt / E1200v2 / wireless negotiation / has a big fat bug in it.
The http protocol is not too bad for me ... can download same files using browser without a problem.
Wired clients are not affected.
I still have a couple E1200v2 here that I play with and have installed many many dd-wrt builds with all the same results when it comes to that particular example.
EDIT: The example above is dealing with a secure ftp server ( ftps )
I have never tried any KONG builds .. they may solve this ????
To answer your question from http://www.dd-wrt.com/phpBB2/viewtopic.php?p=959843#959843
I am really partial to DD-WRT cause they have so many neat builds to play with but since you ask I'll be honest and say the best firmware I have found for the E1200v2 is Tomato-Shibby. It does not have this bug. I've also setup a site to site openVPN TAP using it with two E1200v2 and have never had any problems.
EDIT :
I've been running [dd-wrt.v24-27506_NEWD-2_K3.x_mega-nv64k.bin] (07/09/15)
on the E1200v2 as main router last few days without any problems mentioned above.
The K3.x builds seem to work very well on this router.
Last edited by mrjcd on Tue Aug 04, 2015 21:21; edited 2 times in total
I have never tried any KONG builds .. they may solve this ????
I think so, but I'm quite desperate now so I go back to stock FW. haha.
Thank you, confirming Tomato-shibby. I've always had second thoughts about it at first but I'll certainly try it out this weekend. (y) I know tomato is not that hard to deal with..
After 4 months of using 21676 mini build with a virgin FW, i think it did perform good. not quite. but some things like Wifi speed, faulty 802.11n with mixed devices connect to it. Too hard for me to diagnose. Now, with stock FW, my internet speed seems to improve much. It's stable than before.
Thank you. _________________ Linksys E1200 v2
DD-WRT v24-sp2 (05/27/13) mini - build 21676 (reverted to stock april 7, 2015 wifi issues)
I have been trying to flash my Linksys E1200-RM v2.0 but all attempts to flash to DD-WRT failed.
I don't know why it's not accepting it, I've even tried the 30-30-30 method to get to telnet but telnet fails to allow connection.
(after any flashing attempt it returns to an unsecured yet usable original linksys flash)
Is there an alternate method to flashing this with as little dangers as possible?
I have used DD-WRT on my old WRT54gl for years with no problems at all. (I only set it aside as internet download speeds became faster than it could handle.)
I'm trying to get some kind of client mode working to provide internet to a wired device via a phone hotspot. Apparently Tomato has issues with client mode if the primary isn't also a Tomato router and I'm hoping DD-WRT does not have this issue.
I am a little surprised to hear there are problems with N wireless speeds, but I ultimately don't care that much. I'm going to just go with the 21676 NEWD mini and will report if it worked.
EDIT: To clarify, I already tried Shibby Tomato 124 and 128 and it did not work in client or bridge mode, even when connecting to a router instead of phone hotspot.
EDIT2: I tried with the named mini for the E1200v2 and client mode worked right away. It did have issues with the my work wifi, but that seems to be an issue with fortinet blocking it and no fault of dd-wrt.
Last edited by CapinWinky on Mon Apr 20, 2015 16:09; edited 1 time in total
Not sure why no one pointed this out, but there is a fix for the slow download speeds on N.
In Administration -> Commands put:
Code:
insmod xt_DSCP.ko
Click Save Startup.
Then Enter:
Code:
iptables -t mangle -A PREROUTING -i `nvram get wan_ifname` -j DSCP --set-dscp 0
Click Save Firewall
This works because Comcast and some others encode the IPv4 packets with DSCP value of 8 instead of 0 and a bug in the WMM driver mishandles them. The script converts the DSCP value to 0 when the packet arrives at the WAN port, avoiding the issue.
Not sure why no one pointed this out, but there is a fix for the slow download speeds on N.
In Administration -> Commands put:
Code:
insmod xt_DSCP.ko
Click Save Startup.
Then Enter:
Code:
iptables -t mangle -A PREROUTING -i `nvram get wan_ifname` -j DSCP --set-dscp 0
Click Save Firewall
This works because Comcast and some others encode the IPv4 packets with DSCP value of 8 instead of 0 and a bug in the WMM driver mishandles them. The script converts the DSCP value to 0 when the packet arrives at the WAN port, avoiding the issue.
well, it's not certainly an issue with dscp.. I think that's pointed to a Comcast ISP issue. _________________ Linksys E1200 v2
DD-WRT v24-sp2 (05/27/13) mini - build 21676 (reverted to stock april 7, 2015 wifi issues)
The wireless issues with the E1200v2 are very real and even make dd-wrt unusable on this router for certain things. Since you brought this up I'll tell you what I know without going into any techy details. Certain wireless protocol will completely confuse this router. I have seen the same issues on the E2500 and the WNDR3700v3 but was very rare and only in a couple dd-wrt builds and no I don't remember which.
I have not found a dd-wrt build, including the 18946 for the E1200v2 suitable for me to use as my main router.
Example: Using E1200v2 as router / WAP or whatever...
FTP download will be at 1 mbps at best. Upload not affected and is always scary fast.
Tried different FTP cleints on android phone, Galaxy S3 tab, laptops. Filezilla won't even work and it does a good job on most anything.
The dd-wrt / E1200v2 / wireless negotiation / has a big fat bug in it.
The http protocol is not too bad for me ... can download same files using browser without a problem.
Wired clients are not affected.
I still have a couple E1200v2 here that I play with and have installed many many dd-wrt builds with all the same results when it comes to that particular example.
EDIT: The example above is dealing with a secure ftp server ( ftps )
I have never tried any KONG builds .. they may solve this ????
To answer your question from http://www.dd-wrt.com/phpBB2/viewtopic.php?p=959843#959843
I am really partial to DD-WRT cause they have so many neat builds to play with but since you ask I'll be honest and say the best firmware I have found for the E1200v2 is Tomato-Shibby. It does not have this bug. I've also setup a site to site openVPN TAP using it with two E1200v2 and have never had any problems.
Let me confirm, Tomato by Shibby is the BEST THING that has happened to the e1200. It is way faster than stock 2.0.0.6 (I noticed 2.0.0.7 has been published in January). Stock by the way was faster than DD-WRT for me. Tomato seems to be running rock solid. I flashed from DD-WRT no problem. Works great with Surface by Microsoft in terms of mbps. Downloads are above 67mbps and latancy below 17ms for Charter 60mbps service. Stable! And more features for my liking than DD-WRT, including dynamicDNS for OpenDNS, DNSmasq features, and more. Thanks!!! (Running 128) _________________ WRT-54G V6 & V8 - wrt.v24_micro_generic.bin
Linksys E1200 v2 - Tomato by Shabby (DD-WRT has problems)
EA6300 V1 - Kong+CFE http://www.desipro.de/ddwrt/K3-AC-Arm/dd-wrt.v24-K3_AC_ARM_STD.bin
Make sure you have the E1200 version 2
E1200 v2 is much different than E1200 or E1200 v1
>Install latest Linksys firmware you downloaded.
Can't flash even it. Same error.
Here is parallel router ping. Language is not English, but it's not the problem i suppose.
Looks like link is breaking in flashing process.
Code:
C:\Users\DOrlov>ping 192.168.1.1 -n 40
Обмен пакетами с 192.168.1.1 по с 32 байтами данных:
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Общий сбой.
Общий сбой.
Ответ от 192.168.1.1: число байт=32 время=121мс TTL=100
Ответ от 192.168.1.1: число байт=32 время=1мс TTL=100
Ответ от 192.168.1.1: число байт=32 время=1мс TTL=100
Превышен интервал ожидания для запроса.
Ответ от 192.168.1.2: Заданный узел недоступен.
Ответ от 192.168.1.2: Заданный узел недоступен.
Ответ от 192.168.1.2: Заданный узел недоступен.
Превышен интервал ожидания для запроса.
Ответ от 192.168.1.1: число байт=32 время=984мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время=8мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
Ответ от 192.168.1.1: число байт=32 время<1мс TTL=64
I would hold pin reset (on bottom) for at least 20 seconds or until all lights flash. Wait 30 seconds.
Power cycle router... give it a minute to bootup good and repeat the reset and power cycle.
Yes I would try TFTP.
Best to set your computer to static IP
You will have to put in password admin in the TFTP app and either do the latest Linksys firmware or you can go straight to dd-wrt.
I always use dd-wrt.v24-21061_NEWD-2_K2.6_mini-e1200v2.bin when I've done this.
If TFTP is successful give it a few minutes until lights are steady -- don't even try to access it from http until complete these steps --- then do a pin reset (20 seconds) wait till lights are steady then unplug, wait 10 seconds plug back in.
Set computer back to DHCP
It should give you DHCP IP after 1 minute ... its slow booting dd-wrt.
If it is briefly dropping port function as your pings indicate hopefully the TFTP app will continue with the install
---- or you may have a brick --- do this at your own risk
(y) I know tomato is not that hard to deal with.. 