Re: [PATCH v3] Add a feature for mapping a host unix socket to a guest tcp socket

[Samuel Thibault <samuel.thibault@gnu.org>]

Hello,

Viktor Kurilko, le lun. 04 août 2025 21:05:01 +0700, a ecrit:
> > Does that not behave oddly when given a path?
> 
> I didn't quite understand what you meant. If you mean that we try to parse the
> host address despite the fact that it doesn't make sense for a unix socket,

Yes.

> then I added a check that in the case of using a unix socket, the host
> address should be empty. As an alternative solution, I can suggest
> specifying the unix socket
> path in the host address place and omitting the port initialization in this case.

-serial uses:
              tcp:[host]:port[,server=on|off][,wait=on|off][,node‐
              lay=on|off][,reconnect-ms=milliseconds]
                     The TCP Net Console has two modes  of  operation.  It  can

              unix:path[,server=on|off][,wait=on|off][,reconnect-ms=millisec‐
              onds]
                     A unix domain socket is used instead of a tcp socket.  The

So I'd say we'd want to follow the same principle, i.e.

-hostfwd=unix:hostpath-[guestaddr]:guestport

BTW, your patch needs to update the various documentations of hostfwd,
so users now that it's now possible to use unix sockets.


Samuel