public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Gilberto Ferreira <gilberto.nunes32@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Mapping of VLAN tags to Linux bridges: Is that possible?
Date: Mon, 22 Jul 2024 16:27:57 -0300	[thread overview]
Message-ID: <CAOKSTBvyrxbMf2D9q6irgnjzTYX6CmS1m1-iwEgUB0viOxBuXw@mail.gmail.com> (raw)
In-Reply-To: <mailman.629.1721676254.331.pve-user@lists.proxmox.com>

Hi.
I also think with the SDN is a better way to go, if you want to replicate
the setting throughout the cluster.

Cheers
---


Gilbert



Em seg., 22 de jul. de 2024 às 16:24, David der Nederlanden | ITTY via
pve-user <pve-user@lists.proxmox.com> escreveu:

>
>
>
> ---------- Forwarded message ----------
> From: "David der Nederlanden | ITTY" <david@itty.nl>
> To: Proxmox VE user list <pve-user@lists.proxmox.com>
> Cc:
> Bcc:
> Date: Mon, 22 Jul 2024 19:23:34 +0000
> Subject: Re: [PVE-User] Mapping of VLAN tags to Linux bridges: Is that
> possible?
> Hi Bastian,
>
> This is a good way too indeed, but it has to be done on each node and be
> exactly the same, now with SDN you can manage this from a cluster
> perspective, which is a great advancement and makes it less complex (I
> think, as we manage it per VM).
>
> Kind regards
> David
>
> On 22 Jul 2024 21:18, Bastian Sebode via pve-user <
> pve-user@lists.proxmox.com> wrote:
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
>
> ---------- Forwarded message ----------
> From: "David der Nederlanden | ITTY via pve-user" <
> pve-user@lists.proxmox.com>
> To: Proxmox VE user list <pve-user@lists.proxmox.com>
> Cc: "David der Nederlanden | ITTY" <david@itty.nl>
> Bcc:
> Date: Mon, 22 Jul 2024 19:23:34 +0000
> Subject: Re: [PVE-User] Mapping of VLAN tags to Linux bridges: Is that
> possible?
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

  reply	other threads:[~2024-07-22 19:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6aee1ef2-47f5-4d1c-8600-88cd796be6e7@dkfz-heidelberg.de>
2024-07-22 19:18 ` Bastian Sebode via pve-user
2024-07-22 19:23   ` David der Nederlanden | ITTY via pve-user
2024-07-22 19:27     ` Gilberto Ferreira [this message]
2024-07-22 19:28     ` [PVE-User] [Extern] - " Frank Thommen
2024-07-22 19:27   ` Frank Thommen
2024-07-23 11:14     ` Stefan Radman via pve-user
     [not found]   ` <7de79cbf-90d0-40e2-87ec-dde2f6b21f0c@email.android.com>
2024-07-22 19:28     ` [PVE-User] " Bastian Sebode via pve-user
2024-07-22 18:39 David der Nederlanden | ITTY via pve-user
  -- strict thread matches above, loose matches on Subject: below --
2024-07-22 18:39 David der Nederlanden | ITTY via pve-user

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=CAOKSTBvyrxbMf2D9q6irgnjzTYX6CmS1m1-iwEgUB0viOxBuXw@mail.gmail.com \
    --to=gilberto.nunes32@gmail.com \
    --cc=pve-user@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal