1.6.0 or 1.6.1 working on TP-Link 4300?

[pmerrill]

Does anyone have Gargoyle 1.6.0 or 1.6.1 working properly on a TP-Link 4300 v1?

I had terrible trouble where the router would go into a mode where no one could connect to the internet. I did many reboots with no luck. I finally went back to stock to solve the problem but stock suffers from poor functionality. However, I don't want to go back to Gargoyle unless I can find at least one person with 1.6.0 or 1.6.1 working well.

[Trigger Happy]

I have few problems (VPN, wireless). I wil try to downgrade ...

[spwalmsley]

I have a TP-Link 4300 h/w version 1.6 with the following Gargoyle version history:

1.5.11: installed for ~6 months; 2.4Ghz range issue otherwise ok
1.6.0 with OpenWRT upgrade: Ispyisail build, installed for ~1 month, no issues (fixed 2.4Ghz range issue as per OpenWRT changelog)
1.6.1: installed for ~1 hour, seems to be working ok so far including 2.4Ghz range issue

I only use the basic firewall+router+quota functionality, no VPN or other features, so your mileage may vary if you rely on these.

I used the "factory" image to upgrade from the stock firmware to 1.5.11, then the "sysupgrade" image for subsequent upgrades.

[rsbrux]

I used the "factory" image to upgrade from the stock firmware to 1.5.11, then the "sysupgrade" image for subsequent upgrades.

I plan to sysupgrade my TL-WDR4300 (v1.3) from 1.5.10 to 1.6.1.
Did you backup your 1.5.11 settings and restore them under 1.6.1, or did you configure everything freshly?

[spwalmsley]

I upgraded in two steps, i.e. 1.5.11 -> 1.6.0 -> 1.6.1, but in both cases I preserved the current configuration using the checkbox on the upgrade page.

I also made a copy of my configuration prior to upgrading just to be safe.

[rsbrux]

Well I gathered up my courage and upgraded directly from 1.5.10 to 1.6.1. with "attempt to preserve settings". I had a little trouble with a shared USB drive, which gave me "error: illegal address" when I tried to edit its configuration. Apparently 1.6.1 expected to find a vaiid network address for NFS access, even with NFS disabled or configured for anonymous access. After removing the share, recreating it with NFS access by subnet and specifying my LAN subnet, everything seems to work fine!