CAN201 Introduction to Networking

Coursework 2

Routing simulation

•    You should design only one app for a node, which is used to simulate the routing behavior of a router. For each app, it will start with the initial distance information of neighbors and IP addresses + port numbers of their neighbors. Each app should run without errors and load its own information.

•    Each app should implement UDP communication to exchange information with their neighbors. You should create a protoco to exchange distance vector information, as required by Bellman-Ford.

•    In order to simulate the group behaviors of routers, unfixed number of apps will be started. The starting order of nodes is not fixed.

•    Nodes should asynchronously exchange distance vector information as needed until the algorithm converges. After convergence, each node should output its distance vector table to a json file (one file per node with a given format).

Distance information of each node’s neighbors is stored in a json file named with the node name + “_distance”. (They are given, your apps should load them)

For Graph 1 in the right side, there are four json files to represent these four nodes:

Codes:

•    Python 3;

•    Your application can be implemented using multiple Python scripts;

•    But there is only one application.

A development report:

•    A cover page with your full name and student ID;

•    3~ 8 pages, single column, 1.5x line space, 2.54cm margins, Serif font1 , font size:12pt;

•    PDF format, LaTeX is recommended;

•    Including:

-   Abstract

-   Introduction: project requirement (do not copy from this document), background, literature review (try to find research papers, development reports or testing report of similar apps), and introduce what you did in this coursework;

-   Methodology: proposed protocols (using FSM or mind map), proposed functions and ideas;

-   Implementation: steps of implementation, program flow charts, programming skills (OOP, Parallel…) you used, what difficulties you met and how to solve them;

-   Testing and results: testing environment, testing plan and testing results (screenshot, tables or curves for showing performance)

-   Conclusion: what you did and why you did it. Future plan and so on.

-   Reference [IEEE format]

•    The file structure of your submission:

•    Only ZIP file is allowed to submit.

•    The starting Python script file should be named as “main.py”;

•    Run command: python3 main.py --node 3

1 Eg. Times New Roman, Modern No. 20 or Cambria.

2 It means that if you do not follow the compulsory requirement, your work will be marked as zero.

3 Eg. python3 main.py -- node x. Your app should open x_distance.json and x_ip.json and finally output x_output.json.

-   Well organized structure: 5%

-   Reasonable structure: 3% ~ 4%

-   Disordered structure: 0% ~ 2%

2.1. Abstract (2%)

- Appropriate abstract (2%)

- No abstract (0%)

2.2. Introduction (4%)

- Excellent (4%)

- Lack of necessary parts (1%-3%)

- No introduction (0%)

2.3. Methodology (6%)

- Excellent methodology: sufficient and accurate figures and text description (6%)

- Reasonable methodology: clear figures and text description (3%-5%)

- Incomplete methodology (1%-2%)

- No methodology (0%)

2.4. Implementation (7%)

- Excellent implementation: sufficientsteps of the implementation with proper figures or charts (7%)

- Reasonable methodology: clear steps of the implementation with figures or charts (4%-6%)

- Incomplete implementation (1%-3%)

- No implementation (0%)

2.5. Testing and results (8%)

- Excellent: sufficient testing plan for different cases, sufficient results to show the performance with proper analysis (7%-8%)

- Acceptable: clear testing plan, clear results to show the performance with analysis (3%-6%)

- Lack of testing plan, results or analysis (1%-2%)

- No testing and results (0%)

2.6. Conclusion and reference (3%)

- Excellent conclusion and reference with the correct format (2%-3%)

- Acceptable conclusion and reference (1%)

- No conclusion or incorrect reference (0%)

3.1. Report style and format (3%)

- Beautiful and clear typography: 3%

- Acceptable typography: 2%

- Bad typography: 0% ~ 1%

3.2. Language (2%)

- Accurate and concise language: 2%

- Unclear and confusing language: 0% ~ 1%

Code running environment:

•    The same virtual machine as CW1;

•    You have to test your app using the provided virtual machine without any modification;

• The app that cannot be executed properly in this virtual machine will be marked as zero.

Code testing steps:

1.    Your app (you have only one app with a single python file or multiple python files) will be run on only one virtual machine VM;

2.    Your app will be started in different terminals (run together, but maybe not start together):

python3 main.py --node                

python3 main.py --node               

python3 main.py --node

python3 main.py --node

python3 main.py --node

……

python3 main.py --node

3. Your apps can run without any error (RUN)

4. Each of your apps should be running until getting the final result and write to the corresponding json file (eg. u_output.json …) (RES4 = [RES1, RES2…RESn5]).