[PATCH v3] wg: Support restricting address family of DNS resolved Endpoint

When using wireguard tunnels for providing IPv6 connectivity to machines it can be important to pin which IP address family should be used. Consider a peer using a DNS name with both A/ records, wg will currently blindly follow system policy and use the first address returned by

[PATCH wireguard-go] tun/netstack: bump to latest gvisor

To build with go1.19, gvisor needs 99325baf ("Bump gVisor build tags to go1.19"). However gvisor.dev/gvisor/pkg/tcpip/buffer is no longer available, so refactor to use gvisor.dev/gvisor/pkg/tcpip/link/channel directly. Signed-off-by: Shengjing Zhu --- tun/netstack/go.mod | 3 +-

FreeBSD current socket-src changed. Wireguard not compiling.

Tonight after updating kernel freebsd current I got coredump with wireguard enabled kernel module. As is https://reviews.freebsd.org/D36232 D36232 protosw: refactor protosw and domain static declaration and load (freebsd.org) in wireguard-freebsd/src/support.h ... error =

[PATCH v2] wg: Support restricting address family of DNS resolved Endpoint

When using wireguard tunnels for providing IPv6 connectivity to machines it can be important to pin which IP address family should be used. Consider a peer using a DNS name with both A/ records, wg will currently blindly follow system policy and use the first address returned by

Endpoints are not in sync (latest handshake)

I have two wireguard endpoints that has different opinions about when the last handshake was made: interface: wg0 public key: PauftxCvmti7CDDZ9yj6EKZ+r9zQj6gjb9hvP1whzwQ= private key: (hidden) listening port: 17395 peer: s5dnr91F06+AQ/3o5urOM5Dc1f0gzHOsGjwD+AEmwDA= endpoint:

Re: [Question or feature request] Support multiple peer config file using something like /etc/wireguard/conf.d

Hello, On Tue, 19 Jul 2022 21:36:57 + Quentin Vallin wrote: > I'm trying to separate my peer configuration and automate it.  > > I know that I can use the post hook PostUp = wg addconf /path/to/my/file > > It would be easier to have a special path were wireguard can merge the config >

[PATCH] wg: Support restricting resolved Endpoint address family

On IPv4-only hosts it can happen that the v6 default route pointed at a wireguard interface blackholes wireguard peer traffic intended for the v4 network when the Endpoint hostname resolves to both v6 and v4 records as most hosts will prefer the v6 address by default. This makes using dual-stack

Android App: dynamic configuration

Hi guys, Is there a way planned to pass a dynamically created configuration set to the wireguard android app? I have this use case as following: Some devices receive information about a new, dynamically established VPN and want to connect to it. The information about the IP address, public key

[Question or feature request] Support multiple peer config file using something like /etc/wireguard/conf.d

Hi,  I'm trying to separate my peer configuration and automate it.  I know that I can use the post hook PostUp = wg addconf /path/to/my/file It would be easier to have a special path were wireguard can merge the config file together, like /etc/wireguard/conf.d//.conf.  I don't find anything

[PATCH] wireguard: send/receive: update function names in comments

The functions packet_send_queued_handshakes() and packet_process_queued_handshake_packets() were renamed to wg_packet_handshake_send_worker() and wg_packet_handshake_receive_worker() respectively, but the comments referring to them were not updated accordingly, let's fix it. Signed-off-by: Yuntao

Android app icon isn't displayed in F-Droid clients

https://github.com/NeoApplications/Neo-Store/issues/273#issuecomment-1214153179

Re: Endpoints are not in sync (latest handshake)

> I have two wireguard endpoints that has different opinions about when the > last handshake was made: > > interface: wg0 >   public key: PauftxCvmti7CDDZ9yj6EKZ+r9zQj6gjb9hvP1whzwQ= >   private key: (hidden) >   listening port: 17395 > > peer: s5dnr91F06+AQ/3o5urOM5Dc1f0gzHOsGjwD+AEmwDA= >