Matt Layher
Matt Layher
Hello, I previously used `go-fuzz` with Go 1.4.2, but now that I'm on 1.5.1, it no longer seems to work. In addition, when switching back to 1.4.2, it doesn't seem...
@skoef writes: > I have a question that relates to this issue but is unrelated to WireGuard however: I'm currently running a RAD that I've built myself to send out...
See https://datatracker.ietf.org/doc/html/rfc8781.
After fixing a small compilation failure, it looks like CoreRAD works just fine on FreeBSD. ``` $ sudo tcpdump icmp6 -vvv tcpdump: listening on vtnet0, link-type EN10MB (Ethernet), capture size...
Add the connectionless counterparts alongside the existing connection-oriented API.
I should show folks how to get up and running with VM sockets, so they don't need to do a bunch of Googling like I did.
Hey folks! I was browsing through GitHub search and came across this blog by @jonathangold that talks about using netlink sockets in this project: https://github.com/jonathangold/jonathangold.ca/blob/706d0af6aa568cbd1524b56543410227d466d0db/content/blog/go-netlink-and-select.md Just wanted to let you...
@stapelberg and I had spoken at GopherCon and I believe he mentioned the need to specify an arbitrary net.PacketConn in this package. The problem right now is that we effectively...
Hello again! I had previously suggested that we split the NCSI netlink interaction code into its own package to enable further reuse in the Go ecosystem. I'd be happy to...
The current interface only implements the raw configuration parameters expected by WireGuard devices, but it could be nice to implement some kind of higher level interface to ease configuration for...