I use this old Linksys E2k router for dd-wrt. I am in a foreign country. I wanted to make one that I can connect to StrongVPN on.
I tried a bunch of different builds and finally I found this one that works GREAT!~ Except one small thing.
v24-44715_NEWD-2_K2.6_mega-nv60k
The only issue I ran into is that JFFS2 doesn't seem to work. I think I found why. maybe.
In the JFFS2 startup file, the first few lines and some others look like it keeps it disabled instead of enabling it. I thought maybe possibly that could be the problem?
If possible, can you let me know how I can edit anything to make it work correctly?
Everything else works perfect on this build from what I can tell. I want to add an SSL certificate so my router login will be protected with https. And I need JFFS2 to work properly in order to do it.
Joined: 18 Mar 2014 Posts: 12887 Location: Netherlands
Posted: Tue Sep 07, 2021 15:03 Post subject:
About JFFS2 (dedicate some NVRAM to permanent storage) I think it is no longer supported due to size constraints
44715 is old and has already security issues so it is no longer supported.
K2.6 is perhaps not the best choice as this router can support K3.X (which actually is K4.4)
Where to find builds and how to research see the forum guidelines:
To get the best out of DDWRT and the forum read the forum guidelines full of helpful pointers:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
May I suggest to do the following:
Reset to defaults
upgrade to the K3.X mega build with the same version number 44715.
Reset to defaults after upgrading
Upgrade to 47282 (that is what I am using for my E2000 at the moment)
Reset to defaults again and put settings in manually never restore from a backup file (to a different build)
Be patient take your time
General instructions for OpenVPN client setup are in my signature at the bottom of this post.
Might I suggest to use WireGuard, OpenVPN performance on this router is about 5-6 Mb/s WireGuard triples that.
Most VPN providers nowadays support WireGuard
I was able to get wireguard working with my StrongVPN account.
Thank you very much!
I have a couple notes about this:
It doesn't look like this build will do JFFS2 support on linksys E2000. So if you want to use HTTPS to secure your router with a PKI certificate, it might not work unless there's another way I haven't found yet. Just use a very strong password. I think access to the management interface from the WAN port is blocked anyway. SSHd does work.
I have one noob question. The wireguard instruction told me to uncheck the SPI firewall while running the command to install the VPN configs.
I was able to get wireguard working with my StrongVPN account.
Thank you very much!
I have a couple notes about this:
It doesn't look like this build will do JFFS2 support on linksys E2000. So if you want to use HTTPS to secure your router with a PKI certificate, it might not work unless there's another way I haven't found yet. Just use a very strong password. I think access to the management interface from the WAN port is blocked anyway. SSHd does work.
I have one noob question. The wireguard instruction told me to uncheck the SPI firewall while running the command to install the VPN configs.
Do I leave that unchecked?
Here! Take some money! Thanks for your help!!!
JFFS2 support indeed is no longer present, this router has 8 MB flash and the software itself takes all of that so there is no room left for JFFS2 (the developer could leave some things out and make room but that is the design decision which was made)
Most provider let you make a WireGuard config file which you can use to setup manually, builds after 47282 even have an import utility to import the config file so you can setup with a few mouse clicks.
I have not tested a build later than 47282 on my E2000 so that is why I did not recommend it yet but at this moment we are at 47381.
Most of us either uses SSHd with a key to get to our routers from outside or better setup a WireGuard server alongside the WG client to connect from outside.
To do this you have to use Policy Based Routing for the WG client (or use other methods to free the WAN for traffic)
If you want to do that you can always ask for help here, but most of it is covered in the guides
Some tips if you want to use Policy Based Routing for the Client set your DHCP range starting from .64 for 64 clients so your range will be from .64 - .127
then in the WG PBR field enter xxx.xxx.xxx.64/26 (at the xxx. enter your own network) so that all DHCP clients are using the VPN, if you also have static leases and want those to use the VPN set those to use from .128 - .191 and add in the WG PBR field xxx.xxx.xxx.128/26