Hello, I’m planning on creating a home server and getting some cameras.
I would like to have the server, cameras and all IOT devices be disconnected from the internet but still be able to access them within the house from different devices and maybe have limited access to them when outside.
Do I need a specific hardware for this? And what router would support this? I’m still in the planning phase but I’m looking for budget friendly solutions.
I am most familar with HIP, but there are ways to isolate hosts so that they can only talk to what you want them to talk to in a distinctly different way than a firewall. You could have three hosts (A, B, & C) on the same subnet where A can talk to B & C, but B & C cannot talk to each other. Likewise, A and C could have access to an Internet gateway, while B does not.
So far HIP is the only protocol I have seen for microsegmentation that actually works in an intuitive way, but I suspect Wireguard could be used to the same effect with some creative engineering.
After looking through it a little bit, it sounds like HIP is mainly used for verifying hosts’ identities. It sounds like you’ll still need firewall rules in order to create the scenario in your example, right?
Not if HIP is a part of your network stack (adding a waist). Unfortunately this is not a plug-and-play solution unless you have the budget for my employer’s product, which is not priced for consumers.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
Oh man, uh, here’s a primer: https://mkomu.kapsi.fi/hipl/index.php?index=how
I am most familar with HIP, but there are ways to isolate hosts so that they can only talk to what you want them to talk to in a distinctly different way than a firewall. You could have three hosts (A, B, & C) on the same subnet where A can talk to B & C, but B & C cannot talk to each other. Likewise, A and C could have access to an Internet gateway, while B does not.
So far HIP is the only protocol I have seen for microsegmentation that actually works in an intuitive way, but I suspect Wireguard could be used to the same effect with some creative engineering.
After looking through it a little bit, it sounds like HIP is mainly used for verifying hosts’ identities. It sounds like you’ll still need firewall rules in order to create the scenario in your example, right?
Not if HIP is a part of your network stack (adding a waist). Unfortunately this is not a plug-and-play solution unless you have the budget for my employer’s product, which is not priced for consumers.