Our design is two routers an internal and external one, three subnets DMZ, SRVLAN and URSLAN. We set up two servers a web server running debian, a dns server, and a client running Ubuntu. The goal of this is to have a functional network where we can access our servers from our virtual desktop.
Illustration 1: Network Layer 2 Diagram
Illustration 2: Network Layer 3 Diagram
We are doing everything very lowkey and simple therefore there will be somewhat of a latency between the desktop and the servers. Everything is running thru virtual machines in VMWARE, and therefore we assign each device its own amount of both gb and rams no device reaching over 2 gb and over 512 gb ram
There is no hardware because everything is running virtually.
we are using these protocols DNS, HTTP, TCP, IP. With DNS being the most unknown of the 4, DNS (Domain Name System) which we are using on one of our servers. DNS basically translates a name to an IP address if for example I want to access www.google.com I type in the name www.google.com I could also have typed in its IP address 208.80.152.2 so what the DNS does I that when I enter www.google.com it translates it to the correct IP address 208.80.152.2 and sends you to the website.
| Network name | Gateway | Subnet | Connections |
|---|---|---|---|
| ROUTER-EXT | 10.0.0.1 | DMZ 10.0.0.0/24 | SERVER-DMZ-WEB 10.0.0.2 |
| ROUTER-INT | 192.168.1.1 | SRVLAN 192.168.1.0/24 | SERVER-SRVLAN-DNS 192.168.1.2 |
| ROUTER-INT | 192.168.0.1 | SRVLAN 192.168.0.0/24 | CLIENT-USRLAN 192.168.0.2 |
| ROUTER-EXT | 10.1.0.1 | 10.0.0.0/30 | ROUTER-INT 10.1.0.2 |
Naming convention is used by first defining the device type then what network it is on and last what service it uses. ROUTER-EXT, ROUTER-INT, SERVER-DMZ-WEB, SERVER-SRVLAN-DNS, CLIENT- URSLAN
images: Images for the documentationrecovery: The recovery documentationrouter-*: Configuration files for the routersserver-*: Configuration files for the servers
At the top level is a make file with the following rules:
- router-conf: Build the router configuration files from the Markdown formatted versions.
- recovery: Build a .pdf version of the recovery documentation.
- all: Build all.
To invoke any of these, use the make command:
make *rule name*
VMWare seems to configure its vmnet interfaces to use the .1 IP address of the
network that it is on. On Windows you can change this by changing the static IP
of each interface, the script linux_iface_setup.sh, does the same thing moving
the interfaces to .201 on Debian Linux. Your milage mat vary.