HybridSarcasm

HybridSarcasm Mod , 1 day ago

Tailscale is an overlay network. It will use whatever networking is available. If only one of those NICs is a gateway, then that’s what will be used to reach remote Tailnet resources.

HybridSarcasm Mod , 5 days ago

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.

HybridSarcasm Mod , 5 days ago

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.

HybridSarcasm Mod , 5 days 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 ?

HybridSarcasm Mod , 13 days ago

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.

HybridSarcasm Mod , 13 days ago

https://perfectmediaserver.com/

HybridSarcasm Mod , 14 days 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?

HybridSarcasm Mod , 15 days 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.

HybridSarcasm Mod , 16 days ago

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.

HybridSarcasm Mod , 23 days ago (edited 23 days ago)

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.

HybridSarcasm Mod , 23 days ago

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.

HybridSarcasm Mod , 23 days ago

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

HybridSarcasm Mod , 1 month ago

Quick and easy fix attempt would be to replace the HDD with an SSD. As others have said, the drive may just be failing. Replacing with an SSD would not only get rid of the suspect hardware, but would be an upgrade to boot. You can clone the drive, or just start fresh with the backups you have.

HybridSarcasm Mod , 1 month ago

Check the ZFS pool status. You could lots of errors that ZFS is correcting.

HybridSarcasm Mod , 1 month ago

This community is not unmoderated, nor is it micromanaged. As has been shared in these comments, some members of this community appreciate these new release postings. If you don't, ignore/hide it and/or downvote it and move on.

HybridSarcasm , 1 month ago

Usually, the reason is HACS

HybridSarcasm Mod , 2 months ago

self-hosted doesn't have to mean 'hosted at home'

HybridSarcasm , 2 months ago

Holy shit. In a community where everything is meant to be funny/enjoyable, you people still find a way to shit in it. Who fucking cares about her politics? Go stir up shit somewhere else.

HybridSarcasm Mod , 3 months ago

If you really want to serve the self-hosting community, please improve your documentation. As someone unfamiliar with this product, I have no idea what to do with this once I clone the repo. I hunted and found a compose.yaml file, but it's not clear if this is all I need.

HybridSarcasm Mod , 3 months ago

Yeah, and it's so comprehensive.

yarn install
yarn dev

My point stands.

HybridSarcasm Mod , 3 months ago

It's a stub and almost worthless.

HybridSarcasm Mod , 3 months ago

Per rule #3, this seems to be a general home computing question and not centered around self-hosting. Please consider adding details to clarify how this involves self-hosting.

HybridSarcasm Mod , 3 months ago

Add another DNS server (1.1.1.1, for instance) to your DHCP options. Your DHCP clients will use 1.1.1.1 when the pi-hole isn’t responsive.

HybridSarcasm Mod , 3 months ago (edited 3 months ago)

Yes, your experience will be different if your DNS is being provided by another kind of DNS resolver. If you want a consistent pi-hole experience (and you can’t avoid downtime of your current pi-hole), add another pi-hole to your network and let that be your secondary DNS resolver.

HybridSarcasm Mod , 3 months ago

Except when the ONLY pi-hole is down, which was the original OP’s whole question.