From: Tom Weber <pve@junkyard.4t2.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] More than 10 interfaces in lxc containers
Date: Mon, 24 Aug 2020 18:14:37 +0200 [thread overview]
Message-ID: <890269350b55f29457cd32bc35911a66ebcd36f3.camel@junkyard.4t2.com> (raw)
In-Reply-To: <494606189.360.1598284149700@webmail.proxmox.com>
Am Montag, den 24.08.2020, 17:49 +0200 schrieb Dietmar Maurer:
> > On 08/24/2020 12:54 PM Stephan Leemburg <sleemburg@it-functions.nl>
> > wrote:
> >
> >
> > On 24-08-2020 06:53, Dietmar Maurer wrote:
> > > > If I don't put a tag on the device, it seems to behave like a
> > > > trunk. So,
> > > > that would solve my problem. _If_ the hosts where openvswitch
> > > > enabled.
> > > I am unable to see why you need openvswitch for that? This also
> > > works with
> > > standard linux network.
> >
> > Hi Dietmar,
> >
> > Oh, that is new for me.
> >
> > So, I can have a vlan aware traditional bridge in the firewall
> > that
> > receives tagged frames and at the same time have the clients on
> > the
> > specific 'vlans' receive non-tagged frames for their respective
> > pvid?
> >
> > How can this be configured in Proxmox?
>
> You do not not any special config on the pve host if you do all VLAN
> related
> stuff inside the VM.
You do realize that Stephan is talking about CT not VM? (althought I
don't think such a setup makes sense)
Tom
next prev parent reply other threads:[~2020-08-24 16:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 21:41 Stephan Leemburg
2020-08-22 22:16 ` Stephan Leemburg
2020-08-23 5:03 ` Dietmar Maurer
2020-08-23 5:10 ` Dietmar Maurer
2020-08-23 10:58 ` Stephan Leemburg
2020-08-23 14:24 ` Dietmar Maurer
2020-08-23 15:04 ` Stephan Leemburg
2020-08-23 16:14 ` Stephan Leemburg
2020-08-24 4:53 ` Dietmar Maurer
2020-08-24 10:54 ` Stephan Leemburg
2020-08-24 15:49 ` Dietmar Maurer
2020-08-24 16:14 ` Tom Weber [this message]
2020-08-24 22:09 ` Stephan Leemburg
2020-08-27 11:19 ` Thomas Lamprecht
2020-08-23 15:49 ` Stephan Leemburg
2020-08-23 16:13 ` Tom Weber
2020-08-23 16:35 ` Stephan Leemburg
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=890269350b55f29457cd32bc35911a66ebcd36f3.camel@junkyard.4t2.com \
--to=pve@junkyard.4t2.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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal