Selfhosted

61677 readers

144 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

VyOS or Opnsense (lemmy.world)

submitted 1 day ago by filister@lemmy.world to c/selfhosted@lemmy.world

12 comments fedilink hide all child comments

I read today about VyOS and I really like the idea and approach but I am not sure how it compares to Opnsense in terms of performance and features. I know it doesn't have a GUI, which is a bit of a bummer for me.

I have purchased a mini router PC and I was thinking to build a dedicated router and firewall on it. I also have another PC that I am planning to run as a Proxmox host and install a couple of VMs and LXC containers, as well as Home Assistant along with Omada, as I am thinking of purchasing some TP-Link AP compatible with Omada.

But would love to hear some feedback from people who used both what they think.

Keep in mind that although I am technical and have a fair understanding of networking and VLANs I am not exactly an expert in networking. Does it make sense to go into the VyOS route in that case?

The end goal is to have a dedicated network and routing for the IoT network, dedicated Wireguard, guest WiFi, etc.

you are viewing a single comment's thread
view the rest of the comments

[–] Pomal@sh.itjust.works 4 points 1 day ago (2 children)

Opensense is often bound by single-core operations depending on where a network packet may plumb itself through the kernel. A great example is any PPPoE connections on the base OS BSD. Vyos doesn’t have these same limitations since it’s minted on Linux - which supports traffic steering.

Really though, IaC for vyos has always been rock solid. Even though the persistent config in Opnsense is cool, adding new features or configs can be a bit of a pain in the ass

[–] irmadlad@lemmy.world 2 points 1 day ago* (last edited 1 day ago) (1 children)

Opensense is often bound by single-core operations depending on where a network packet may plumb itself through the kernel

Didn't downvote, but when would this become an issue? Pfsense is about the same way as far as single-core operations, tho IDS/IPS like Suricata can utilize multiple threads. My standalone pfsense box sits between my modem and the rest of the network. I haven't noticed any sluggishness or stuttering. Throughput seems quite reasonable, and supports a diverse group of devices attached to the network.

[–] Pomal@sh.itjust.works 3 points 1 day ago

I gave the example of PPPoE, the other option is to read the linked kernel docs to understand traffic steering and infer where those situations could occur.