From: Maxim Samoylov <max7255@yandex-team.ru>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: [Qemu-devel] [PATCH RFC 4/4] net/slirp: add ipv6-hostfwd option for user netdev type
Date: Tue, 30 Oct 2018 17:00:26 +0300 [thread overview]
Message-ID: <f16cf85c-61ee-ed2a-f089-050fb32607aa@yandex-team.ru> (raw)
In-Reply-To: <ba3b8e2d-8d3a-b738-3d87-d56def3ab1e3@redhat.com>
On 26.10.2018 09:14, Thomas Huth wrote:
> On 2018-10-26 01:03, Maxim Samoylov wrote:
>> This allows forwarding TCP6 and UDP6 connections down to
>> netdev=user connected guests.
>>
>> Signed-off-by: Maxim Samoylov <max7255@yandex-team.ru>
>> ---
>> hmp-commands.hx | 31 ++++++++
>> include/net/slirp.h | 2 +
>> net/slirp.c | 214 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>> qapi/net.json | 3 +-
>> 4 files changed, 249 insertions(+), 1 deletion(-)
>>
>> diff --git a/hmp-commands.hx b/hmp-commands.hx
>> index db0c681..b0e1a08 100644
>> --- a/hmp-commands.hx
>> +++ b/hmp-commands.hx
>> @@ -1448,6 +1448,37 @@ STEXI
>> Remove host-to-guest TCP or UDP redirection.
>> ETEXI
>>
>> +#ifdef CONFIG_SLIRP
>> + {
>> + .name = "ipv6_hostfwd_add",
>> + .args_type = "arg1:s,arg2:s?,arg3:s?",
>> + .params = "[hub_id name]|[netdev_id] [tcp|udp]:[hostaddr6]:hostport-guestaddr6:guestport",
>> + .help = "redirect TCP6 or UDP6 connections from host to guest (requires -net user)",
>> + .cmd = hmp_ipv6_hostfwd_add,
>> + },
>> +#endif
>> +STEXI
>> +@item hostfwd_add
>> +@findex hostfwd_add
>> +Redirect TCP6 or UDP6 connections from host to guest (requires -net user).
>> +ETEXI
>> +
>> +#ifdef CONFIG_SLIRP
>> + {
>> + .name = "ipv6_hostfwd_remove",
>> + .args_type = "arg1:s,arg2:s?,arg3:s?",
>> + .params = "[hub_id name]|[netdev_id] [tcp|udp]:[hostaddr6]:hostport",
>> + .help = "remove host-to-guest TCP6 or UDP6 redirection",
>> + .cmd = hmp_ipv6_hostfwd_remove,
>> + },
>
> Hi,
>
> could you please remove the "[hub_id name]" touple here? I recently sent
> a patch to deprecate it for the IPv4 version, too:
>
> https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg03198.html
>
Ok
> Also I think it would make sense if you mention in the help text that
> IPv6 addresses have to be given with square brackets?
>
> Thanks,
> Thomas
>
Sure, missed that thing.
---
Maxim Samoylov, max7255@yandex-team.ru
next prev parent reply other threads:[~2018-10-30 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 0:03 [Qemu-devel] [PATCH RFC 0/4] slirp: support hostfwd for ipv6 addresses Maxim Samoylov
2018-10-26 0:03 ` [Qemu-devel] [PATCH RFC 1/4] slirp: add helper for tcp6 socket creation Maxim Samoylov
2018-10-27 11:11 ` Samuel Thibault
2018-10-27 11:13 ` Samuel Thibault
2018-10-30 13:58 ` Maxim Samoylov
2018-10-30 16:00 ` Samuel Thibault
2018-10-26 0:03 ` [Qemu-devel] [PATCH RFC 2/4] slirp: add helper for udp6 " Maxim Samoylov
2018-10-27 11:13 ` Samuel Thibault
2018-10-26 0:03 ` [Qemu-devel] [PATCH RFC 3/4] slirp: add helpers for ipv6 hostfwd manipulation Maxim Samoylov
2018-10-27 11:23 ` Samuel Thibault
2018-10-26 0:03 ` [Qemu-devel] [PATCH RFC 4/4] net/slirp: add ipv6-hostfwd option for user netdev type Maxim Samoylov
2018-10-26 6:14 ` Thomas Huth
2018-10-30 14:00 ` Maxim Samoylov [this message]
2018-10-27 11:38 ` Samuel Thibault
2018-11-05 23:05 ` Eric Blake
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=f16cf85c-61ee-ed2a-f089-050fb32607aa@yandex-team.ru \
--to=max7255@yandex-team.ru \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=thuth@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).