Not sure if this is the right place to request this, if you're interested in adding it, or if its even possible
I have dual WAN, one is AT&T Fiber 1G/1G and the other is Verizon 5G with a limited amount of upload bandwidth, just 30Mb/s at max usually.
I have 2 Wireguard tunnels. One is to my VPS which I want to be up no matter what, but the other is to Mullvad, and torrent traffic goes across it. If I fail over to my secondary WAN, I really don't want a torrent to start seeding and use 100% of the upstream bandwidth and cause interruptions with normal traffic
I've looked around, and I don't see an easy way to force this tunnel to only go out through the main gateway. I could make a static route, but the IP on the other end sometimes changes, and I can't put a hostname into the static routes page
Is there a way with this tool that it could be possible to add a flag to the peer name so it stays on a single interface and does not failover? perhaps tunnel@WAN_DHCP and then wgfix could see the @WAN_DHCP and know to not let it go away from WAN_DHCP
Just a thought, I know some other people would like that functionality too
Not sure if this is the right place to request this, if you're interested in adding it, or if its even possible
I have dual WAN, one is AT&T Fiber 1G/1G and the other is Verizon 5G with a limited amount of upload bandwidth, just 30Mb/s at max usually.
I have 2 Wireguard tunnels. One is to my VPS which I want to be up no matter what, but the other is to Mullvad, and torrent traffic goes across it. If I fail over to my secondary WAN, I really don't want a torrent to start seeding and use 100% of the upstream bandwidth and cause interruptions with normal traffic
I've looked around, and I don't see an easy way to force this tunnel to only go out through the main gateway. I could make a static route, but the IP on the other end sometimes changes, and I can't put a hostname into the static routes page
Is there a way with this tool that it could be possible to add a flag to the peer name so it stays on a single interface and does not failover? perhaps tunnel@WAN_DHCP and then wgfix could see the @WAN_DHCP and know to not let it go away from WAN_DHCP
Just a thought, I know some other people would like that functionality too