Hello,

Just spent a good week installing my home server. Time to pause and lookback to what I’ve setup and ask your help/suggestions as I am wondering if my below configuration is a good approach or just a useless convoluted approach.

I have a Proxmox instance with 3 VLAN:

  • Management (192.168.1.x) : the one used by proxmox host and that can access all other VLANs

  • Servarr (192.168.100.x) : every arr related software + Jellyfin (all LXC). All outbound connectivity goes via VPN. Cant access any VLAN

  • myCloud (192.168.200.X): WIP, but basically planning to have things like Nextcloud, Immich, Paperless etc…

The original idea was to allow external access via Cloudlfare tunnel but finally decided to switch back to Tailscale for “myCloud” access (as I am expected to share this with less than 5 accounts). So:

  • myCloud now has Tailscale running on it.
  • myCloud can now access Servarr VLAN

Consequently to my choice of using tailscale, I had now to use a DNS server to resolve mydomain.com:

  • Servarr now has pihole as DNS server reachable across all VLAN

On the top of all that I have yet another VLAN for my raspberry Pi running Vaultwarden reachable only via my personal tailscale account.

I’m open to restart things from scratch (it’s fun), so let me know.

Also wondering if using LXCs is better than docker especially when it comes to updates and longer term maintenance.

  • athes@lemmy.worldOPEnglish
    2·
    13 days ago

    Thx for the feedback, I don’t have multiple router no. If I had would it be still called VLAN? I thought the V was Virtual for achieving that LAN segmentation with one router. With one router, don’t you think the security added is the same level as configuring a firewall on each VM/LXC ?

    • just_another_person@lemmy.worldEnglish
      1·
      13 days ago

      Well it wouldn’t matter if your router is the thing that someone gets into. All you’re doing is separate traffic in different subnets, and if that’s your goal, you’re good to go.

      • curbstickle@lemmy.dbzer0.comEnglish
        2·
        13 days ago

        You are aware that a firewall rule is how you would address - in software, with logic - someone trying to get from VLAN C to VLAN A, right?

        That its part of the method you’d use as a layer of security to prevent someone gaining access to.your router?

        Assuming the router is compromised from the start is similarly just nutso.

          • curbstickle@lemmy.dbzer0.comEnglish
            2·
            13 days ago

            That’s not how any of this works… At all.

            No, its managed by the firewall. The existence of a VLAN does not grant it access to egress. The firewall needs to permit that behavior.

            Your entire understanding of how a logical network works is wrong. I’m not trying to be a dick - this is just really bad information that you’re sharing.

            • just_another_person@lemmy.worldEnglish
              2·
              13 days ago

              JFC 🤦

              How are you NOT understanding what OP thinks is happening, versus what you thinks is happening?

              If I get shell access to this router I have access to ALL NETWORKS. VLAN won’t help any of this.

              • curbstickle@lemmy.dbzer0.comEnglish
                3·
                13 days ago

                HOW WOULD YOU GET SHELL ACCESS TO HIS ROUTER FROM A FIREWALLED OFF VLAN THAT DOES NOT GAIN ACCESS TO THE MANAGEMENT VLAN THE ROUTER IS ON.

                Holy crap dude.

                BASIC networking.

              • curbstickle@lemmy.dbzer0.comEnglish
                1·
                13 days ago

                Thats my line.

                I’m also done having any sort of discussion with you, there is a fundamental misunderstanding of logical network design here, and I have no interest in correcting that. Enjoy your day.