On 5/3/18 7:15 PM, Jason A. Donenfeld wrote:
ip route add 192.168.100.0/24 dev wg0
Thank you everyone, that was it. Once I added an explicit route for the
remote IP block on each server it ALL worked (and latency is pretty
good, under 30ms over about a 10-hop route).
Somehow I had gotten th
Hi,
If v6 is disabled, no packets will make it to the v6 sockets, and you
should be fine. To entirely disable the creation of that socket,
disable the ipv6 module, via ipv6.disable=1 on the kernel command
line. This shouldn't actually be necessary for you though.
Jason
___
Hello Andy,
The mistake you've made is that your NOC servers don't have a route
indicating that 192.168.100.0/24 should go to wg0, and likely your
Linode server doesn't have a route indicating that 192.168.99.0/25
should go to wg0. Instead, packets to these addresses are going out of
your default
I haven't understood well your configuration, but I can suggest you to
give a look to mine, in which a "gateway" is implemented. Look in
particular Example 2 (Esempio 2). For the few Italian words you could
just use an online translator, but they are not so much important
https://groups.google.com
On 03.05.2018 23:53, Andy Dorman wrote:
> I am trying to set up VPN traffic between a local debian server cluster
> (allowed 192.168.99.x/24) and a Linode VM cluster (also debian, allowed
> 192.168.100.x/24).
>
look at the outcome of *ip route* and try to understand where your
traffic for the 1
We are just getting started with Wireguard, so I apologize in advance
for any stupid mistakes I have made to cause this.
I am trying to set up VPN traffic between a local debian server cluster
(allowed 192.168.99.x/24) and a Linode VM cluster (also debian, allowed
192.168.100.x/24).
I have s
Debian kernel 4.15.11
WG 0.0.20180420-1
Hi
Is there a way to constrain WG to ipv4? ipv6 is disabled on the server
and the WG iface has indeed just assigned an ipv4 address but netstat
-tulpn is still showing the WG port on upd6?
udp 0 0 0.0.0.0:45065 0.0.0.0:*
udp6
