/Recent content in CS 4700 Network Fundamentals on CS 4700Hugoen-USCopyright (c) 2020-2024 ThuliteWed, 25 Aug 2021 15:24:08 -0400/docs/syllabus/Wed, 25 Aug 2021 15:23:30 -0400/docs/syllabus/<h2 id="course-description">Course Description</h2> <p>Computer networking is a rapidly advancing field, and the Internet is already an integral part of society. It is therefore important for computer scientists and computer engineers to be familiar with the fundamentals of computer networking. This course will focus on the <ins>architecture, algorithms, and protocols of the Internet</ins>. Topics include local area networking, routing, congestion control, network security, and applications such as peer-to-peer and content distribution networks. This course will be systems oriented, and students will work on hands-on projects to learn how to build and understand Internet applications.</p>/docs/schedule/Wed, 25 Aug 2021 15:23:42 -0400/docs/schedule/<p>Note on the readings: the section (§) symbol refers to chapters from the <em>Computer Networks: A Systems Approach</em> textbook.</p> <table class="table-striped table-hover table-sm small"> <thead> <tr> <th>Week of</th> <th>Slides</th> <th>Readings</th> <th>Homework</th> <th>Projects &amp; Exams</th> </tr> </thead> <tbody> <tr> <td>Jan. 7-9</td> <td><a href="/slides/Intro.pptx">Intro</a>, <a href="/slides/History.pptx">History</a></td> <td>§1.1-1.6, 2.1-2.3, <a href="https://beej.us/guide/bgnet/html/">Beej&rsquo;s Guide</a></td> <td></td> <td></td> </tr> <tr> <td>Jan. 12-16</td> <td><a href="/slides/Architecture.pptx">Architecture</a>, <a href="/slides/Physical.pptx">Physical Layer</a></td> <td>§2.4-2.8</td> <td></td> <td></td> </tr> <tr> <td>Jan. 20-23</td> <td><a href="/slides/Data_Link.pptx">Data Link Layer</a></td> <td>§3.1, 3.4</td> <td></td> <td><a href="/docs/projects/project-1-socket-basics/">Proj. 1</a> due Jan. 20</td> </tr> <tr> <td>Jan. 26-30</td> <td><a href="/slides/Bridging.pptx">Bridging and Switching</a></td> <td>§3.2-3.3</td> <td>Hw. 1 due Jan. 30</td> <td></td> </tr> <tr> <td>Feb. 2-6</td> <td><a href="/slides/Network.pptx">Network Layer</a></td> <td>§4.1</td> <td>Hw. 2 due Feb. 6</td> <td><a href="/docs/projects/project-2-ftp-client/">Proj. 2</a> due Feb. 3</td> </tr> <tr> <td>Feb. 9-13</td> <td><a href="/slides/Intra_Domain_Routing.pptx">Intra-domain Routing</a>, <a href="/slides/Inter_Domain_Routing.pptx">Inter-domain Routing</a></td> <td>§5.1-5.2</td> <td>Hw. 3 due Feb. 13</td> <td></td> </tr> <tr> <td>Feb. 17-20</td> <td><a href="/slides/Transport.pptx">Transport Layer</a></td> <td>§6.1-6.4</td> <td>Hw. 4 due Feb. 20</td> <td></td> </tr> <tr> <td>Feb. 23-27</td> <td><a href="/slides/Congestion_Control.pptx">Congestion Control</a></td> <td>§9.1, 9.3, 9.4;</td> <td>Hw. 5 due Feb. 27</td> <td><a href="/docs/projects/project-3-bgp-router/">Proj. 3</a> due Feb. 24</td> </tr> <tr> <td>Mar. 2-6</td> <td><strong>Spring Break</strong></td> <td></td> <td></td> <td></td> </tr> <tr> <td>Mar. 9-13</td> <td><strong>Midterms</strong>, <a href="/slides/NAT.pptx">NAT</a></td> <td></td> <td></td> <td></td> </tr> <tr> <td>Mar. 16-20</td> <td><a href="/slides/DNS.pptx">DNS</a></td> <td></td> <td></td> <td><a href="/docs/projects/project-4-reliable-transport-protocol/">Proj. 4</a> due Mar. 17</td> </tr> <tr> <td>Mar. 23-27</td> <td><a href="/slides/Bootstrapping.pptx">DHCP and ARP</a></td> <td></td> <td>Hw. 6 due Mar. 27</td> <td></td> </tr> <tr> <td>Mar. 30-Apr. 3</td> <td><a href="/slides/Web.pptx">Web</a></td> <td><a href="https://www.npr.org/2022/11/18/1137657496/third-party-cookie-data-tracking-internet-user-privacy">How the cookie became a monster</a></td> <td>Hw. 7 due Apr. 3</td> <td></td> </tr> <tr> <td>Apr. 6-10</td> <td><a href="/slides/TLS.pptx">Transport Layer Security</a></td> <td></td> <td>Hw. 8 due Apr. 10</td> <td><a href="/docs/projects/project-5-web-crawler/">Proj. 5</a> due Apr. 7</td> </tr> <tr> <td>Apr. 13-17</td> <td><a href="/slides/DNS_Security.pptx">DNS Security</a></td> <td></td> <td>Hw. 9 due Apr. 17 (<strong>slip day use prohibited</strong>)</td> <td></td> </tr> <tr> <td>Apr. 20-24</td> <td><strong>Final: 3:30 - 5:30pm</strong></td> <td></td> <td></td> <td><a href="/docs/projects/project-6-dns-server/">Proj. 6</a> due Apr. 21 (<strong>slip day use prohibited</strong>)</td> </tr> </tbody> </table>/docs/projects/project-1-socket-basics/Wed, 25 Aug 2021 15:24:08 -0400/docs/projects/project-1-socket-basics/<div class="alert alert-info" role="alert"> <b>This project is due at 11:59pm on January 20, 2026.</b> </div> <h2 id="description">Description</h2> <p>This assignment is intended to familiarize you with writing simple network code. You will implement a client program that plays a variant of the recently-popular game <a href="https://www.powerlanguage.co.uk/wordle/">Wordle</a>. Your program will make guesses for the secret word, and the server will give you information about how close your guess is. Once your client correctly guesses the word, the server will return a <em>secret flag</em> that is unique for each student. If you receive the <em>secret flag</em>, then you know that your program has run successfully.</p>/docs/projects/project-2-ftp-client/Wed, 25 Aug 2021 15:24:08 -0400/docs/projects/project-2-ftp-client/<div class="alert alert-info" role="alert"> <b>This project is due at 11:59pm on February 3, 2026.</b> </div> <h2 id="description">Description</h2> <p>The goal of this project is to deepen your ability to write network code. At this point you can open a socket and send and receive simple messages. In this project, you will implement a client for a more complex protocol, that has more features, and uses two sockets rather than one.</p>/docs/projects/project-3-bgp-router/Wed, 25 Aug 2021 15:24:08 -0400/docs/projects/project-3-bgp-router/<div class="alert alert-info" role="alert"> <b>The final project is due at 11:59pm on February 24, 2026.</b> </div> <h2 id="description">Description</h2> <p>In this project, you will implement a simple BGP router. There are several educational goals of this project:</p>/docs/projects/project-4-reliable-transport-protocol/Wed, 25 Aug 2021 15:24:08 -0400/docs/projects/project-4-reliable-transport-protocol/<div class="alert alert-info" role="alert"> <b>This project is due at 11:59pm on March 17, 2026.</b> </div> <h2 id="description">Description</h2> <p>You will design a simple transport protocol that provides reliable datagram service. Your protocol will be responsible for ensuring data is delivered in order, without duplicates, missing data, or errors. Since the local area networks at Northeastern are far too reliable to be interesting, we will provide you with access to a virtual environment that will emulate an unreliable network.</p>/docs/projects/project-5-web-crawler/Wed, 25 Aug 2021 15:24:08 -0400/docs/projects/project-5-web-crawler/<div class="alert alert-info" role="alert"> <b>This project is due at 11:59pm on April 7, 2026.</b> </div> <h2 id="description">Description</h2> <p>This assignment is intended to familiarize you with the HTTP protocol. HTTP is (arguably) the most important application level protocol on the Internet today: the Web runs on HTTP, and increasingly other applications use HTTP as well (including Bittorrent, streaming video, Facebook and Twitter&rsquo;s social APIs, etc.).</p>/docs/projects/project-6-dns-server/Wed, 25 Aug 2021 15:24:08 -0400/docs/projects/project-6-dns-server/<div class="alert alert-info" role="alert"> <b>This project is due at 11:59pm on April 21, 2026. </b> </div> <h2 id="description">Description</h2> <p>You will design and implement an recursive DNS server. Your server will be (a) the authoritative server for a specified domain, and be (b) responsible for serving as a recursive resolver for a number of local clients. In doing part (b), your server will be required to interact with other DNS servers, maintain an (accurate) DNS cache, and avoid succumbing to any security vulnerabilities. You will use the real DNS protocol, though you should <em>not</em> communicate directly with any real DNS servers.</p>/privacy/Tue, 06 Oct 2020 08:47:36 +0000/privacy/<p>This website is hosted on a server at Northeastern University. This webserver collects logs of routine usage. No data is shared or sold with third parties.</p>