tcpdump/wireshark

in-class exercise(s):
 tcpdump/wireshark
 wireshark - parts 4,5,7,8
 MAC addresses
 MAC spoofing

5th edition:
pp. 1-36
48-56
61-68

read - Kurose Chapter 5 "The Link Layer..."
6th edition:
433-438
445-449,453-460
462-476

5th edition:
441-448
455-459,463-469
469-486

print - TCP/IP and tcpdump Pocket Reference Guide from SANS Institute. I suggest you print it out 2-sided, fold it into 3 panels, and carry it with your materials for this class.

optionally do - an exercise for familiarization with fundamental linux commands if you feel you would benefit from it. Networking is not a linux technology. It is OS-agnostic, but you must employ it by running some software commands, and those are not OS-agnostic. They must be commands written to run on some platform or other, be it Mac, Windows, linux, or otherwise. In this class I utilize linux for that purpose so for that reason "tourist level" mastery of the linux command "language" is needed. (In class, I will accompany you as your translator.)

Network stack

Suites & layers

Ethernet, a protocol example

tcpdump

wireshark

interfaces & routes

arp

in-class exercise(s):
 capture arp/ping session
 netmask legality
 netmasks' size effect
 ifconfig/route
 auto network config
 capture arp/ping session

Interfaces & Routes

ARP address resolution

addresses

internetworks (routing)

bridging

6th edition:
305-310
317-319
331-335
338-352

5th edition:
315-320
327-329
341-345
348-365

read - Brown Chapter 1 "Basic IP Connectivity" pp 1-11

do - netmask legality

do - MAC vs IP addresses per instructor's supplementary formatting and submittal instructions.

do - IP packet delivery

IP Addresses

internetworks

IP addresses

IP packet delivery

bridging

traceroute

in-class demo:
 hub vs switch

6th edition:
461-482

5th edition:
486-493

read - about tcpdump filters

Brown pp 143-149, ping
Brown pp 150-51, traceroute

the ping program - and its underlying ICMP protocol
meet - the guy who wrote it (r.i.p.)
read - his account of the ping story.

traceroute
  listen - to this podcast segment about how it works

do - measuring latency with ping

traceroute

miscellaneous but essential

socket api

port forwarding

firewalls

in-class exercise(s):
 directed use of  letter-upgrader sample programs
 internetworking
 clients & servers
 xinetd
 port-forward  lab

read - about socket API programming

Brown p56, port forwarding

study - the code for the "world's simplest client-server pair": 
 - letter-upgrader server
 - letter-upgrader's client
They exemplify the stucture of client and server programs through their use of the socket API. For contrast with them, take a quick look at the other two pairs,
 - upper-echoback server
 - client for echo-back server
and
 - web (file-send) server
 - client for file-send server,
which are a little more complicated but also reflect the standard socket programming structure. Satisfy yourself that you can identify the structure within those other two pairs.

Networks: services

Networks: sockets

Port forwarding methods

Firewalls

tcp

udp protocol

tcp protocol

netstat

netcat

in-class exercise(s):
 nmap scanner

Brown  pp151-155, netstat

netstat
  listen - to a discussion of netstat (starting from about 14:00 min)

examine an nmap cheat sheet - here's a quick reference card for nmap.

nmap

netstat

netcat

apache

in-class exercise(s):
 dns name server
 apache web server

apache web site
apache documentation

a summary how CGI works

examine an Apache cheat sheet - here's a quick reference card for Apache. It's formatted to be printed out as 2 pages, front-to-back on a single sheet, then folded tri-fold.

listen - to the dns training video in file dns.avi. (You can also get it by anonymous ftp from the pub directory at sputnik. It's about 13MB.)

Apache (web server)

Apache CGI

HTTP protocol

BIND (name server)

DNS protocol

nfs

dhcpd (address server)

DHCP protocol

nfs

Samba (MS fileshare client) 

SMB (MS fileshare) protocol