From: Tomas Pospisek <tpo-UQchlGytWBLoPl2ZpcX+cw@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: veth.4
Date: Fri, 2 Nov 2012 14:25:43 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1211021413490.9880@localhost> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2851 bytes --]
Hello linux-man ML and Michael,
below you'll find a manpage about the veth virtual ethernet device. The
manpage is a summarisation of the sparse information about veth I found on
the net.
I'd be glad if veth(4) could find a place in the manpages because
allthough I was using veth's a lot lately, I had no idea about how they
work and so didn't my peers. So I suspect a manpage might be useful.
In my ignorance I've chosen section 4 for the manpage, maybe there's a
better one.
You can find the manpage below
Thanks,
*t
***************************************************************
.\" Copyright (c) 2012 Tomáš Pospíšek (tpo_deb-UQchlGytWBLoPl2ZpcX+cw@public.gmane.org),
.\" Fri, 02 Nov 2012 13:37:33 +0100
.\"
.\" This is free documentation; you can redistribute it and/or
.\" modify it under the terms of the GNU General Public License as
.\" published by the Free Software Foundation; either version 2 of
.\" the License, or (at your option) any later version.
.\"
.\" The GNU General Public License's references to "object code"
.\" and "executables" are to be interpreted as the output of any
.\" document formatting or typesetting system, including
.\" intermediate and printed output.
.\"
.\" This manual is distributed in the hope that it will be useful,
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.\" GNU General Public License for more details.
.\"
.\" You should have received a copy of the GNU General Public
.\" License along with this manual; if not, write to the Free
.\" Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111,
.\" USA.
.\"
.\"
.TH veth 4 2012-11-02 "Linux" "Linux Programmer's Manual"
.SH NAME
veth \- Virtual Ethernet Device
.SH DESCRIPTION
The \fBveth*\fP 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.
Because of their original purpose for tunneling \fBveth\fP devices
are allways created in pairs, that are interconnected with
each other. When one \fBveth\fP end receives a packet it
appears on its pair and vice versa.
\fBVeth\fP devices can be manipulated with the
.BR ip (8)
tool. See \fB ip link help\fP for more information.
.SH "SEE ALSO"
.BR ip (8) ,
.BR clone (2)
.SH COLOPHON
This page is based on Pavel Emelianov's veth driver submission to
the LKML and on the
.BR clone (8)
manpage.
It is part of release 3.44 of the Linux
.I man-pages
project.
A description of the project,
and information about reporting bugs,
can be found at
http://man7.org/linux/man-pages/.
***************************************************************
next reply other threads:[~2012-11-02 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 13:25 Tomas Pospisek [this message]
2012-11-03 7:12 ` veth.4 Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkjF-tO4X=REyfA=XG25s-SHfNwkCTmi4vXFbvQPWZZQyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-11-03 21:35 ` veth.4 Tomas Pospisek
2012-11-04 0:35 ` veth.4 Eric W. Biederman
[not found] ` <87zk2ytdbu.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2012-11-04 1:43 ` veth.4 Pavel Emelyanov
[not found] ` <5095C848.9000501-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2012-11-05 4:11 ` veth.4 Eric W. Biederman
[not found] ` <87vcdksn7l.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2012-12-13 9:56 ` veth.4 Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkiQFFkGq9tXT2n8KeaWuQxqh4HyU5YG6tHB5TYPvkNSVA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-12-13 10:05 ` veth.4 Tomas Pospisek
2012-12-13 10:31 ` veth.4 Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1211021413490.9880@localhost \
--to=tpo-uqchlgytwblopl2zpcx+cw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox