public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stephan Leemburg <sleemburg@it-functions.nl>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] More than 10 interfaces in lxc containers
Date: Sun, 23 Aug 2020 18:35:07 +0200	[thread overview]
Message-ID: <bd16d600-389b-fc24-df7a-8b05aa7ef6c5@it-functions.nl> (raw)
In-Reply-To: <9631e68f5947725e8c6cae3494872cf00df18569.camel@junkyard.4t2.com>

Am Sonntag, den 23.08.2020, 12:58 +0200 schrieb Stephan Leemburg:
>> Good afternoon Dietmar,
>>
>> The reason is separation of client's resources on the machine(s).
>>
>> In firewalling, it is not uncommon to use a lot of VLAN's.
>>
>> For example at one of my clients that I do consultancy for, they
>> have
>> more than 60 VLAN's defined on their firewall.
> probably not helping with your original Problem, but running (such) a
> firewall in a LXC feels totally wrong to me.
That is not my setup. The customer runs very expensive firewalls and all 
interfaces are vlan interfaces on top of link aggregations.
>
> Putting the FW in a VM is fine for me, but I surely don't want it to be
> a part of the hosts network stack.

Maybe I should reconsider my thought in migrating from a kvm that runs 
pfSense to a debian container that runs iptables in the same kernel and 
network stack as the node.

Thanks for your input. I will do some more research and educated thinking.

Best regards,

Stephan

>
> Regards,
>    Tom
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>



      reply	other threads:[~2020-08-23 16:35 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
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 [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=bd16d600-389b-fc24-df7a-8b05aa7ef6c5@it-functions.nl \
    --to=sleemburg@it-functions.nl \
    --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 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