Selfhosted

40183 readers

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

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

what are the realistic requirements for opnsense? (lemmy.ca)

submitted 1 year ago* (last edited 1 year ago) by imaradio@lemmy.ca to c/selfhosted@lemmy.world

19 comments fedilink hide all child comments

I'm a pretty novice person considering installing opnsense for my personal home use.

Their documentation has what would seem to be incomplete hardware requirement.

For example it does not list any network hardware. I assume you need at least 1 Ethernet connection. I recall reading somewhere that you might need 2 network cards? One for in and one for out?

What about network card specs? I have old computers lying around that exceed the CPU/RAM/SSD requirements but cards are practically antiques. Should I upgrade? If so, to what?

ETA: The best internet I could subscribe to where I'm at is 1024 Mbps down, 50 Mbps up. So don't worry about wasting fibre speeds. :(

Does anyone know about a more thorough description of requirements?

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

[–] imaradio@lemmy.ca 1 points 1 year ago (1 children)

thanks for all the info!

i am definitely a person who will always change the defaults for no particular reason. so I appreciate the warning. except I don't quite know what you mean by "assignments". do you mean like the names? eth0? or their functions? I do like the idea of having a physical jack that's always guaranteed to allow access no matter what I foul up otherwise.

all these years I have been running my home network with a collection of routers just kind of attached together in a way that shouldn't work due to "double nat" according to everything I ever read, but it is pretty much functional if not at all optimized. maybe if you don't believe in double nat it won't happen to you.

[–] towerful@programming.dev 2 points 1 year ago

I've done crazy things and never had an issue with double nat. But that's all on small networks.

Assignment as in what opnsense is aware of.
Whether that is a physical NIC (NICs aren't assigned by default), virtual NICs (IE multiple vlans on a physical nic), or PPPoE/PPPoA/whatever

Watch a video of the install process, then watch a video of assigning additional interfaces.
They will be able to explain and show it to you better than I can type!