From: Jason A. Donenfeld Date: Tue, 22 May 2018 14:47:15 +0000 (+0200) Subject: Fix markdown X-Git-Tag: 0.0.20180524~14 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=82d12e85bb625d2d0d72c043ac2c85146ab23f86;p=thirdparty%2Fwireguard-go.git Fix markdown --- diff --git a/README.md b/README.md index 4939937..92ef4da 100644 --- a/README.md +++ b/README.md @@ -40,11 +40,11 @@ It is currently a work in progress to strip out the beginnings of an experiment ### FreeBSD -This will run on FreeBSD. It does not yet support sticky sockets. Fwmark is mapped to `SO\_USER\_COOKIE`. +This will run on FreeBSD. It does not yet support sticky sockets. Fwmark is mapped to `SO_USER_COOKIE`. ### OpenBSD -This will run on OpenBSD. It does not yet support sticky sockets. Fwmark is mapped to `SO\_RTABLE`. Since the tun driver cannot have arbitrary interface names, you must either use `tun[0-9]+` for an explicit interface name or `tun` to have the program select one for you. If you choose `tun` as the interface name, and the environment variable `WG_TUN_NAME_FILE` is defined, then the actual name of the interface chosen by the kernel is written to the file specified by that variable. +This will run on OpenBSD. It does not yet support sticky sockets. Fwmark is mapped to `SO_RTABLE`. Since the tun driver cannot have arbitrary interface names, you must either use `tun[0-9]+` for an explicit interface name or `tun` to have the program select one for you. If you choose `tun` as the interface name, and the environment variable `WG_TUN_NAME_FILE` is defined, then the actual name of the interface chosen by the kernel is written to the file specified by that variable. ## Building