Version 1.13.0 : Based on OpenWrt 19.07.8

[ispyisail]

Additionally, I will do a hard reset 30/30/30 to put it back in operation.

Does nothing.

There is however a OpenWRT reset procedure..............

[ispyisail]

Router reset (factory reset) to find your base speed

I have performed a factory reset and the problem has been solved.

Receiving full speed

Additionally, I will do a hard reset 30/30/30 to put it back in operation.

thanks for the support and advice

As you turn on features the router will slow down

[runner75]

Hi, any update?

[Lantis]

1.15 is in early testing

[wilsonhlacerda]

Hi all, long time don't see you. Just to report successful flash + BUG on 1.13 with TP-LINK TL-WDR4300 (maybe this affects also TL-WDR3600 and others, as they are similar):

WDR4300 was running Gargoyle v1.9.X just fine.
Loaded defaults. Rebooted.
Updated it to v1.12 NOT preserving settings on GUI.
Loaded defaults. Rebooted.
Updated it to v1.13 NOT preserving settings on GUI.
Loaded defaults. Rebooted.
Reseted using reset button. Power off. Power on.

All fine. And now the BUG:
Configured it initially as a very simple main router: DHCP, AP, wifi 2.4Ghz only.
No matter if setting 40Mhz or not, it always transmit in 20Mhz (shows 40Mhz on GUI but using an wifi analyzer I see in fact it is 20Mhz). The bandwidth setting is useless. After some reboots and tests Gargoyle offer me to choose "Global" or my country, alerting me that it will affect wifi.
Doesn't matter if I choose Global or my country, the 40Mhz never works.

Then I reseted it again and forced by command line (SSH) the wifi radio to run my country + no scan = 1.
Now bandwidth on GUI works perfectly: I set 40Mhz and router does transmit this way.

I have not tried Gargoyle v1.14 yet to see if this bug is fixed or not (I read a user's problem upgrading WDR4300 to it and as I was short on time I avoided it meanwhile).

[Lantis]

It’s not a bug.
The 40MHz width on 2.4GHz must first scan and ensure it will not cause interference before transmitting at this width. That is the standard.
Setting noscan intentionally violates this standard.

It’s not really advised, but do what you want.