 | |||||||||||
| |||||||||||
 |
|||||||||||
| |
| ||||||||||||||||
| ShaoLin Aptus 2.0 Installation and Operations Guide | ||
|---|---|---|
| Prev | Chapter 3. Planning your system and network | Next |
If you are migrating to Aptus in your existing network, you must read the following. This include issues with DHCP server, Windows networking and other networks.
If you have a DHCP server in the network, Aptus server can co-exists with other DHCP servers without interference, also Aptus clients will not listen to other DHCP servers as well. But for ease of centralized IP address management, we strongly recommend you to turn off your existing DHCP server because Aptus already got a build-in DHCP service. If you are running the old ISC-DHCP server version 2 which comes with most of the common Linux distributions, the old DHCP configuration file /etc/dhcpd.conf is compatible with Aptus, you will just need to copy the old /etc/dhcpd.conf to /etc/var/opt/aptus/var/opt/aptusd.conf then it will automatically recognize the old settings.
Some distributions such as Redhat 7.2 and 7.3 turn on a firewall by default. Since Aptus requires a trusted interface to connect to Aptus clients, that means you have to disable filtering for the interface that is connected to Aptus clients. You can still have your firewall on for other network interfaces.
If you would like to setup Aptus with a firewall, there are some consideration on the nfs mount daemon and you cannot use NIS to do user authentication. There are some discussion about setting up NFS with a firewall, please see the NFS Howto for more details.
By default, Aptus server uses NIS to authenticate users from Aptus clients. If you already have NIS server in the network, Aptus server can co-exists with other NIS servers in the network. Users can still authenticate to your original NIS server, and you can configure Aptus server to bind to your original NIS server. Modify the file /var/opt/aptus/mygroup/groupfs/etc/yp.conf or go to "Aptus Configurator" -> "NIS Client" to change the group or host setting. Note, you will have to disable NIS in "Aptus Configurator" -> "Module Config" (at the main page), set "use NIS" to "No".
If your existing Linux server is a terminal server, you can install Aptus in your server where Aptus and the terminal service can co-exists. If your terminal server is running a DHCP server, see Section 3.1.1.
Since most of the Unix support NFS, Aptus clients and server can use NFS mounts to access to existing Unix server's file systems. You may want to synchronize some security control with other Unix boxes using NIS.
Technically, Windows and DOS will live with Linux without interference. Aptus server can also serve Windows and DOS clients with Samba server, you may also use the Aptus server as a DHCP service for Window clients as well. However, Aptus use RPC (Remote procedure calls) with NFS (Network File Systems), which comes from a Unix background and assumes the network is friendly with secure ports. MS-Windows and DOS are single user OSes which does not have the concept of secure ports, see the Section 7.3 for more details.
