this post was submitted on 15 Aug 2023
37 points (97.4% liked)

Selfhosted

39231 readers
362 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
37
WiFi setup (lemmy.omat.nl)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/selfhosted
9 comments fedilink hide all child comments
 

Hi,

I sometimes hear/read people putting their tv and other devices on a guest Wifi or even on a separate VLAN. Most guest WiFi's also have client isolation. I can understand that desire but I'm always wondering how that works in real life.

If you have a TV on a guest Wifi, how can you still cast things to it, as I assume your phone is on a different Wifi.

If you put your heating a different VLAN, how can you control the heating from your server that's on a different VLAN?

What's your setup in this regard. Is it worth to split? And what do you split and what not?

you are viewing a single comment's thread
view the rest of the comments
[–] youngerpants 1 points 1 year ago

This is what Layer 3 is for. You need to open the relevant port between vlans (e.g. TCP 443 for https) on the firewall. I think its UDP 1900 but may vary by appliance.

I'd also allow multicast, ICMP (ping) and DNS between your vlans as a minimum depending on what they're used for.