All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willem Mulder <willemmaster@hotmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1724590] [NEW] Usermode networking hostfwd only listens on IPv4
Date: Wed, 18 Oct 2017 14:40:55 -0000	[thread overview]
Message-ID: <150833765599.17635.13860559072232712887.malonedeb@gac.canonical.com> (raw)

Public bug reported:

When forwarding ports in usermode networking (-net user,hostfwd=), QEMU
binds to IPv4 only. Therefore, connecting to the port over IPv6 results
in 'connection refused'.

I experienced this in QEMU 2.10.1, but it looks to still be present in
the current master (861cd431c99e56ddb5953ca1da164a9c32b477ca), since
slirp_hostfwd in net/slirp.c uses in_addr instead of in6_addr.

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1724590

Title:
  Usermode networking hostfwd only listens on IPv4

Status in QEMU:
  New

Bug description:
  When forwarding ports in usermode networking (-net user,hostfwd=),
  QEMU binds to IPv4 only. Therefore, connecting to the port over IPv6
  results in 'connection refused'.

  I experienced this in QEMU 2.10.1, but it looks to still be present in
  the current master (861cd431c99e56ddb5953ca1da164a9c32b477ca), since
  slirp_hostfwd in net/slirp.c uses in_addr instead of in6_addr.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1724590/+subscriptions

             reply	other threads:[~2017-10-18 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 14:40 Willem Mulder [this message]
2018-06-02  8:42 ` [Qemu-devel] [Bug 1724590] Re: Usermode networking hostfwd only listens on IPv4 Samuel thibault
2018-06-04  7:29 ` Thomas Huth
2019-08-23 14:15 ` Bilal Wasim
2021-04-22  4:08 ` Thomas Huth
2021-06-21  4:17 ` Launchpad Bug Tracker

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=150833765599.17635.13860559072232712887.malonedeb@gac.canonical.com \
    --to=willemmaster@hotmail.com \
    --cc=1724590@bugs.launchpad.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.