linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Tiwei Bie <tiwei.bie@linux.dev>
To: development@efficientek.com
Cc: linux-um@lists.infradead.org, tiwei.bie@linux.dev
Subject: Re: No more non-root networking modes?
Date: Tue, 18 Nov 2025 14:08:55 +0800	[thread overview]
Message-ID: <20251118060855.3714863-1-tiwei.bie@linux.dev> (raw)
In-Reply-To: <20251117203131.479a1cfd@crass-HP-ZBook-15-G2>

On Mon, 17 Nov 2025 20:31:31 -0600, Glenn Washburn wrote:
> Hi all,
> 
> I'm just now noticing that earlier this year obsolete networking
> transports were removed (commit 65eaac591b75). This included SLiRP,
> which was to my knowledge the only transport that supported network
> access as an unprivileged user (no privileged access needed to setup
> the transport either). Am I wrong about that? If not, I'm curious as to
> why functionality that could not be achieved by other means was
> dropped? And if there are any work arounds? I can understand why other
> transports that need privileged access to setup, but were inferior to
> other existing transports would be removed. I write this as someone who
> is currently using the SLiRP transport.

vec also supports networking without privileged access:

https://www.kernel.org/doc/html/v6.17/virt/uml/user_mode_linux_howto_v2.html#vde-vector-transport
https://lore.kernel.org/all/bfa07f4d-16a3-476b-9314-b8052ec198b1@antgroup.com/

Regards,
Tiwei


      reply	other threads:[~2025-11-18  6:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18  2:31 No more non-root networking modes? Glenn Washburn
2025-11-18  6:08 ` Tiwei Bie [this message]

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=20251118060855.3714863-1-tiwei.bie@linux.dev \
    --to=tiwei.bie@linux.dev \
    --cc=development@efficientek.com \
    --cc=linux-um@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).