Foolish discussion about connections and networks
Foolish discussion about connections and networks
You're asking some tricky networking questions. Let's break it down:
1. You can use 192.168.0.1 as the default gateway for all networks, even though they're on different subnets. You might need to set up additional gateways (10.1 and 20.1) if you want full control.
2. Yes, you should tag your VLAN IDs on WS2019 for proper segmentation.
3. Placing 0.0 on VLAN 1 makes sense for local devices, while 10.0 and 20.0 align with standard subnet practices.
4. Consider dropping the secondary DNS server if you're confident in using Google's DNS. Both servers point to the same providers, so it might not add value.
I won't connect to this network since it overlaps with many home setups, especially if you ever use a VPN or SIMmilr. Is server 2019 the router? Avoid Windows Server as a router. Each subnet has its own gateway IP address—I don’t know about tagged packets. I’ll skip 0, but that name makes sense. I prefer staying away from 0.0. Or consider using the 10.0.0.0/8 range. Why are you relying on your own DNS servers? Are you running Active Directory?
You're correct, they were initially set up on a 0.0 network, and I don't want to try to identify every device with static IP addresses right now. They're planning to upgrade switches and APs; if they proceed, I'll likely shift them to another scope. My apologies for the unclear phrasing earlier. Their router appears to be a Watchguard T30, though I'm open to other possibilities. I think they might retain it but could move it to a Sophos XG switch. I don't think I'll need to tag packets, but I'm aware their current switches require manual tag/untag/exclude. I'd prefer moving them outside the 192 range altogether, though we'll monitor AD usage and its longevity. They're transitioning mainly to Macs, and most of what I need can be handled on a Synology.