From: Gleb Natapov <gleb@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/5] Marry slirp and qemu character device.
Date: Mon, 5 Jan 2009 18:21:10 +0200 [thread overview]
Message-ID: <20090105162110.GA7803@redhat.com> (raw)
In-Reply-To: <496228C9.3090701@codemonkey.ws>
On Mon, Jan 05, 2009 at 09:35:37AM -0600, Anthony Liguori wrote:
> Gleb Natapov wrote:
>> Trap TCP connection to special IP/port inside slirp and redirect its
>> traffic to a qemu character device. Add option to prevent connections
>> through slirp to outside world. Add migration support for "special"
>> sockets. This allow slirp to be used for secure communication between
>> host and guest management agents.
>>
>
> Do you have some simple client/server that you're using for testing?
> The patches look good to me, I'd like to test them first though before
> applying. I guess I could just use a combination of socat/md5sum but
> I'm wondering if you have anything more sophisticated already.
>
socat/md5sum exactly what I am using :)
--
Gleb.
next prev parent reply other threads:[~2009-01-05 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 15:14 [Qemu-devel] [PATCH v2 0/5] Marry slirp and qemu character device Gleb Natapov
2009-01-05 15:15 ` [Qemu-devel] [PATCH v2 1/5] Redirect slirp traffic to/from " Gleb Natapov
2009-01-07 16:52 ` Anthony Liguori
2009-01-05 15:15 ` [Qemu-devel] [PATCH v2 2/5] Add vmchannel command line option Gleb Natapov
2009-01-05 15:15 ` [Qemu-devel] [PATCH v2 3/5] Add slirp_restrict option Gleb Natapov
2009-01-05 15:15 ` [Qemu-devel] [PATCH v2 4/5] Add "restrict" and "ip" option to "user" net option Gleb Natapov
2009-01-05 15:15 ` [Qemu-devel] [PATCH v2 5/5] Add support for vmchannel socket migration Gleb Natapov
2009-01-05 15:35 ` [Qemu-devel] [PATCH v2 0/5] Marry slirp and qemu character device Anthony Liguori
2009-01-05 16:21 ` Gleb Natapov [this message]
2009-01-05 15:38 ` Anthony Liguori
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=20090105162110.GA7803@redhat.com \
--to=gleb@redhat.com \
--cc=qemu-devel@nongnu.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).