Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Thursday, October 4, 2012

Cisco Valet routers and DD-WRT

Upgrade Your Linksys Router, Literally!Aug 2010 Read it! Do not use a build greater than 3,7MB!!!!
Do not use builds older than build 14929 (8/12/10) if you want support (Broadcom recommended builds)
Cisco Valet
Model H.W. rev FCC ID Platform & Frequency [MHz] RAM [MB] Flash [MB] Ant. Conn. Type WLAN NIC WLAN standard [802.11] mini PCI Serial port JTAG port Eth. port count Power Input [V/A] Special Features Notes min required DD-WRT version Notes for Running DD-WRT
M10 1.0 Q87-M10 Broadcom BCM4716A@300 32 4 Internal Broadcom b/g/n - 1  ? 4 LAN 1 WAN 12V 0.5A  ? K26 build 15334 Yes
M10 2.0 Q87-M10V2 Broadcom BCM5357@300 32 4 Int. Broadcom b/g/n - 1  ? 4 LAN 1 WAN 12V 0.5A Gb WAN & LAN WIP No
M20 1.0 Q87-M20 Broadcom BCM4716@300 32 4 Internal Broadcom b/g/n - 1 1 4 LAN 1 WAN 12V 1A Gb switch K26 build 14929 Yes
Model        Initial Firmware                                File Upgrade Firmware File

Valet M10 v1.0 dd-wrt.v24-18946_NEWD-2_K2.6_mini_m10.bin dd-wrt.v24-18946_NEWD-2_K2.6_openvpn_small.bin
Valet M20 v1.0 dd-wrt.v24-18946_NEWD-2_K2.6_mini_m20.bin dd-wrt.v24-18946_NEWD-2_K2.6_openvpn_small.bin

!!!Attention: Always clear your browser cache before flashing!!!
 Builds based on r19210 or newer:
 Builds labeled kingkong nv32k are suitable for Asus RT-N16 Builds labeled kingkong nv60k are suitable for E3200 / E4200
 Builds labeled nv32k are suitable for Netgear WNR3500L V1, Asus RT-N16, Linksys WRT610 V1/V2, Belkin F7D4302/F7D3302
 Builds labeled nv60k are suitable for Linksys E2500 / E3000 / 4200 Builds based on r17940 or never:
 Builds labeled kingkong are suitable for Asus RT-N16 Builds labeled nv32k are suitable for Netgear WNR3500L V1, Asus RT-N16, Linksys WRT610 V1/V2, Belkin F7D4302/F7D3302
 Builds labeled nv60k are suitable for Linksys E3000 / 4200
 Before r17940: !Always choose a build that contains the name of your router model!
 Builds labeled "kingkong" are full featured builds only suited for >=16MB flash space.
 Builds labeled "newd" include the latest wireless drivers.
You may experience low signals on 2,4Ghz single radio units.
 Builds without "newd" include the latest recommended wireless driver. This one is well tested and should provide a stable signal

30-30-30 hard reset
Download the firmware for your router version. (you may need it latyer)
Disconnect the router from UTP cables (not the power cable).
Push reset button for 30 secs.
Without releasing reset button, disconnect power cord.
Hold the reset button for another 30 secs.
Replug the power cord.
Still hold the reset button for another 30 secs.
Release the reset button and give the router about 10 secs to resettle.
Disconnect power cord for another 10 secs and then reconnect.
All should be in default settings now.

There is a dd-wrt page that details how to recover from a bad firmware flash. Even though you're not using dd-wrt firmware, it still applies.:

Valet M10 v1 
Non volatile RAM: 32 MB
Flash RAM: 4 MB (use FW-build and type with not more than 3,8-3,9 MB)
 use at your own risk. Micro and all 535x builds are not compatible with MIMO routers.
About file names: (up to 9059)
-nogiga: means that there in no gigabit switch driver inside.
-535x: builds for routers with BCM5350, BCM5352 and BCM5354 cpu
      (some other routers also work with this builds, you can
       check if you have wl0_corerev=7 or 9, then it will work).
       note: there is no gigabit switch driver in RC5..-535x builds.
       RC6..-535x incudes gigabit switch driver if not indicated
-SF: build for routers with serial flash chip, e.g. Belkin v2000.
Starting with 9068 there are new names:
- VINT:  vintage build (old driver), works on any router but 5354 based
- NEWD:  new driver with multi bssid support, works on any router but 
 (Broadcom series?) 4702 (4710) based
- SF:  build for routers with serial flash chip, e.g. Belkin v2000.
- WRH54G:  build only for Linksys WRH54G router
General rules: if you have old router with 4702 (4710) cpu and mini-pci
radio, you MUST use VINT build, if you have 5354 based router, you must
use NEWD build. All other routers can run both (VINT or NEWD) builds.
For gigabit routers always use NEWD.
Cisco Valet M10 (ver1) test firmware more info there!
The M series is just like the E series afaik. In other words: larger nvram space compared to the identical hardware they replaced. That's why you see WRT610v2 users all putting the E3000 CFE on their routers, etc. Although I suppose once someone gets it on their M10 they can just rip the CFE and share for all.
I've just had the chance to check an E1000 cfe (thanks to barryware who bought a router only for making dd-wrt support possible).
There is no different chipset between an WRT160v3 (Chipset Broadcom BCM4716A@300 )
, an M10v1 (Chipset Broadcom BCM4716A@300 ) or an E1000v1 (Broadcom BCM4716A@300) , it is only the E2000 (Broadcom BCM4717A@354) and E3000 (Broadcom BCM4718@480) that has got the bigger nvram
Yes, I know, the E1000 has a fancier case colour and the stock firmware may have some extra features (Easy WPS connect?) that the others don't have, but that is basically what differs between them.
I've got a Cisco Valet M10 v1 currently running DD-WRT v24-sp2 (10/26/10) mini - build 15508M NEWD-2 K2.6 Eko.
From what I understand after the initial flash of the dd-wrt.v24-15508_NEWD-2_K2.6_mini_m10.bin I should be able to now use any of the builds that follow.
It's been running solid on this build for a few months now. I'd like to enabled IPv6 which is not supported on the mini, so I'd need to flash dd-wrt.v24-16758_NEWD-2_K2.6_std_nokaid_small.bin now I believe.
From reading the peacock thread I believe that the m10 build is only required for the initial flash and then standard builds can be used. Am I understanding that correctly?
The Valet has 4MB flash and the standard build is 3,456 KB so I'm assuming it will fit fine.

Just found
This seems to be a big improvement (??????)

I just installed dd-wrt.v24-17598_NEWD-2_K2.6_mini from
and it works great with the M10 V1. No issues yet!

It worked fine for me as well. I am using my M10 as a Client Bridge to run a media player. (Works much better than the wireless-N Usb adapter I was using.)
I should also mention that my Valet is also a version 1.0 but would not load "dd-wrt.v24-15257_NEWD-2_K2.6_mini_m10.bin" as recommended at the beginning of this thread but 17598 loaded right up like you said it would.

First thing I found is that searching the router database indicated the router is NOT supported by DD-WRT. However, the wiki indicates it is a WIP with an official stable release to made available in the near future, however, the information on the wiki has not been updated in some time.
I was rather surprised to find the firmware attached to the first post in this thread for the M10, but was a little concerned with how dated it was. (over a year old) However, I was even more surprised when I looked at the DD-WRT ftp site to discover that apparently Eko has been producing builds supporting the M10 and M20 routers for quite awhile, and several people have reported success in using them.
I plan to try installing one of these builds on an M10 later tonight, and will post with my results.
However, there is some information which despite my looking, I have been unable to find any reliable source of information.
First is wireless chipset information. In the past I was able to find a great deal of detailed information on the specification of the Broadcom wireless chips in some of the other Linksys router, for example, the E2000, explaining how they are built and what kind of wireless performance you can expect from them, however, I have been unable to find any information for this for either the M10 or it's hardware twin the E1000.
Also, I have been unable to find any information about HOW to actually apply the M10 build - most of the routers I have flashed in the past with DD-WRT have required special initial flashing before applying the final version of DD-WRT, however, I have been unable to find any such information for the M10. Most of the information I have found showing recommended builds and such in such places as the peacock thread appear to be quite dated and probably not apply anymore. 

Anyhow, once I decided flashing the M10 was definitely the way I wanted to go, the big question was what version to flash.
After reading the peacock thread and the recommended build threads, the big problem was that the recommended most stable versions 14929 and 15230 aren't available for the M10 at all.
Also, many of the newest builds (17xxx) don't have an M10 version either.
I ended up choosing build 15962 as being as close as I could get to the recommended most stable builds without going backwards.
Even though the router was fresh out of the box, I did a 30-30-30 reset just to be safe. I then logged into the GUI from Firefox on a Linux laptop, and loaded the firmware through the web GUI upgrade.
The upgrade took successfully and I then did another 30-30-30 to make sure everything was correct.
Everything seems to be working

anthonymo wrote:
Alright after reading some of the test build threads I just took a big breath and put the std-nokaid-small NEWD-2 K2.6 Eko build onto my M10, it worked like a charm, no problem, so anybody wondering... GO for it.

I'm going to flash nokaid now!
EDIT: I flashed the file attached to the first post
30/30/30 reset
Then flashed:
30/30/30 reset
Works fine
This also works to turn the led from yellow to blue:
I just brought the M10 at Walmart. The hardware version was 1.0. I upgraded the router to Ver.2.0.03 (build 4)from Cisco's site. I then upgraded the router to dd-wrt.v24-15257_NEWD-2_K2.6_mini_m10.bin. It took without problems. I found a new firmware dd-wrt.v24-17990_NEWD-2_K2.6_mini.bin; I upgraded to that firmware without problems. So far the router was been rock stable without any issues.
Each time before and after an upgrade I did the 30/30/30 reset. Remember to do this!

I prefer the 17990. It seems more stable and fast with my Internet, PS3, Xbox, and VoIP. I look forward to later builds. 

Just tested my Cisco/Linksys Valet M10 (v1.0) with DD-WRT v24-sp2 (12/24/10) std-nokaid-small and it's up and running no problems.
With a few script mods (below) I've got native IPv6 enabled for wireless and eth clients.
Admin - Management - IPv6 Support
IPv6 = Enable
Radvd = Enable
Radvd config:

interface br0 {
AdvSendAdvert on;
prefix ABCD:ABCD:1000:1::/64 {
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
Replace the "ABCD:ABCD:1000:1::/64" with your own /64 subnet for the client side of the network.
Save the settings.
Then in:
Admin - Commands:
Put the below as the start-up script.

sleep 5
ip addr add ABCD:ABCD:0:1::5/64 dev vlan2
ip addr add ABCD:ABCD:1000:1::1/64 dev br0
ip -6 route add 0::/0 via ABCD:ABCD:0:1::1 dev vlan2
kill -HUP $(cat /var/run/
radvd -C /tmp/radvd.conf
Replace the ABCD:ABCD:0:1::5/64 with the IP address for your WAN interface (in the Valet's your wan is vlan2 not vlan1 as most others).
Replace ABCD:ABCD:1000:1::1/64 with the IP for your LAN interface.
Replace ABCD:ABCD:0:1::1 with the IP of the default gateway on the WAN interface.
Save that as a 'Start Up Script', then reboot your router. Your clients should now have IPv6 enabled.
Important: There isn't any IPv6 firewall in this small build, so clients will need to be wary and have their own PC's firewall enabled. There also isn't anywhere to configure IPv6 DNS's (it needs another DHCP module for that) so your IPv4 dns's need to also be able to resolve v6 addresses for you. 

Just wanted to update you on the correct IPv6 Private address Scope. Please attempt to refrain from using random prefix generation as its used might be reserved for other uses (ABCD:ABCD:0:1::5/64 - not sure what its reserved for but it could pose an issue if its some public scope) fc00::/7 is acceptable private prefix and could be used as fc00:0:0:1::5/64. If you have this working please update me as I am testing this now.

The concept of private networks and special address reservation for such networks has been carried over to the next generation of the Internet Protocol, IPv6.

The address block fc00::/7 has been reserved by IANA as described in RFC 4193. These addresses are called Unique Local Addresses (ULA). They are defined as being unicast in character and contain a 40-bit random number in the routing prefix to prevent collisions when two private networks are interconnected. Despite being inherently local in usage, the IPv6 address scope of unique local addresses is global.

A former standard proposed the use of so-called "site-local" addresses in the fec0::/10 range, but due to major concerns about scalability and the poor definition of what constitutes a site, its use has been deprecated since September 2004 by RFC 3879.
it says v2 on the bottom of the unit. the box is the same.
Success. I found a v1 at canada computers. The differences between the exterior of the box is:
V2: serial starts with CVJ11K
The small text under "M10" at the front says "Cisco Valet"
V1: serial starts with CVJ01K
Under "M10" it says "Cisco Valeta"

Upgraded to 17990 and...
repeater mode buggy on 17990... main ap is wep 128 bit, virtual ap is wpa2 mixed tkip/aes.
intel 5300 sees only wpa, radio type n, and can only connect at 54.
Cisco m10 connected at n speeds. but inssider sees two virtual ap's, one with mac all 00 one with normal mac.
g1 phone sees wpa2 and only one virtual ap.
Tried forcing wpa2 aes on virtual ap and won't connect to main ap at all and rssi of virtual fluctuates between -100 and normal. can't connect with 5300 nor g1. didnt try it with am10.
Edit: i got it to connect with the 5300 with n speeds. with wpa2 with aes. it still feels buggy because i have to reconnect many times to connect.
tried wpa/wpa2 mixed tkip+aes again and the 5300 is connecting normally. not sure what changed.

First I did the 30-30-30 reset. Then, from the Linksys firmware web gui (v., I installed dd-wrt.v24-17990_NEWD-2_K2.6_mini_m10.bin . Did the 30-30-30 reset again. This version worked somewhat, but had several "bugs", namely, I could only save settings using IE. Firefox would simply error out (ad blockers and all disabled).
So, did a 30-30-30 reset again, from IE I installed dd-wrt.v24-17990_NEWD-2_K2.6_mini.bin . Last, a final 30-30-30. This version works great! My signal strength & speed have improved. My $20 M10 just became worth much more thanks to DD-WRT.
My only problem is I am unable to access the Admin GUI via HTTPS. I have the check box ticked, but it still wont work. I have to use HTTP only.

Clear cache in Firefox and Use:

another solution:
I have the same issue. It is probably just a quirk in previous builds. To be honest it is a little problem considering some the issues other people have when they flash their router. The only thing you can really do is flash a different build and see if it is any more stable than the previous. That is the fun of flashing. I wouldn't go with the mini build though. The nokaid-small build works fine for me.
Archivo: dd-wrt.v24-18024_NEWD-2_K2.6_openvpn_small.bin 3388 KB 20/12/2011
So far with build 18024 repeater bridge functionality works perfectly. I have no idea about long-term stability though, I've only had it running for a day.
I'm going to try a multi-router WDS setup next. I want to use these for a house which requires several wirelessly connected APs, and I figure WDS with a single SSID is simpler than having three or four APs with different SSIDs. Given how cheap these things are, I figure that as long as WDS works reliably I can blanket the house with wifi for relatively low cost.
Has anyone tried WDS on these yet?


Archivo: dd-wrt.v24-18007_NEWD-2_K2.6_mini_m10.bin 3369 KB 14/12/2011
Archivo: dd-wrt.v24-18007_NEWD-2_K2.6_openvpn_small.bin 3388 KB 14/12/2011

Archivo: dd-wrt.v24-18740_NEWD-2_K2.6_openvpn_small.bin 3392 KB 15/03/2012

Archivo: dd-wrt.v24-19327_NEWD-2_K2.6_openvpn_small.bin 3568 KB 06/06/2012

Archivo: dd-wrt.v24-19342_NEWD-2_K2.6_mini_m10.bin 3449 KB 08/06/2012
Archivo: dd-wrt.v24-19342_NEWD-2_K2.6_openvpn_small.bin 3568 KB 08/06/2012
Archivo: dd-wrt.v24-19519_NEWD-2_K2.6_mini_m10.bin 3477 KB 20/07/2012
Archivo: dd-wrt.v24-19519_NEWD-2_K2.6_openvpn_small.bin 3592 KB 20/07/2012

 Last build on testing!:
Archivo: dd-wrt.v24-20086_NEWD-2_K2.6_mini_m10.bin 3457 KB 06/10/2012

I was just able to put onto two M10 V1s 
First I flashed to 2.00.03, then the firmware above. Works well.  
???????????? does not exist!!
I currently have a Cisco Valet M10 v1 running:
DD-WRT v24-sp2 (09/09/11) mini - build 17598M NEWD-2 K2.6 Eko

VPN support
You can load dd-wrt.v24-18777_NEWD-2_K2.6_openvpn_small.bin as it is only 3.3MB

Just upgraded my M10 (v1) from 17790 to 18777 via the web GUI. (
It was a no-brainer and took about 2 minutes. I did NOT do a 30-30-30 reset. I haven't tested all functionality, but so far, everything seems to be working great.
(Side note: I did the same upgrade on my Netgear WNR2000 v2, also with success)

Updated to the 2.0 Cisco Firmware
Installed the M10 Firmware
Updated to a newer version of dd-wrt
At this point, it was great but one thing I wanted was SNMP. So, I took the plunge and installed:
Everything went well and so far so good. This is more of an access point so I am not using all the features. But I like what I have seen so far.

Valet M10 -going with DD-wrt as follows:
All flashing done from web GUI
Flashed stock Firmware from Cisco Ver.2.0.03 (build 4)looks a lot like the interface on early linksys routers,circa 1999
30/30/30 reset
wait 20 minutes
30/30/30 reset
wait 20 minutes
30/30/30 reset
Configured as my primary internet router, WAN on a cable modem, firewall, and NAT. That is all working great, much faster than stock. Have not had a chance to test other features yet on this one, I have a TP-Link TL-WR841ND v.7 running as a client bridge on the same network, with, which is DD-WRT v24-sp2 (03/19/12) std according to the GUI, but that goes in a different thread, and it's all working great for 2 days now. I hope this will help somebody out, cuz I had to do some digging to get these two routers going-OPS, notice I posted only results, not questions. Very Happy
Next project: upgrade Ubiquity picostation 2. 

i've been lurking on this forum for the past week to flash my cisco valet m10 v1.
yesterday i finally gained enough confidence to flash the router.
it had v1.0.0 stock firmware from cisco.
i didn't upgrade the stock firmware, 
-) 30/30/30 reset and went directly with dd-wrt.v24-18946_NEWD-2_K2.6_mini_m10.bin
-) upload .bin
-) wait 5min before clicking continue (is what the installation page says to do)
-) wait for another 20min (power still on)
-) another 30/30/30 reset
those are all the steps i took.
it worked fine up to that point.
plug in cable (from modem) into WAN port.
plug in cable from LAN port to my pc, i can access internet (yay!)
now, problem comes with the WAP..
all i want is to set this router to be the central access point for internet that is connect to the modem right away..
i tried to set my WAP to be the same as my old router (which is dlink that is not compatible with dd-wrt), same SSID, same channel, same encryption, same pw.
result: my netbook was able to detect the network and tried to connect automatically, but couldn't connect to the internet at all (saying unidentified network).
so i tried another way, i reset everything to factory default (through web gui), change ssid name to something new, put in same encryption, different password.
result: netbook was able to detect, punch in the new password, client accepted the pw, and still, unidentified network..
this time around, i tried to reset again through web gui, and tried to connect right away with my netbook..
result: netbook was able to detect (dd-wrt as default ssid), but was asking for a password (which was not even set yet).. my netbook even said this is unsecured network..
anybody can help me with this?
what could that non-existent password be?
i don't think it has something to do with the old MAC addr, since i tried my client to set up new connection..
i also don't think it's from ISP, because otherwise i wouldn't be able to connect to internet from my pc (which is on LAN cable).
since nobody had replied anyways, i thought i'd just edit the post..
in the end, i reflashed my router to
it is working under WAP2-AES, but will not work on WEP.
it keeps saying mismatch password..
although i would still prefer WEP, so i can connect my older devices, but i guess WEP isn't supported yet on this build..
That build must be broken
15962 or

Those build are stable
They will have the loopback bug
Find the thread for loopback bug and do as it says

Flash your M10 v1 with this:

I am having stability issues with 18767 as well. Configuration here is repeater bridge using WPA2 Pers. AES on both repeated and provided signals [same key]. No extra fancy configuration: everything else pretty basic. 4 wireless clients are under the repeater coverage and after a while [few hours] all clients under the repeater loose their Wifi connection. Apparently the Valet M10 "lost" the virtual interface servicing clients but I still can ping the M10 via the repeater interface, from other clients from the main AP: It seems the M10 interface toward the main AP is up but the M10 interface toward the clients is down... the only way to recover from this fault is a unplug/wait 10 sec./plug. Often a reboot from the HTML interface won't do it.

This problem is also present with 18024 build. I have tested with *_M10 builds and also the generic *_mini builds but same behavior.
Anyone has a recommended stable build for plain repeater configs?

K26 builds are known to have many problems with repeater/repeater bridge
I would recommend first trying power cycle
30-30-30 reset
Power cycle
And try it again
Otherwise, if you want a good repeater/repeater bridge, get a K24 router

 UPDATE: I have tried a few builds up to now and one has proven to be much better than all what I've tried so far: EKO build 18946
It has been running for 4 days now , in plain vanilla repeater bridge, and crashed only once and self recovered compared with other builds crashing every 2-3 hours and did not self recover. So for all you repeater guys out there , it might be worth to give a try to EKO 18946.

So before writing this update I wanted to make sure the system was stable, and it has been the case for almost 2 weeks time now so I am confident about this update. The previous update did not work well after all for me again, after 2-3 days the wireless clients under the repeater bridge started to loose the Wifi signal...

I found out that repeater bridge can have limitations/problems when more than one wireless client device (PC/laptop) is connected under the repeater bridge. The recommendation in this case is to use WDS instead of repeater bridge. WDS also has the advantage of not translating MAC addresses and is the recommended way when many clients are connecting to the repeater bridge (probably eases DHCP as well..). Here is the link where you can find the limitation and recommendations:
WDS step-by-step configuration are a few clicks away from the above link.
It has been working for more than 2 week without a single interruption (that I am aware of..) and system uptime confirms.
I am using build BS 18767 which can be found here:
WDS is enabled, with same SSID, Same encryption (WPA2/AES) between main AP and WDS M10 client and I followed the step-by-step instructions.
Note: WDS requires some config on both the main AP and the repeater bridge, so this solution only works well when you have access to both AP's. Apparently, WDS is not standardized among vendors but in my case, the main AP (linksys E2000) is also running DD-WRT on the recommended build, so perfect for me.
So there is hope for extending wireless network with the Valet M10! Hopefully, it can help a few people that were in the same situation than me.

Having problems with the repeater bridge setting on M10 running 18946. I'm able to get the repeater bridge working if I disable the security on the primary router.However, the M10(repeater bridge) can't connect to the primary router if the primary router uses either WPA-PSK or WPA2-PSK (only tried these two security modes). Anyone knows how to fix this problem? 100% sure that the password and the security type match.
Repeater and Repeater Bridge have many unsolved problems on K26 builds, sorry.
If you have access to the main AP, you can try using WDS instead of Repeater Bridge. Please check for compatibility tests between DD-WRT and you AP. You can find the list here:
It worked for me and is stable but my main AP is also running DDWRT

on my m10 v1 im using DD-WRT v24-sp2 (06/08/12) std-nokaid-small (SVN revision 19342) and not noticing any issues so far. dont know if any of you are feeling brave but just wanted to throw that out there Smile

 I started off using the standard procedure mentioned in this thread and followed this route:
flash 18946 mini
wait a few minutes
flash 18946 std nokaid small
wait a few minutes
a day or so later get all antsy and wonder what happens when we try the latest!
flash 19342 std nokaid small
wait a few minutes

yay working well!

I have following running on M10 v1 and it is configured as repeater bridge.
The main router is a 2Wire gateway. After M10 reboots, everything works fine. But just in a few minutes, computer connected to M10 cannot ping main router anymore. It seems M10 lost the connection to the main router. Any suggestions? Should I try a different build?

After tried various versions of dd-wrt and many frustrations, I finally flashed with Tomato on Valet M10 v1. It is much more stable now.
I have switched from ddwrt to tomato but am having no success getting it to extend my wireless network. I had some success using ddwt so want to revert back. The problem is when I try and flash the ddwrt firmware I get an error file has invalid header. I have read that I need to modify then binary header but am unsure how to do that or what software to use.
Stock firmware (v1 that I can download that will enable me to flash back without having the file invalid header error (the one on the Linksys site has v2 firmware and I assume I don't want to go to that version as it will no longer be flash able?)
The know how to modify the header on the ddwrt firmware so I can update then reflash.
Or a version of ddwrt firmware that has the valid header so I can download.
Any help would be greatly appreciated
Here should be the link to the latest firmware
hope it helps i dont know how to modify the other stuff

Thanks for the reply I have checked the Cisco site for the original firmware my concern is that it states its version 2 and apparently version 2 of the m10 is not upgradable to ddwrt so I am concerned if I upgrade that firmware I will be left unable to upgrade again to ddwrt
Go to downloads section there is a drop down menu where you can choose your hardware version, which in your case would be version one, the most up to date version of the firmware is Ver.2.0.03 (build 4), this is the exact same website and exact same version that i have used to go back and forth several times as i also have an M10 v1
I fixed my Cisco Valet Plus M20 router
Installed 18774 on to my refurb M20 (with the mini_M20 specific build) with great ease. Everything seems to be working correctly.

No comments: