All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralph G <1887604@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1887604] [NEW] Forward host UNIX socket to guest TCP port
Date: Wed, 15 Jul 2020 03:51:04 -0000	[thread overview]
Message-ID: <159478506417.12547.6442940817184262205.malonedeb@soybean.canonical.com> (raw)

Public bug reported:

Hello. I've been racking my brain trying to work out if this is
possible.

I would like to be able to forward to a guest TCP port, via a host UNIX
socket to avoid opening a TCP port on the host. For example:

qemu-system-i386 [...] -nic user,hostfwd=unix:/path/to/socket-:22

and then connect to the VM like:

ssh -o "ProxyCommand socat - unix-connect:/path/to/socket" user@0.0.0.0

QEMU, as versatile as it is, doesn't appreciate my intuited syntax
"hostfwd=unix:...". It is also unhappy with:

qemu-system-i386 [...] \
    -chardev socket,id=foo,path=/path/to/socket,server,nowait \
    -nic user,hostfwd=chardev:foo-:22

And:

qemu-system-i386 [...] \
    -nic user \
    -chardev socket,id=foo,path=/path/to/socket,server,nowait \
    -chardev socket,id=foo,host=10.0.2.15,port=22

I already found out how to connect in the opposite direction, **from**
guest TCP to host UNIX, via guestfwd -> cmd -> socat. So I feel like
there ought to be a way.

If this is not yet a feature I would like to request it, and if it is,
please tell me how!

** Affects: qemu
     Importance: Undecided
         Status: New


** Tags: feature-request

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

Title:
  Forward host UNIX socket to guest TCP port

Status in QEMU:
  New

Bug description:
  Hello. I've been racking my brain trying to work out if this is
  possible.

  I would like to be able to forward to a guest TCP port, via a host
  UNIX socket to avoid opening a TCP port on the host. For example:

  qemu-system-i386 [...] -nic user,hostfwd=unix:/path/to/socket-:22

  and then connect to the VM like:

  ssh -o "ProxyCommand socat - unix-connect:/path/to/socket"
  user@0.0.0.0

  QEMU, as versatile as it is, doesn't appreciate my intuited syntax
  "hostfwd=unix:...". It is also unhappy with:

  qemu-system-i386 [...] \
      -chardev socket,id=foo,path=/path/to/socket,server,nowait \
      -nic user,hostfwd=chardev:foo-:22

  And:

  qemu-system-i386 [...] \
      -nic user \
      -chardev socket,id=foo,path=/path/to/socket,server,nowait \
      -chardev socket,id=foo,host=10.0.2.15,port=22

  I already found out how to connect in the opposite direction, **from**
  guest TCP to host UNIX, via guestfwd -> cmd -> socat. So I feel like
  there ought to be a way.

  If this is not yet a feature I would like to request it, and if it is,
  please tell me how!

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


             reply	other threads:[~2020-07-15  4:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15  3:51 Ralph G [this message]
2021-05-07  4:40 ` [Bug 1887604] Re: Forward host UNIX socket to guest TCP port Thomas Huth
2021-05-19 19:08 ` Ralph G
2021-05-21 12:16 ` Thomas Huth

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=159478506417.12547.6442940817184262205.malonedeb@soybean.canonical.com \
    --to=1887604@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.