Selfhosted

40152 readers

435 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

Initial steps with OPNSense (lemmy.world)

submitted 10 months ago by skipmorrow@lemmy.world to c/selfhosted@lemmy.world

10 comments fedilink hide all child comments

I am going to build a router with OPNSense (in Proxmox, on an HP thin client). I am stuck with setting up the networking (I have the Inel 4-port card). I don't really know how to get started. Right now my device has one LAN cable going into it, and my consumer router is doing everything. I can set up a bridge for the other ports, but what IP address will I use for the LAN? I can't use 192.268.0.1 because that will collide with my consumer router. Do I just take my consumer router offline while I am setting this up?I'd rather not because for sure I will get stuck and will want to look something up online. I guess I could use my phone but not the best when I am trying to see someone setting up something like this.

Silly question, I know, but I just can't think of a clean way to get this going with minimal disruption. In a nutshell, what's a good strategy for setting up and testing the OPNSense while it's not actually doing any routing and then seemlessly drop it in and start working on it?

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

[–] fuckwit_mcbumcrumble@lemmy.world 2 points 10 months ago

When I install a new router I do the initial install with all network connections disconnected (physically or virtually since it’s proxmox). Once I get my IPs and ports set how I want I do the switcherydoo and disconnect the old one and connect the new one.

If you’re using the same subnet and your router has the same IP address the only down time should be the process of connecting devices, and maybe a bit for DHCP on your wan side. All internal devices should continue working fine, but expect their IPs to jump around as they get new DHCP leases.