Difference between revisions of "Netaa"

From Embedded Xinu
Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{Historical}}
 +
 
=Team Members=
 
=Team Members=
 
''(All emails are @mu.edu)''
 
''(All emails are @mu.edu)''
Line 73: Line 75:
 
**<strike>Shell command udpstat</strike> [completed March 24, 2008]
 
**<strike>Shell command udpstat</strike> [completed March 24, 2008]
  
===Saturday April 5: X11===
+
===Monday, May 5: TCP Deadline===
 
*Research
 
*Research
 +
**[http://www.faqs.org/rfcs/rfc793.html TCP RFC]
 +
**[[Image:TCPIP_State_Transition_Diagram.pdf]]
 +
===Future Development===
 +
*X11
 +
**[http://en.wikipedia.org/wiki/X11 Wikipedia]
 
**[http://en.wikipedia.org/wiki/X11 Wikipedia]
 
**[http://en.wikipedia.org/wiki/X11 Wikipedia]
 
**[http://toastytech.com/guis/remotex11.html Other implementation]
 
**[http://toastytech.com/guis/remotex11.html Other implementation]
Line 80: Line 87:
 
**[http://www.faqs.org/rfcs/rfc1013.html X11 RFC]
 
**[http://www.faqs.org/rfcs/rfc1013.html X11 RFC]
 
**[http://www.x.org/wiki/ X.org]
 
**[http://www.x.org/wiki/ X.org]
**[http://www.faqs.org/rfcs/rfc793.html TCP RFC]
 
  
 
=Cautions=
 
=Cautions=

Latest revision as of 22:23, 11 September 2013

✘ This page is currently inactive and is retained primarily for historical interest.
A historical page is usually one that is no longer maintained or no longer relevant.

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) [completed February 29, 2008]
    • send [completed February 28, 2008]
    • receive [completed February 22, 2008]
    • receiveDaemon [completed February 27, 2008]
    • arpTimer - cache timeout [completed February 29, 2008]
    • shell command (arp) [completed February 28, 2008]
  • ICMP (Internet Control Message Protocol) [completed February 28, 2008]
    • echo request [completed February 22, 2008]
    • echo reply [completed February 28, 2008]
    • daemon [completed February 22, 2008]
    • shell command (ping) [completed February 27, 2008]
  • Shell commands [completed February 28, 2008]
    • snoop (packet sniffer) [completed February 26, 2008]
    • ethstat [completed February 28, 2008]
    • guesswho [completed February 23, 2008]
  • Other [completed February 27, 2008]
    • 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.

Wednesday, April 2: Part 2 Deadline [completed April 2, 2008]

  • DHCP (Dynamic Host Configuration Protocol) -- Aaron & Cathy [completed April 1, 2008]
  • Traceroute -- Adam & Kyle [completed April 2, 2008]
  • Rdate -- Tim & Brian [completed April 3, 2008]
  • UDP -- Aaron & Adam [completed March 28, 2008]
    • UDP RFC
    • UDP Daemon [completed March 24, 2008]
    • UDP ports device [completed March 28, 2008]
    • Shell command udpstat [completed March 24, 2008]

Monday, May 5: TCP Deadline

Future Development

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. Memory fragmentation occurs when packets are received and processed.