1. 01 Sep, 2006 2 commits
  2. 29 Aug, 2006 1 commit
    • Mike Hibler's avatar
      Revised version of "max delay" packet dropping in dummynet. · f0b988f1
      Mike Hibler authored
       * Delay specified in ticks.
       * Drop performed as packets were leaving the delay queue (i.e., leaving
         dummynet).  This is more accurate in terms of calculating time spent
         in dummynet, and can be used with all strategies of BW/delay shaping
         (constant values, distributions, table lookup), but required that
         ultimately-dropped packets get put on the BW queue, changing the timing
         of things.
       * Delay specified in milliseconds.
       * Drops perfromed as packets enter the bandwidth queue (i.e., arrive
         in dummynet).  Here drops are based on estimates of how long a packet
         would spend in dummynet and thus only works with constant delay/BW
         shaping characteristics, but does more accurately reflect queuing
      The estimate is done by looking at the length in bytes of the bandwidth
      queue (including the candidate packet) for the pipe, determining how long
      it will take to transmit that many bytes, and then adding the delay value
      for the pipe.
  3. 25 Aug, 2006 1 commit
  4. 24 Aug, 2006 1 commit
    • Jonathon Duerig's avatar
      Fixed the traffic model so that it is now in line with what Rob and I... · c6fa578a
      Jonathon Duerig authored
      Fixed the traffic model so that it is now in line with what Rob and I discussed. Delays are before the write with the write size cached. Writes expire based on an expiration date.
      Miscellaneous fixes. Open problem: PacketSensor does not deal correctly with zero-sized packets. I changed KernelTcp to pass such packets because otherwise there is no way to do state changes based on SYN/FIN/other packets. SYN is handled ok for now because of a change noted below. FIN is not.
      Added a StateSensor. As I discovered, using the kernel tcp_info data structure isn't useful when dealing with fields that change on a packet by packet basis because the kernel information is retrieved at processing time and not capture time. For instance, it is useless when trying to determine whether a connection was established by the time a particular packet was sent (to determine whether it is part of the three-way-handshake). The StateSensor keeps track of the state machine and correlates it to the packet involved. This allows the other sensors to rely on it to distinguish between connection setup and the rest of the connection traffic. Added references to it in the PacketSensor, the DelaySensor and the ThroughputSensor.
      Changed the way packet information was transmitted to the sensors to make it easier to add new packet types (as will be necessary when accept()s are handled).
      Fixed all outstanding flaws in the basic feedback mechanism. In short, "Its alive!". Currently the only data being transmitted is the base rtt (MinDelay). Now that the feedback is working in a basic form, it will be easier to get the other characteristics online.
  5. 18 Aug, 2006 1 commit
  6. 11 Aug, 2006 1 commit
  7. 01 Jun, 2006 1 commit
  8. 24 Apr, 2006 1 commit
  9. 11 Apr, 2006 2 commits
  10. 06 Apr, 2006 1 commit
  11. 27 Mar, 2006 1 commit
  12. 14 Mar, 2006 1 commit
    • Jonathon Duerig's avatar
      Added standalone support for multiple streams. Added a logging infrastructure.... · 302e1855
      Jonathon Duerig authored
      Added standalone support for multiple streams. Added a logging infrastructure. Added a trivial application for testing purposes (dumb-client and dumb-server). Added the capability for running the standalone stub with a tcpdump replay. Added support for changing buffer sizes. Added shell files for experiment management, reset.sh which is to reset the dummynet settings between runs and run-iperf.sh which encapsulates a set of options to iperf.
  13. 02 Feb, 2006 2 commits
  14. 01 Feb, 2006 1 commit
  15. 30 Jan, 2006 1 commit
  16. 20 Jan, 2006 1 commit
  17. 19 Jan, 2006 1 commit
  18. 18 Jan, 2006 1 commit
    • Jonathon Duerig's avatar
      Expanded monitor to be more generic (not bound to a particular IP address... · 4f1ffb87
      Jonathon Duerig authored
      Expanded monitor to be more generic (not bound to a particular IP address ,etc.). Added throughput measurement to the stub (note that the throughput measurements are not sent to the monitor, only printed to the screen). Added the first primitive traffic modeling to the stub. Changed the stub defines to agree with the monitor (monitor port == 4200).
  19. 20 Dec, 2005 1 commit