This was my initial synopsis of the desired server

1. Slackware Current Iso
2. Slackware Current Download

Server Design Plan

From the Manufacturer. Slackware Linux is an advanced OS, designed with twin goals, ease of use, and stability as top priorities. Features: Runs the 2.4.26 version of the Linux kernel from ftp.kernel.org. Special kernels were prepared to support hardware such as SCSI controllers, USB keyboards and mice, parallel-port IDE devices, IBM PS/2 machines with the Microchannel bus, and even speech. LxPupSc is available in both 32-bit and 64-bit flavours and is a version of LxPup built using Woof-CE with components from Slackware-Current, Ponce.cc, and Puppy Slacko-14.2. There are separate forum threads for LxPupSc and for LxPupSc64 LxPupSc downloads are hosted at SourceForge.

Overview/Scope

The Server should serve as a multifunctional in house hub which is capable of, but not limited to, Network Traffic Management, Firewall/Proxy Services, Web Services, VPN Services, IP Camera Management, Media Streaming, Multi Client Backup, Virtual Machine Hosting, and Mass Storage of Client Data.
As it will only be expected to serve 3 primary workstations and as many as 8 secondary clients, being an in-home server, the overall requirements should remain relatively low in comparison to most enterprise servers.

Hardware

Slackware Current Iso

Motherboard/Processor/Memory Reqs.
64-bit X4 Processor >= 3.2GHz
>= 16 Gb DDR 3 1600
PCIe 3.0
USB 3.0 / eSATA
SATA III
AMD-V / Intel VT (Virtualization Capability)

Networking Reqs.
>= X2 Gigabit Ethernet Adapters

Storage Reqs.
>= 1 128GB SATA III SSD
>= 3 1TB SATA III HDD*

1 3.5” Multi-Drive RAID Enclosure (must correspond to HDDs)

*These disks may be greater in size than 1TB and greater in number than 3, and may or may not be SSD’s, but they should ideally be identical

Power Reqs.

>= 400 watt PSU (main unit)

Cooling Reqs.
>= 2 250mm Fans
>= 2 120mm Fans

Software

Slackware Current Download

Operating System
Slackware 64-bit Linux Server

Services
dhcp-3 (Network Management)
iptables (Firewall)
Tor (Proxy)
Kippo (SSH Honeypot)
LAMP Server (Web)
OpenVPN (VPN)
ZoneMinder (IP Camera Management)
Plex (Media Server)
rsync (Backup)
KVM (Virtual Machine Hosting)
NFS (Mass Storage)
SSH (Administration)
SFTP (Administration)

Other Packages
/Slackware-64/D Package (Compilers & Dev Tools)
/Slackware-64/K Package (Linux Kernel Source)
multilib gcc & glibc (multi library support for 32-bit & 64-bit programs)

Implementation

Arrangement/Configuration
The main board, components, & primary SSD will reside in a single chassis/rack enclosure. The secondary network storage/backup hard disk array will be in a separately powered and cooled enclosure and connect with either an eSATA or USB 3.0 Depending on RAID hardware election. We will also mount/arrange various network devices and provide a system for surge protection and eventually temperature and voltage monitoring as well as a battery backup for the entire system.

Network Configuration
The major network components consist of the Cable Modem, one or more Gigabit Switch(es), one or more Wireless Access Point(s), CAT6e Ethernet Cables, several RJ45 Wall Plates, the Server, and multiple Client Devices.

The Physical Arrangement will bring the internet connection through a wired connection from the Cable Modem into the servers 1st NIC Device and out from the 2nd NIC Device into the switch, the switch will in turn be wired to the WAPs and Wall plates where it will subsequently provide access to the Client Devices through both wired and wireless connections. The use of CAT6e and Gigabit devices will ensure maximum internet throughput and LAN connection speed.

The Logical Arrangement of the network will have the server’s 1st NIC Device Acquire the external IP Address from the Cable Modem and Create one or more Domain(s) (DHCP) which will allow for the routing of traffic to multiple devices through the use of a static gateway IP assigned to the 2nd NIC Device and the assignment of internal IP Addresses of downstream devices. All traffic routed through the Server (In & Out) will be filtered through the Firewall, and depending on the connection, a proxy service.

Services