From: Bastian Sebode via pve-user <pve-user@lists.proxmox.com>
To: David der Nederlanden | ITTY <david@itty.nl>,
Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: Bastian Sebode <b.sebode@linet-services.de>
Subject: Re: [PVE-User] Mapping of VLAN tags to Linux bridges: Is that possible?
Date: Mon, 22 Jul 2024 21:28:49 +0200 [thread overview]
Message-ID: <mailman.630.1721676531.331.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <7de79cbf-90d0-40e2-87ec-dde2f6b21f0c@email.android.com>
[-- Attachment #1: Type: message/rfc822, Size: 4709 bytes --]
From: Bastian Sebode <b.sebode@linet-services.de>
To: David der Nederlanden | ITTY <david@itty.nl>, 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 21:28:49 +0200
Message-ID: <d3239b7f-8128-4358-a9f8-5f7eddad2d3e@linet-services.de>
Hi David,
thanks for the clarification. Off course it has to be done on all nodes.
I should have a closer look on SDN soon. ;-)
Regards
Bastian
On 22.07.24 21:23, David der Nederlanden | ITTY wrote:
> 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
--
Bastian Sebode
Fachinformatiker Systemintegration
LINET Services GmbH | Cyriaksring 10a | 38118 Braunschweig
Tel. 0531-180508-0 | Fax 0531-180508-29 | http://www.linet-services.de
LINET in den sozialen Netzwerken:
www.twitter.com/linetservices | www.facebook.com/linetservices
Wissenswertes aus der IT-Welt: www.linet-services.de/blog/
Geschäftsführung: Timo Springmann, Mirko Savic und Moritz Bunkus
HR B 9170 Amtsgericht Braunschweig
USt-IdNr. DE 259 526 516
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent 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
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 ` Bastian Sebode via pve-user [this message]
2024-07-22 18:39 [PVE-User] " 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=mailman.630.1721676531.331.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=b.sebode@linet-services.de \
--cc=david@itty.nl \
/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