Limitation of Wireless and Multiuser

One wireless flaw we en counted was errors. When configuring wireless on floor 2 & 4, we discovered that Packet Tracer would crash. This meant we were unable to configure these floors.

We also discovered when using the Browsers on a student PC, there is a time out. When trying to view Site 2's website, we could receive a timeout message. In a real scenario, this would be fixable.

The Packet Tracer Activity

In accompany to our network, we also have a Packet Tracer Activity.

What we have created is a simplified version of our Baratiwa network. This provides a challenge to configure a working network following the steps we have written.

Similar to tests we participate in networking, we have restricted and controlled the parameters. This can allow us to more precisely control what can and can't be done, from Graphic user interfaces to start-up configs and set-ups.

This give the user the chance to try Vtp, Dhcp, and the basic addressing & passwords. The end result is a working mini school network.

Finalised WAN connection

we finalised the wan setup yesterday with the internet simulation web server and host for testing, we also managed to get http services working between sites 2 and 3 with access to the other groups web server and their access to ours.

Gonna go in on Wednesday and hopefully get connectivity to site 1's website if they can get through their acl's

Final Presentation

Work has proceeded on creating the finalised version of our presentation.

This has been completely remade, but by using our past presentation & slides as ideas for what to include in this new one.

It is approximately twice as long as our prior presentation (slide-wise).

Report Writing

I've started preparing the basic template for our report to start with. Had to create a brand new document because the template supplied was so hard to work with. Using brand new styles in comparison to an original document and the supplied template.

Unfortunately, it is recommended that the report be written entirely in Microsoft Word because Google Documents does not understand the formatting. When converted, the report looks undesirable. 

At the moment, all that needs configuring on our report is the page numbers prior to the Table of Contents. Since it was thrown together in about 15 minutes of Sunday afternoon-ness, my abilities using Microsoft Word are somewhat hampered, so I have forgotten for the life of me how to change where the page numbers should start from 1. Maybe another 15 minutes worth of my Sunday can figure this out.

Change Log updates to District Network

I have added a change log to Google Drive where Tavita, Richard and myself can post the various changes to the packet tracer file for the District Network. Here is the latest changes to the district network:

## V0.4

• Did some housecleaning.
• Renamed Packet Tracer names of servers from ‘DomainNameServer’ to ‘DNS’ and from ‘RadiusServer’ to ‘RS’.
• Added notes describing addressing information for both DNS and RS servers.
• Named Frame Relay Cloud ‘FR_Cloud’.
• Regained access to EdgeRouter, removed old secret password + old message of the day and old login banners.
• Added note describing addressing information for both GigabitEthernet interfaces within server network.
• Added new encrypted enable password on EdgeRouter.
• Added new login and message of the day banners.
• Modified addressing information of interfaces that link to the CoreSwitch & Servers.

I have also included a 'To Do' list in the change-log. Perhaps a seperate document would be required for that? Otherwise I will create a page on this blog to accompany the 'To Do' list so that we can establish what still needs to be done on this network before it is finished. Until then, this is still what needs to be considered on this network before it is finished:

• Research multi-link for packet tracer. Possibly implement.
• Configure DNS to actually supply Domain Name information to clients on school network.
• Configure Radius server to actually supply login information for routers/switches on school & district networks.

Inter-connectivity

We collaborated with the other groups to connect the 3 networks together, as originally required in the aim.
The connections were later created in Packet Tracer by using a Frame-Relay cloud.

Adding a server to Baratiwa

We decided to relocate the server processes to a dedicated server, as opposed to running various services on the router.

We implemented the DHCP process on to the server. This reduces strain on the router. We also added a helper-address to make sure that DHCP continued to work.

For a test, we also enabled HTTP and a local DNS. This let us create a locally hosted website and translation. This is a similar idea to MIT's Cisco start page.

Access and security between sites

Site 1 & 2 to us (Admin)

Allow:

• Internet (Http, Https)
• Ping, Icmp (Between routers)
• DNS

Block:

• Telnet
• SSH
• Carpet Block (Block everything)

Other:

• NTP (Centralised time)

Sites 1 & 2 to the internet

Allow:

• Internet (Http, Https)
• FTP (Inwards)

Block:

• Remote connections (Telnet, Ssh, Rdp)
• Everything else

Packet Tracer - Physical Simulation

We discovered some of the realism to Packet Tracer and how it treats wireless.

As our building is multi-floored, we wanted to be able to show the physical layout of devices and their wireless coverage.

Packet tracer does not allow a building with more than one floor, so we created 5 individual buildings to represent each floor.

This let our building have good wireless coverage, without risk of channels overlapping and causing interference. 

One unexpected realistic part of packet tracer was the length of cable that can transmit. As each floor was linked to the Central switch via copper cabling, the connection would start to drop if the connection was more than 100 meters apart in physical view. To help alleviate this issue, we decided to put the Central switch and main router on floor 3, making floors 1 & 5 evenly far away.