all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Lx Renner <lxr@lx-zone.net>
To: pve-devel@pve.proxmox.com
Subject: Re: [pve-devel] [PATCH pve-network 0/7] always use a vnet bridge model
Date: Fri, 22 Jan 2021 20:45:12 +0100	[thread overview]
Message-ID: <3B4E56CC-0C26-4DBE-8B0C-676B55A13A29@lx-zone.net> (raw)

Hi,

I saw you were working on pve networking.

 - https://lists.proxmox.com/pipermail/pve-devel/2020-May/043629.html

I have reported the following: https://forum.proxmox.com/threads/ovs-qinq-config.82894/

May I ask for your advice how to do that with the new model in pve to configure networking? i essence it is the typical example/use case many others have reported how to connect external devices and x-connect the traffic in an isolated manner over the physical switch and OVS to PVE hosted VMs.

Your help is very appreciated,
/Lx





                 reply	other threads:[~2021-01-22 19:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B4E56CC-0C26-4DBE-8B0C-676B55A13A29@lx-zone.net \
    --to=lxr@lx-zone.net \
    --cc=pve-devel@pve.proxmox.com \
    /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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal