From 82f357e6157d2e126da43134abcacc60a5e6033b Mon Sep 17 00:00:00 2001 From: doktornotor Date: Thu, 30 Jul 2015 18:24:56 +0200 Subject: softflowd - do not restart on boot plus style fixes - Do not try to restart service on boot, otherwise it may get started twice via /etc/rc.start_packages (Fixes bug #4731). - Add standard XML and copyright headers. - Remove doubled spaces between sentences in descriptions. - Developer style guidelines (spacing, braces). --- config/softflowd/softflowd.xml | 94 ++++++++++++++++++++++++++++++++---------- 1 file changed, 73 insertions(+), 21 deletions(-) (limited to 'config') diff --git a/config/softflowd/softflowd.xml b/config/softflowd/softflowd.xml index 55065429..2960a560 100644 --- a/config/softflowd/softflowd.xml +++ b/config/softflowd/softflowd.xml @@ -1,6 +1,45 @@ + + + + + + softflowd - 0.9.8_2 pkg v1.1 + 1.2 softflowd: Settings pkg_edit.php?xml=softflowd.xml&id=0 @@ -50,7 +89,7 @@ Hop Limit hoplimit - Set the IPv4 TTL or the IPv6 hop limit to hoplimit. softflowd will use the default system TTL when exporting flows to a unicast host. When exporting to a multicast group, the default TTL will be 1 (i.e. link-local). + Set the IPv4 TTL or the IPv6 hop limit to hoplimit. softflowd will use the default system TTL when exporting flows to a unicast host. When exporting to a multicast group, the default TTL will be 1 (i.e. link-local). input @@ -76,7 +115,7 @@ Flow Tracking Level flowtracking - Specify which flow elements softflowd should be used to define a flow. track_level may be one of: "full" (track everything in the flow, the default), "proto" (track source and destination addresses and protocol), or "ip" (only track source and destination addresses). Selecting either of the latter options will produce flows with less information in them (e.g. TCP/UDP ports will not be recorded). This will cause flows to be consolidated, reducing the quantity of output and CPU load that softflowd will place on the system at the cost of some detail being lost. + Specify which flow elements softflowd should be used to define a flow. track_level may be one of: "full" (track everything in the flow, the default), "proto" (track source and destination addresses and protocol), or "ip" (only track source and destination addresses). Selecting either of the latter options will produce flows with less information in them (e.g. TCP/UDP ports will not be recorded). This will cause flows to be consolidated, reducing the quantity of output and CPU load that softflowd will place on the system at the cost of some detail being lost. select