homelab

6602 readers

1 users here now

founded 4 years ago

MODERATORS

My Homelab addiction took a turn for the worse today when I finally figured out how to do 802.11q on my switch. (lemmy.zip)

submitted 4 months ago* (last edited 4 months ago) by possiblylinux127@lemmy.zip to c/homelab@lemmy.ml

18 comments fedilink hide all child comments

Help I now have several lans

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

[–] Lem453@lemmy.ca 5 points 4 months ago (1 children)

The correct way of doing this is to never interact with an iot device directly. Put all of them on the same network with Home Assistant and then control all of them only via Home Assistant. Then you make one exception for home assistant to be accessible to the other networks.

This also allows you to disable Internet access for every single iot device Except home assistant.

[–] czardestructo@lemmy.world 1 points 4 months ago (1 children)

I have so much trash on my network. For instance my security cameras are decentralized and we use tinycam on android to view them so I had to allow an exception for rtsp to get between the dirty iot WiFi and our normal WiFi. Our WiFi connected Bose speakers and Spotify is also another set of annoyance, they will only work if you try to connect to them from the same subnet via Spotify and app. I've tried to NAT the traffic and it didn't work.

[–] Lem453@lemmy.ca 1 points 4 months ago

It's not easy but they only way to make it all work without creating massive security holes is to only buy things that allow connection with open standards (which means home Assistant can connect to it.