Difference between revisions of "ECE497 Project WireShark"

From eLinux.org
Jump to: navigation, search
(Added Wireshark project page)
 
Line 67: Line 67:
  
 
== Theory of Operation ==
 
== Theory of Operation ==
 +
<ref>General Overview</ref>
 +
[[
 +
<gallery>
 +
File:Test|framed
 +
</gallery>
 +
]]
 +
  
Give a high level overview of the structure of your software.  Are you using GStreamer?  Show a diagram of the pipeline.  Are you running multiple tasks?  Show what they do and how they interact.
 
  
 
== Work Breakdown ==
 
== Work Breakdown ==
 +
 +
Job to do:
 +
Get wireshark running on the beagelbone black.
 +
 +
 +
Requirements Specification
 +
 +
The user shall be able to monitor tcp/ip traffic on the beaglebone black.
 +
The user shall be able to use wiresharks large capabilities to filter and analyze datapackets.
 +
 +
The user should be able to use a graphical interface.
 +
 +
 +
Major tasks:
 +
Evaluation of the portability of wireshark to the beaglebone black.
 +
 +
Cross compile approach.
 +
 +
Thinking of the problem in a different way. Evaluating if the traffic can be monitored in a other way.
 +
 +
Find out how to filter out ssh relikts.
 +
 +
Writing the parser.
 +
 +
Testing the parser.
 +
 +
Find out how named pipes work.
 +
Putting it all together
 +
Write a makefile to compile the sources.
 +
  
 
List the major tasks in your project and who did what.
 
List the major tasks in your project and who did what.

Revision as of 13:56, 31 October 2013

thumb‎ Embedded Linux Class by Mark A. Yoder


Team members: Ben Paras, Manuel Stephan

Grading Template

I'm using the following template to grade. Each slot is 10 points. 0 = Missing, 5=OK, 10=Wow!

00 Executive Summary
00 Installation Instructions 
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments: I'm looking forward to seeing this.

Score:  10/100

(Inline Comment)

Executive Summary

We want to try to port WireShark and see what we could get working on the BeagleBone.

We were able to put the source code on the bone and run the autogen.sh script. We launched the configure script and multiple dependencies were discovered and we're trying to figure out ways to resolve those dependencies.

So far WireShark itself isn't working due to the lack of dependency resolution.

The level of depth of this project varies at it really depends on how fast we can get it ported and what else we could do if time is permitting. We're running into quite a few issues despite some quick progress. We'll see what happens over time.


Packaging

If you have hardware, consider Small Build, Big Execuition for ideas on the final packaging.

Installation Instructions

Give step by step instructions on how to install your project.

  • Include your github path as a link like this to the read-only git site: https://github.com/MarkAYoder/gitLearn.
  • Be sure your README.md is includes an up-to-date and clear description of your project so that someone who comes across you git repository can quickly learn what you did and how they can reproduce it.
  • Include a Makefile for you code.
  • Include any additional packages installed via opkg.
  • Include kernel mods.
  • If there is extra hardware needed, include links to where it can be obtained.

User Instructions

Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.

Highlights

Here is where you brag about what your project can do.

Include a YouTube demo.

Theory of Operation

[1] [[

]]


Work Breakdown

Job to do: Get wireshark running on the beagelbone black.


Requirements Specification

The user shall be able to monitor tcp/ip traffic on the beaglebone black. The user shall be able to use wiresharks large capabilities to filter and analyze datapackets.

The user should be able to use a graphical interface.


Major tasks: Evaluation of the portability of wireshark to the beaglebone black.

Cross compile approach.

Thinking of the problem in a different way. Evaluating if the traffic can be monitored in a other way.

Find out how to filter out ssh relikts.

Writing the parser.

Testing the parser.

Find out how named pipes work. Putting it all together Write a makefile to compile the sources.


List the major tasks in your project and who did what.

Also list here what doesn't work yet and when you think it will be finished and who is finishing it.

Future Work

Suggest addition things that could be done with this project.

Conclusions

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.




thumb‎ Embedded Linux Class by Mark A. Yoder

  1. General Overview