From: "Rémi Denis-Courmont" <remi@remlab.net>
To: Kfir Lavi <lavi.kfir@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: tun.c non formal header protocol?
Date: Thu, 24 Feb 2011 21:04:40 +0200 [thread overview]
Message-ID: <201102242104.40835.remi@remlab.net> (raw)
In-Reply-To: <AANLkTikpkgiTRDJe0gxuXosp_uvg0gKM_c7GcvL+hhLm@mail.gmail.com>
Le jeudi 24 février 2011 20:37:32 Kfir Lavi, vous avez écrit :
> I would like to use custom protocol over tun/tap device.
Over TAP, you can only exchange Ethernet frames. However you can use whatever
network layer you like (so long as it has an Ethernet type associated).
Over TUN, you can exchange packets without any link layer header, for any
network layer protocol defined in Linux.
In principles, you can probably just use a (Ethernet) type that is not used by
any existing stack in the Linux kernel. But I don't see any point in doing so,
as the kernel will just drop the packets on the floor afterward.
> I'm grabbing packets, and changing them, to deliver via tap,
> to a listener that knows this custom protocol.
> The custom protocol is just wrapping the packet with another
> small header.
> Is it possible to move custom packets via tun.c ?
It's difficult to say without a clearer picture what you are trying to do.
--
Rémi Denis-Courmont
http://www.remlab.info/
http://fi.linkedin.com/in/remidenis
prev parent reply other threads:[~2011-02-24 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTin-PJs07ruhhbC5U0DmqFd-rP8Csorethz_1kes@mail.gmail.com>
2011-02-24 18:37 ` tun.c non formal header protocol? Kfir Lavi
2011-02-24 19:04 ` Rémi Denis-Courmont [this message]
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=201102242104.40835.remi@remlab.net \
--to=remi@remlab.net \
--cc=lavi.kfir@gmail.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).