HybridSarcasm

joined 1 year ago
MODERATOR OF
[–] [email protected] 4 points 3 months ago

Leaving this post here since it's an interesting project to keep an eye on, but the conversation isn't constructive. So, locking the comments.

[–] [email protected] 1 points 3 months ago

Would they have to be VLAN aware if the switch port was already tagged AND if OP doesn’t care to consider untagged traffic ?

[–] [email protected] -2 points 3 months ago (1 children)

With the disclaimer that Proxmox has nothing to do with this question, I’m forced to assume this is just a networking issue that happens to use OPNsense as the router. Because of that, I must advise that you seek help from a networking-focused community. There’s no clear link to self-hosting in this post, which is required per Rule 3.

[–] [email protected] 4 points 3 months ago* (last edited 3 months ago) (7 children)

If the connections are already tagged as you come into the Proxmox server, then you need only to create interfaces for them in Proxmox (vmbr1, vmbr2, etc). EDIT: if you’re doing PCI passthrough of the physical NICs, ignore this step.

Then, in OPNsense, you just adding the individual interfaces. No need to assign a VLAN inside OPnsense because the traffic is already tagged on the network (per your earlier statement).

Whether or not the managed switch that has tagged each port is also providing VLAN isolation, you’ll simply use the OPNsense firewall to provide isolation, which it does by default. You’ll use it to allow the connections access to the fiber WAN gateway.

[–] [email protected] 22 points 4 months ago (2 children)

You’ll need to be far more descriptive than “I can’t get it to work.” I can almost guarantee you that Fedora is not the problem.

[–] [email protected] 1 points 4 months ago

I’m a little lost on how a container would mess with your boot loader (GRUB). That aside, most of what you’re explaining to do with the containers. These are OS-agnostic. What do the container logs tell you?

[–] [email protected] 10 points 4 months ago

This is really more of a home networking issue than anything having to do with self-hosting, especially since it centers on a consumer router. Please consider posting this in one of the many Lemmy home networking communities.

[–] [email protected] 3 points 4 months ago (1 children)

I’m going to allow this post, despite its age and likely obsolescence. I encourage community members to use up and down votes to judge its value to the community.

[–] [email protected] 1 points 4 months ago (1 children)

I am with you on the advantages of running it in a VM. The isolation a VM provides is really nice. Snapshots FTW.

[–] [email protected] 3 points 4 months ago (1 children)

That’s not a definitive support statement about Docker being unsupported. In fact, even in the Admin Guide, it only provides recommendations. The comment I replied said Docker is unsupported by Proxmox. I maintain that there is no such statement from Proxmox.

[–] [email protected] 3 points 4 months ago* (last edited 4 months ago) (6 children)

Proxmox is Debian at its core, which is supported by Docker. There’s no good reason to not run Docker on the bare metal in a homelab. I’d be curious to know what statement Proxmox has made about supporting Docker. I’ve found nothing.

view more: ‹ prev next ›