Posted: Fri Apr 28, 2017 16:12 Post subject: Re: success
didge wrote:
Just wanted to report that i was able to successfully install the latest dd-wrt 04-24-2017-r31899 firmware on a TP-Link AC1900 archer c9 v1 that I had previously updated to TP Link's latest firmware (4.1.0 Build 20160517 Rel. 35411).
A few things worth mentioning:
- the new wireless network is "ddwrt" and router interface is accessible at http://192.168.1.1 (archer c9 previously used 192.168.0.1 as default).
- the router's wired connection/lan ports didn't work initially. Had to go to uncheck: Setup > DNSMasq for DNS checkbox.
Posted: Sun Apr 30, 2017 1:41 Post subject: Re: success
Elwin92 wrote:
didge wrote:
Just wanted to report that i was able to successfully install the latest dd-wrt 04-24-2017-r31899 firmware on a TP-Link AC1900 archer c9 v1 that I had previously updated to TP Link's latest firmware (4.1.0 Build 20160517 Rel. 35411).
A few things worth mentioning:
- the new wireless network is "ddwrt" and router interface is accessible at http://192.168.1.1 (archer c9 previously used 192.168.0.1 as default).
- the router's wired connection/lan ports didn't work initially. Had to go to uncheck: Setup > DNSMasq for DNS checkbox.
Thanks dd-wrt team!
Have you been able to get VPN working properly?
I previously experienced issues with setting up VPN client on earlier betas from March. I have just installed 31899 and the VPN connects fine. I was on 30880(?) from November 2016 previously but have now updated. I will report here if I run into any problems
EDIT:
Did a reboot this morning and OpenVPN Client wouldn't initiate. Additionally, I couldn't get SSH access even after enabling it on GUI. I have flashed back to stock for the time being. Really just want this router to do OpenVPN client and NAS reliably.
I apologize in advance if this has been covered but frankly after reading all these pages and posts about the C9 and C1900 I'm still confused.
I have a new TP-Link AC1900 High-Power Black unit I just purchased here in Canada. I was going to update the firmware. The TP-Link site has big warningsNOT to flash the US firmware if I'm outside the US. (duh)
Now, if I have this "new" model purchased outside the US of A, with "un-american" firmware, I'm hoping that I can, even though I live outside the "land of the free" flash dd-wrt on it.
Am I correct in this assumption ?
I see a listing for tp_archer-c1900 in the beta directory. There is firmware listed there, minty fresh as of today 5/2 that says "factory-to-dwrt.bin" ... I'm tempted to use this to flash my new AC1900. Can someone who owns an AC1900 or recently flashed this verify it will work ? (Flashing from stock)
Is there a beta build for the AC1900 that's considered the better/best available ...
Posted: Thu May 04, 2017 2:02 Post subject: OpenVPN hell
Hello all,
Like many of you I'm trying to get the OpenVPN client working correctly and consistently. Like many of you I'm failing.
I'm on 31825. Had no issues flashing it.
After a solid day of configuration I was able to get the OpenVPN client working. It wasn't connecting on startup because it wasn't able to resolve the VPN hostname (despite having correct DNS settings). I had to go to the VPN tab after startup and hit "apply settings". I assume this is because something in the startup process is out of order. Anyway the connection lasted for a week without issue so I thought that was fine.
But now it's dropping every hour or so, and then not reconnecting. Keep Alive isn't keeping anything alive. When it drops the VPN tab will just read "Client: WAIT". This is totally unusable.
Has anyone tried two newer (> 31825) builds and got stable VPN behavior? Alternately, is there a build # that anyone out there gets stable VPN behavior with? This is really the only feature I care about.
Posted: Sat May 06, 2017 7:38 Post subject: Re: OpenVPN hell
mfan wrote:
But now it's dropping every hour or so, and then not reconnecting. Keep Alive isn't keeping anything alive. When it drops the VPN tab will just read "Client: WAIT". This is totally unusable.
Has anyone tried two newer (> 31825) builds and got stable VPN behavior? Alternately, is there a build # that anyone out there gets stable VPN behavior with? This is really the only feature I care about.
Or is it time to just buy a different router?
I have two Archer C9 v1s, and both are running 30880. I figure I'll stick with that until other folks report there's no quirkiness to later builds.
One of the Archer C9s is my primary router (router #1) that most things, including my NAS, are plugged into.
The second Archer C9 (router #2) is functioning as a repeater of router #1, but also has the OpenVPN client running on it.
Stable and smooth for me so far, but I've learned the hard way not to get impatient and skip 30-30-30 before flash, and 30-30-30 after flash.
I was pondering a way to have the router restart automatically when the VPN dropped in another thread:
Because I had a similar experience regarding the watchdog being no help. However, hubermania's comment makes a lot of sense. Even with a killswitch, the router can still ping normally if you're using, let's say, 8.8.8.8 (Google DNS).
They suggested using an *internal* IP from your VPN instead for the watchdog. Like what you see on the Status->OpenVPN logs when you're connected successfully. If your VPN goes down, it won't be able to ping the internal IP the same way it can Google DNS, or OpenDNS, or... you get the picture.
I haven't tried that method yet, because the convoluted scripts I cobbled together are working for now, and I'm kind of from the "if it ain't broke" school of thought. But it makes a lot of sense.
Anyhoo, with both routers on 30880 and OpenVPN client running on router #2, it's stable and successfully restarting when the VPN goes down. Just my personal experience.
Last edited by cecoates on Sat May 06, 2017 17:36; edited 1 time in total
And I straight up glued them to the back of each router. It keeps them both around CPU 50.0 °C / WL0 40.0 °C, give or take a few degrees. But it's also a cooler time of year. During hotter months it seems closer to CPU 60.0 and WL0 50.0 °C.
Maybe that would help with stability? I don't overclock or anything, and the routers are on shelves/tables, so they're not locked in a cabinet without airflow.
I have been unable to flash my new black AC1900 "high-power" V1 hardware to dd-wrt. It is a CA (Canadian). The back of the unit states V1 hardware, as does the firmware update page. It's presently running tp-links 20160201-rel42677.
I reset the router to factory defaults and flashed the using the factory-to-ddwrt.bin
I first tried flashing r30880 (11-14-2016) since this had a lot of positive feedback. Got error -5533
I then tried r29409 (4/5/2016) also got error -5533
I then decided to try a build f31899 4/24/2017 as well as the most recent build.
In all cases the firmware uploads fine and immediately gets error code -5533
I read about TP locking the firmware but everything recent states that this was only done for a short time and that they now allow users to flash dd-wrt. They even mention dd-wrt on their firmware update page.
So, not sure what I'm doing wrong here. I'm using the beta versions for tp-link ac19000 and uploading the factory-to-ddwrt.bin file.
Posted: Tue May 09, 2017 22:40 Post subject: Works so far with 20161008 firmware
I successfully flashed the 30880 release to my US C9v1 with stock 20161008 firmware. I softbricked it using the 20160517 firmware, and had to use tftpd to push the recovery bin.
I'll update later with how it goes after configuring it. Currently posting this through the C9 on DD-WRT
Posted: Tue May 09, 2017 23:15 Post subject: Re: Works so far with 20161008 firmware
voilsb wrote:
I successfully flashed the 30880 release to my US C9v1 with stock 20161008 firmware. I softbricked it using the 20160517 firmware, and had to use tftpd to push the recovery bin.
I'll update later with how it goes after configuring it. Currently posting this through the C9 on DD-WRT
I had no luck with r30880, error -5533. I suppose I could try and downgrade my tp-link firmware to flash but I only can find the "latest".
Did you just reset to defaults and flash the factory-to-ddwrt.bin ?
Posted: Tue May 09, 2017 23:38 Post subject: Re: Works so far with 20161008 firmware
For some reason this won't display with BBCode enabled ...
[quote="tbalon"]
I had no luck with r30880, error -5533. I suppose I could try and downgrade my tp-link firmware to flash but I only can find the "latest".
Did you just reset to defaults and flash the factory-to-ddwrt.bin ?[/quote]
Are you using a US v1 router? If so, I found the firmware here: [url]http://www.tp-link.com/us/download/Archer-C9_V1.html#Firmware[/url] and downloaded this version: [url]http://static.tp-link.com/Archer_C9(US)_V1_161008_1478653422432k.zip[/url]
As for the error -5533, did you see that in the TP-link GUI when flashing, or did you get it somewhere else? I never got an error message flashing, but I did end up with the all-led-flashing-slow and had to restore it by renaming the original TP-Link firmware (the 20160517) to archerc9v1_tp_recovery.bin, per the instructions here: [url]https://www.dd-wrt.com/wiki/index.php/TP_Link_Archer_C9[/url]
Something I might suggest trying, is using the exact firmwares on the wiki page. So TP-Link 160517, factory-to-ddwrt release 04-05-2016-r29409, and DD-WRT v3.0-r30385 std (08/12/16).
What I find interesting, is that after I softbricked my router, when I went to check available firmware the 20160517 version was no longer available for me to download. I may have accidentally grabbed a firmware not for US routers.
Some other quirks, the first time I did 30/30/30 after flashing the TPLink firmware, then after flashing the first DDWRT. Then I had a dead router.
The second time, I did 30/30/30 after I restored the TPLink firmware, flashed DDWRT from TPlink, then finished the 2nd flash thru DDWRT, *THEN* I did the second 30/30/30. That may be significant; I don't know.
Finally, I'm posting this on VPN while connected thru the router's OpenVPN client.
I'm using the beta specifically for the C1900. My router hardware is marked CA not US on the back panel. This is a C1900 High Power model. Which from what I can gather is a C9 with 800 mw output.
I followed the steps outlined in this forum and reset my AC1900 to factory defaults. I used the factor-to-ddwrt.bin as detailed.
The error code: -5533 is displayed on the web page immediately after the firmware uploads. I can see it loading in the display, when it gets to 100%, it stops and displays the error.
Posted: Thu May 11, 2017 22:34 Post subject: Archer C9 USB3 quirk?
apologies if this has been discussed before, but I haven't been able to find anything relevant.
experiencing a weird quirk here. I've just installed dd-wrt on v1 C9, and it's mostly working as expected. however, my external USB3 drive that used to work fine under stock firmware no longer mounted. the drive itself is fine, verified by mounting it on another system.
now here comes the juicy part: I have usb2 and usb3 drives plugged into both USB2 and USB3 ports, respectively. if I swap them, they both mount just fine! granted, in this case they both work in usb2 mode, but this confirms that the USB3 port itself is operational — it's just refusing to recognize anything USB3 in there (I tried with a couple other USB3 drives, none of them mounted). I went through a couple of recent firmware versions, same effect observed; currently on build 31924.
TL;DR — USB3 port only mounts non-USB3 devices
anyone has observed it, fixed it, has any ideas on how to further diagnose or fix it?
Great success, upgrading to v3.0-r31722 std (03/21/17)
of an Archer C9 V1 from previous version r30880 11/14/16
which only problem was losing settings after restart but stable over all.
Will be checking upon 31722 the next few days and give my feedback if I came across of any issue with this version.
Screenshot_1.png
Description:
Filesize:
4.04 KB
Viewed:
28936 Time(s)
_________________ Oh, so they have internet on computers now!
