History

Dan Williams 731298003c plugins/testutils: pass CNI_CONTAINERID to plugins in testcases

Recent CNI specification changes require the container ID on ADD/DEL,
which the testcases were not providing.  Fix that up so things work
when this repo gets CNI revendored.

2018-04-26 11:24:30 -05:00

macvlan_suite_test.go

build: some small improvements; bump to go1.10

2018-04-12 16:59:51 +02:00

macvlan_test.go

plugins/testutils: pass CNI_CONTAINERID to plugins in testcases

2018-04-26 11:24:30 -05:00

macvlan.go

delete link and ip if err when cmdAdd to avoid resource leak.

2017-11-27 15:26:07 +08:00

README.md

Move documentation folder to individual READMEs

2017-05-16 16:46:15 +02:00

README.md

macvlan plugin

Overview

macvlan functions like a switch that is already connected to the host interface. A host interface gets "enslaved" with the virtual interfaces sharing the physical device but having distinct MAC addresses. Since each macvlan interface has its own MAC address, it makes it easy to use with existing DHCP servers already present on the network.

Example configuration

{
	"name": "mynet",
	"type": "macvlan",
	"master": "eth0",
	"ipam": {
		"type": "dhcp"
	}
}

Network configuration reference

name (string, required): the name of the network
type (string, required): "macvlan"
master (string, required): name of the host interface to enslave
mode (string, optional): one of "bridge", "private", "vepa", "passthrough". Defaults to "bridge".
mtu (integer, optional): explicitly set MTU to the specified value. Defaults to the value chosen by the kernel.
ipam (dictionary, required): IPAM configuration to be used for this network.

Notes

If are testing on a laptop, please remember that most wireless cards do not support being enslaved by macvlan.
A single master interface can not be enslaved by both macvlan and ipvlan.