from small one page howto to huge articles all in one place

search text in:




Other .linuxhowtos.org sites:gentoo.linuxhowtos.org



Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

209580

userrating:


May 25th. 2007:
Words

486

Views

258586

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

149876

userrating:


April, 26th. 2006:

Druckversion
You are here: manpages





veth

Section: Devices and Network Interfaces (4)
Updated: 202-0-08
Index Return to Main Contents
 

NAME

veth - Virtual Ethernet Device  

DESCRIPTION

The veth devices are virtual Ethernet devices. They can act as tunnels between network namespaces to create a bridge to a physical network device in another namespace, but can also be used as standalone network devices. veth devices are always created in interconnected pairs. A pair can be created using the command: # ip link add <p-name> type veth peer name <p-name> In the above, p-name and p-name are the names assigned to the two connected end points. Packets transmitted on one device in the pair are immediately received on the other device. When either device is down, the link state of the pair is down. veth device pairs are useful for combining the network facilities of the kernel together in interesting ways. A particularly interesting use case is to place one end of a veth pair in one network namespace and the other end in another network namespace, thus allowing communication between network namespaces. To do this, one can provide the netns parameter when creating the interfaces: # ip link add <p1-name> netns <p1-ns> type veth peer <p2-name> netns <p2-ns> or, for an existing veth pair, move one side to the other namespace: # ip link set <p2-name> netns <p2-ns> ethtool(8) can be used to find the peer of a veth network interface, using commands something like: # ip link add ve_A type veth peer name ve_B; # Create veth pair # ethtool -S ve_A; # Discover interface index of peer NIC statistics:
     peer_ifindex: 16 # ip link | grep [aq][ha]16:[aq]; # Look up interface 16: ve_B@ve_A: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc ...  

SEE ALSO

clone(2), network_namespaces(7), ip(8), ip-link(8), ip-netns(8)


 

Index

NAME
DESCRIPTION
SEE ALSO





Support us on Content Nation
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2025 Sascha Nitsch Unternehmensberatung GmbH
Valid XHTML1.1 : Valid CSS
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 12.9 ms