Dd-wrt V24 Sp1 Vint

[Asdrubal Dagreat]

CommentBualdoot on 12-Dec-2008: The comments below are from before I added the install instructions above. The comment below was refering to a comment that i removed, because it talked about not being sure if the WRT54Gv2 had more than 2MB memory, which of course we know it does. As for the instructions it gave that he refers to, they were not very clear, so, I made my own set of instructions based off the v1-v1.1 instructions.

all set [Comment from jas3 on 16-Mar-2008: The above worked for me. I then updated from standard to dd-wrt.v23_vpn_generic.bin which succeeded as well] May08, When upgrading to v24, please do a full firmware reset (hold reset button for 30 seconds on power up). I did not do this when upgrading to v24 and was getting all sorts of strange behaviors from my router. After resetting and then reconfiguring the router, all was well.

Comment MoT 11:01, 2 Jul 2007 (CEST) : I have been able to flash the VPN version on my V2.0, after flashing from the original Linksys firmware to the mini version first. I followed the V4 tutorial.

After flashing to the mini version, I couldn't flash to the VPN version at first, as I was immediately redirected to a blank page when trying to flash. This seemed to be a problem with IE7, with Firefox, it went fine.

Comment I Use Dial 13:54, 21 Jul 2007 (PDT) I installed mini to my v2.2 through Linksys GUI and had forgotten to reset factory defaults before uploading. I had same problem with blank screen loading but Firefox didn't help. Unplugged it, did a hard reset, unplugged it again, and everything was fine. Then uploaded latest stable version without issue.

Comment Glc 19:00, 31 October 2007 (CET) v2.0 Installed mini generic over Linksys firmware using the web interface, followed by standard generic with web interface. Setting to PPPoE knocked out the WAN port, worked fine in DHCP. Flashed back to mini generic and everything works as advertised.

Comment : Installed mini, then standard generic. No problems except I can't overclock. I try 216 but when applying and restarting all router lights flash together periodically every few seconds. Hard resetting using button takes router back to factory settings and then it works fine. Tried twice on v23 sp2 and once on v24 RC5.

Comment (March 19, 2008) : Just installed dd-wrt on my WRT54G v2 router. I started by installing wrt54gv2 v24 rc6.2 mini through the Linksys web interface and then after I got that installed I used the new dd-wrt mini interface to install wrt54gv2 v24rc6.2 standard generic. Everything is running smothly and I had no problems in getting dd-wrt installed.

Comment --Dlfretz 18:05, 29 August 2008 (CEST)I was able to install the standard version after flashing the mini version. I just couldn't go straight to the standard version. I installed with Firefox 3.0 on Windows. This is an original Linksys WRT-54G version 2.0

Comment: 28 Sept 08 Uploaded v24sp1-micro generic on a v.2.0 - now I can't upload anything else. Have tried the VINt and the mega-generic and while the upload and reboot appear to be successful, the router still reports the micro version and features are unchanged.

Comment - skaterkfbs - Followed these instructions for a v2.2 and worked perfectly. I had trouble trying to go directly from LinkSys v4.21.1 firmware to DD-WRT v24 VINT Standard. Had to use the middle DD-WRT v24 VINT Mini.

Comment atlasit July 2009: After installing the mini firmware to a WRT54G v2.0 using IE8, clicked the Continue button and did a hard reset. The screen that comes up after the reset prompts to change the user and password of the router. It would not continue after clicking the button until I viewed the page in 'Compatibility Mode'. Then it took the changes.

Comment --Educmale 06:07, 11 November 2009 (CET): With Ver2.2, I noticed that both the VINT-std and the STD versions install and work fine, almost ---- the STD version won't allow a virtual wireless LAN to connect using WPA2-pers security, while operating in repeater mode. It acts like there is a bug there, in the STD version, in that virtual area -- Odd, as the STD version -will- connect as a wireless access point, using the same WPA2-pers setup. In contrast, VINT will allow the same set up to let the WPA2-pers function either as an AP or a virtual wireless Lan. [The STD version was the one available 3days ago; perhaps this bug will be fixed, one day?]

Comment --GNUton 12:37, 15 November 2010 (CET): Today I bricked my WRT54G 2.0 installing dd-wrt through the linksys web interface. I tried to install the generic mini firmware using Chromium 7.0 on Ubuntu. It uploaded fine the image on the router but at the end it showed an error message.

[Comment --n8hfi: On a very old WRT54G v1.0, I found it necessary to upgrade with a newer Linksys firmware before I could load DD-WRT. The original firmware (Linksys v1.00.8 Dec 24 2002) gave a "incorrect image file" error on on both the mini and standard DD-WRT v23 SP2 images. The following sequence was performed with the HTML GUI and Microsoft Internet Explorer Web browser:

[redhedjim: 2013-09-01 WRT54G v1.1 with recent Linksys firmware]Signed on to the Linksys, did a factory reset. Used the web browser to upload a mini-Generic release (happened to be build 13064, from the Router Database page). Router rebooted to DD-WRT (that was easy!). Did a 30-30-30 reboot, and DD-WRT was running. Uploaded the std_Generic build (also 13064). Found that odd things happened from to time, and the site survey did not work. Re-read the Peacock post, 13064 is not a good release - DO NOT TRUST THE ROUTER DATABASE to recommend a release. Did a telnet into the router to determine corerev (see Peacock step 4, nvram get wl0_corerev) to confirm that corerev=4. Therefore, I needed a VINT build. I used EKO VINT 12548, and everything was rosy. Then tried EKO VINT 13491, and again everything was great.

SUMMARY: Use the Linksys web interface to FIRST install a generic mini build, then 30-30-30. Then install a VINT EKO standard build (or any other build that fits), I had best success with 12548 and 13491. 30-30-30, and then do your detailed configuration. I have tested Site Survey, AP, Client, Client Bridge, and Repeater Bridge, all work fine. I have not tested VOIP, OpenVPN, etc., so do not know if these work in the build numbers listed above.[end redhedjim]

[dgb: 2009.04.25 V1.0 hardware with 1.02.1 firmware]On a V1.0 box with firmware 1.02.1 Feb 2003... First there is no administration tab, look under "system". With IE and eventually with Firefox pushing the Upgrade button resulted in a chooser (browser). I choose the dd-wrt bin file and pushed the Upgrade button, the browsers each failed. IE reported the server was busy or not available. Firefox sent a dump off to microsoft. So I located and tried to install a newer linksys firmware load - same results. I then loaded up netscape, turned off the blockers, configured it to open popups in a new tab, choose the newer linksys firmware and pressed update. It showed a progress bar as the firmware was loaded into the vintage box, Eventually the page went blank on " ". Lights occasionally flicker as I impatiently wait and document the differences I've seen to this point.

Still using NS and under Adminstration/Firmware Upgrade I selected the dd-wrt load dd-wrt.v24-9517_vint_voip, an upload progress bar displayed followed by "upgrade are failed!", I choose continue... Repeating the process has the same result. Third attempt, this time with IE - same result. I surmise that the router is not actually attempting to flash itself, but failing the .bin file. This for two reasons, the progress bar never gets much past 50% and the router never 'goes away", in fact it reports and error and wants to continue. The progress bar actually completes once then starts again before the failure notice.

Now I'm guessing here, but maybe some sick firmware developer who wasn't even in college when v1.0 hardware was available coded in an assert that the .bin file must be able to fit within the smaller modern architectures. I used IE to get the linksys firware to use dd-wrt.v24-9517_VINT_mini and "Upgrade is successful" from the unit. Pressed "continue" presented root/admin and here's my old friend dd-wrt! I can feel a new wireless bridge being born... 30/30/30 more Scotch, more beer.

The old box is now running dd-wrt v24(05/20/08)voip uptime 1 min. There probably isn't a lot of this old stuff out there so maybe this isn't of interest to anyone else - but if you're trying, get netscape for that first giant step...[end dgb]

The KRACK vulnerability was announced on 10/17/2017 and it is the most significant networking vulnerability since Heartbleed. It is documented here [1] by it's finder. The vulnerability allows an attacker that is within wifi range of the Access Point and the wifi client to tap into a connection made with WPA2 and see the unencrypted data going over it.This attack is primarily a client attack. dd-wrt contains client wireless code that is used for certain operations (repeating, etc) and is thus vulnerable. dd-wrt does NOT support 802.11r-2008 Fast Roaming which means it's server code is not vulnerable. (many commercial AP's do, however)

While it is true that these same issues exist on WiFi networks that do not have encryption turned on, the user does get a warning message from their operating system when connecting to one of those networks.

Note that Repeater Bridge has been broken in the K2.6 builds after build 26125 for Broadcom devices (it works in K3.x builds) due to wireless driver issues. Client Bridge works. So if you need that you must move to K3.x builds to have the vulnerability fixed or downgrade to K2.4 builds (if your device supports it)

IPv6 was broken in build 33555 and only K2.4 and Mini (both lack IPv6) should be used in that build. Build 33607 had some issues with wireless radios particularly on dual radio devices and should be avoided. IPv6 was fixed in build 33679 however that build is larger than 33555 and Mega and std_nokaid_small versions of that build MAY NOT LOAD on a number of devices (primarily certain Netgear devices which reserve some of the flash in a separate partition) both 4MB and 8MB flash devices are affected.

3a8082e126