IntroductionInstructionsSubmission and GradingExercise OverviewRecommended ReadingStandard TracerouteSample InvocationsSample OutputVersatile TracerouteSample InvocationsSample OutputStatistics ReportingSample InvocationsSample OutputPath DiagnosticsLossRoute Load BalancingServer Load BalancingSample InvocationsSample OutputFirewall HandlingFirewalkSample InvocationSample OutputEstablished MethodSample InvocationSample OutputGhost TracerouteSample InvocationSample OutputWrap-UpProject #2 : Traceroute Next GenerationCS155: Computer and Network SecurityDue: May 4th, by 11:59pm (Part 1),Due: May 11th, by 11:59pm (Part 2)Spring 2009Contents1 Introduction 31.1 Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 Submission and Grading . . . . . . . . . . . . . . . . . . . . . . . 31.3 Exercise Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4 Recommended Reading . . . . . . . . . . . . . . . . . . . . . . . 52 Standard Traceroute 62.1 Sample Invocations . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Versatile Traceroute 73.1 Sample Invocations . . . . . . . . . . . . . . . . . . . . . . . . . . 73.2 Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Statistics Reporting 84.1 Sample Invocations . . . . . . . . . . . . . . . . . . . . . . . . . . 84.2 Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Path Diagnostics 115.1 Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.2 Route Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . 125.3 Server Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . 125.4 Sample Invocations . . . . . . . . . . . . . . . . . . . . . . . . . . 125.5 Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Firewall Handling 146.1 Firewalk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146.1.1 Sample Invocation . . . . . . . . . . . . . . . . . . . . . . 146.1.2 Sample Output . . . . . . . . . . . . . . . . . . . . . . . . 146.2 Established Method . . . . . . . . . . . . . . . . . . . . . . . . . 146.2.1 Sample Invocation . . . . . . . . . . . . . . . . . . . . . . 1416.2.2 Sample Output . . . . . . . . . . . . . . . . . . . . . . . . 146.3 Ghost Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . 156.3.1 Sample Invocation . . . . . . . . . . . . . . . . . . . . . . 156.3.2 Sample Output . . . . . . . . . . . . . . . . . . . . . . . . 157 Wrap-Up 1521 IntroductionTraceroute is one of the key tools used for network troubleshooting and scouting.It has been available since networking’s early days. Because traceroute is basedon TTL header modification, it crafts its own network packets.The goal of this project is to re-implement a traceroute with cutting edgetechniques designed to improve its scouting capabilities and bypass SPI firewalls.In this project you will learn about packet injection and sniffing. The projectalso teaches about more subtle topics such as network latency, packet filtering,and Q.O.S.1.1 InstructionsThis project has to be completed sequentially as each part depends on theprevious ones. You are required to work in groups of at most 2 people (one-person teams, while allowed, are discouraged). The required coding languageis C. You should consider using libnet [1] and libpcap [2], however using rawsockets is permitted as well.Note that the exercises become progressively more difficult, with Exercise 5likely to consume the greatest amount of effort. Please plan your work accord-ingly: there is no penalty for early submission.1.2 Submission and GradingThe project is due in two parts. The first part includes exercises 1 and 2, andthe second part should be fully functional, including exercises 1, 2, 3, 4, and5. The first part will be worth 40% of the project grade, which means thatexercises 1 and 2 will be graded entirely based on your part 1 submission. Inall, exercises will have equal weight, about 20% of the project grade each.Submission is by email to [email protected], and is due by 11:59pmon May 4th for Part 1 and by 11:59pm on May 11th for Part 2. Provide atgz archive that contains your code. When extracted, you project has to bein a directory named project2 name1[ name2] where name1 (and name2 whenpresent) is(are) the last name(s) of the student(s) it the team. The subjectline of the email needs to be ”CS155 project2”. Please include in the body ofthe e-mail the name of each member of the team, as well as their email addresses.3Your code will be compiled under Linux Ubuntu with the lastest version oflibpcap and libnet installed. To compile your project, the script will use thecommand make, executed in the project directory specified above. Then it willlaunch our tests, using an executable name ”traceng”—you have to make sureyour make file results in this executable name, in the same project directory.Our tests will involve tracing from Stanford to www.apple.com, www.google.de,www.amazon.co.uk. We will test every feature you implemented against thesehosts.Make sure that the command line options and the output format are correctlyimplemented as they will be used by our script during the grading process.Specific examples of how we are going to test your executable are provided laterin …
View Full Document
Unlocking...