mdns, casting and printers across vlans: the real headaches

Solvediotnetwork-designvlan7 replies · 186 views · started
Accepted solution by Kira A. — hmmm make sure your switches and access points support VLAN tagging before planning :D Unmanaged switches will pass tagged traffic…
  1. hmmmm ok we run a retail store with one flat network: PCs, the server, security cameras, everything. it works. but i keep reading that IoT devices are a big risk and should be isolated 🙏 is a separate VLAN worth the effort here, and what tends to break when you do it??

    budget is limited and so is my time 😅 if segmentation is worth it, Id like to do it once, proprely, without having to rebulid everything. experiences from ppl with similar setups would be really helpful here. thx in advance!!

    4
  2. been there man segmentation is worth it mainly cuz many door access controllers run old, rarely patched firmware. putting them on their own VLAN with firewall rules that block traffic toward staff networks limits what an attacker can reach from a compromised device.

    36 1 helpful
  3. finally got it working, thanks everyone u guys are the best!!!

    thumbsup

    2 0 helpful
  4. oof the minimum useful setup is three segments: staff, guest, IoT. Default deny from IoT to staff, allow staff to IoT only on the ports needed (for example, the camera NVR web UI or printing ports).

    thumbsup

    3 4 helpful
  5. this. so much this

    1 0 helpful
  6. hmmm make sure your switches and access points support VLAN tagging before planning :D Unmanaged switches will pass tagged traffic unpredictably or not at all. worked for me anyway 🤷

    0 5 helpful
  7. @kira_shader yesss isolated the security cameras, kept printers on teh staff side 🔥 Two small rules and everything still works. Thanks for the practical advice. cant believe it was that simple lol

    party

    4 0 helpful

Reply to this topic

Sign in or create an account to reply.