CPSC 341 Networking

Networking - August 2008
CPSC 341 - Assignments: 8/25 - 10/15
Earl Rodd erodd@malone.edu Extension 8546 www.malone.edu/erodd

Monday 8/25

Due:
Class:

Course introduction. Note: The first two weeks are probably the heaviest in the course due to the number of (potentially) new terms and concepts. Also since we do not have a final exam, we will move quite quickly in early weeks of the semester.
Chapter 1 concepts. 1.1 - 1.3

Wednesday 8/27

Due:

Read chapter 1: Sections 1.1-1.3
Homework: Chapter 1. Page 67. R1, R4, R5, R7, R8

Class:

Chapter 1 concepts: 1.4 - 1.5

Friday 8/29

Due:

Homework: Chapter 1: Page 68: R9, R13, R14, R15, R18

Class:

Chapter 1 concepts: 1.6 - 1.8

Monday 9/1

Due:
Class:

No Class - Labor Day

Wednesday 9/3

Due:

Read the remainder of chapter 1.
Homework: Chapter 1. Page 68-69. R19, R23.

Class:

Review homework
Finish chapter 1
Introduce Wireshark if time

Friday 9/5

Due:

Read Ethereal (Wireshark) Lab Pages 76-77

Class:

Review homework
Introduce Wireshark. See Wireshark installation and usage instructions on TS111 LINUX systems.
Note:In addition to the textbook website, the PDF files with the Wireshark labs are on the R: drive (R:\ERODD\ETHLABS or /home/square/tdrive/erodd/ethlabs).

Monday 9/8

Due:

Homework: Page 70-73: P2, P3, P8a (not 8b), P16b, P16c, P16d (16d mentions a site on another continent - one you can try is theage.com.au or www.theaustralian.news.com.au or www.bbc.com.uk). Note: To do 16b and 16c and 16d, you need to use the traceroute function. "traceroute.db" is available as a command line command on the lab LINUX systems. Another command, "tracepath", which is similar in function, but has some inner workings different, is also available on LINUX lab systems. Also note that the Windows systems in the lab also have "traceroute" function, but with the name "tracert". To run in Windows, open a command window (START/RUN/cmd.exe) and type the "tracert" command.
Read chapter 2: Pages 81-96

Class:

Introduce Wireshark lab (INTRO).
Chapter 2: Section 2.1

Wednesday 9/10

Due:

First Wireshark lab (INTRO). Note: Wireshark labs will often involve a considerable amount of work in examining various cases. Even though there may not be a lot to turn in for each lab, the labs are designed to lead students to understand how network protocols operate. Exams will assume that students understand concepts brought out in Wireshark labs.

Class:

Introduce Wireshark lab.
Chapter 2: Section 2.1

Friday 9/12

Due:
Class:

HTTP (Section 2.2)
FTP (Section 2.3)

Monday 9/15

Due:

Read sections:
Review questions page 178: R6, R8, R10,R13, R14(*), R15. Page 181: Problems P4 and P5 page 181.
(*)Use commands such as the bottom of page 101 for a model (only the GET and Host: are required). Note: Page 113 has an example of "If-modifed-since". The example of an "If-modified-since" has an error: You must put a timezone after the time such as:
If-modified-since: Mon, 18 Sep 2006 09:09:10 EST
- Some Windows system may not have "telnet" installed. If not, use a LINUX system in TS111.
- Telnet to
```
telnet www.malone.edu 80
```
- Use file /erodd/ttest.htm (a very simple file - you can check it with a browser at "www.malone.edu/erodd/ttest.htm")
- First do it without the "If-Modified-Since" command.
- Remember to press Enter an extra time after the last header line!
- HTTP commands are case-sensitive.
- When using "If-modified-since", use the current time/date.
- HTTP commands must be EXACT. You don't get error messages telling you what is wrong is you type commands in error!
To turn in: Write down the results of your testing.

Class:

Open book quiz on chapter 1. Bring your calculator!!
email (SMTP) 2.4
DNS 2.5
Introduce HTTP Wireshark lab

Wednesday 9/17

Due:

Review questions page 179: R18, R19.
HTTP Wireshark lab (Warning: This is a substantial lab!)

Class:

Review HTTP lab
Peer to Peer 2.6 (Note: We will not cover the details of index maintenance and operation in P2P.)
Introduce Wireshark (Ethereal) lab for DNS - Note: the lab talks about using ipconfig (Windows command) to clear the DNS cache prior to running Wireshark. In our labs, we only have Wireshark on LINUX, not Windows so you cannot do this. If you have problems with no messages for DNS, you can try stopping/starting the network with:
```
sudo ifdown eth0
# Wait a few seconds
sudo ifup -a
```

Friday 9/19

Due:

Review questions P 179-180: R21, R23 (1/3 weight assignment)
DNS Wireshark Lab

Class:

Sockets 2.7. See Java sample
Introduce a341socklab.htm
Overview of the Transport Layer
UDP

Monday 9/22

Due:
Class:

Review
Start Chapter 3 topics

Wednesday 9/24

Due:

Sockets Lab

Class:

Exam 1 on chapters 1 and 2. Bring a calculator! There are quantitative problems! Remember, a byte has 8 bits.

Friday 9/26

Due:

Chapter 3 review questions: R3, R5(think about this one!), R5, R7, R8, Problem: P1, P5
Quantitative Problems - you may print this sheet and work problems on the sheet.
Read sections 3.1-3.3

Class:

Review Exam
Principles of reliable data transfer. Note: Students are not responsible to know the details of which function goes with the various numbered methods such as rdt 1.0, rdt 2.0 etc. But students are responsible to understand the concepts and terms: ACK/NAK/ARQ/BitError/Lossy/SequenceNumber/DuplicatePackets/StopAndWait/GoBackN.

Monday 9/29

Due:

Read sections 3.4 and 3.5 through 3.5.4. Note: We will cover the principles in 3.4 (principles of reliable transport), but not all the detailed scenarios possible.
Wireshark Lab: UDP
Quantitative Problems II - Analysis.

Class:

Review homework
Principles of reliable data transfer
TCP

Wednesday 10/1

Due:

Review questions: Chapter 3: R9, R10, R11, R12, Also try R13 to see the difference. Nothing to hand in for R13. Problems P7 and P13.
For R12, you need to access an applet. The URL with the index to the applets is at (Click Applets on left column):
http://wps.aw.com/aw_kurose_network_4/63/16303/4173750.cw/index.html
Read 3.5.5 and 3.5.6.

Class:

Flow Control
TCP Connection Management

Friday 10/3

Due:

Review questions Chapter 3: R14 (a-g), R15, R16 (R16 refers to figure 3.31 on page 248). Problems P22, P23(a). Instead of P23(b) answer this: If 1460 bytes of data are in each packet (not counting headers), how many packets are required to send the file?
Read 3.6. Note: We will cover the basic principles of congestion control, but not the detailed scenarios.

Class:

Congestion and TCP mechanisms

Monday 10/6

Due:

Wireshark Lab: TCP

Class:

Review homework
Finish TCP issues
Network layer

Wednesday 10/8

Due:

Chapter 3 review questions R17 (Don't think too hard, the answer is simple), R18. Problems: P24(a, b, and c), P25, P26, P28 (to answer this, consider the possibilities for what might have happened to the "lost packet"), P41. This assigment counts as 1 1/2 daily assignments.

Class:

Network layer - Forwarding/Routing, Network service models, Datagram vs. Virtual Circuit

Friday 10/10

Due:

Chapter 4 review questions: R1, R2, R3, R4(first question only), R5(Modified question: For these services, which are provided by The Internet's network layer service and which are provided by ATM's CBR or ABR service models: (a) In order packet deliver; (b) guaranteed minimal bandwidth; (c) guaranteed maximum jitter. R6. Problem: P1.

Class:

Review homework
Routers
Introduction to IP

Monday 10/13

Due:

Chapter 4 review questions: R7, R9, R10, R11, Problem P7, P8

Class:

IP: Forwarding/addressing, DHCP, NAT

Wednesday 10/15

Due:

Chapter 4 review questions: R12, R13, R15, R16, R17, R18, Problem P16, P17

Class:

IP: DHCP, NAT, ICMP, IPV6
Start routing
Hand out take home exam on TCP (an Wireshark trace reading exercise). Counts as 1/2 of an exam. Due 10/22.