Gargoyle Forum

silentjoshua wrote:I created an account just to confirm that this does indeed work. I had the exact same model number and did all the research. I'm glad someone was able to take the plunge to give me some confidence to try this with (what is to me) an expensive router I can't afford to replace!

I used version 1.9.2 archer c7 v2 to install.

It was a seamless installation other than below..

One word of advice is that you will need to disable any pop up blockers or other extensions on your browser to upload the firmware effectively.

So far no hitches. I'll report if there are any.

I have a C7 V2 as well. Current stock firmware version 3.13.34 Build 131217 Rel. 60903n.

I was planning on flashing 1.9.2 as well but wanted to check with you to make sure all is still well before doing so? Any problems or things to be aware of?

Thanks

I have been running 1.9.2 on my v2 without any issue, it's been up for 24 days now.

Upgraded to 1.11.0 today. As advised did not keep preferences. It took about a couple hours to get everything set properly but seems to be working fine now.

There was a bit in the middle where DNS lookups from clients were failing. `nslookup somedomain.ca` from Windows failed with "connection refused". I couldn't find any setting within Gargoyle GUI that might have caused that. Changing DNS servers under "Connection >> DHCP" had no effect. After a couple of reboots the problem went away.

Image used: gargoyle_1.11.0-ar71xx-generic-archer-c7-v2-squashfs-sysupgrade.bin

Upgraded to 1.13 interim release today. Did not preserve settings.

Image used: gargoyle_1.13.x-ath79-generic-tplink_archer-c7-v2-squashfs-sysupgrade.bin, courtesy of @RomanHK web mirror of @ispyitail's torrent build.

(ref viewtopic.php?f=14&t=12588&p=57532#p57532)

This firmware update prompted by several weeks of on-again off-again flakey behaviour that did not seem to be cured by reboots or cycling power.

@maphew

what about 1.12.x

DNS problems?
1. Disable the option to use OpenNIC DNS servers:


2. You can enter your own DNS servers for which you know the correct validation of domains (Google, Cloudfare, CZ.NIC, ...). I use CZ.NIC servers:


3. Have you tried updating client network card drivers?

You must wait for the DNS cache (TTL) to clear for the changes to take effect!

It should also be noted that DNS uses a cache as well as a negative cache, so this can be fixed by simply restarting the router.
In the extreme case, it can also be a faulty DNSSEC signature key - but this is an exceptional condition.

If you have free space in the router (like me, I use this option), you can run your own DNS validating server with DNSSEC + TLS support with an encrypted bridge, eg UNBOUND.

ispyisail wrote: ↑

Fri Oct 30, 2020 3:57 am

@maphew

what about 1.12.x

Umm, sorry but I don't understand the question. Do you mean did I try 1.12.x? No, I went from 1.11 to 1.13.

maphew wrote: ↑

Sun Nov 08, 2020 7:42 pm

ispyisail wrote: ↑

Fri Oct 30, 2020 3:57 am

@maphew

what about 1.12.x

Umm, sorry but I don't understand the question. Do you mean did I try 1.12.x? No, I went from 1.11 to 1.13.

Even numbers are more stable than odd

1.12. is more stable than 1.11 and 1.13 in theory