Hi Jason, Jason A. Donenfeld writes: > > - 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.
The version in OpenBSD's package repositories is old, yes. > 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. Yes, I did try it (successfully). > > 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? This is for some special handling in OpenBSD's Go ports infrastructure. -- Anthony J. Bentley
