Posted: Sun Jul 14, 2019 11:47 Post subject: wrt160n v1 unable to flash generic_vpn build
In an attempt to revitalise an old wrt160n v1 , i was able to flash it with a current v24 mini build. All went and looks well. But i am unable to flash the v24 generic_vpn build. According to the peacock thread and wrt160n wiki i should be able to flash it, since it is smaller in size then the 4mb flash size. But i keeps getting refused. Anything i'm doing wrong?
Could it be that the wrt160n v1 only was able to run openvpn with the now obsolete eko vpn_small build? And if this is the case, is there an alternative for it?
There is a mips-r1-mini-vpn build that may work, but a safe bet would be to have a means to recover your router if it bricks. I am not saying that this is a de-facto solution, but it's the only alternative that I am aware of.
Posted: Mon Jul 15, 2019 18:14 Post subject: Re: wrt160n v1 unable to flash generic_vpn build
dipswitch wrote:
i was able to flash it with a current v24 mini build. All went and looks well. But i am unable to flash the v24 generic_vpn build. According to the peacock thread and wrt160n wiki i should be able to flash it, since it is smaller in size then the 4mb flash size. But it keeps getting refused.
What build were you trying? The current latest k2.4 build 40276 vpn_generic.bin is 3928064 bytes.
If what you tried is smaller than that, it could just be a bad build, or your router has a different MTD layout for the linux partition. Attach a `dmesg` output showing the partitions. Or try other f/w as kp69 noted... _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Uploading the vpn firmware binary takes a very short time. After that, a "upload complete" message appears and the device reboots, but the new firmware didnt stick. Flashingtime is way too short so i guess it is rejected.
There is a mips-r1-mini-vpn build that may work, but a safe bet would be to have a means to recover your router if it bricks. I am not saying that this is a de-facto solution, but it's the only alternative that I am aware of.
The freshtomato mips r1 k26 minivpn build seems to be 4112384 bytes in size, which i dont understand. Why do they release such a build, since it wouldnt fit any 4mb device?
Joined: 08 May 2018 Posts: 14224 Location: Texas, USA
Posted: Mon Jul 15, 2019 23:01 Post subject:
I figured it was going to be a stretch. I have never known anyone to get vpn builds of DD-WRT or otherwise on any 4mb device. That being said, though, since I do tinker with the FT build environment, I can take a look to see what is included in the mini-vpn-mips-R1 build and ask you what you don't want or need and run a test build. However, on a device that old, running vpn is like pissing in the wind IMHO. Not that it won't work, but it will be S-L-O-W.
I figured it was going to be a stretch. I have never known anyone to get vpn builds of DD-WRT or otherwise on any 4mb device. That being said, though, since I do tinker with the FT build environment, I can take a look to see what is included in the mini-vpn-mips-R1 build and ask you what you don't want or need and run a test build. However, on a device that old, running vpn is like pissing in the wind IMHO. Not that it won't work, but it will be S-L-O-W.
It was only my intention to repurpose the device, partially for the fun of it and also because for simple tasks it can still be a usable device. I used to be able to flash generic-vpn builds in 4mb broadcom devices, i'm unsure why this suddenly isnt possible anymore? As far as i can remember, the golden rule always was: vpn functionality: broadcom 4mb, atheros qualcomm 8mb.
Joined: 08 May 2018 Posts: 14224 Location: Texas, USA
Posted: Tue Jul 16, 2019 0:16 Post subject:
dipswitch wrote:
kernel-panic69 wrote:
I figured it was going to be a stretch. I have never known anyone to get vpn builds of DD-WRT or otherwise on any 4mb device. That being said, though, since I do tinker with the FT build environment, I can take a look to see what is included in the mini-vpn-mips-R1 build and ask you what you don't want or need and run a test build. However, on a device that old, running vpn is like pissing in the wind IMHO. Not that it won't work, but it will be S-L-O-W.
It was only my intention to repurpose the device, partially for the fun of it and also because for simple tasks it can still be a usable device. I used to be able to flash generic-vpn builds in 4mb broadcom devices, i'm unsure why this suddenly isnt possible anymore? As far as i can remember, the golden rule always was: vpn functionality: broadcom 4mb, atheros qualcomm 8mb.
I may have been thinking 2MB devices. There's been so much changed in the source code, there is no telling. At least you can still use it as an AP. If you don't need multi-wan support or pptpd, there is a small chance of running a stripped down mini-VPN build of FT that might fit.
I'm trying to flash r40276/broadcom/dd-wrt.v24_vpn_generic.bin [...]
Uploading the vpn firmware binary takes a very short time. After that, a "upload complete" message appears and the device reboots, but the new firmware didnt stick. Flashing time is way too short so i guess it is rejected.
Ok, so you could use an older build; whatever the latest was that fit.
That shows it's a 0x400000 chip (4.00 MB), and the 'linux' partition is 0x3f0000-0x40000 = 3866624 bytes = 3.6875 MB
That is a -bit- more than the generic Peacock verbiage. The last build that should fit is:
36808 dd-wrt.v24_vpn_generic.bin 30-Aug-2018 12:40 3850240
Of course, always check the new build thread before flashing, esp for old k.4 builds, as they aren't tested as often. /looking...
I'm trying to flash r40276/broadcom/dd-wrt.v24_vpn_generic.bin [...]
Uploading the vpn firmware binary takes a very short time. After that, a "upload complete" message appears and the device reboots, but the new firmware didnt stick. Flashing time is way too short so i guess it is rejected.
Ok, so you could use an older build; whatever the latest was that fit.
That shows it's a 0x400000 chip (4.00 MB), and the 'linux' partition is 0x3f0000-0x40000 = 3866624 bytes = 3.6875 MB
That is a -bit- more than the generic Peacock verbiage. The last build that should fit is:
36808 dd-wrt.v24_vpn_generic.bin 30-Aug-2018 12:40 3850240
Of course, always check the new build thread before flashing, esp for old k.4 builds, as they aren't tested as often. /looking...
First of all, my apologies for the late respone; seems i didnt get a topic notification.
That being said, it worked! This is great. Now this device can be put to use, albeit in a simple role, for a second time. This is what i enjoy most, repurposing hardware to make it function beyond its original use and functionset.
To express my gratitude, i made a little donation to the ddwrt team. Thank you.
