I am worried that there is not really a benefit of doing that, just more noise and energy consumption.

  • Treczoks@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    11 months ago

    Why would you want to do this, anyway? Or, as I as a developer regularly have to ask our sales people: what do you actually want to achieve that led you to this question?

    • Ajen@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      11 months ago

      Here’s my use-case, I’m pretty sure the first 2 are pretty common (common enough to be supported by most OEM firmware):

      • main LAN
      • guest LAN (isolated from “main” but can access internet)
      • IoT LAN (isolated from internet, can be accessed from “main”; prevents devices from phoning home)
      • Treczoks@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        11 months ago

        But you don’t need several LANs for this. This can easily done with proper routing. A can access internet and internal network addresses. B can only access internet, and C can only reach internal addresses.