JakeHillion/dissertation-0-project-proposal
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

removed DHCP, added more chapters

Browse Source
This commit is contained in:
Jake Hillion 2020-10-20 15:28:41 +01:00
parent 113351006e
commit a9885f35f0
1 changed files with 11 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
project-proposal.tex
View File

@ -89,8 +89,6 @@ To achieve this congestion control, I will initially use TCP flows, which includ
When the Local Server has a packet it wishes to send outbound, it will place the packet and some additional security data in a queue. The multiple congestion controlled links will each be consuming from this queue when they are not congested. This will cause greedy load balancing, where each connection takes all that it can get from the packet queue. As congestion control algorithms adapt to the present network conditions, this load balancing will alter the balance between links as the capacity of each link changes.
To make integration of this solution as simple as possible, the Local Server will endeavour to provide a DHCP server on the client interface. This will allow the client to automatically configure its IP, as is often the case with an ISP.
Security is an important consideration in this project. Creating a multipath connection and proxies in general can create additional attack vectors, so I will perform a review of some existing security literature for each of these. However, as the tunnel created here transports entire IP packets, any security added by the application or transport layer will be maintained by my solution.
The structure of the Wireguard project is also a good fit for this project. The elements are presented as follows:
@ -136,8 +134,8 @@ A sample network is provided in Figure \ref{fig:sample-network-session-based}.
\node[squarednode] (modemb) [below right=0.5 and 1 of natrouter] {Modem B};
\node[squarednode] (webserver) [above right=0.25 and 1 of modema] {Web Server};
\node[squarednode] (voipserver) [right=of modema] [below=of webserver] {VoIP Server};
\node[squarednode] (vpnserver) [right=of modemb] [below=of voipserver] {Corporate VPN};
\node[squarednode] (voipserver) [below right=0.25 and 1 of modema] {VoIP Server};
\node[squarednode] (vpnserver) [below right=1.75 and 1 of modema] {Corporate VPN};
% Edges
\draw[->] (client.east) -- (natrouter.west);
@ -232,8 +230,10 @@ Milestone: A virtual router acting as a virtual Internet for these tests. 3 stan
This section should focus on the security of the application. This would include the ability for someone to maliciously use a Remote Server to perform a DoS attack.
Draft the introduction chapter.
\noindent \\
Milestone: An analysis of how the security of this solution compares, both with other multipath solutions and a network without any multipath solution applied.
Milestone: An analysis of how the security of this solution compares, both with other multipath solutions and a network without any multipath solution applied. A drafted introduction chapter.
\subsection*{30/11/2020 - 20/12/2020 (Weeks 8-10)}
@ -244,10 +244,10 @@ Milestone: A piece of software that can act either as the Local Server or Remote
\subsection*{21/12/2020 - 10/01/2021 (Weeks 11-13)}
Create mock connections for tests that support variable speeds, a list of packet numbers to lose and a number of packets to stop handling packets after. Produce the first draft of the preparation chapter.
Create mock connections for tests that support variable speeds, a list of packet numbers to lose and a number of packets to stop handling packets after. Finalise the introduction chapter. Produce the first draft of the preparation chapter.
\noindent \\
Milestone: Mock connections and tests for the existing single transport. A draft of the preparation chapter.
Milestone: Mock connections and tests for the existing single transport. A finalised introduction chapter. A draft of the preparation chapter.
\subsection*{11/01/2021 - 07/02/2021 (Weeks 14-17)}
@ -260,19 +260,17 @@ Milestone: The Local Server and Remote Server are capable of balancing load betw
\subsection*{08/02/2021 - 21/02/2021 (Weeks 18-19)}
Implementation of a DHCP server for the Local Server. This should create a DHCP pool with a single address, that of the Remote IP.
As well as code in this period, it is important to complete the preparation chapter, and complete a solid draft of the implementation chapter of the dissertation.
Finalise the drafted preparation chapter. Draft the implementation chapter. Produce a non-exhaustive list of graphs and tests that should be included in the evaluation section.
\noindent \\
Milestone: The router behind the Local Server should automatically receive the Public IP of the Remote Server from DHCP. The dissertation should have a completed preparation chapter, and an acceptably drafted implementation chapter.
Milestone: Completed preparation chapter. Drafted implementation chapter. A plan of data to gather to back up the evaluation section.
\subsection*{22/02/2021 - 21/03/2021 (Weeks 20-23)}
Complete dissertation.
Finalise the implementation chapter. Gather the data required for graphs. Draft the evaluation chapter. Draft the conclusions chapter.
\noindent \\
Milestone: Benchmarks and graphs for non-extended success criteria complete and added. Complete dissertation draft handed to DoS and supervisor for feedback.
Milestone: Finalised implementation chapter. Benchmarks and graphs for non-extended success criteria complete and added. First complete dissertation draft handed to DoS and supervisor for feedback.
\subsection*{22/03/2021 - 25/04/2021 (Weeks 24-28)}