Hi Anthony, On Thu, Jun 21, 2018 at 3:05 AM Anthony J. Bentley <anth...@anjbe.name> wrote: > Oops, I accidentally sent out my (unfinished, broken) wireguard-go draft > from last week. Attached is the working version I meant to send out.
Thanks. A few notes on what you just sent: > - ipcErrorProtocol = -int64(unix.EPROTO) > + ipcErrorProtocol = -int64(95) The x/sys/unix Go package now supports EPROTO on OpenBSD. Did you have an old stale version in your Gopath? Filippo added it there three or four weeks ago. You cobbled together in your OpenBSD-centric readme a few fragments from the upstream readme. One of those fragments your cribbed is: > To remove the > interface, use the usual 'ifconfig tun0 destroy', or you may instead remove > the > control socket via 'rm -f /var/run/wireguard/tun0.sock' I know that the `rm -f` version works on OpenBSD, but I'm not sure `ifconfig tun0 destroy` will have the effect you were hoping for; can you try this and see if it works there? The BSDs are all very different about interface destroy handling, and I can't remember which behavior OpenBSD exhibited. > ALL_TARGET = git.zx2c4.com/wireguard-go Does that do what you think it does? Shouldn't the target just be "wireguard-go"? Or is there some special-case openbsd-go handling happening? Regards, Jason
