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.
You can’t use the same subnet on different vlans if you ever intend for both of them to reach the internet.
In that case you’d need a second router which just defeats the purpose
And to be clear about things, because that comment doesn’t make any sense for VLANs - a VLAN can contain multiple subnets. You will not have a single subnet across multiple VLANs.
The poster i was responding to equated subnetting to vlans. I might have misunderstood what they meant though. It sounded like they wanted to use the same subnet per vlan, which wont work if you want them routed in the same gateway.
Reading it again they make it sound like you can’t subnet all of these networks on a switch without vlan, which you definitely can.
I could for example connect 4 different devices on the subnet 192
168.10.x/24 and have them reach each other. I could also connect 4 more devices in the same switch but on a different network 192.168.20.x/24 and it would work.
You were responding to me, and I most definitely didn’t equate the two. Maybe you meant to respond to someone else.
In any case, you can route between vlans (and subnets), but without a route you aren’t communicating between those vlans or.between subnets.
Also, you can have multiple subnets in a vlan, but you can’t have a single subnet across vlans.
The range (x.x.10.x and x.x.20.x from your example) is only the subnet side, you could have both of those subnets in one vlan. But you could not, for example, have x.x.10.x/24 exist in vlan 10 and vlan 20.
Sorry about my confused rambling 😅
Yes, the example was to demonstrate the difference between subnetting and vlan. Albeit simplified. What you said is right.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
You can’t use the same subnet on different vlans if you ever intend for both of them to reach the internet. In that case you’d need a second router which just defeats the purpose
They are all defined as 192.168.x.y/24 Doesn’t this make them in different subnets?
Yes.
And to be clear about things, because that comment doesn’t make any sense for VLANs - a VLAN can contain multiple subnets. You will not have a single subnet across multiple VLANs.
Your config is fine in that regard.
You dont need to have the same subnet on different vlans. You also dont need them to each have a router, that isn’t how this works.
Each VLAN gets a gateway, in a subnet accessible within that VLAN.
Under no circumstances do you need a separate physical router for having 2 VLANs on the same network. That’s not how VLANs work.
The poster i was responding to equated subnetting to vlans. I might have misunderstood what they meant though. It sounded like they wanted to use the same subnet per vlan, which wont work if you want them routed in the same gateway.
Reading it again they make it sound like you can’t subnet all of these networks on a switch without vlan, which you definitely can. I could for example connect 4 different devices on the subnet 192 168.10.x/24 and have them reach each other. I could also connect 4 more devices in the same switch but on a different network 192.168.20.x/24 and it would work.
You were responding to me, and I most definitely didn’t equate the two. Maybe you meant to respond to someone else.
In any case, you can route between vlans (and subnets), but without a route you aren’t communicating between those vlans or.between subnets.
Also, you can have multiple subnets in a vlan, but you can’t have a single subnet across vlans.
The range (x.x.10.x and x.x.20.x from your example) is only the subnet side, you could have both of those subnets in one vlan. But you could not, for example, have x.x.10.x/24 exist in vlan 10 and vlan 20.
Sorry about my confused rambling 😅 Yes, the example was to demonstrate the difference between subnetting and vlan. Albeit simplified. What you said is right.