Archer C7 (US) v2 locks up with Wireguard
Posted: Thu Jun 30, 2022 5:38 pm
Super THANKS for all the fantastic work on this product! I've been a fan since buying a 1043 from you years ago. Sorry if this issue is a dupe, but some of the forum pages time out when I try to check. Maybe corrupted?
I'm trying to build what I hope is a fairly typical setup for Wireguard, using the 1.13 GUI pages. See below if the target setup matters.
The problem I'm running into is that my router locks up completely when I get to the point of saving the configuration. Specifically, I'm starting with my first of two TP Link/Archer C7v2 devices. My steps are:
1. go to Connection/Wireguard, enable Wireguard config as Server
2. fill out Server Config with Generate Keys, change Internal IP and subnet, SAVE (all OK)
3. Add Allowed Clients, fill in Client Config(.conf) page with Client Name, Generate Keys, update Client Internal IP (gets auto-updated) and Subnet Behind Client data. (all OK)
4. Save Changes on Client Config page (LOCKS UP!)
By Locks Up, I mean that the router goes to spinning during the save but never completes. I went to dinner and came back (>1 hour) and it was still spinning. While spinnng, the router apperared on, with lights flickering normally, DHCP clients attached, but no connectivity. Attached devices could not access internet or each other and could not access the router by web, by ssh or even ping.
Multiple reboots did not change the router, it rebooted and provided DHCP addresses, appeared okay visually, but no connections to LAN or WAN by any means. I even tried booting it with WAN connected under a different router and it did not request a WAN IP on the other router's DHCP.
The only recovery I could get was a full 30-30-30 reset, which returned me to base 1.13 settings. Fortunately I do have a restore point to load in.
I've tried the process multiple times, sometimes with minor variations, but the Save Changes on the Add Peer/Client Config(.conf) page always locks me up.
Any ideas?
---------------------
Target Setup
Basic goal is for two (or more) Locations to be on the same subnet so that they can share access to each others' resources, but each have DHCP control over a limited IP range. In this example, Location A has 255 addresses under 172.16.4 and Location B has 255 under 172.16.5, but once joined by Wireguard they are all in one shared subnet. Potentially expand to Locations C and D.
Location A
(172.16.4.0/22)
>> Gargoyle A (Server)
(172.16.4.1 LAN/x.x.x.x DDNS WAN)
>> Modem A
----- Internet -----
<< Modem B
<< Gargoyle B (Client)
172.16.5.1 LAN y.y.y.y DDNS WAN)
Location B
(172.16.5.1/22)
I'm trying to build what I hope is a fairly typical setup for Wireguard, using the 1.13 GUI pages. See below if the target setup matters.
The problem I'm running into is that my router locks up completely when I get to the point of saving the configuration. Specifically, I'm starting with my first of two TP Link/Archer C7v2 devices. My steps are:
1. go to Connection/Wireguard, enable Wireguard config as Server
2. fill out Server Config with Generate Keys, change Internal IP and subnet, SAVE (all OK)
3. Add Allowed Clients, fill in Client Config(.conf) page with Client Name, Generate Keys, update Client Internal IP (gets auto-updated) and Subnet Behind Client data. (all OK)
4. Save Changes on Client Config page (LOCKS UP!)
By Locks Up, I mean that the router goes to spinning during the save but never completes. I went to dinner and came back (>1 hour) and it was still spinning. While spinnng, the router apperared on, with lights flickering normally, DHCP clients attached, but no connectivity. Attached devices could not access internet or each other and could not access the router by web, by ssh or even ping.
Multiple reboots did not change the router, it rebooted and provided DHCP addresses, appeared okay visually, but no connections to LAN or WAN by any means. I even tried booting it with WAN connected under a different router and it did not request a WAN IP on the other router's DHCP.
The only recovery I could get was a full 30-30-30 reset, which returned me to base 1.13 settings. Fortunately I do have a restore point to load in.
I've tried the process multiple times, sometimes with minor variations, but the Save Changes on the Add Peer/Client Config(.conf) page always locks me up.
Any ideas?
---------------------
Target Setup
Basic goal is for two (or more) Locations to be on the same subnet so that they can share access to each others' resources, but each have DHCP control over a limited IP range. In this example, Location A has 255 addresses under 172.16.4 and Location B has 255 under 172.16.5, but once joined by Wireguard they are all in one shared subnet. Potentially expand to Locations C and D.
Location A
(172.16.4.0/22)
>> Gargoyle A (Server)
(172.16.4.1 LAN/x.x.x.x DDNS WAN)
>> Modem A
----- Internet -----
<< Modem B
<< Gargoyle B (Client)
172.16.5.1 LAN y.y.y.y DDNS WAN)
Location B
(172.16.5.1/22)