general high-level discussion about spectrum
 help / color / mirror / Atom feed
From: Alyssa Ross <alyssa.ross@unikie.com>
To: Juha Park <Juha.Park@tii.ae>
Cc: "discuss@spectrum-os.org" <discuss@spectrum-os.org>
Subject: Re: Feature to bridge host network from netvm and other vm
Date: Wed, 23 Nov 2022 12:18:52 +0000	[thread overview]
Message-ID: <20221123121852.bpdr6nmk5em4uawd@x220> (raw)
In-Reply-To: <DX1P273MB0981C419E2C814147ABF8E66940C9@DX1P273MB0981.AREP273.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]

On Wed, Nov 23, 2022 at 07:41:00AM +0000, Juha Park wrote:
> Hello.
>
> In the spectrum OS, as far as I know, all appvms will connect to outside through netvm.
> And each appvm has different subnet.
> However, sometimes, a app should be able to access the host network by bridging.
> For example, an P2P app needs to send and receive multicast or broadcast to find other peers.
>
> I wonder if it(bridging to host network) is possible in spectrum OS model, and if possible,
> I want to know how to do it.
> And if there is no such feature, I want to know the plan or opinion to support such app in spectrum OS.

Hi, thanks for your question!

First, to clarify, in Spectrum, the goal is to avoid having any
networking on the host at all, by passing network adapters through to
VMs.  That's immaterial to your question about multicast, etc., just
something important to be aware of.

Bridged networking is definitely on the agenda.  I don't know yet
exactly how it will work — networking isn't my area of expertise.
As I understand it, one possibility would be to run an NDP proxy in the
network VM, so each VM would get its own IPv6 address on the host
network — as I recall, that's how Chrome OS does it.  But what exactly
we end up doing will depend on how people who understand networking
better than me (possibly such as yourself) think it should be done.

In general, I'm not too happy with the current state of Spectrum's
networking — I did it in the way that was easiest to get basic
functionality up and running, especially because a key technology for
doing it better (virtio-vhost-user) wasn't mature enough at the time.
Revisiting it is definitely on the cards, so it's really useful to hear
about use cases like this.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-11-23 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  7:41 Feature to bridge host network from netvm and other vm Juha Park
2022-11-23 12:18 ` Alyssa Ross [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=20221123121852.bpdr6nmk5em4uawd@x220 \
    --to=alyssa.ross@unikie.com \
    --cc=Juha.Park@tii.ae \
    --cc=discuss@spectrum-os.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).