2014-09-23 19:32:47 +00:00
|
|
|
# netlink - netlink library for go #
|
2014-09-01 03:27:34 +00:00
|
|
|
|
2021-09-21 14:35:17 +00:00
|
|
|
[![Build Status](https://app.travis-ci.com/vishvananda/netlink.svg?branch=master)](https://app.travis-ci.com/github/vishvananda/netlink) [![GoDoc](https://godoc.org/github.com/vishvananda/netlink?status.svg)](https://godoc.org/github.com/vishvananda/netlink)
|
2014-10-31 19:27:21 +00:00
|
|
|
|
2014-09-01 03:27:34 +00:00
|
|
|
The netlink package provides a simple netlink library for go. Netlink
|
|
|
|
is the interface a user-space program in linux uses to communicate with
|
|
|
|
the kernel. It can be used to add and remove interfaces, set ip addresses
|
|
|
|
and routes, and configure ipsec. Netlink communication requires elevated
|
|
|
|
privileges, so in most cases this code needs to be run as root. Since
|
|
|
|
low-level netlink messages are inscrutable at best, the library attempts
|
2016-06-15 05:00:47 +00:00
|
|
|
to provide an api that is loosely modeled on the CLI provided by iproute2.
|
2014-09-01 03:27:34 +00:00
|
|
|
Actions like `ip link add` will be accomplished via a similarly named
|
|
|
|
function like AddLink(). This library began its life as a fork of the
|
|
|
|
netlink functionality in
|
|
|
|
[docker/libcontainer](https://github.com/docker/libcontainer) but was
|
|
|
|
heavily rewritten to improve testability, performance, and to add new
|
|
|
|
functionality like ipsec xfrm handling.
|
|
|
|
|
|
|
|
## Local Build and Test ##
|
|
|
|
|
|
|
|
You can use go get command:
|
|
|
|
|
|
|
|
go get github.com/vishvananda/netlink
|
|
|
|
|
|
|
|
Testing dependencies:
|
|
|
|
|
|
|
|
go get github.com/vishvananda/netns
|
|
|
|
|
|
|
|
Testing (requires root):
|
|
|
|
|
|
|
|
sudo -E go test github.com/vishvananda/netlink
|
|
|
|
|
|
|
|
## Examples ##
|
|
|
|
|
|
|
|
Add a new bridge and add eth1 into it:
|
|
|
|
|
|
|
|
```go
|
|
|
|
package main
|
|
|
|
|
|
|
|
import (
|
2017-06-24 04:55:36 +00:00
|
|
|
"fmt"
|
2014-11-25 17:04:52 +00:00
|
|
|
"github.com/vishvananda/netlink"
|
2014-09-01 03:27:34 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
func main() {
|
2015-06-14 04:01:03 +00:00
|
|
|
la := netlink.NewLinkAttrs()
|
|
|
|
la.Name = "foo"
|
2017-06-24 04:55:36 +00:00
|
|
|
mybridge := &netlink.Bridge{LinkAttrs: la}
|
|
|
|
err := netlink.LinkAdd(mybridge)
|
|
|
|
if err != nil {
|
|
|
|
fmt.Printf("could not add %s: %v\n", la.Name, err)
|
|
|
|
}
|
2014-09-01 03:27:34 +00:00
|
|
|
eth1, _ := netlink.LinkByName("eth1")
|
|
|
|
netlink.LinkSetMaster(eth1, mybridge)
|
|
|
|
}
|
|
|
|
|
|
|
|
```
|
2015-06-14 04:01:03 +00:00
|
|
|
Note `NewLinkAttrs` constructor, it sets default values in structure. For now
|
|
|
|
it sets only `TxQLen` to `-1`, so kernel will set default by itself. If you're
|
|
|
|
using simple initialization(`LinkAttrs{Name: "foo"}`) `TxQLen` will be set to
|
|
|
|
`0` unless you specify it like `LinkAttrs{Name: "foo", TxQLen: 1000}`.
|
2014-09-01 03:27:34 +00:00
|
|
|
|
|
|
|
Add a new ip address to loopback:
|
|
|
|
|
|
|
|
```go
|
|
|
|
package main
|
|
|
|
|
|
|
|
import (
|
2014-11-25 17:04:52 +00:00
|
|
|
"github.com/vishvananda/netlink"
|
2014-09-01 03:27:34 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
func main() {
|
|
|
|
lo, _ := netlink.LinkByName("lo")
|
|
|
|
addr, _ := netlink.ParseAddr("169.254.169.254/32")
|
|
|
|
netlink.AddrAdd(lo, addr)
|
|
|
|
}
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
## Future Work ##
|
|
|
|
|
|
|
|
Many pieces of netlink are not yet fully supported in the high-level
|
2014-09-19 02:09:35 +00:00
|
|
|
interface. Aspects of virtually all of the high-level objects don't exist.
|
|
|
|
Many of the underlying primitives are there, so its a matter of putting
|
|
|
|
the right fields into the high-level objects and making sure that they
|
2014-09-01 03:27:34 +00:00
|
|
|
are serialized and deserialized correctly in the Add and List methods.
|
|
|
|
|
|
|
|
There are also a few pieces of low level netlink functionality that still
|
|
|
|
need to be implemented. Routing rules are not in place and some of the
|
|
|
|
more advanced link types. Hopefully there is decent structure and testing
|
|
|
|
in place to make these fairly straightforward to add.
|
2017-10-20 20:38:07 +00:00
|
|
|
|