LAN5 to LAN3 IP

[Vilhonator]

Oh and I use 192.168.1.1 etc as an example.

You can use any IP range which is reserved for private networks, 192.168.1.0/24 is just most common. https://www.ionos.com/help/server-cloud-infrastructure/private-network/private-ip-address-ranges/ <---- you can use any of ranges in question for private networks

[Ice_Drake1]

If your server needs access to different networks and you want to restrict access from certain computers, that's easy thing to solve.

If you want to avoid having to buy expensive multiport server NIC, check if it's current one supports IEE 802.1Q (That's standard VLAN Tag support), setup a VLANs on the switch and on the server and that's it.

Downside to that is, you need to setup VLANs (if you haven't) which isn't that hard but it is alot of work.

Yeah, troubleshooting VLANs is even more of a pain. I had an issue where I forgot to place a VLAN to a trunk port. It causes a particular untagged port at the other end has no connection to its DHCP server. I spend hours trying to figure why that is the case. I eventually realize that I was looking at the wrong place.

I used to setup the server as VM with three separate ethernet ports - one for each network. Now that I replaced that server with a physical one. I only have one port. Since I don't think I can setup that port as VLAN trunk, I end up giving that server special network access to the other devices on the other networks.

[Vilhonator]

If your server needs access to different networks and you want to restrict access from certain computers, that's easy thing to solve.

If you want to avoid having to buy expensive multiport server NIC, check if it's current one supports IEE 802.1Q (That's standard VLAN Tag support), setup a VLANs on the switch and on the server and that's it.

Downside to that is, you need to setup VLANs (if you haven't) which isn't that hard but it is alot of work.

Yeah, troubleshooting VLANs is even more of a pain. I had an issue where I forgot to place a VLAN to a trunk port. It causes a particular untagged port at the other end has no connection to its DHCP server. I spend hours trying to figure why that is the case. I eventually realize that I was looking at the wrong place.

I used to setup the server as VM with three separate ethernet ports - one for each network. Now that I replaced that server with a physical one. I only have one port. Since I don't think I can setup that port as VLAN trunk, I end up giving that server special network access to the other devices on the other networks.

Check the model of network chip that server has, many of them have VLAN support. If you bought Workstation or server grade motherboard (AsrockPro, Asus Prime, Creator or WS and supermicro motherboards are ones I know are workstation and server motherboards) or actual server, their built in network chips do have VLAN support.

Nowadays pretty much any modern motherboard network chips have VLAN support

[Vilhonator]

Also if you use intel motherboard which has ECC RAM support, then it definetly has network chip with vlan support.

All intel motherboards which support ECC ram are designed for servers and workstations