In the following Picture the architecture model that NITOS testbed relies on, is illustrated

NITOS architecture diagram

NITOS Server

One machine equipped with at least two ethernet ports, is the minimum requirement to start deploying your own testbed. For security reasons, the server-setup may be deployed on several machines.

Development Server

A development server relies on NITOS testbed intranet and its basic feature is to provide ease of use in source code development and compilation procedures. NITOS users can take advantage of that facility because Nitos-Dev has all the development versions of the packages that are used on the testbed node images, so the user does not have to download any extra software or check any version compatibilities.This is particularly convenient for wireless driver development because typically they have to get compiled against certain versions of the kernel source. On Nitos-Dev we have done all this work for the developers. The major motivation for building Nitos-Dev was to deal with file transfer latency. For example, click modular router executable is typically 11 MB in size. Changing code, recompiling and transferring the new executable can be very frustrating, if the link quality with the testbed’s front-end is not fast enough.

We use two [ D-Link DES1228P] PoE switches for wired connection between server and nodes.