1 .\" Copyright (c) 2012 Tomáš Pospíšek (tpo_deb@sourcepole.ch),
2 .\" Fri, 03 Nov 2012 22:35:33 +0100
3 .\" and Copyright (c) 2012 Eric W. Biederman <ebiederm@xmission.com>
5 .\" This is free documentation; you can redistribute it and/or
6 .\" modify it under the terms of the GNU General Public License as
7 .\" published by the Free Software Foundation; either version 2 of
8 .\" the License, or (at your option) any later version.
10 .\" The GNU General Public License's references to "object code"
11 .\" and "executables" are to be interpreted as the output of any
12 .\" document formatting or typesetting system, including
13 .\" intermediate and printed output.
15 .\" This manual is distributed in the hope that it will be useful,
16 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
17 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
18 .\" GNU General Public License for more details.
20 .\" You should have received a copy of the GNU General Public
21 .\" License along with this manual; if not, write to the Free
22 .\" Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111,
26 .TH veth 4 2017-10-03 "Linux" "Linux Programmer's Manual"
28 veth \- Virtual Ethernet Device
32 devices are virtual Ethernet devices.
33 They can act as tunnels between network namespaces to create
34 a bridge to a physical network device in another namespace,
35 but can also be used as standalone network devices.
38 devices are always created in interconnected pairs.
39 A pair can be created using the command:
43 # ip link add <p1-name> type veth peer name <p2-name>
51 are the names assigned to the two connected end points.
52 interconnected with each other.
54 Packets transmitted on one device in the pair are immediately received on
56 When either devices is down the link state of the pair is down.
59 device pairs are useful for combining the network
60 facilities of the kernel together in interesting ways.
61 A particularly interesting use case is to place one end of a
63 pair in one network namespace and the other end in another network namespace,
64 thus allowing communication between network namespaces.
67 can be used to test if a networking device is a
69 device, and to find the peer network interface.