[PATCH v2] wg-quick: openbsd: fix alternate routing table syntax

route(8) has always used the `-T` option to specify the routing table; there is no `rdomain` option. Signed-off-by: Ankur Kothari --- src/tools/wg-quick/openbsd.bash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/tools/wg-quick/openbsd.bash b/src/tools/wg-quick/openbsd.b

Re: Wireguard command line tools for Android

I assume you have set the client configs to connect to something like " vpn.example.com:" . How does DNS resolve this when inside your local LAN? Does it resolve to the same public IP address that your DSL router is connected to, or does it resolve to an internal address like 192.168.1.1? The way

Re: [PATCH] wg-quick: Fix alternate routing table syntax on OpenBSD

Hi Janne, Thanks. I wonder how I came up with the rdomain syntax in the first place. Perhaps out of ifconfig.c incorrectly. Jason ___ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: [PATCH] wg-quick: Fix alternate routing table syntax on OpenBSD

According to "man route" on openbsd, the -T is how its supposed to be run: The other commands relating to adding, changing, or deleting routes have the syntax: *route* [*-dnqtv*] [*-T* rtable] *add* [modifiers] destination gateway The manpage for "route" doesn't even contain "

Wireguard command line tools for Android

Hey all, I've recently set up my private VPN with Wireguard. I am running my local server behind a DSL router with a variable public IP address, accessible via dyndns and NAT, and several mobile clients (Android, Notebooks). Everything is working fine so far, except of one issue that I would li

After I start the Wireguard service, VMs from same network are not reachable via local IP

Hi Guys, I have a very strange issue, and I do not understand why is working like this.. I have 3 ( A,B ) VMs, 2 in the same network and 1( C ) outside of this network. A: Just a VM in the same network with B, not able to ping VM B when Wireguard is UP on B.. 3: ens19

Re: [PATCH] wg-quick: Fix alternate routing table syntax on OpenBSD

Hi Ankur, Thanks for this. Could you provide your Signed-off-by line? Also, why is this required? Is this a recent change in syntax? A new syntax? Was the syntax always wrong? What's the deal? Thanks, Jason ___ WireGuard mailing list WireGuard@lists.zx2

Re: Wireguard in OpenVZ with NETIF_F_VIRTUAL feature

Hi Jason, thanks very much for your input. Yes I also realized that the NETIF_F_VIRTUAL is a Virtuozzo specific thing and almost lost hope with this. However with your patch applied I get a failure at dkms build and lots of warnings in the log that NETIF_F_LLTX is redefined. I'm not familiar with

[PATCH] wg-quick: Fix alternate routing table syntax on OpenBSD

--- src/tools/wg-quick/openbsd.bash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/tools/wg-quick/openbsd.bash b/src/tools/wg-quick/openbsd.bash index b234609..2cadeec 100755 --- a/src/tools/wg-quick/openbsd.bash +++ b/src/tools/wg-quick/openbsd.bash @@ -293,7 +293,7 @@ ad

Re: Wireguard in OpenVZ with NETIF_F_VIRTUAL feature

Works like a charm! I can compile without any problems and I get 2Gbits/s out of the box between to containers on different hosts. Thanks a lot! Beni Am 19.07.19 um 17:25 schrieb Jason A. Donenfeld: > How's this look? > https://git.zx2c4.com/WireGuard/commit/?id=08f1bfe29a08d9f10f9fa4c47e07a3501a

Windows tunnel shows established but traffic sometimes does not move after recycling tunnel

Hi! I submit a report on a problem encountered attempting to use WireGuard in a Windows-to-Windows "VPN gateway/proxy" deployment. I have a test deployment available in case I can provide further data for ease of debugging. Scenario: * Server A set up as WireGuard server, accepting connections

Windows 10 Traffic Dump on Wireguard Interface

Hi, I am an early adopter of Wireguard and trying out various network configurations. I have issues passing certain types of traffic from a MacOS Wireguard client to a Windows 10 Wireguard server (master). To troubleshoot this I normally do a network traffic dump on each side, among other thi