Homelab

This is what a router is for. To communicate between clans.

This setup might work, if you get the routing right. Set the default Route to the interface where your internet is connected to. If it is a Windows be careful to set up only one default route (this gets wrong easy and is hard to catch)

But i would not recomment this setup, try to use a (virtual) firewall or at least a router and learn about trunks/tagging to avoid buying unnecessary nics.

This is what firewall ACL rules are for.

User your router to route between vlans. It will require you set up proper firewall rules. Then you can access it from any system you like.

Alternatively just pass the tagged traffic to your desktop and set them up to each have their own IP address on your main NIC. There really is no reason to have a NIC for each VLAN.

What is your current network setup? Where are these Vlans setup on?

This seems like an odd setup that you need to change IP's to access the different Vlans, if you have something that is capable of setting up Vlans, then it would be capable setting things up to allow access across Vlans?

If you don't want everything on the main network to access all areas, you could create a 5th Vlan that only certain devices like the device you use to check on everything sits on that has access across all areas of the network. I do this at home as the Wife and Kids devices sit on a separate network to my devices which can go anywhere they like.

You current nic may support VLAN trunking, so you could have multiple IP addresses on a single physical nic, so wouldn't need 4 physical interfaces.

But as the others said, use routing or a firewall to do this.

The way to do this with an L3 managed switch is to use inter-vlan routing and access control lists.

First part is simple enough, enable IP routing in the switch, then give your vlan interfaces an IP address.

To control which nets can talk to others you build ACLs and attach the policy to the vlan. For instance, you can permit your workstation on the main net to talk to anything on nets 2, 3, and 4, and conversely they can talk back to only your workstation if you wish. Then you can deny anything on nets 2 - 4 from talking to each other.

if they're all separate ip spaces and everything is directly connected and on linux it should work fine. directly connected is the best route. people are saying windows is weird so i believe them.

You change your IP address only and you have access to different devices?

Or you change your IP address and plug into a different switchport / switch / device?

If its the first, you're not running separate vlans, you're running separate subnets over the same layer2 network.