LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

veth.4: Add a more direct example 

iproute2 allows you to specify the netns for either side of a veth
interface at creation time.  Add an example of this to veth(4) so
it doesn't sound like you have to move the interfaces in a
separate step.

Verified with commands:
    # ip netns add alpha
    # ip netns add bravo
    # ip link add foo netns alpha type veth peer bar netns bravo
    # ip -n alpha link show
    # ip -n bravo link show

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Devin J. Pohly 2020-05-18 15:58:28 -05:00 committed by Michael Kerrisk
parent 3514b9beba
commit 1b0b13fe97
1 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
man4/veth.4
View File

@ -63,13 +63,23 @@ A particularly interesting use case is to place one end of a
.B veth
pair in one network namespace and the other end in another network namespace,
thus allowing communication between network namespaces.
To do this, one first creates the
.B veth
device as above and then moves one side of the pair to the other namespace:
To do this, one can provide the
.B netns
parameter when creating the interfaces:
.PP
.in +4n
.EX
# ip link set <p2-name> netns <p2-namespace>
# ip link add <p1-name> netns <p1-ns> type veth peer <p2-name> netns <p2-ns>
.EE
.in
.PP
or, for an existing
.B veth
pair, move one side to the other namespace:
.PP
.in +4n
.EX
# ip link set <p2-name> netns <p2-ns>
.EE
.in
.PP