Recent content by dacid44

Odd, that doesn't seem to be working. The only logs are: Aug 24 16:46:04 rc_service: service 19928:notify_rc start_wgc1 Aug 24 16:46:04 custom_script: Running /jffs/scripts/service-event (args: start wgc1)

I meant more in terms of documentation. Many blog posts/wiki articles/etc walking through how to set up wireguard (using something like wg-quick, with conf files) use "client" vs "server". Either way, it's set up now, and I know that the firmware treats them differently. It returns 1. I did...

The only difference I see here is that for some reason it's added a route to the VPS' endpoint address explicitly through the default gateway. e.g. <wg endpoint ip> via 192.168.4.1 dev eth0. I'd guess that's just to ensure that even if the wireguard tunnel is the default gateway, that the...

So the firmware has its own definition of server or client? Huh. By server or client I'd just meant which end of the wireguard tunnel listens, and which one connects (e.g., server listens for incoming connections, client has an endpoint specified and connects to a listening server) as that's...

I SOLVED IT! 🥳 I was looking through ip a and ip route, and realized that the problem was in the default subnet of the wireguard interface. In DD-WRT, this was my configuration: The interface IP address is set to 192.168.5.2, and it explicitly asks for a subnet. In ASUSwrt-Merlin, however...

I seem to be misunderstanding what VPNDirector is doing then. I had assumed that it specifies what outbound requests from the LAN get routed through the tunnel instead of the WAN. How would I configure it to allow inbound requests? Or did you just mean that if the router can't send packets back...

This might just be an iptables thing, but I can't figure it out. Short version: I'm trying to forward packets from a VPS to the router over wireguard (router is client) and forward them to the correct device on the LAN. I have a setup that I'm trying to carry over from my old DD-WRT router...