CHANGELOG

   1 version 0.7.7 2007-01-??
   2
   3 - testing version, 0.8 will be stable release
   4 - faster startup times using iptables-restore (credit: Martin "Ludva" Svoboda)
   5 - compiles and runs correctly on both 32bit and 64bit platforms
   6
   7 version 0.7 2007-01-29
   8
   9 - There were good reasons to rename iptables hashing to iptables indexing.
  10   Hashing is different algorithm, which offers constant complexity
  11   independent on number of hashed entries and high memory requirements, while
  12   iptables indexing used in Prometheus offers log8(N) complexity and relatively
  13   low memory requirements compared to hashing.
  14 - Multiple keywords can be defined and used in /etc/hosts-like nodelist,
  15   which allows definition of various data limits for different users or
  16   definition of both symetrical and asymetrical virtual lines in same config.
  17 - Following prometheus.conf variables were made keyword-dependent:
  18   KEYWORD-magic-relative-limit, KEYWORD-magic-relative-prio,
  19   KEYWORD-magic-fixed-limit, KEYWORD-magic-fixed-prio, KEYWORD-,
  20 - Following new prometheus.conf keyword-dependent variables were added:
  21   KEYWORD-html-color
  22 - Following prometheus.conf variables were removed as obsolete and confusing:
  23   htb-ceil-bonus-divide, htb-ceil-divide
  24
  25 version 0.6 2006-06-29
  26
  27 - Hyper-optimized iptables hashing (automatic, but compile-time configurable)
  28 - Option hashtable-treshold was made now obsolete
  29 - No "Proxy" column in statistics when qos-proxy-enable is set to 0
  30 - iptables verbose output parsing was rewritten
  31 - Unfinished implementation of some pps limiting and soft-restart related code
  32 - Maybe I have changed something else too, but it was long time since last release
  33
  34 version 0.5.3 2005-08-15
  35
  36 - Predictable error messages generated by tc and iptables were
  37   redirected to /dev/null
  38 - magic-fixed-prio and magic-relative-prio can be used even with
  39   magic-fixed-limit and magic-relative-limit set to 0
  40 - Minor bugs in data initializtion were fixed, so program should
  41   compile and run also on exotic non-X86 plaforms like BusyBox Linux
  42
  43 version 0.5.2 2005-06-19
  44
  45 - Fixed long integer traffic counter overflow at 4 gigabytes (up or down)
  46 - Fixed incorrect inclusion of http proxy traffic in direct traffic
  47 - Fixed incorrectly displayed parameters of asymetrical upload (Jakub Walczak)
  48 - Dry run (-d switch) output beautification
  49 - Added check if minimum data transfer value is greater then 0 kbps
  50 - magic-priorities added, allows better soft-shaping wihtout reducing HTB ceil
  51
  52 version 0.5.1 2005-03-22
  53
  54 - Fixed serious bug in 0.5 release
  55
  56 version 0.5 2005-03-21
  57
  58 - Better compatibility with up-to-date gcc and new HTB in 2.6.x kernel
  59 - Enterprise Research and Planning (ERP) analysis implemented
  60 - Credit file support implemented (for use with magic-relative-limit)
  61 - magic-relative-limit-4prio now allows softer FUP using HTB prio
  62 - digital-divide-weirdness-ratio added, only tested value is "2"
  63 - qos-leaf-discipline and other new prometheus.conf keywords added
  64
  65 version 0.4 2004-11-02
  66
  67 - HTTP proxy traffic accounting bug fixed (occured with hashed iptables)
  68 - free bandwith traffic shaping (allowed unlimited upload with hashing)
  69 - maximal guaranted speed increased to 2048 kbps (just tc namespace problem)
  70   (Read: it seems that maximum index of tc classes is restricted to 10000)
  71 - qos-proxy-ip can be inside qos-free-zone even if qos-proxy-enable
  72   (Read: Single machine can run NAT/firewall, HTTP proxy and Prometheus QoS)
  73 - command line argument -n (no delay) overrides qos-free-delay keyword
  74   (Read: Separate configuration file for first run and daily run is not needed)
  75 - traffic from unregistered IPs is monitored even with hashing enabled
  76
  77 version 0.3 2004-10-13
  78
  79 - massive performance improvement thanks to hashing of iptables
  80 - hashtables for /24 subnets are forced if there are 256+ traffic classes
  81 - hashtables can be forced using new option hashtable-treshold)
  82 - qos-free-zone is now optional (use qos-free-zone 0)
  83 - minor bug fix: -h command line arugment now overrides config file
  84
  85 version 0.2 2004-09-20
  86
  87 - daily logging of data transfered in individual traffic classes
  88 - preview feature (create HTML hall of fame without reseting counters)
  89 - delay feature (useful for creating QoS-free period without reseting counters)
  90 - <A NAME=""> anchors with hostnames of individual traffic classes
  91 - tested succesfuly on our upgraded 10Mbps-full duplex, <1000 packets/sec
  92
  93 version 0.1
  94
  95 - initial release
  96 - tested succesfuly on our 3Mbps-full duplex line