Unfortunately the 23503 build didn't solve my networking/vlan issues either. Does anyone have an approach to solve this?
What is your networking/vlan issue exactly? I didn't follow your posts.
The thread is indeed getting large .
My issue is that when I make any changes on the VLAN config (like assigning a specific VLAN to a port, even if that port is unconnected)) the router locks up after about 20s and doesn't come back anymore. It then requires a 30-30-30 (well, a 0-0-30 works too) to recover. Another poster had similar issues but associated with a port-config setting (might have been duplex, not sure). This leads me to conclude something is not entirely right /w the networking bit but I don't know if anyone else is running into this.
You might want to set the "Speed & Duplex" on your PC/laptop LAN Card to 100 Mbps Full Duplex. It works for me.
Considering the "creepy" case of reverting firmware:
As you can see below (from page 1 of this thread) the flash memory is divided into 7 areas.
Notice that there are 2 rootfs and linux area. So if you flash once, you flash to 1 area but not in other.
There is a nvram variable which is used by cfe to determine from which partition it should boot.
Also my opinion if the partial boots variables is incremeted beyond certain value it will try to boot from "other partition" which it thinks is the "good" firmware.
To overcome this: you have to flash the firmware 2 times, so it goes to both partition.
Wow, this is such an eye opener. And yeah, I totally agree. It's not really a bug. So you're saying that I have to flash the router twice? Like I flash ddwrt from the Linksys firmware, then once more from the ddwrt firmware (by choosing firmware upgrade)?
Unfortunately the 23503 build didn't solve my networking/vlan issues either. Does anyone have an approach to solve this?
What is your networking/vlan issue exactly? I didn't follow your posts.
The thread is indeed getting large .
My issue is that when I make any changes on the VLAN config (like assigning a specific VLAN to a port, even if that port is unconnected)) the router locks up after about 20s and doesn't come back anymore. It then requires a 30-30-30 (well, a 0-0-30 works too) to recover. Another poster had similar issues but associated with a port-config setting (might have been duplex, not sure). This leads me to conclude something is not entirely right /w the networking bit but I don't know if anyone else is running into this.
You might want to set the "Speed & Duplex" on your PC/laptop LAN Card to 100 Mbps Full Duplex. It works for me.
So, to clarify: if I don't make vlan changes all's ok. It's when I do make those changes, even on an unconnected port, then my router freezes.
Maybe I should pose the question differently: has anyone successfully set up vlans on dd-wrt on this router? Could you share your experience/configs?
Posted: Tue Feb 25, 2014 21:39 Post subject: 23598
Just want to say thanks for this been hoping we would get support for this router First time installing dd-wrt actually but running the 23598 build and did the 30/30/30 all seems to be fine though I havent tried to force 5ghz yet as I read that doesnt work yet or may never but thats ok.
My question I wanted to ask should we install this firmware twice cause I read that somewhere cant remember. I downgraded to classic and like I said i did the 30/30/30 installed the firware, waited for about 5 min did a hard rest and everything seems to be sticking no sign of the original firmware. So just curious but thanks again dd-wrt and Brainslayer!
Posted: Thu Feb 27, 2014 6:33 Post subject: revert to stock firmware
Have someone solved the reverting problem.
I've tried last night on build 23598.
First time I'd flashed on build 23503 but went into a unstopable reboot. Then I did a 30/3030 reboot.The router went to 23598!
But when I reboot it. The router went into reboot again and again.
After one more 30/30/30 I'd flashed 23598 again.The router seems to be OK.
So What's the final solution?I think it's the only problem to solve on EA2700.
This is a bit offtopic, but I couldnt figure out a better place to ask : I have got a cisco EA2700, my plan for it was to be flashed with ddwrt or openwrt, but there seems to be a problem with the unit. When connected to the power supply and the power switch is switched on all the leds start blinking ( that is the ethernet ports lights - both green and amber ) and I have no way to connect to the unit. Can somebody suggest any way of finding what is wrong with my router ? Thanks a lot in advance.
This is a bit offtopic, but I couldnt figure out a better place to ask : I have got a cisco EA2700, my plan for it was to be flashed with ddwrt or openwrt, but there seems to be a problem with the unit. When connected to the power supply and the power switch is switched on all the leds start blinking ( that is the ethernet ports lights - both green and amber ) and I have no way to connect to the unit. Can somebody suggest any way of finding what is wrong with my router ? Thanks a lot in advance.
This does not work for me. Everything flashes fine and the hardreset works fine. But I keep seeing the Linksys Classic web UI when I navigate to http://192.168.1.1
Is there some step I'm missing?
(Btw, everyone is flashing the .trx file via "Firmware Upgrade" right?)
Posted: Fri Mar 07, 2014 16:59 Post subject: thought i was good
Hell i dont even know anymore mine finally reverted back to stock but only after I started making changes.
Im not sure as to which one it was but after setting up my wifi and security and the basics I added a dhcp reservation for my ps3 and put on the dmz for testing an error I was getting on my ps3 network settings page. Anyway I reboot the router and bam! Stock garbage was in my face again.
I also tested rebooting a ton of time before make the wifi changes and basics settings changes but after doing that it seemed like it caused it to not want boot to dd wrt. So I flashed again ofcourse doing a 30/30/30 and installing with ie waiting a few minutes before even touching it and doing another 30/30/30 and reboot a ton of times.
I then set it all back up reboot a ton of times to test thinking its all good for real this time and then I dared to make the dhcp reservation and add the ps3 to dmz again and bam!
So I said heck with it for now but I really want this to work. Anyone have any ideas? Maybe just wait for a stable version?
Thanks btw Im still grateful for who puts the time in to make this.
Joined: 05 Mar 2014 Posts: 193 Location: Edmonton, AB
Posted: Fri Mar 21, 2014 17:07 Post subject:
robo77 wrote:
nolimitz wrote:
For testing purposes, i tried o reboot and see if it goes back to linksys.
4 reboots then back to linksys stock, flashed dd wrt from stock again then flashed dd-wrt twice. 5 reboots, back to linksys stock.
Please help, it will eventually go back to stock after 4-5 reboots, the bad thing is that once it goes back to stock, wireless is open with no encryption (even if i set it to on before dd-wrt upgrade), i dont want anyone to access my network!
That was exactly my problem and I solved it by adding to Administration -> Commands -> Startup these lines:
nvram set partialboots=0
nvram commit
Joined: 05 Mar 2014 Posts: 193 Location: Edmonton, AB
Posted: Fri Mar 21, 2014 18:30 Post subject:
Thank you very much for getting back. When mine ran for 24 hrs without trouble, I thought it was stable. Lo and behold when I set up VPN client and rebooted I was greeted with Linksys firmware. I remembered reading your advice and quickly added those two lines yesterday.
It was still on DD-WRT this morning but I had connectivity issues--PC wouldn't connect at all. Strange. I didn't have the time to look into it. Those two lines shouldn't interfere with the VPN startup commands, right? I am a novice in this.
Thanks again.
Joined: 05 Mar 2014 Posts: 193 Location: Edmonton, AB
Posted: Fri Mar 21, 2014 18:59 Post subject:
Thank you. I set it up yesterday night and everything worked. I had a policy based routing and checked it twice by setting a static ip and changing it to dynamic. Both times it worked in the night. This morning it was in static and didn't work. I left it at that. Will check later.
.
