schnapper79

it's exactly your example in [wgctrl-go/cmd/wgctrl/](https://github.com/WireGuard/wgctrl-go/tree/master/cmd/wgctrl). I call it either by: `sudo ./main` or by: `sudo ./main wg0`

it's an imx6 with debian stretch and a kernel 4.1.15. I am using a cross compiled "boringtun" and i do also cross compile your "main.go". ```bash $ ls /var/run/wireguard wg0.sock...

Is there a way how i can check which type of interface the client is looking for? it seems that `client.Device("wg0")` returns an unknown type and so i don't run...

hi.. after some digging with Printf I finally ended in `internal/wglinux/client_linux.go `, namly here: ```go // Device implements wginternal.Client. func (c *Client) Device(name string) (*wgtypes.Device, error) { ... //[long function...

I added a check for empty []genlink.Message if error is still nil: ```go // execute executes a single WireGuard netlink request with the specified command, // header flags, and attribute...

I will try to get my toolchain on my ARM device tomorrow... All I can say that now it's working perfectly so far.

`collect2: fatal error: ld terminated with signal 9 [Killed]` This seems to be a "out of memory" - problem. For me it helped to make a big enough swapfile to...

you didnt rename node_modules/jade-bootstrap to pug-bootstrap. So if you change in those two demo views (index.pug and error.pug) from `extends ../node_modules/pug-bootstrap/layouts/starter ` to `extends ../node_modules/jade-bootstrap/layouts/starter` it works as expected.