1. 17 Feb, 2007 1 commit
  2. 16 Feb, 2007 2 commits
  3. 15 Feb, 2007 1 commit
  4. 14 Feb, 2007 5 commits
  5. 13 Feb, 2007 3 commits
  6. 12 Feb, 2007 1 commit
  7. 07 Feb, 2007 1 commit
  8. 06 Feb, 2007 1 commit
  9. 19 Dec, 2006 1 commit
  10. 13 Dec, 2006 1 commit
  11. 06 Dec, 2006 1 commit
  12. 01 Dec, 2006 1 commit
  13. 24 Oct, 2006 1 commit
    • Mike Hibler's avatar
      New environment variable LIBNETMON_CONNECTTIMO to control how many times · d311c511
      Mike Hibler authored
      libnetmon will attempt to connect to the monitor before giving up.
      It used to try once and give up (still the default behavior).  Set this
      to N to try N times one second apart or 0 to try forever.
      
      If you start your app automatically from the ns/template, then you can
      set a value in the ns file with either:
      	set opt(LIBNETMON_CONNECTTIMO) 10
      for the "old school" ns file, or:
      	$ns define-template-parameter LIBNETMON_CONNECTTIMO 10
      in a template.  Note that this will only work if you fire your app via
      the program agent, otherwise you won't get the environment variable.
      d311c511
  14. 08 Oct, 2006 1 commit
  15. 06 Oct, 2006 1 commit
  16. 03 Oct, 2006 3 commits
  17. 29 Sep, 2006 1 commit
  18. 28 Sep, 2006 2 commits
    • Jonathon Duerig's avatar
    • Mike Hibler's avatar
      Numerous changes: · d6dfc183
      Mike Hibler authored
       * cloudinfo.in: change to handle hybrid (split BW/delay handling)
         delay pipe setup, also a hack to allow you to run the .in file out
         of your source tree
      
       * init-elabnodes.pl: handle hybrid cloud/lan model, use xmlrpc to find
         type of plab nodes and setup delays accordingly
      
       * auto-*.sh: continued attempts to get a meaningful exit status out
         of them for the program agent--still doesn't work
      
       * run-monitor-libnetmon.sh: make sure initial conditions get properly
         propogated
      d6dfc183
  19. 22 Sep, 2006 1 commit
  20. 19 Sep, 2006 2 commits
  21. 18 Sep, 2006 1 commit
    • Kirk Webb's avatar
      · a290c985
      Kirk Webb authored
      Modify the monitor to use the event system directly via the python SWIG
      wrapper object (requested by Rob).  The monitor no longer forks and execs
      tevc for set_link operations.  Tested the additional code here by transplanting
      it into a test script.  Works as expected there, but has not been tested
      in situ.
      a290c985
  22. 15 Sep, 2006 1 commit
    • Mike Hibler's avatar
      Mostly cleanup. · cde74d7a
      Mike Hibler authored
      * generate the initial conditions for monitors to pass into the stubs
        (must use -i to start-experiment to do this)
      
      * make sure install-tarball does not return til tarballs are installed!
        (or til timeout)
      
      * move ip mapping and initial conditions files to /local/logs so they
        become part of the record
      
      * fix up exit status' returned by auto-* stubs so program-agent
        can detect real failures
      cde74d7a
  23. 14 Sep, 2006 1 commit
    • Jonathon Duerig's avatar
      Added better monitoring of replay save/load format. Changed census function to... · ee9ee12f
      Jonathon Duerig authored
      Added better monitoring of replay save/load format. Changed census function to reduce the possibility of future size errors. New monitoring is hierarchical and should be essentially free as long as the #define in saveload.cc is commented out. Added LeastSquaresThroughput to the sensorlist and the definitions in monitor.py. A couple of miscellaneous fixes.
      ee9ee12f
  24. 01 Sep, 2006 3 commits
  25. 29 Aug, 2006 1 commit
    • Mike Hibler's avatar
      Revised version of "max delay" packet dropping in dummynet. · f0b988f1
      Mike Hibler authored
      OLD:
      
       * 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.
      
      NEW:
      
       * 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
         behavior.
      
      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.
      f0b988f1
  26. 25 Aug, 2006 1 commit
  27. 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.
      c6fa578a