qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: anton.ivanov@kot-begemot.co.uk
Cc: Anton Ivanov <antivano@cisco.com>,
	pbonzini@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
	afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH] net: L2TPv3 transport
Date: Mon, 10 Mar 2014 16:05:29 +0100	[thread overview]
Message-ID: <20140310150529.GC32400@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1394451098-296108-1-git-send-email-anton.ivanov@kot-begemot.co.uk>

On Mon, Mar 10, 2014 at 11:31:38AM +0000, anton.ivanov@kot-begemot.co.uk wrote:
> From: Anton Ivanov <antivano@cisco.com>
> 
> This tranport allows to connect a qemu nic to a static Ethernet
> over L2TPv3 tunnel. The transport supports all options present
> in the linux kernel implementation. It allows qemu to connect
> to any linux host running kernel 3.3+, most routers and network
> 
> Signed-off-by: Anton Ivanov <antivano@cisco.com>
> ---
>  net/Makefile.objs |    1 +
>  net/clients.h     |    2 +
>  net/l2tpv3.c      |  585 +++++++++++++++++++++++++++++++++++++++++++++++++++++
>  net/net.c         |    3 +
>  qapi-schema.json  |   59 +++++-
>  qemu-options.hx   |   94 +++++++--
>  6 files changed, 730 insertions(+), 14 deletions(-)
>  create mode 100644 net/l2tpv3.c

This patch is missing the [PATCH v4] revision number and still uses
IPPROTO_L2TP, which is being discussed in the previous thread.  I guess
it will be necessary to send one more revision once that discussion is
finished.

Stefan

  reply	other threads:[~2014-03-10 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 11:31 [Qemu-devel] [PATCH] net: L2TPv3 transport anton.ivanov
2014-03-10 15:05 ` Stefan Hajnoczi [this message]
2014-03-10 15:09   ` Anton Ivanov (antivano)
2014-03-10 16:06 ` Eric Blake
2014-03-10 16:31   ` Anton Ivanov

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=20140310150529.GC32400@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=afaerber@suse.de \
    --cc=antivano@cisco.com \
    --cc=anton.ivanov@kot-begemot.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).