Hey Pipacs,
I've been receiving reports of strange bugs from grsec users with
WireGuard. The first set of bugs was a heisenbug crash, and I never
found the root cause, but it seemed to happen in the rx path. Then
today Timothée emailed another different bug from a grsec box, also
along the rx path
Hi,
With the following setup, both client & server running:
* Arch Linux
* kernel 4.9.11.r20170257-1-grsec
* wireguard-dkms & wireguard-tools 0.0.20170223
Server:
interface: wg0
public key: ...
private key: ...
listening port: 51820
peer: ...
endpoint: ...:51820
allowed ips: 192.16
Hey Jorg,
Moving this to a new thread.
On Sun, Feb 26, 2017 at 7:25 PM, Jörg Thalheim wrote:
> In this context, I found the following rules useful to bypass the vpn for
> some routes:
>
> #!/usr/bin/env bash
> # /etc/wireguard/.sh
>
> if [ "${1:-down}" = "up" ]; then
> action="add"
> else
>
In this context, I found the following rules useful to bypass the vpn for some
routes:
#!/usr/bin/env bash
# /etc/wireguard/.sh
if [ "${1:-down}" = "up" ]; then
action="add"
else
action="del"
fi
ip rule $action priority 32763 to 192.168.0.0/16 lookup main
ip rule $action priority 32763 to 1
