Gargoyle Forum

On a wireless bridge with Gargoyle Routers on both ends, I can reach the client router (192.168.0.176) from the host side, and the client router can reach a wired client connected to its LAN port (192.168.0.8), but trying to ping that client from the host side results in "Destination Port Unrea...

Problem solved, but took me some time. I tried a sysupgrade -v -n -F /tmp/random_path_to_USB_drive/gargoyle-1.15.X_xxx.bin first. This did install, but resulted in a router that was unresponsive and never reached a working state. SYS LED kept flashing, no connection possible, eventually the SYS LED ...

I'm having the same kind of problem trying to upgrade my old TL-WR1043ND V1.1 from 1.12.x to 1.13 or 1.15. It runs out of memory and the update fails. Which processes may be killed/disabled to temporarily save RAM? The router has local storage on USB, currently used only for plugin-root. Would it be...

Okay, one walk and one hour later, I was successful in creating new keys on both routers (both GCM-256 only). The only thing I did differently: restart the browser, delete cookies. Seems there really is some JavaScript caching or whatnot in the running session messing up the creation, as simply relo...

Even after stopping the server and clearing all keys, the list with the configured clients remains populated. On the test router with the server running, the IP displayed for Client1 was 10.0.8.3, but when editing it's settings it is shown as Client2 and 10.0.8.2 (server is default 10.0.8.1). Trying...

I don't know what's happening here, but was able to reproduce the error with both CBC-256 and GCM-256 ticked. Stop Server, delete keys and try again with CBC-256 alone: Success. Stop server again, delete keys, tick both, save: errors out. There's no way to clear the cache, and I didn't change the lo...

If the IP range in use is not 192.168.1.0/24, updating Gargoyle devices without keeping the settings is quite troublesome. In every case, I've got to gain physical access to the device in question, involving a hike across the property and climbing ladders. Proposal: Keep the IP assignment for the LA...

Performed yet another try, this time with "AES-CBC 256bit" unticked and only "AES-GCM 256bit" active. Seems to have worked this time, after only 57 seconds I got a running and connected OpenVPN Server. Seems like the "CBC" config is troublesome. Fri Apr 7 09:34:05 2023 ...

Next try, same outcome. At around 09:10, Delete keys, setup server and one client, 35s for the "busy" spinner to close, logfile as follows: Fri Apr 7 09:05:13 2023 daemon.notice netifd: wwan (9441): udhcpc: received SIGTERM Fri Apr 7 09:05:13 2023 daemon.notice netifd: wwan (9441): udhcpc:...

Something is proper broken there, you’ve got not config files or certificates. Disable, click clear certificates. Start from scratch. Set it up with at least 1 client. Let it finish. That is what I did prior to this last try. There may be a race condition on the network restarting which is causing ...