6
Keeping "smart" devices on guest network
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 May 2025
6 points (100.0% liked)
Privacy
39217 readers
471 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
A better solution is to use a pihole to block all domains that the TV pings, and only let through ones that allow you to use streaming apps (i.e. netflix API domain.)
Another good solution is to block WAN access for specific devices and only allow them to communicate over LAN. This would be done on your Router. This method would allow local streaming using Jellyfin but wouldn't allow streaming apps like Netflix since that requires communication with the outside Internet.
If you're worried about your IoT devices on your LAN the problem isn't necessarily that they can access WAN but rather that there's a security vulnerability and that they can be accessed by the WAN. Once a device is compromised and attacker can then use it as a "beachhead" to access other devices on your network.
So for example, with my setup every IoT device is on a separate VLAN (the guest network acts similarly) which can't get access to WAN, can't be accessed from the WAN and can't initiate any network calls to any other VLAN. Now my primary VLAN can talk to my IoT VLAN, and IoT can talk back, it just can't start the communication.
This does pose a problem for TVs though that need to talk to Jellyfin as hinted at in the original post. So what you could do is create a specific firewall rule that allows the TVs to at least initiate communication to Jellyfin but not any other device on your primary VLAN. This will probably require a more sophisticated router though than most of the consumer ones out there. Just be mindful that if n IoT device is compromised they can then try to attack the jellyfin server to jump to your other VLAN and then the rest of your network.