From ff1b76ab83c6a0174e945faa49031a638356c194 Mon Sep 17 00:00:00 2001
From: luis <luis@e0a8ed71-7df4-0310-8962-fdc924857419>
Date: Tue, 22 Jun 2010 11:05:49 +0000
Subject: [PATCH] Updated with the latest DONE items

---
 todo/nping.txt | 32 +++++++++++++++++---------------
 1 file changed, 17 insertions(+), 15 deletions(-)

diff --git a/todo/nping.txt b/todo/nping.txt
index 20e3a946a..9d0e18747 100644
--- a/todo/nping.txt
+++ b/todo/nping.txt
@@ -166,8 +166,8 @@
   contain options and therefore, the maximum payload len should be
   65535 - 20(ip header) - 40 (ip options) -20(tcp header) -20(tcp options);
 
-* Make sure randomnly generated checksums are in fact invalid and don't match
-  the correct checksum. There is a 1/65535 chance of this happening. 
+* Make sure randomnly generated checksums in IPv6-TCP/UDP are in fact invalid
+  and don't match the correct checksum. 
 
 * Fyodor:
   <<in some cases it might be nice to have an option which sends all 
@@ -181,12 +181,6 @@
   common_modified.cc, keep in mind that we may want to share David's UDP
   payload code between Nping and Nmap.
 
-* Change info about TODO file in http://nmap.org/nping web page.
-    - If you wish to contribute code to Nping there is a TO-DO list you can have 
-    - a look at (file "TODO" in the source package).
-    + If you wish to contribute code to Nping there is a TO-DO list you can have 
-    + a look at (file "todo/nping.txt" in nmap's source package).
-
 * In some cases, when using nping through a VPN connection, nsi_pcap_linktype()
   returns something different to DLT_EN10MB, and Nping fatals. Investigate
   why this happens to nping and is not a problem for Nmap. Also, determine
@@ -196,9 +190,6 @@
   The first one works, and the other one fatals with the "Currently only
   Ethernet is supported." (error message @ nping.cc:1717).
     
-* Update documentation for option --delay, including that now, time
-  specification as float numbers is supported (eg: --delay 0.1 meaning 100ms)
-
 * When doing ICMP echo traceroute (with --traceroute), unless the user
   supplies a custom round count (-c/--count), Nping only sends 5 packets
   (default round count). This is usually not enough to reach hosts
@@ -221,10 +212,6 @@
 * Make nping issue a warning when user supplies a payload in TCP-Connect
   mode.
 
-* Check if there is any problem with -e "". Maybe we shouldn't let users
-  supply a NULL name, but make them use the "any" specifier. Add doc
-  about this and update the test description (MISC_12).
-
 * It may be nice to let users set the IP header lenght field. Maybe they
   want to stress tcp/stacks with this.
 
@@ -507,3 +494,18 @@
   add uneven bytes of IP options. We are truncating the result, because
   the header length is expressed in 32 bit words.
 
+[DONE] Check if there is any problem with -e "". Maybe we shouldn't let users
+  supply a NULL name, but make them use the "any" specifier. Add doc
+  about this and update the test description (MISC_12).
+
+[DONE] Update documentation for option --delay, including that now, time
+  specification as float numbers is supported (eg: --delay 0.1 meaning 100ms)
+
+[DONE] Change info about TODO file in http://nmap.org/nping web page.
+    - If you wish to contribute code to Nping there is a TO-DO list you can have 
+    - a look at (file "TODO" in the source package).
+    + If you wish to contribute code to Nping there is a TO-DO list you can have 
+    + a look at (file "todo/nping.txt" in nmap's source package).
+
+[DONE] Make sure randomnly generated checksums are in fact invalid and don't match
+  the correct checksum. There is a 1/65535 chance of this happening.