All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bilal Wasim <1724590@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1724590] Re: Usermode networking hostfwd only listens on IPv4
Date: Fri, 23 Aug 2019 14:15:13 -0000	[thread overview]
Message-ID: <156656971397.2597.5973308798225466710.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 150833765599.17635.13860559072232712887.malonedeb@gac.canonical.com

Hi Guys - I'm currently trying to use IPv6 with QEMU on ARM / AARCH64 Models (Sabre-Lite / Zync SOCs) and I see this problem. The system gets an IPv6 address from the QEMU in-built router which can be used to ping the default gateway (the dhcp router itself). All this is good but not really useful as I want to communicate with a TCP6 client on the host (Windows / Linux) machine running on port 8080. I've added the co-responding port mappings (like I do with IPv4) but I never receive packets from the host OS which is this issue. So I have the following questions, 
- It seems that this issue is still open and on the wishlist. Is this correct ? If so, is there any ETA to when someone will take this up ? If none, may be I can look at this ;-).. I'm currently using QEMU 3.0
- Assuming that its not working, what are the alternatives that I can use ? I understand that there is TAP-TUN Networking where the QEMU model can communicate with the hardware interface over a bridge.. This should work with IPv6.. Can you confirm ?

This needs quick closure on my side and so quick comments will be
appreciated..

Thanks, 
Bilal

-- 
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


  parent reply	other threads:[~2019-08-23 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 14:40 [Qemu-devel] [Bug 1724590] [NEW] Usermode networking hostfwd only listens on IPv4 Willem Mulder
2018-06-02  8:42 ` [Qemu-devel] [Bug 1724590] " Samuel thibault
2018-06-04  7:29 ` Thomas Huth
2019-08-23 14:15 ` Bilal Wasim [this message]
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=156656971397.2597.5973308798225466710.malone@chaenomeles.canonical.com \
    --to=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.