6a696e03e7
* migrate to golang.zx2c4.com/wireguard/wgctrl This commit introduces the usage of wgctrl. It avoids the usage of exec calls of the wg command and parsing the output of `wg show`. Signed-off-by: leonnicolas <leonloechner@gmx.de> * vendor wgctrl Signed-off-by: leonnicolas <leonloechner@gmx.de> * apply suggestions from code review Remove wireguard.Enpoint struct and use net.UDPAddr for the resolved endpoint and addr string (dnsanme:port) if a DN was supplied. Signed-off-by: leonnicolas <leonloechner@gmx.de> * pkg/*: use wireguard.Enpoint This commit introduces the wireguard.Enpoint struct. It encapsulates a DN name with port and a net.UPDAddr. The fields are private and only accessible over exported Methods to avoid accidental modification. Also iptables.GetProtocol is improved to avoid ipv4 rules being applied by `ip6tables`. Signed-off-by: leonnicolas <leonloechner@gmx.de> * pkg/wireguard/conf_test.go: add tests for Endpoint Signed-off-by: leonnicolas <leonloechner@gmx.de> * cmd/kg/main.go: validate port range Signed-off-by: leonnicolas <leonloechner@gmx.de> * add suggestions from review Signed-off-by: leonnicolas <leonloechner@gmx.de> * pkg/mesh/mesh.go: use Equal func Implement an Equal func for Enpoint and use it instead of comparing strings. Signed-off-by: leonnicolas <leonloechner@gmx.de> * cmd/kgctl/main.go: check port range Signed-off-by: leonnicolas <leonloechner@gmx.de> * vendor Signed-off-by: leonnicolas <leonloechner@gmx.de>
52 lines
2.1 KiB
Markdown
52 lines
2.1 KiB
Markdown
# netlink [](https://github.com/mdlayher/netlink/actions) [](https://pkg.go.dev/github.com/mdlayher/netlink) [](https://goreportcard.com/report/github.com/mdlayher/netlink)
|
|
|
|
Package `netlink` provides low-level access to Linux netlink sockets.
|
|
MIT Licensed.
|
|
|
|
For more information about how netlink works, check out my blog series
|
|
on [Linux, Netlink, and Go](https://mdlayher.com/blog/linux-netlink-and-go-part-1-netlink/).
|
|
|
|
If you have any questions or you'd like some guidance, please join us on
|
|
[Gophers Slack](https://invite.slack.golangbridge.org) in the `#networking`
|
|
channel!
|
|
|
|
## Stability
|
|
|
|
See the [CHANGELOG](./CHANGELOG.md) file for a description of changes between
|
|
releases.
|
|
|
|
This package has a stable v1 API and any future breaking changes will prompt
|
|
the release of a new major version. Features and bug fixes will continue to
|
|
occur in the v1.x.x series.
|
|
|
|
In order to reduce the maintenance burden, this package is only supported on
|
|
Go 1.12+. Older versions of Go lack critical features and APIs which are
|
|
necessary for this package to function correctly.
|
|
|
|
**If you depend on this package in your applications, please use Go modules.**
|
|
|
|
## Design
|
|
|
|
A [number of netlink packages](https://godoc.org/?q=netlink) are already
|
|
available for Go, but I wasn't able to find one that aligned with what
|
|
I wanted in a netlink package:
|
|
|
|
- Straightforward, idiomatic API
|
|
- Well tested
|
|
- Well documented
|
|
- Doesn't use package/global variables or state
|
|
- Doesn't necessarily need root to work
|
|
|
|
My goal for this package is to use it as a building block for the creation
|
|
of other netlink family packages.
|
|
|
|
## Ecosystem
|
|
|
|
Over time, an ecosystem of Go packages has developed around package `netlink`.
|
|
Many of these packages provide building blocks for further interactions with
|
|
various netlink families, such as `NETLINK_GENERIC` or `NETLINK_ROUTE`.
|
|
|
|
To have your package included in this diagram, please send a pull request!
|
|
|
|
|