Netaa

Team Members

(All emails are @mu.edu)

• Aaron Gember: aaron.gember, (414) 550-5820
• Adam Koehler: adam.koehler
• Brian Smith: brian.smith
• Cathy Vuong: catherine.vuong
• Kyle Jackson: kyle.jackson
• Tim Blattner: timothy.blattner

Team email list: agember-es{at}mscs{dot}mu{dot}edu

Documentation

File:Netaa network daemons plan.pdf

File:Netaa network send plan.pdf

Timeline

Thursday, February 14: Meeting

• 6pm in Cudahy 310

• Adam, Tim, and Kyle are researching ICMP. Aaron, Brian, and Cathy are researching ARP.
• Extra shell commands will be assigned at next meeting.

Monday, February 18: ICMP Subgroup Meeting

• 3:45pm in Cudahy 310
• Meeting before class to go over questions or concerns on implementation.

Thursday, February 21: Meeting

• 6pm in Cudahy 310
• Meeting to ensure progress and to assign the remaining pieces of the project.

Wednesday, February 27 Sunday, March 2: Part 1 Deadline

• ARP (Address Resolution Protocol)
  • send [complete February 28, 2008]
  • receive [completed February 22, 2008]
  • receiveDaemon [completed February 27, 2008]
  • arpTimer - cache timeout
  • shell command (arp) [completed February 28, 2008]
• ICMP (Internet Control Message Protocol)
  • echo request [completed February 22, 2008]
  • echo reply [completed February 28, 2008 --- future time issue TBR]
  • daemon [completed February 22, 2008]
  • shell command (ping) [completed February 27, 2008]
• Shell commands
  • snoop (packet sniffer) [completed February 26, 2008]
  • ethstat [completed February 28, 2008]
  • guesswho [completed February 23, 2008]
• Other
  • netSend [completed February 26, 2008]
  • chkSum [completed February 27, 2008]

Monday, March 3: Project Team Meeting

• Discuss part two of the project, all team members should read up on all parts of the second stage before the meeting occurs.

Tuesday, March 11: Part 2 Deadline

• DHCP (Dynamic Host Configuration Protocol)
  • RFC
  • Wikipedia Page
• Traceroute
  • ICMP Wiki Page
  • Wikipedia Page
• Rdate
  • Time Protocol
  • man page

Cautions

1. Be aware of critical sections, you may need to disable and restore interrupts.

Known Bugs

1. Sporadically receive PDE errors, running etherClose seems to fix things.
2. Ping reply data time is grabbed correctly and entered, but it sometimes is from the future :).