Simple netlink library for go.
Go to file
Alessandro Boch e361359783 Add String() method to user structures (#116)
Signed-off-by: Alessandro Boch <aboch@docker.com>
2016-05-09 16:53:16 -07:00
nl Provide netlink handle (#104) 2016-05-08 11:35:49 -07:00
.travis.yml make the gre test pass 2015-12-18 12:14:58 -08:00
LICENSE Initial commit of netlink package 2014-08-31 20:34:46 -07:00
Makefile Cleanup from golint and go vet 2016-03-19 17:12:26 -07:00
README.md Add info about NewLinkAttrs to readme 2015-06-13 21:01:03 -07:00
addr.go Remove FlagsMask from Addr struct 2015-12-09 11:30:21 +01:00
addr_linux.go Provide netlink handle (#104) 2016-05-08 11:35:49 -07:00
addr_test.go Cleanup from golint and go vet 2016-03-19 17:12:26 -07:00
bpf_linux.go Fix 32bit warnings in bpf_linux.go 2016-03-18 11:13:40 -07:00
class.go Cleanup from golint and go vet 2016-03-19 17:12:26 -07:00
class_linux.go Provide netlink handle (#104) 2016-05-08 11:35:49 -07:00
class_test.go Cleanup from golint and go vet 2016-03-19 17:12:26 -07:00
filter.go Cleanup from golint and go vet 2016-03-19 17:12:26 -07:00
filter_linux.go Provide netlink handle (#104) 2016-05-08 11:35:49 -07:00
filter_test.go Skip test if bpf syscall is unavailable 2016-02-28 23:52:26 -08:00
handle.go Provide netlink handle (#104) 2016-05-08 11:35:49 -07:00
handle_test.go Provide method to query for specific policy (#115) 2016-05-09 16:52:35 -07:00
link.go Cleanup from golint and go vet 2016-03-19 17:12:26 -07:00
link_linux.go Provide netlink handle (#104) 2016-05-08 11:35:49 -07:00
link_test.go Cleanup from golint and go vet 2016-03-19 17:12:26 -07:00
link_tuntap_linux.go Drop cgo usage for ifReq structure. 2015-10-02 11:54:54 +01:00
neigh.go Use LinkIndex instead of Link obj in Route, Neigh 2014-10-13 16:09:09 -07:00
neigh_linux.go Provide netlink handle (#104) 2016-05-08 11:35:49 -07:00
neigh_test.go Fix go vet errors 2015-02-12 11:00:59 -08:00
netlink.go Cleanup from golint and go vet 2016-03-19 17:12:26 -07:00
netlink_test.go IPVlan support 2015-02-11 14:18:57 -08:00
netlink_unspecified.go Change logic of setting protinfo attrs 2015-02-17 14:16:48 -08:00
protinfo.go Fix some style issues as suggested by golint 2015-06-18 17:41:46 -07:00
protinfo_linux.go Provide netlink handle (#104) 2016-05-08 11:35:49 -07:00
protinfo_test.go Change logic of setting protinfo attrs 2015-02-17 14:16:48 -08:00
qdisc.go Cleanup from golint and go vet 2016-03-19 17:12:26 -07:00
qdisc_linux.go Provide netlink handle (#104) 2016-05-08 11:35:49 -07:00
qdisc_test.go [qdisc] add support for replace/change 2015-11-11 23:57:32 -05:00
route.go Add route table number as significant info about route object (#103) 2016-04-28 13:16:53 -07:00
route_linux.go Provide netlink handle (#104) 2016-05-08 11:35:49 -07:00
route_test.go remove routeFilter struct and use route and mask instead 2015-12-08 23:35:55 +01:00
rule.go Remove FlagMask from Rule 2015-12-09 14:07:11 +01:00
rule_linux.go Provide netlink handle (#104) 2016-05-08 11:35:49 -07:00
rule_test.go Cleanup from golint and go vet 2016-03-19 17:12:26 -07:00
xfrm.go Add Mark field to xrfm state and policy (#110) 2016-04-30 20:31:59 -07:00
xfrm_policy.go Add String() method to user structures (#116) 2016-05-09 16:53:16 -07:00
xfrm_policy_linux.go Provide method to query for specific policy (#115) 2016-05-09 16:52:35 -07:00
xfrm_policy_test.go Provide method to query for specific policy (#115) 2016-05-09 16:52:35 -07:00
xfrm_state.go Add String() method to user structures (#116) 2016-05-09 16:53:16 -07:00
xfrm_state_linux.go Provide method to query for specific policy (#115) 2016-05-09 16:52:35 -07:00
xfrm_state_test.go Provide method to query for specific policy (#115) 2016-05-09 16:52:35 -07:00

README.md

netlink - netlink library for go

Build Status GoDoc

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 to provide an api that is loosely modeled on the CLI provied by iproute2. 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 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:

package main

import (
    "net"
    "github.com/vishvananda/netlink"
)

func main() {
    la := netlink.NewLinkAttrs()
    la.Name = "foo"
    mybridge := &netlink.Bridge{la}}
    _ := netlink.LinkAdd(mybridge)
    eth1, _ := netlink.LinkByName("eth1")
    netlink.LinkSetMaster(eth1, mybridge)
}

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}.

Add a new ip address to loopback:

package main

import (
    "net"
    "github.com/vishvananda/netlink"
)

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 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 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.