John, It is possible: There are two scenarios: 1. You want the IP-addresses to coexist on the same physical network, or 2. You set up a separate physical network for the 192-space. This requires an extra NIC into your server. Now, there are a couple of IF's: - If you want the terminals to get their addresses via DHCP you'd better go for alternative 2, but if you use static addresses there are no issues. - If you want your terminals to have access to other systems (on the 212-network, the internet, etc.) you need to start routing in your server. Here we go: 1. Assuming static addresses, access to external systems required. - Configure a secondary IP-address to your current NIC in the server, e.g. 192.168.0.1/255.255.255.0 - Switch on routing in your server (use Yast2, for instance). - In your terminals: set their addresses to 192.168.0.2 -3 -4 etc. and the default gateway to 192.168.0.1 (i.e. the server's address). That's all you need to do. 2. Assuming DHCP, access to external systems required. - Add another Ethernet NIC to your server - Configure it's IP address: e.g. 192.168.0.1/255.255.255.0 - Switch on routing (Yast2) - Set up the DHCP server daemon (see the Howto's) to distribute addresses from 192.168.0.2..254, mask 255.255.255.0 and Gateway 192.168.0.1, and start it. That's it. (Of course this second example goes for static addresses as well.) As your terminals today are on the 212-network I assume that you do not need to run a Firewall in the server, but if that is required you can use Firewall2. HTH /Henrik
participants (1)
-
Hahnsson Henrik