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.
Just throwing in the usual over-complication. The OP can do this with a simple OpenWRT router and by setting a few firewall rules. To be fair there are even some comercial routers from Asus and Netgear with their stock firmware that will allow you to block a device from accessing the internet.
Consumer routers fall apart when you want to do many common networking tasks, like setting up a VLAN on a separate subnet with pinhole access, so when faced with having to buy a significantly more expensive SMB router vs the cheap FOSS solutions others have mentioned, you’re better off just going the FOSS route.
Note: some consumer routers can be flashed with FOSS firmware, but be prepared to waste days tinkering and testing.
What you’re describing is not what the OP is asking for. He simply wants a quick solution to block a couple of devices from accessing internet.
I don’t get your “note” as that’s precisely what I suggested the OP to do. And if you actually read the manual and pick a recommend model it can be as simple as uploading the firmware using the router’s firmware upgrade feature.
The scenario you described can be done with OpenWrt on a consumer router and it isn’t that complex to setup. Even older hardware like the Netgear R7800 will be able to handle that.
OpenWRT and Untangle are the most user-friendly Linux options for running on your own hardware, but most people in homelab use pfsense or opnsense which are based on FreeBSD.
I do the exact same thing, only over PFSense (no issues with OPNSense at all, I just get along with PFSense better). 6 VLANs and 7 APs around the house, no VLAN can see the other, and all my "smart devices work exclusively local, and if I need to reach them from outside, I VPN into my house over WireGuard.
It sounds more complicated than it is. Once it’s all set up, it just works.
Put them all behind a firewall and configure it to block outgoing connections. Then forward the ports you need to the internal machines. Then only something connecting from the outside can talk to them. They won’t be able to initiate a connection.
(Keep in mind, this would also block things like DNS lookups, in case that’s important to you.)
There’s already some good answers here, just wanted to share my “solution”
I had a similar problem where I wanted some specific device to not have internet connection but still be on LAN. My lazy ass solution was to manually set the network settings with default gateway set to 0.0.0.0. With IPv6 it would be [::].
But this is not meant to be an advice. You may not even be able to manually set network settings on some of those IoT devices, and removing default gateway from DHCP server is not exactly an elegant solution. Perhaps you could set it to serve different settings based on MAC, but then the other solutions are perhaps simpler and better in some other way.
As I said, this is not an advice.
This one of those questions I am overwhelmingly eqipped to answer, but only with the weird proprietary knowledge about software defined networking and microsegmentation that my job has endowed me with…
So I’ll resist the urge to give you that overcomplicated answer and just say get a firewall like others have suggested.
I bought myself a mikrotik router to force myself to understand networking better. So I would really like to hear your over complicated answer that comes from professional needs. pretty please 🙂
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.
My router’s admin console, OOTB, gives me the option to either deny individual devices (based on MAC, etc.) access to the external internet, or create a second (or third, etc.) WiFi network that, itself, is not connected to the outside.
What’s your router? Can you install OpenWrt on it? OpenWrt provides a GUI for the firewall where you can set that a specific device won’t be able to access the internet with a few clicks.
If you want an OoTB solution you can get a Cloud Gateway from Ubiquiti (the ultra is like $200 I think) and use its vlan feature though you may need another switch.
Otherwise, if you’ve got unlimited time to tinker, proxmox or pfsense are ok options.
I personally run the UDM SE and I highly recommend this approach if you don’t want to roll it yourself.
I havent even bothered with it yet but my router has individual settings for internet access for devices. You can even set them in homeassistant. A other idea might be pihole since it works as dns in my home. But that also makes a lot of it absurd because the phone home function on a lot of these is blocked by pihole anyway.
You’d put a router with firewall capabilities in place of that cloud on the right. The devices you don’t want to have internet access will be put into a different subnet than your normal home LAN on the left. You’ll then make a “Deny all” rule so that the devices on the right can’t leave their subnet, with the exception of any explicit allow rules that you make.
This, pretty much - except you can do it with one router, the internet access point/gateway router.
Set up DMZ that can only access internal network, then set up a VPN and use that to access DMZ. If you need to, you can make a pinhole for one service or another, but you shouldn’t need to because they’re exposed to the LAN, and the LAN is accessible via VPN.
I suppose “DMZ” isn’t exactly the right term, there, because that’s typically somewhat exposed externally, but… …same idea, just no external exposure.
If you have an AVM Fritz!Box home router you can simply create a new profile that disallows internet access and set the devices you want to “isolate” to that profile. They will be able to access the local network and be accessed by the local network just fine, but they won’t have any outgoing (or incoming) connectivity.
Does the router creates the VLAN or the access points?
Also to achieve this I have to gave wiregaurd on a device connected to the internet right? I can’t install it on my home server if I wanted it disconnected from the internet, correct?
I was attempting this, but TP link doesnt actually care to tag their different SSIDs to vlans and don’t provide the configuration to, I only found that their guest may be tagged on some models. Just a word of caution, I think I’ll have to use IP range filters to achieve this
I know vlans is the answer, but I don’t know how to set it up. I really need to do this with my own network some day. There must be an OPNsense guide for this, I know it…
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).
For home, use your firewall. Either physical ports on the firewall with dumb switches or vlans with managed layer 2 switches.
There are many ways to do this. Proxmox can do it with ovs if all your devices are virtualized. Pfsense is probably the most straightforward.
The best way to run pfsense is on dedicated hardware. This would work for you https://protectli.com/vault-4-port/
You’ll also then need switches or a managed switch with vlans for each network segment.
Just throwing in the usual comment that OPNSense is a pfSense fork with a nicer interface.
Just throwing in the usual over-complication. The OP can do this with a simple OpenWRT router and by setting a few firewall rules. To be fair there are even some comercial routers from Asus and Netgear with their stock firmware that will allow you to block a device from accessing the internet.
Consumer routers fall apart when you want to do many common networking tasks, like setting up a VLAN on a separate subnet with pinhole access, so when faced with having to buy a significantly more expensive SMB router vs the cheap FOSS solutions others have mentioned, you’re better off just going the FOSS route.
Note: some consumer routers can be flashed with FOSS firmware, but be prepared to waste days tinkering and testing.
Just a few notes:
What you’re describing is not what the OP is asking for. He simply wants a quick solution to block a couple of devices from accessing internet.
I don’t get your “note” as that’s precisely what I suggested the OP to do. And if you actually read the manual and pick a recommend model it can be as simple as uploading the firmware using the router’s firmware upgrade feature.
The scenario you described can be done with OpenWrt on a consumer router and it isn’t that complex to setup. Even older hardware like the Netgear R7800 will be able to handle that.
Adding to that that you can also easily make a separate WiFi network (tied to a vlan even) for IoT. OpenWRT makes this very easy.
Pfsense and opnsense are also very good for this.
OPNSense for the win.
https://www.reddit.com/r/selfhosted/comments/17i1dns/pfsense_just_messed_with_their_userbase_again/?rdt=49503
Vlans firewall rules and something to route between the different networks.
This can all be achieved with pretty much every Linux installation.
deleted by creator
No, but your home server will. That’s what is needed.
Have your server firewalled and only communicate to your “no internet” devices via these ports.
Should be straightforward.
Are there any decent interfaces for configuring routing and vlans with linux these days?
OpenWRT?
OpenWRT and Untangle are the most user-friendly Linux options for running on your own hardware, but most people in homelab use pfsense or opnsense which are based on FreeBSD.
Hadn’t heard of untangle.
OPNsense is excellent. You can run it on a cheap mini PC with multiple Ethernet ports and it makes a great router. I run several VLANs through it.
Edit: It’s based on FreeBSD, not Linux, in case that matters to you.
Excellent, thanks!
I do the exact same thing, only over PFSense (no issues with OPNSense at all, I just get along with PFSense better). 6 VLANs and 7 APs around the house, no VLAN can see the other, and all my "smart devices work exclusively local, and if I need to reach them from outside, I VPN into my house over WireGuard. It sounds more complicated than it is. Once it’s all set up, it just works.
Put them all behind a firewall and configure it to block outgoing connections. Then forward the ports you need to the internal machines. Then only something connecting from the outside can talk to them. They won’t be able to initiate a connection.
(Keep in mind, this would also block things like DNS lookups, in case that’s important to you.)
There’s already some good answers here, just wanted to share my “solution”
I had a similar problem where I wanted some specific device to not have internet connection but still be on LAN. My lazy ass solution was to manually set the network settings with default gateway set to 0.0.0.0. With IPv6 it would be [::].
But this is not meant to be an advice. You may not even be able to manually set network settings on some of those IoT devices, and removing default gateway from DHCP server is not exactly an elegant solution. Perhaps you could set it to serve different settings based on MAC, but then the other solutions are perhaps simpler and better in some other way.
As I said, this is not an advice.
Vlan I think. Don’t quote me on it
he’s right, though. and a router between them.
vlans are not needed, but they are better than just using different ip ranges without physical seperation
I was just quoting COP because they said not to quote them
i know, still wanted to add something 🤷
install openwrt on you router.
most routers that arent garbage support it.
This one of those questions I am overwhelmingly eqipped to answer, but only with the weird proprietary knowledge about software defined networking and microsegmentation that my job has endowed me with…
So I’ll resist the urge to give you that overcomplicated answer and just say get a firewall like others have suggested.
Please don’t, if it wasn’t useful for me someone else might find it useful
https://lemmy.ml/comment/9601780
I bought myself a mikrotik router to force myself to understand networking better. So I would really like to hear your over complicated answer that comes from professional needs. pretty please 🙂
I was just looking into this for myself. Can I ask what you went with?
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.
My router’s admin console, OOTB, gives me the option to either deny individual devices (based on MAC, etc.) access to the external internet, or create a second (or third, etc.) WiFi network that, itself, is not connected to the outside.
Perhaps you have similar settings?
Mine doesn’t, what router are you using?
Asus RT-AC65
What’s your router? Can you install OpenWrt on it? OpenWrt provides a GUI for the firewall where you can set that a specific device won’t be able to access the internet with a few clicks.
My router doesn’t support OpenWrt, I’m planning on buying a new budget friendly one to support it
Thank you for the
If you want an OoTB solution you can get a Cloud Gateway from Ubiquiti (the ultra is like $200 I think) and use its vlan feature though you may need another switch.
Otherwise, if you’ve got unlimited time to tinker, proxmox or pfsense are ok options.
I personally run the UDM SE and I highly recommend this approach if you don’t want to roll it yourself.
I havent even bothered with it yet but my router has individual settings for internet access for devices. You can even set them in homeassistant. A other idea might be pihole since it works as dns in my home. But that also makes a lot of it absurd because the phone home function on a lot of these is blocked by pihole anyway.
You’d put a router with firewall capabilities in place of that cloud on the right. The devices you don’t want to have internet access will be put into a different subnet than your normal home LAN on the left. You’ll then make a “Deny all” rule so that the devices on the right can’t leave their subnet, with the exception of any explicit allow rules that you make.
This, pretty much - except you can do it with one router, the internet access point/gateway router.
Set up DMZ that can only access internal network, then set up a VPN and use that to access DMZ. If you need to, you can make a pinhole for one service or another, but you shouldn’t need to because they’re exposed to the LAN, and the LAN is accessible via VPN.
I suppose “DMZ” isn’t exactly the right term, there, because that’s typically somewhat exposed externally, but… …same idea, just no external exposure.
If you have an AVM Fritz!Box home router you can simply create a new profile that disallows internet access and set the devices you want to “isolate” to that profile. They will be able to access the local network and be accessed by the local network just fine, but they won’t have any outgoing (or incoming) connectivity.
I have a similar set-up
I use a wireless access point that can expose multiple ssid with different vlans (I think it a fairly common feature)
my router runs openwrt and the iot vlan is in a different firewall zone
use wireguard to remotely access the lan zone
Does the router creates the VLAN or the access points?
Also to achieve this I have to gave wiregaurd on a device connected to the internet right? I can’t install it on my home server if I wanted it disconnected from the internet, correct?
I was attempting this, but TP link doesnt actually care to tag their different SSIDs to vlans and don’t provide the configuration to, I only found that their guest may be tagged on some models. Just a word of caution, I think I’ll have to use IP range filters to achieve this
I know vlans is the answer, but I don’t know how to set it up. I really need to do this with my own network some day. There must be an OPNsense guide for this, I know it…