Networking Workshop
0368-3500-47/48/49
Semester II, 2005
Classes:
Sunday, Kaplun 118,
15:00-17:00
|
Yehuda Afek afek at cs.tau.ac...,
Nir Andelman andelman
at cs.tau.ac…
|
Basic
Requirements from all projects:
•
Well documented and usable:
All project must
·
be usable by others after you finish it and after you have left the
university. The code should be well
documented and explained with accompanying documents.
·
A
PRD, (Product
Requirement Document) in which you define the project, from very high level
goals and specification to more detailed explanation of inputs, outputs,
output windows (if graphics is involved) and expected behavior under
different conditions and inputs.
• Schedule:
·
March 13: First version of the PRD is due March
13.
·
April 3: Detailed project Design Document is due.
·
April 10: Begin implementation.
·
May 8: Presentation of first version of the
project.
·
June 5: Final project ready.
·
July
3: Projects are submitted
after all corrections, bug fixes.
•
Presentation: Projects
must have convenient and easy to use presentation of the results, usually
with graphical presentation (when ever appropriate). If necessary the project will have other
easy to use outputs. Think of the users that will have to use the
project.
•
Groups: Projects may be done in groups of 2 or 3 students.
•
Programming Language: Preferably projects will be written in the C
programming language.
Suggested Project
Layer 2 Network view:
Your program will periodically "talk"
with the different L2 devices in Schreiber building to construct the
topological view of the Network in the building. Including:
All switches and routers, all hosts, and gate ways. For each host, its L3 IP address will be
given and the physical port on the last switch to which it is connected will
be provided. More details will come as
we go. One of the sources of
information your program will use is the different MIBs
(via SNMP) - will explain in the class.
See for example
The commands we used in the lab were:
snmpwalk -v 1 -c public shaar.math.tau.ac.il
or
snmpwalk -v 1 -c public 132.67.x.x [mib
group]
snmpwalk -v 1 -c public 132.67.8.31
17.4.3.1.2
see net-snmp.org for more details on the
snmpwalk agent.
Look at
|