1[![Build Status](https://travis-ci.org/containernetworking/plugins.svg?branch=master)](https://travis-ci.org/containernetworking/plugins) 2 3# plugins 4Some CNI network plugins, maintained by the containernetworking team. For more information, see the individual READMEs. 5 6Read [CONTRIBUTING](CONTRIBUTING.md) for build and test instructions. 7 8## Plugins supplied: 9### Main: interface-creating 10* `bridge`: Creates a bridge, adds the host and the container to it. 11* `ipvlan`: Adds an [ipvlan](https://www.kernel.org/doc/Documentation/networking/ipvlan.txt) interface in the container. 12* `loopback`: Set the state of loopback interface to up. 13* `macvlan`: Creates a new MAC address, forwards all traffic to that to the container. 14* `ptp`: Creates a veth pair. 15* `vlan`: Allocates a vlan device. 16* `host-device`: Move an already-existing device into a container. 17#### Windows: windows specific 18* `win-bridge`: Creates a bridge, adds the host and the container to it. 19* `win-overlay`: Creates an overlay interface to the container. 20### IPAM: IP address allocation 21* `dhcp`: Runs a daemon on the host to make DHCP requests on behalf of the container 22* `host-local`: Maintains a local database of allocated IPs 23* `static`: Allocate a static IPv4/IPv6 addresses to container and it's useful in debugging purpose. 24 25### Meta: other plugins 26* `flannel`: Generates an interface corresponding to a flannel config file 27* `tuning`: Tweaks sysctl parameters of an existing interface 28* `portmap`: An iptables-based portmapping plugin. Maps ports from the host's address space to the container. 29* `bandwidth`: Allows bandwidth-limiting through use of traffic control tbf (ingress/egress). 30* `sbr`: A plugin that configures source based routing for an interface (from which it is chained). 31* `firewall`: A firewall plugin which uses iptables or firewalld to add rules to allow traffic to/from the container. 32 33### Sample 34The sample plugin provides an example for building your own plugin. 35