all you who bricked your routers trying to go to the 3.x version, could you try what some of us RT-N16 users did which was to flash to 21530 first(it probably won;t be usable and buggy), the flash the latest either 21676 or 22118.
the link to 21530 is on an earlier page in this thread and also in the 22118 thread. _________________ Please state what make and model router plus the build number and type of DD-WRT you are using. Screen prints and a network diagram can are also helpful. Before you create a new post, use the search function. Chances are your issue has happened to someone else.
Hi,
I have an E2500 that I can not access via wifi
I have done several times a 30-30-30 and several times tried different firmware of this forum page
(I have DD-WRT v24-sp2 (14/05/13) mega installed at this moment)
If I have configured my router for repeater (wpa2 personal AES / channel 1) , then all I can see my router (stable 2.4 ghz signal via inSSIDer) but when I enter the correct password, I can not connect to my router by wifi.
( also tried different types of passwords )
even if no password is configured on the E2500, I can not connect to my router by wifi
even if I do not set a password on my main router (E4200 with original linksys firmware).
If I set the E2500 router (temporarily) as a AP (with lan cable) then there is no problem.
I have experience with dd-wrt because my old router wrt54g worked well.
(but this is a G network and I'd like to have all N network at home)
What am I doing wrong or am I forgetting something with configuring
have anyone experienced this or can anyone help me pls
Well this is a known issue with dd-wrt for cpu;s freq smaller than 400mhz and the only solution is overclocking, what is your current cpu frequency?
On k2.6 I get over 100mbit, same router on K3 is 65/70mbit so I do not think this is a CPU issue...
It is a CPU issue and I don't know what build your are using or what you have changed, but K3 builds are at least as fast as K26 builds, done some extensive testing with a setup, that had exactly the same revision, hw and settings only different kernel. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Well this is a known issue with dd-wrt for cpu;s freq smaller than 400mhz and the only solution is overclocking, what is your current cpu frequency?
On k2.6 I get over 100mbit, same router on K3 is 65/70mbit so I do not think this is a CPU issue...
It is a CPU issue and I don't know what build your are using or what you have changed, but K3 builds are at least as fast as K26 builds, done some extensive testing with a setup, that had exactly the same revision, hw and settings only different kernel.
If you read the threads you'll see many people complaining about the exact same thing when switching to K3 on the 610n v2 and a few other units and saying that suddenly speeds are locked to 65/70mbit. When I flash back I get in excess of 100mbit no problem on a single TCP stream. So no I really do not think it is a CPU issue since I've seen more than 5 counts of this from others and I can reproduce the issue by flashing different builds...
My old 610n v1 with much slower CPU running 2.6 does 100+ yet the v2 when running K3 doesn't with a much faster CPU? Not buying it. Also overclocking does not change speeds in the slightest either so that also rules out a bottleneck there (unless the clock setting isn't taking effect).
Running 610n v2 latest K3 build 22118 but also have had the problem on previous K3 builds. Older K2.6 builds I was able to do 100mbit+ so its impossible that its 'a CPU issue' since my router hasn't changed its CPU last I noticed
Well this is a known issue with dd-wrt for cpu;s freq smaller than 400mhz and the only solution is overclocking, what is your current cpu frequency?
On k2.6 I get over 100mbit, same router on K3 is 65/70mbit so I do not think this is a CPU issue...
It is a CPU issue and I don't know what build your are using or what you have changed, but K3 builds are at least as fast as K26 builds, done some extensive testing with a setup, that had exactly the same revision, hw and settings only different kernel.
If you read the threads you'll see many people complaining about the exact same thing when switching to K3 on the 610n v2 and a few other units and saying that suddenly speeds are locked to 65/70mbit. When I flash back I get in excess of 100mbit no problem on a single TCP stream. So no I really do not think it is a CPU issue since I've seen more than 5 counts of this from others and I can reproduce the issue by flashing different builds...
Yes I read those reports and they were with older builds than current. Since I added a few performance fixes I know what I'm talking about.
Quote:
My old 610n v1 with much slower CPU running 2.6 does 100+ yet the v2 when running K3 doesn't with a much faster CPU? Not buying it. Also overclocking does not change speeds in the slightest either so that also rules out a bottleneck there (unless the clock setting isn't taking effect).
Running 610n v2 latest K3 build 22118 but also have had the problem on previous K3 builds. Older K2.6 builds I was able to do 100mbit+ so its impossible that its 'a CPU issue' since my router hasn't changed its CPU last I noticed
I think the issue is HW specific though...
CPU issue we are talking about is in regard to older hw <400Mhz that won't do 100MBit+ you did not mention before that you have an 610v2. Now when we are talking about the 610v2, I ran iperf test with that hw and it did 110MBit with K3 and 109MBit with K26, usually you will get a bit more with speedtests than with my iperf test.
Therefore you have a problem with your configuration. flashing back and forth between K26 and K3 is not going to work without a reset. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Would you suggest at this point I do another full reset on the latest build? I must confess I didn't full reset between the latest build and previous and if your iperfs are returning 100mbit plus as you say it must be a config issue on my end... hmmmph!
However I was doing full resets between 2.6 and 3 builds, probably something specific to my config in that case as you say.
Would you suggest at this point I do another full reset on the latest build? I must confess I didn't full reset between the latest build and previous and if your iperfs are returning 100mbit plus as you say it must be a config issue on my end... hmmmph!
However I was doing full resets between 2.6 and 3 builds, probably something specific to my config in that case as you say.
I have flashed last BrainSlayer fw on my new Buffalo D1800H.
Now i would like to test K3. Flashing "dd-wrt.v24-K3_AC" over webgui should be ok? But can i backflash from K3 to Buffalo with "ddwrt2buff_d1800h191fw_m.bin"? And before flashing i would also like to know hob to flash back from K3 to BrainSlayer build, with bin or trx?
Full reset and now seeing speeds of 90mbit so thats a lot better, going from 480mhz to 533mhz does not yield any throughput gains I can see, is overclocking working properly on the latest builds for the 610n v2?
Posted: Sun Aug 25, 2013 10:08 Post subject: Cisco Linksys E2000 - bricked (recovered through TFTP)
Cisco Linksys E2000
Went from
DD-WRT v24-sp2 (12/24/10) mega
(SVN revision 15962)
to try
dd-wrt.v24-22118_NEWD-2_K3.x_mega-e2000.bin
at first it seemed E2000 to come up.
Ping (over WDS) went up from 5-6ms to 10-12ms.
Tried to flash it again for the heck of it, and then it went into blinking-power light
192.168.1.1 was available and responsive to recovery through TFTP - recovered with dd-wrt.v24-22118_NEWD-2_K2.6_mini-e2000.bin
(Used DrayTek's router tools).
Then flashed dd-wrt.v24-22118_NEWD-2_K2.6_mega-nv60k.bin
... WiFi did not work at all on this though.
Went back to
dd-wrt.v24-21061_NEWD-2_K2.6_mini-e2000.bin
followed by
dd-wrt.v24-21061_NEWD-2_K2.6_mega-nv60k.bin
and keeping my fingers crossed now.
WDS does not seem to work yet properly though.
(15962 was getting unstable for me for WDS - looking for a working multi-router WDS build for the E2000 - 5Ghz band).
Successfully upgraded from k2.6 to k3.x. Router model is WNDR3700v3. Went from 21676 mega in k2.6 to the same exact build in k3.x. No issues and everything is working perfectly.
On another belkin f7d router using the k3 specific for my router prior to madman999 advice I flashed latest release and I get upgrade failed right away. I'm not very experienced with ddwrt dev but I noticed the belkin routers will fail right away if the flash is not compatible which is a good thing. I like to continue helping is there a dev site to report issues formally? I like to help out more now I figured out how to unbrick my routers.
going from a 2.6 build to 3.x 21530 to 3.x 22118? _________________ Please state what make and model router plus the build number and type of DD-WRT you are using. Screen prints and a network diagram can are also helpful. Before you create a new post, use the search function. Chances are your issue has happened to someone else.
