Gargoyle Forum

Long reply, but hope it is helpful... Ok, thanks for the responses. And I understand the time lag, absolutely no worries. Your efforts are super and very much appreciated. I've done my best to document the process with specifics in the hope that it may help you and others. 1. When you say, "In ...

Does anyone else report having Wireguard working in both directions on Gargoyle, i.e., with devices in the Server LAN able to access devices behind the subnet of the Client LAN?

Wondering if it's me or if a broader issue.

Lol...says you. I'm on Fedora 38 right now. They have a problem with the latest glibc library and openvpn. There are some workarounds for it that I may try, but right now openvpn doesn't work. Pretty sure it is not related to Gargoyle, though. I think your updates in 1.14 handle any problems it had,...

I shared screen shots via private message

Text posted again below. Posting with screenshots (.png) failed with error: Error Sorry, the board attachment quota has been reached. --- *********Client********** WAN: dhcp from ISP LAN: 172.16.24.1/22 cat /etc/config/wireguard_gargoyle config server 'server' option enabled '0' option ip '10.64.0.1...

Any news on this? I'm having the same issue. I have two TP-Link Archer C7 v5 routers, both with 1.14.0 I also have tried with two C7 v2 routers. Client to Server works great. Server back to client (with client defined as having a subnet) does not work. Traceroute from server to client shows no hops ...

More info: I can't get back in with a Failsafe boot. Your comment that it is some routing issue seemed right, so I tried a new approach, access the router by its IPv6 address. It worked! Now I can see any of the settings in the GUI. I still can't access by SSH or Telnet, though, in part because I do...

Finally back to trying this Wireguard on V13.0. Now have screen shots, too. 1. Today I unbricked my Archer C7 v5 by doing a TFTP recovery to TP-Link firmware. 2. Then I loaded a factory version of Gargoyle v13.0 3. I set a few of my network configs (not many, as I expect to be need resets anyway) a)...

Update: I still had 192.168.0.1 network in the Peer subnet settings before. 10.64.0.1 for the Wireguard address, but 192 for the subnet behind it. I modified the subnet behind to 172.16.5.1 and saved...LOCK UP. And now I'm having trouble recovering the C7 v5. Recovery complete, but back to square on...

Update: tried same on an Archer C7 v5. Worked fine. Now need to figure if the difference is because v2 vs. v5 or if the specific v2 has some problem.