Posted: Thu Jan 26, 2017 4:38 Post subject: TP-Link Archer C8 V1 - Easy install using 2016 r30949
Just an FYI.
I have an TP-Link Archer C8 V1 purchase February 2016. Its TP-Link firmware level was loaded with Archer C8_V1_150515.
I download the latest beta from the dd-wrt site,
12-15-2016-r30949 › tplink_archer-c8v1.
Via the Archer GUI I "reset to factory defaults".
NOTE: DO NOT 30-30-30 Broadcom ARM per the following
Code:
I then followed the "Peacock" process 30-30-30 to "really reset the unit".
Went into the Archer GUI, uploaded/updated with the factory-to-ddwrt.bin beta.
NOTE: ALWAYS wait at least 5 minutes after initial flash file has uploaded.
Code:
Waited 45 seconds while the firmware "burned in".
NOTE: DO NOT 30-30-30 Broadcom ARM per the following
Code:
Then performed the Peacock 30-30-30 reset again.
I've been online since.
No really speed improvement to the internet. I get about 135 Mb/s download speeds from ookla. About 5.8 Mb/s upload. Same as the Archer firmware I was using.
Did play around with a 16 GB NTFS/USB3 stick. Internally from the CLI I am seeing 50 MB/s with a cat to /dev/null (date ; cat /tmp/mnt/sda1/645 MB file > /dev/null ; date). Going thru a CIFS mount to a laptop/SSD drive, 300 Mb/s WiFi, the most I see is 12 MB/s.
Go figure.
Anyway, "it all seems to work". Thanks to the dd-wrt team for a little bit of fun.
I even got the ssh public key to putty/puttygen private key working. It let's me turn off the http/https support in the GUI and go to the cli to turn up the http listener when needed. Still working on getting http server to use "my" cert keys. I haven't found an easy to create free/permanent certs.
Using firefox socks v5 proxy support was another "fun" adventure.
Again, it all seems to "work as designed".
javascript:emoticon('')
Mod edit: Annotated dubious practices in this post as they are known to cause issues. You do NOT 30-30-30 Broadcom ARM devices and you DO wait at least 5 minutes for initial flash and upgrades to finish. -kp69
There's no point in opening thread just for this. Just another feedback that should have been put under 30949 new build thread. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
So what still is important after reading is the question of reverting to stock. Is this finally possible? What about the hardware drivers GBit connection. Are we still limited to some ~400MBit/s software driver or is the latest release capable of using the full bandwith via a cabled connection?
So what still is important after reading is the question of reverting to stock. Is this finally possible? What about the hardware drivers GBit connection. Are we still limited to some ~400MBit/s software driver or is the latest release capable of using the full bandwith via a cabled connection?
Thanks for you feedback so far!
It's not possible to revert, only C9.
The limitation you say is about NAT being done by CPU not hardware accelerated. That won't change in a near future since it was like that for years. If your ISP allows it use IPv6 instead, or use a spare router between your tplink and the modem running on stock firmware. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
')
