From: Jan Kiszka <jan.kiszka@web.de>
To: Alexander Graf <agraf@suse.de>
Cc: "Mark McLoughlin" <markmc@redhat.com>,
"Anthony Liguori" <aliguori@us.ibm.com>,
"René Rebe" <rene@exactcode.de>, "Gleb Natapov" <gleb@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Sascha Wilde" <wilde@intevation.de>
Subject: Re: [Qemu-devel] [PATCH] slirp: add 'cmd:' target for guestfwd
Date: Fri, 06 Jul 2012 01:56:57 +0200 [thread overview]
Message-ID: <4FF629C9.6030907@web.de> (raw)
In-Reply-To: <1338709501-7740-1-git-send-email-agraf@suse.de>
[-- Attachment #1: Type: text/plain, Size: 4554 bytes --]
On 2012-06-03 09:45, Alexander Graf wrote:
> When using guestfwd=, Qemu only connects the virtual server's TCP port
> to a single chardev. This is useless in most cases, as we usually want
> to have more than a single connection from the guest to the outside world.
>
> This patch adds a new cmd: target to guestfwd= that allows for execution
> of a command on every TCP connection. This leverages the same code as
> the -smb parameter, just that here the command is user defined.
>
> Reported-by: Sascha Wilde <wilde@intevation.de>
> Signed-off-by: Alexander Graf <agraf@suse.de>
>
> ---
>
> v1 -> v2:
>
> - rebase to current master
> - fix documentation
> ---
> net/slirp.c | 44 +++++++++++++++++++++++++++-----------------
> qemu-options.hx | 22 +++++++++++++++++++++-
> 2 files changed, 48 insertions(+), 18 deletions(-)
>
> diff --git a/net/slirp.c b/net/slirp.c
> index 96f5032..41cd058 100644
> --- a/net/slirp.c
> +++ b/net/slirp.c
> @@ -616,25 +616,35 @@ static int slirp_guestfwd(SlirpState *s, const char *config_str,
>
> fwd = g_malloc(sizeof(struct GuestFwd));
> snprintf(buf, sizeof(buf), "guestfwd.tcp.%d", port);
> - fwd->hd = qemu_chr_new(buf, p, NULL);
> - if (!fwd->hd) {
> - error_report("could not open guest forwarding device '%s'", buf);
> - g_free(fwd);
> - return -1;
> - }
>
> - if (slirp_add_exec(s->slirp, 3, fwd->hd, &server, port) < 0) {
> - error_report("conflicting/invalid host:port in guest forwarding "
> - "rule '%s'", config_str);
> - g_free(fwd);
> - return -1;
> - }
> - fwd->server = server;
> - fwd->port = port;
> - fwd->slirp = s->slirp;
> + if ((strlen(p) > 4) && !strncmp(p, "cmd:", 4)) {
> + if (slirp_add_exec(s->slirp, 0, &p[4], &server, port) < 0) {
> + error_report("conflicting/invalid host:port in guest forwarding "
> + "rule '%s'", config_str);
> + g_free(fwd);
> + return -1;
> + }
> + } else {
> + fwd->hd = qemu_chr_new(buf, p, NULL);
> + if (!fwd->hd) {
> + error_report("could not open guest forwarding device '%s'", buf);
> + g_free(fwd);
> + return -1;
> + }
> +
> + if (slirp_add_exec(s->slirp, 3, fwd->hd, &server, port) < 0) {
> + error_report("conflicting/invalid host:port in guest forwarding "
> + "rule '%s'", config_str);
> + g_free(fwd);
> + return -1;
> + }
> + fwd->server = server;
> + fwd->port = port;
> + fwd->slirp = s->slirp;
>
> - qemu_chr_add_handlers(fwd->hd, guestfwd_can_read, guestfwd_read,
> - NULL, fwd);
> + qemu_chr_add_handlers(fwd->hd, guestfwd_can_read, guestfwd_read,
> + NULL, fwd);
> + }
> return 0;
>
> fail_syntax:
> diff --git a/qemu-options.hx b/qemu-options.hx
> index 8b66264..ecf7ca1 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -1421,8 +1421,28 @@ Then when you use on the host @code{telnet localhost 5555}, you
> connect to the guest telnet server.
>
> @item guestfwd=[tcp]:@var{server}:@var{port}-@var{dev}
> +@item guestfwd=[tcp]:@var{server}:@var{port}-@var{cmd:command}
> Forward guest TCP connections to the IP address @var{server} on port @var{port}
> -to the character device @var{dev}. This option can be given multiple times.
> +to the character device @var{dev} or to a program executed by @var{cmd:command}
> +which gets spawned for each connection. This option can be given multiple times.
> +
> +You can either use a chardev directly and have that one used throughout Qemu's
> +lifetime, like in the following example:
> +
> +@example
> +# open 10.10.1.1:4321 on bootup, connect 10.0.2.100:1234 to it whenever
> +# the guest accesses it
> +qemu -net user,guestfwd=tcp:10.0.2.100:1234-tcp:10.10.1.1:4321 [...]
> +@end example
> +
> +Or you can execute a command on every TCP connection established by the guest,
> +so that Qemu behaves similar to an inetd process for that virtual server:
> +
> +@example
> +# call "netcat 10.10.1.1 4321" on every TCP connection to 10.0.2.100:1234
> +# and connect the TCP stream to its stdin/stdout
> +qemu -net 'user,guestfwd=tcp:10.0.2.100:1234-cmd:netcat 10.10.1.1 4321'
> +@end example
>
> @end table
>
>
Thanks, queued.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-07-05 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 7:45 [Qemu-devel] [PATCH] slirp: add 'cmd:' target for guestfwd Alexander Graf
2012-07-05 23:56 ` Jan Kiszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-04 6:12 Alexander Graf
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=4FF629C9.6030907@web.de \
--to=jan.kiszka@web.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=gleb@redhat.com \
--cc=markmc@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rene@exactcode.de \
--cc=wilde@intevation.de \
/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).