Posted: Fri Aug 27, 2010 11:30 Post subject: jffs2
Hello, I have a question about this router.
How do I add jffs2 functionality to this router? I know I have to get the right build and I know the std build does not include it. I've tried a couple of the generic mini builds but they do not work. Can anybody point me to the right build that would allow this functionality, if it is possible at all. Thanks. Alan
There is no room for jffs in Atheros N-routers with only 4MByte flash.
There is only one build size for them, standard, there is no mini version. _________________ Kernel panic: Aiee, killing interrupt handler!
Hi again. After testing and testing and testing... well, you get the idea, and after steveg1701 saying that I might get better result with a lower TX, I've tried that, and guess what, he was rigth, 10x steveg1701. Now I can get stable 300 mbps and a real throughput of ~80 mbps (this is even higher than trendnet firmware). The setting are:
TX Power: 30
Antenna Gain: 2
Then - AP, N-Only(2.4GHz), CTS
RTS Threshold: Disable
Short Preamble: Enable
Outdoor Band: Disable
Channel Width: Turbo (40MHz)
TX and RX Antenna Chains: 1+3 (I think the second antenna is considered the 3rd)
AP Isolation: Enable
Radar: Enable
W. Channel: 11
C. Chanel: lower
Sensitivity and Max A C:100
This setting are working very well in my case, I hope in your case will work the same. Tested with Speedtest.net (I have a 100 Mbps line) and Xirrus Wi-Fi Monitor(very good for testing).
Hi andy4theherd, I was thinking that raising the power will improve the signal and the outdoor band will improve the distance the signal can travel, obviously I was wrong.
Noob question - How do I get the latest supported ddwrt firmware for my 652? Going thru' the router database does not give me an option of downloading any files.
I picked up a TEW 632 brp. After opening the box I noticed it was marked as rev 1.3R. I should have taken note of the factory firmware but I believe it was newer then some of the other installs recommended. I attempted flashing with tew632brp-factory-to-ddwrt-firmware but this failed on multiple tries. I then flashed the firmware with TEW632BRPA1_FW110B19. This was successful. Next I flashed again with tew632brp-factory-to-ddwrt-firmware which was successful (DD-WRT v24-sp2 (08/07/10) std - build 14896 ). DD-WRT up and running with no problem. I setup the router and tried a bunch of settings but was only getting 65 mbs connection. After following the above settings I instantly connected at 150 mbs.
On a side note. I took my 'old' router - WRT54G2 V1 (DD-WRT v24-sp1 (07/28/0 micro - build 10015 ) and plugged that back into the TEW 632. I wanted to use it for wireless G connections and other throttled connections. This took some testing of different setting but now it's connecting without issue and any all devices that were connecting to this old router are still connecting without issue. I've got dd-wrt running on 192.168.1.2 on the wrt54G2.
Posted: Thu Oct 28, 2010 16:59 Post subject: VPN on Trendnet 652BRP/D-link 615
Hi. I have been using DD-WRT v24-sp2 (08/07/10) std - build 14896 on Trendnet TEW-652BRP for a while now. Haven't had any problems. But now I need to have VPN capability added to this router for remote access to my network. Is there any way to add VPN support or is there a VPN build for this router model?
I guess, my question is: can I use the generic VPN firmware with this router? The router database only lists files that seem specific to this hardware.
Joined: 22 Oct 2009 Posts: 157 Location: North East - USA
Posted: Sun Nov 28, 2010 15:29 Post subject:
I you mean TEW-652BRP, mine is v1.1 and works with DD-WRT. _________________ WNR3500L DD-WRT-18730-Kong Gateway/Firewall/NAS
WRT54G-TM DD-WRT-14929 Mega (heatsink + 250MHz oc)
WHR-G300N DD-WRT-20548(external antennas)
2x E2000 Tomato-Toastman 0501.2 AP (external antennas)
TEW-652BRP Gargoyle 1.5.9 Client Bridge (antenna upgrade + heatsinks + ventilation)
Joined: 22 Oct 2009 Posts: 157 Location: North East - USA
Posted: Fri Dec 03, 2010 23:56 Post subject:
Keith6110 wrote:
mrg666 wrote:
I you mean TEW-652BRP, mine is v1.1 and works with DD-WRT.
Really? I couldn't get mine to work with the 1.0v.
Can you post which version you used if you don't mind? Thanks
Since some of the later firmwares did not work for the initial flash, by try and error, I could use 14896 factory-to-ddwrt version for the first flash. Then, I upgraded to later versions using regular ddwrt builds for TEW-652BRP. Again by try and error, I am using 14929 right now; it works the best for me. _________________ WNR3500L DD-WRT-18730-Kong Gateway/Firewall/NAS
WRT54G-TM DD-WRT-14929 Mega (heatsink + 250MHz oc)
WHR-G300N DD-WRT-20548(external antennas)
2x E2000 Tomato-Toastman 0501.2 AP (external antennas)
TEW-652BRP Gargoyle 1.5.9 Client Bridge (antenna upgrade + heatsinks + ventilation)
Ok, here's how I got it working on a Trendnet TEW-632BRP:
I uploaded a custom zip file to simplify things. Get it from the following link and extract it before beginning: http://www.sendspace.com/file/a8o195
Note, these same steps should work for TEW-652BRP as well.
First, I modded my Trendnet into a "DLINK DIR-615 REV C" by using these steps. (Some of you may have already done this back when DDWRT wasn't available)
After I turned my Trendnet into a "DLink", I updated its firmware to version 3.10 using the "dir615_revC_firmware_310.bin" file via the web interface.
Then, I updated the "DLink" firmware with the "dir615-revC-fw310&up_-_factory_to_interim_dd-wrt_firmware.bin" file via the web interface and did a 30/30/30 reset.
Finally, I updated the firmware again with a corresponding real DDWRT firmware from the router database, either "tew632brp-firmware.bin" or "tew652brp-firmware.bin" for proper hardware identification by the firmware. These 2 files are already included with the zip file, but it's best to grab the latest version from the router database.
Enjoy
It does not work for me. I have TEW-652BRP rev 1.2, successfully upgraded to DIR615 3.01, but cant upgrade to 3.10. Upgrade fail!
All other methods like recovery mody, web update failed either...