From: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Vmbr bridge permissions and SDN improvements?
Date: Mon, 7 Mar 2022 11:51:08 +0000 [thread overview]
Message-ID: <1537a6436d9966208f5cdc3741ad419134b17bc4.camel@groupe-cyllene.com> (raw)
In-Reply-To: <60b926a31d88487986c6743c35031822@chester.ac.uk>
Hi,
my patches from october are here
https://lists.proxmox.com/pipermail/pve-devel/2021-October/050211.html
(does somebody have time to review them ?)
Le vendredi 04 mars 2022 à 11:08 +0000, Neil Hawker a écrit :
> Hi,
>
> We're currently using version 7.1-10 and have the use case where we
> need to hide the vmbr bridges from normal users to prevent them
> circumventing network security that is applied through SDN vNets.
>
> For context, our setup is a Proxmox cluster that is used as a
> learning environment for students where they can create and manage
> their own VMs to practice their Cybersecurity skills in an isolated
> environment. Being able to hide the vmbr bridges from users would
> achieve this.
>
> I have found on the community forum
> (https://forum.proxmox.com/threads/sdn-group-pool-permissions.93872)
> that Spirit had contributed changes that have yet to be
> accepted/merged in that would achieve this as well as some SDN GUI
> improvements.
>
> I appreciate developers are very busy, but is it possible for Sprit's
> changes to be included in an upcoming version and if so, any rough
> idea when they might get released?
>
> Thanks
> Neil
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
prev parent reply other threads:[~2022-03-07 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 11:08 Neil Hawker
[not found] ` <48dda161-4379-c446-6e92-67dafaf92532@binovo.es>
2022-03-07 10:01 ` Neil Hawker
2022-03-07 11:51 ` DERUMIER, Alexandre [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=1537a6436d9966208f5cdc3741ad419134b17bc4.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=pve-devel@lists.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.