this post was submitted on 25 Mar 2024
6 points (80.0% liked)

Selfhosted

39964 readers
395 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Anyone tried it? I'm planning but saw the benchmark is pretty bad. Unsure if I interpret correctly.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 7 months ago

I think the default firewall rules allow all VLANs to talk to each other, so you have to add a rule to prevent that.

This traffic will go through the CPU (I think), so benchmarks are heavily dependent on hardware.

If traffic on two different VLANs needs to talk with high throughput, you might ask yourself why they're on different VLANs.

I have 2 cameras on their own VLAN and they're only allowed to talk to my NVR. The amount of traffic is pretty low and the CPU use is negligible, so I haven't bothered to put the NVR on that VLAN.