[Qemu-devel] [Bug 1724590] Re: Usermode networking hostfwd only listens on IPv4

[Bilal Wasim]

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