|
Re: Security Issues
You can also break the networks into 3 network ranges: say 192.168.0.0/24, 192.168.1.0/24, 192.168.2.0/24. Each of the subnets would use the exactly the same wire and computers on the same network IP number could and would only see others on their network. This filtering takes place in the network card diver or if you have a really smart network card in the hardware. Other network packets just aren't passed up the TCP/IP stack.
The problem comes with the server. You will have to configure the server to have multiple subnets on the same card. I know that Linux can do this and I'm sure the M$ can do it is well. I have not done this with M$, but have done it with Linux. The cards get a network ID of eth0:1, eth0:2 and so on. You could have the server forward packets from one network to another (and you would have to do something like this to get computers to get to the Internet). I call the multi-homed network cards, but I don't know if this is the correct term.
You could also do this by putting 3 network cards (more expensive) in your server and give each card its own subnet number 192.162.1.x, 192.168.3.x, etc. Any switch or hub will work because they just forward NIC numbers and not IP numbers.
|