Dan Williams a49f908168 ip: place veth peer in host namspace directly ...

Instead of moving the host side of the veth peer into the host
network namespace later, just create it in the host namespace
directly.

Signed-off-by: Dan Williams <dcbw@redhat.com>

2021-07-21 09:59:11 -05:00

..

addr_linux.go

Enable Windows CI (Appveyor)

2017-11-10 08:09:29 -08:00

cidr.go

ipam/host-local: support multiple IP ranges

2017-06-12 21:14:44 +02:00

ip_suite_test.go

build: some small improvements; bump to go1.10

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

ip_test.go

pkg/ip: introduce a new type IP to support formated <ip>[/<prefix>]

2021-04-13 17:53:43 +08:00

ip.go

pkg/ip: introduce a new type IP to support formated <ip>[/<prefix>]

2021-04-13 17:53:43 +08:00

ipforward_linux_test.go

pkg/ip: Add missing error check

2018-09-20 11:04:13 +02:00

ipforward_linux.go

plugins: update to spec version 1.0.0

2021-02-11 23:27:08 -06:00

ipmasq_linux.go

change source of ipmasq rule from ipn to ip

2019-04-25 15:59:02 +08:00

link_linux_test.go

ip: place veth peer in host namspace directly

2021-07-21 09:59:11 -05:00

link_linux.go

ip: place veth peer in host namspace directly

2021-07-21 09:59:11 -05:00

route_linux.go

Enable Windows CI (Appveyor)

2017-11-10 08:09:29 -08:00

utils_linux.go

plugins: update to spec version 1.0.0

2021-02-11 23:27:08 -06:00