Am 2021-01-23 17:52, schrieb Ken D'Ambrosio:
The client connects just fine, and it can talk to the server's VPN IP
(192.168.50.1) as well as its internal interface (192.168.10.1).
Likewise, the server can talk to 192.168.50.11. But nothing gets
inside to other 192.168.10.x hosts. I do have
On Sat, 23 Jan 2021 11:52:56 -0500
Ken D'Ambrosio wrote:
> Hey, all. I'm relatively new to WireGuard, and have a RasPi at my house
> doing firewall duty. Installed WG on it, and on a VPS, and am trying to
> get the VPS to access hosts on my home subnet. So:
>
> VPS <-192.168.50.0/24->
Hey, all. I'm relatively new to WireGuard, and have a RasPi at my house
doing firewall duty. Installed WG on it, and on a VPS, and am trying to
get the VPS to access hosts on my home subnet. So:
VPS <-192.168.50.0/24-> RasPi <--> [192.168.10.0/24]
And, clearly, I'm doing something wrong.
---
src/wg-quick/darwin.bash | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/wg-quick/darwin.bash b/src/wg-quick/darwin.bash
index cde1b54..9c92f87 100755
--- a/src/wg-quick/darwin.bash
+++ b/src/wg-quick/darwin.bash
@@ -449,7 +449,7 @@ cmd_usage() {
cmd_up() {
Hello!
I've been using wg-quick on macOS 10.14, with wireguard-tools at 1.0.20200827.
I had one issue prompt investigation, DNS changes persisted after an interface
failed to come up. I found a second, related issue, and added an extra error
handling case in the wg-quick/darwin.bash script to
---
src/wg-quick/darwin.bash | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/wg-quick/darwin.bash b/src/wg-quick/darwin.bash
index 9c92f87..e9bdfea 100755
--- a/src/wg-quick/darwin.bash
+++ b/src/wg-quick/darwin.bash
@@ -296,7 +296,7 @@ set_dns() {
local
Hi
Thanks, maybe the powers-that-be would consider your change to be a fix
and accept it into the next release? I guess by removing the default
route I am causing the bind to fail as it doesn't know which interface
to bind to which has the same result as removing the bind. The bit of
code
I am working on a project where I create Wireguard tunnels on demand
and tear down the tunnel whenever it is not needed anymore. I have
been using the tunnel.dll and start/stop the tunnel service from
another windows service. Almost always the service doesn’t start in
one try. So I have to keep
Hi
I built Wireguard with the change you made below and confirm it fixes
the longstanding problem I had - I can now connect to a peer over the
PulseSecure tunnel and even simultaneously connect to another peer over
the default route (with the MultipleSimultaneousTunnels=1 registry entry).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
A new version, v1.0.20210124, of the backported WireGuard kernel module for
3.10 <= Linux <= 5.5.y has been tagged in the git repository.
== Changes ==
* compat: SYM_FUNC_* was backported to c8s
* compat: skb_mark_not_on_list was
10 matches
Mail list logo
