dionhouston
New Around Here
Hello everyone,
Environment: ASUS RT-AX88U, current firmware (388.9_2)
First kudos on the people that fixed the old WireGuard clashes with NAT Acceleration. I'm glad that's history. I use WireGuard between my Mom's network, and my home network, and previously was using separate devices for that purpose due to the bug.
Question: I think everyone knows that there is no difference between a WireGuard server and a client, as they are all peers. Under my former set up, I set endpoints at both locations, so they are mutually reachable. With a WireGuard "server" I can get the listen port, but then the router wants to control the keys. As a "client" I can connect to my server, which is cool, but there's no way to set the listen port - it appears to be random.
I tried adding NVRAM variables wgc_port and wgc1_port -- neither did anything.
Is this possible to make happen? I know I can go the reverse direction (by making keys), but I'd like my router to be primary on Wireguard connections.
Thanks!
Environment: ASUS RT-AX88U, current firmware (388.9_2)
First kudos on the people that fixed the old WireGuard clashes with NAT Acceleration. I'm glad that's history. I use WireGuard between my Mom's network, and my home network, and previously was using separate devices for that purpose due to the bug.
Question: I think everyone knows that there is no difference between a WireGuard server and a client, as they are all peers. Under my former set up, I set endpoints at both locations, so they are mutually reachable. With a WireGuard "server" I can get the listen port, but then the router wants to control the keys. As a "client" I can connect to my server, which is cool, but there's no way to set the listen port - it appears to be random.
I tried adding NVRAM variables wgc_port and wgc1_port -- neither did anything.
Is this possible to make happen? I know I can go the reverse direction (by making keys), but I'd like my router to be primary on Wireguard connections.
Thanks!
Last edited:
