Router/Version: DIR-890L-A1
Firmware: DD-WRT v3.0-r33492 std (10/10/17)
Kernel: Previous: 2????
Mode/Status: Internet gateway
Reset: No Issues/Errors: None found so far in 30min.
Notes: basic setup as main AP and router for home network _________________ D-Link DIR-825 B1 - DD-WRT v3.0-r35681 std (04/06/18) modded with 2 USB ports
Netgear R6700v1 - DD-WRT v3.0-r47608 std (10/28/21)
D-Link DIR-890L - DD-WRT v3.0-r44863 std (11/24/20)
Router: Buffalo WZR-1750DHP
Firmware: buffalo-wzr-1750dhp-webflash.bin (v3.0-r33492 std)
Kernel: Linux 4.4.91 #2089 SMP Tue Oct 10 09:24:08 CEST 2017 armv7l
Status: Working
Reset: No
Notes on configuration:
I needed to erase nvram as web UI factory reset nor 30/30/30 would completely clear out prior configs.
Flashed v3.0-r33492 mega on two E2000.
One is a router with 2.4Ghz SSID, vlans, trunked port, virtual SSID for guest. The other 2.4Ghz access point only, vlans, trunked port, virtual SSID for guest.
The usual tweak on wireless TX power to 50mW and CPU to 300MHz.
One issue I experienced is I accidentally disabled WiFi and then had no wireless (obviously) or wired connectivity. I held the E2000 reset button for 15 seconds until the LEDs flashed and had to start over. Needless to say I won't be doing that again.
Other than that, no issues. _________________ --------------------------------------------------
VLANs, port trunking, virtual SSID (Guest)
DNSmasq, NTP, syslog, nflow
Hub and spoke, multi-site, routed VPN (OpenVPN client), split tunnel
1 DNS zone per site, forward, reverse look-up across all sites
Asus RT-AC68U rev A2 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC68U rev C1 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Netgear R7000 DD-WRT v3.0-r48138 std (01/17/22)
Linksys E2000 DD-WRT v3.0-r33492 mega (10/10/17)
Hey, sorry to bug you with a private message but for some reason I was not permitted to post a reply to your post (I am new to the forum so maybe that's it). I too have a Linksys E2000 running an older ddwrt build that I use as a repeater. It is fairly stable and gets the job done but it cuts out on me quite a bit too. I would perhaps like to try one of the newer builds and I saw how recent your post was. In any event, can you tell me how I go about erasing the nvram and what you meant by "The usual tweak on wireless TX power to 50mW and CPU to 300MHz"? Any other info would be appreciated as well.
Upon reboot then do the work to properly reset and configure as described next.
Use a terminal emulator like putty and telnet to the e2000.
Login name is root and password is the same as your admin password. Then issue two commands:
Code:
erase nvram
reboot
This will correctly factory reset as the factory reset in the web UI will not erase all settings.
Upon reboot, connect to the e2000 with a wire to keep things simple and telnet into it again on the default IP 192.168.1.1, then issue the following commands:
Code:
nvram set clkfreq=300,150,75
nvram commit && reboot
Once rebooted, set the TX power under Wireless > Advanced Settings to 50.
The last thing I would do is disable CTS protection mode. I've done quite a bit of testing with this and see great benefits. Others may disagree and recommend to leave it enabled out of principle.
I prefer wires when possible instead of WDS or repeater. The last thing would be to change the beacon to 50 in an environment with more than one access point, so that roaming happens faster (assuming same SSID on all access points).
John _________________ --------------------------------------------------
VLANs, port trunking, virtual SSID (Guest)
DNSmasq, NTP, syslog, nflow
Hub and spoke, multi-site, routed VPN (OpenVPN client), split tunnel
1 DNS zone per site, forward, reverse look-up across all sites
Asus RT-AC68U rev A2 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC68U rev C1 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Netgear R7000 DD-WRT v3.0-r48138 std (01/17/22)
Linksys E2000 DD-WRT v3.0-r33492 mega (10/10/17)
Hey, sorry to bug you with a private message but for some reason I was not permitted to post a reply to your post (I am new to the forum so maybe that's it). I too have a Linksys E2000 running an older ddwrt build that I use as a repeater. It is fairly stable and gets the job done but it cuts out on me quite a bit too. I would perhaps like to try one of the newer builds and I saw how recent your post was. In any event, can you tell me how I go about erasing the nvram and what you meant by "The usual tweak on wireless TX power to 50mW and CPU to 300MHz"? Any other info would be appreciated as well.
Upon reboot then do the work to properly reset and configure as described next.
Use a terminal emulator like putty and telnet to the e2000.
Login name is root and password is the same as your admin password. Then issue two commands:
Code:
erase nvram
reboot
This will correctly factory reset as the factory reset in the web UI will not erase all settings.
Upon reboot, connect to the e2000 with a wire to keep things simple and telnet into it again on the default IP 192.168.1.1, then issue the following commands:
Code:
nvram set clkfreq=300,150,75
nvram commit && reboot
Once rebooted, set the TX power under Wireless > Advanced Settings to 50.
The last thing I would do is disable CTS protection mode. I've done quite a bit of testing with this and see great benefits. Others may disagree and recommend to leave it enabled out of principle.
I prefer wires when possible instead of WDS or repeater. The last thing would be to change the beacon to 50 in an environment with more than one access point, so that roaming happens faster (assuming same SSID on all access points).
I also have E2000's running incredibly old builds as standalone APs. I went looking for newer builds after I heard about the KRACK vulnerability, and found this thread link in the Wiki.. But this build came out right as KRACK went public so it's obviously not patched. Are there any KRACK-patched builds that work on these old boys?
Hey, sorry to bug you with a private message but for some reason I was not permitted to post a reply to your post (I am new to the forum so maybe that's it). I too have a Linksys E2000 running an older ddwrt build that I use as a repeater. It is fairly stable and gets the job done but it cuts out on me quite a bit too. I would perhaps like to try one of the newer builds and I saw how recent your post was. In any event, can you tell me how I go about erasing the nvram and what you meant by "The usual tweak on wireless TX power to 50mW and CPU to 300MHz"? Any other info would be appreciated as well.
Upon reboot then do the work to properly reset and configure as described next.
Use a terminal emulator like putty and telnet to the e2000.
Login name is root and password is the same as your admin password. Then issue two commands:
Code:
erase nvram
reboot
This will correctly factory reset as the factory reset in the web UI will not erase all settings.
Upon reboot, connect to the e2000 with a wire to keep things simple and telnet into it again on the default IP 192.168.1.1, then issue the following commands:
Code:
nvram set clkfreq=300,150,75
nvram commit && reboot
Once rebooted, set the TX power under Wireless > Advanced Settings to 50.
The last thing I would do is disable CTS protection mode. I've done quite a bit of testing with this and see great benefits. Others may disagree and recommend to leave it enabled out of principle.
I prefer wires when possible instead of WDS or repeater. The last thing would be to change the beacon to 50 in an environment with more than one access point, so that roaming happens faster (assuming same SSID on all access points).
I also have E2000's running incredibly old builds as standalone APs. I went looking for newer builds after I heard about the KRACK vulnerability, and found this thread link in the Wiki.. But this build came out right as KRACK went public so it's obviously not patched. Are there any KRACK-patched builds that work on these old boys?
Thanks! (Another Matt, LOL!)
802.11r (fast forming) which is generally enabled for VoIP devices is probably not implemented on dd-wrt. And even if it were would be disabled by default. Please correct me if I'm wrong. Also, is your wireless traffic that interesting that someone will go to all this trouble to use the vulnerability to peek inside? _________________ --------------------------------------------------
VLANs, port trunking, virtual SSID (Guest)
DNSmasq, NTP, syslog, nflow
Hub and spoke, multi-site, routed VPN (OpenVPN client), split tunnel
1 DNS zone per site, forward, reverse look-up across all sites
Asus RT-AC68U rev A2 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC68U rev C1 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Netgear R7000 DD-WRT v3.0-r48138 std (01/17/22)
Linksys E2000 DD-WRT v3.0-r33492 mega (10/10/17)
While the 33492 did flash properly, I had issues with the wifi repeater bridge working properly.
If you are using your router for that I don't recommend it. I was getting security errors even thought my settings were correct. I went back to build 25974(dd-wrt.v24-25974_NEWD-2_K2.6_mega-nv60k.bin) based on this thread https://www.dd-wrt.com/phpBB2/viewtopic.php?t=304125&start=1.
Flashed the mini first and then build 25974.
jjwatmyself, I did follow your instructions to a T. Are you using the router as repeater bridge?
While the 33492 did flash properly, I had issues with the wifi repeater bridge working properly.
If you are using your router for that I don't recommend it. I was getting security errors even thought my settings were correct. I went back to build 25974(dd-wrt.v24-25974_NEWD-2_K2.6_mega-nv60k.bin) based on this thread https://www.dd-wrt.com/phpBB2/viewtopic.php?t=304125&start=1.
Flashed the mini first and then build 25974.
jjwatmyself, I did follow your instructions to a T. Are you using the router as repeater bridge?
I am not using WDS or repeater bridge any more on E2000 as was able to run a wire (strongly recommend). In fact I would use a powerline adapter before WDS or repeater bridge. You may need to move breakers on your panel to the same side in order to get the best signal.
I tested WDS and repeater bridge on 25974. I had horrific performance issues after some time though BUT had not performed erase nvram when moving to 25974. I now suggest is needed on the E2000 after installing any build due to this as have witnessed how bad things can be when not doing so. The web UI factory reset doesn't clear things out for some reason. I don't know if that's just on the E2000 or not.
The instructions I provided are good for any build. There are lots of other teaks that people talk about in the forums for all the different routers, but I am yet to find basis for implementing any other than those I provided, some of which are E2000 specific. Unless you can prove it makes a difference why change a default right?
DD-WRT is not for the faint of heart. Once you find a build that does what you need, stick with it until you find an issue or need something it doesn't do. _________________ --------------------------------------------------
VLANs, port trunking, virtual SSID (Guest)
DNSmasq, NTP, syslog, nflow
Hub and spoke, multi-site, routed VPN (OpenVPN client), split tunnel
1 DNS zone per site, forward, reverse look-up across all sites
Asus RT-AC68U rev A2 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC68U rev C1 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Netgear R7000 DD-WRT v3.0-r48138 std (01/17/22)
Linksys E2000 DD-WRT v3.0-r33492 mega (10/10/17)
DD-WRT is not for the faint of heart. Once you find a build that does what you need, stick with it until you find an issue or need something it doesn't do.
I have to completely disagree with this. Cost of a used E2000 is about $10 and they are readily available. The new builds have bug fixes, close security holes, and have additional features. The big reason for holding on to the old builds is for baseline comparison, and because on some devices (like the Netgears) 8MB flash <> 8MB because they waste a lot of flash space for unusual partitions that seem to accomplish no purpose.
If the device is effectively worthless then you should have no qualms about upgrading it. I have a box of old routers with street values of < $10 USD that are bricks. I hold on to them just in case one day the supply of ultra-cheap used routers dries up and I'm scrambling for a router for a customer. But so far all I see is that while the junk bins at the thrift store used to be full of old 54g stuff now they are full of old 300N stuff and even some AC devices now are trickling in.
NEVER underestimate the ability of end users to drop $200 into a device then a year later when they start having problems with it because they don't know squat about how to configure it, tossing it into the donation bins at the thrift stores, rather than spending the time to learn how to properly configure it. As long as people are lazy the market will be flooded with old routers like the E2000 and dd-wrt users should damn the torpedoes full speed ahead on updating.
DD-WRT is not for the faint of heart. Once you find a build that does what you need, stick with it until you find an issue or need something it doesn't do.
I have to completely disagree with this.
I read your post twice and I think we are both saying almost the same thing but using different words.
The only thing I will add is that new code is not always better code. dd-wrt forums are littered with posts from testers for each build on what's newly broken and newly fixed for their respective make and model.
Having a known build with problems or feature limitations you can live with is sometimes better. This is the reason I don't recommend upgrading for the sake of upgrading, or upgrading more frequently.
Builds with bug fixes or feature enhancements do one of two things: if they do not effect the environment then implementing helps the admin sleep better and nothing more. If they fix or add something that was impacting the environment in a measurable fashion then everyone's lives get a little easier, the admin can claim a win and the admin also sleeps better. _________________ --------------------------------------------------
VLANs, port trunking, virtual SSID (Guest)
DNSmasq, NTP, syslog, nflow
Hub and spoke, multi-site, routed VPN (OpenVPN client), split tunnel
1 DNS zone per site, forward, reverse look-up across all sites
Asus RT-AC68U rev A2 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC68U rev C1 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Netgear R7000 DD-WRT v3.0-r48138 std (01/17/22)
Linksys E2000 DD-WRT v3.0-r33492 mega (10/10/17)
While the 33492 did flash properly, I had issues with the wifi repeater bridge working properly.
If you are using your router for that I don't recommend it. I was getting security errors even thought my settings were correct. I went back to build 25974(dd-wrt.v24-25974_NEWD-2_K2.6_mega-nv60k.bin) based on this thread https://www.dd-wrt.com/phpBB2/viewtopic.php?t=304125&start=1.
Flashed the mini first and then build 25974.
jjwatmyself, I did follow your instructions to a T. Are you using the router as repeater bridge?
I am not using WDS or repeater bridge any more on E2000 as was able to run a wire (strongly recommend). In fact I would use a powerline adapter before WDS or repeater bridge. You may need to move breakers on your panel to the same side in order to get the best signal.
I tested WDS and repeater bridge on 25974. I had horrific performance issues after some time though BUT had not performed erase nvram when moving to 25974. I now suggest is needed on the E2000 after installing any build due to this as have witnessed how bad things can be when not doing so. The web UI factory reset doesn't clear things out for some reason. I don't know if that's just on the E2000 or not.
The instructions I provided are good for any build. There are lots of other teaks that people talk about in the forums for all the different routers, but I am yet to find basis for implementing any other than those I provided, some of which are E2000 specific. Unless you can prove it makes a difference why change a default right?
DD-WRT is not for the faint of heart. Once you find a build that does what you need, stick with it until you find an issue or need something it doesn't do.
Ok. I have been running the mini build for years and had no issues as a repeater bridge. I use wired connections only and then bridge them to the other router.
I did erase the nvram as suggested by you with the latest build and still had issues. So not sure if it was the build or the router.
I just wanted give feedback in case anyone else is running it for the repeater bridge. So far build 25974 is working fine.
And thanks for your instructions!! They were very helpful in the process.
@mthornto88 if you are using wires to connect routers (using the lan ports on both of them off course) then I recommend you set the wireless mode to AP (access point) not repeater bridge. On the second router, you just set a different static IP, disable DHCP, disable wan, and configure the ssid and security to be identical to the main router. _________________ --------------------------------------------------
VLANs, port trunking, virtual SSID (Guest)
DNSmasq, NTP, syslog, nflow
Hub and spoke, multi-site, routed VPN (OpenVPN client), split tunnel
1 DNS zone per site, forward, reverse look-up across all sites
Asus RT-AC68U rev A2 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC68U rev C1 DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Asus RT-AC1900P DD-WRT v3.0-r48138 std (01/17/22)
Netgear R7000 DD-WRT v3.0-r48138 std (01/17/22)
Linksys E2000 DD-WRT v3.0-r33492 mega (10/10/17)
@mthornto88 if you are using wires to connect routers (using the lan ports on both of them off course) then I recommend you set the wireless mode to AP (access point) not repeater bridge. On the second router, you just set a different static IP, disable DHCP, disable wan, and configure the ssid and security to be identical to the main router.
Sorry you misunderstood. I am using wired connections to the e2000 in another room and then bridging that back to the main router in another room. The routers are in two different rooms.
The only thing I will add is that new code is not always better code
Correct. I probably should have stated that if the admin updates and the newer build is worse - they should back-rev
But, the admin SHOULD be updating. The issue really is in the frequency. I would say that in a business, where an admin is being paid to keep an eye on this sort of thing, an admin should be looking into updating devices around every 6 months to a year at most. That also predicates using same models everywhere as well as adequate sparing.
Home/Consumer users are really the worst case scenario because once they get something working they just want to ignore it forever. Until that is it breaks and then they go buy a new one. If they get a couple years out of a device costing less than USD $100 they are usually happy. What is really dumb is that the wifi standards just don't change that quickly and as time passes they will be changing even less. So you have people discarding 4 year old wifi routers and buying brand new ones thinking they are getting something newer and better when the reality is that it's not any better than what they had. And that's just the APs the clients are worse.
You have weird scenarios like in my own home where the AP is twice as old as the average age of the phones and laptops it's feeding yet the phones and laptops which are newer use older wifi standards than the AP.
Or you get stuff like the laptop I'm typing this on has a wifi chip from Intel that has drivers from Intel that are 3 years younger than the youngest ones released by HP which made the laptop.
The problem with consumer gear is unless you sell it cheap, it won't sell and the only way the vendors can really sell the stuff cheap is to eliminate just about every shred of support possible on it. So the computer industry has created this myth that if you buy a cheap hardware device it's going to be "done" and never need updates.
