summaryrefslogtreecommitdiff
path: root/interface-definitions/flow-accounting-conf.xml.in
AgeCommit message (Collapse)Author
2021-12-25flow-accounting: T4106: support specification of capture packet lengthChristian Poessinger
2021-12-25flow-accounting: T4105: drop "sflow agent-address auto"Christian Poessinger
The implementation of the "auto" option to specify the sflow/netflow agent-address is very error prone. The current implementation will determine the IP address used for the "auto" value as follow: Get BGP router-id 1) If not found use OSPF router-id 2) If not found use OSPFv3 router-id 3) If not found use "the first IP address found on the system Well, what is the "first IP address found"? Also this changes if DHCP is in use. Also another disadvantage is when the BGP/OSPF/OSPFv3 router-id is changed, the agent-address is not updated upon the next reboot of the system. This task is about removing the "auto" keyword from the CLI at all and make it either entirely configurable by the user and hardcode the value in CLI, or not use this at all. If "auto" is specified we will query the system in the above order and set the proper router-id in the CLI. If none can be found the CLI node is removed.
2021-12-25flow-accounting: T4099: rename "netflow source-ip" to source-addressChristian Poessinger
sFlow uses the source-address CLI node and netflow uses source-ip this is just confusing and should be synced to the common source-address CLI node.
2021-12-25flow-accounting: T4097: move to get_config_dict()Christian Poessinger
2021-12-24smoketest: flow-accounting: add sflow and netflow testcasesChristian Poessinger
2021-12-06sflow: T4046: Add source-address for sflowViacheslav
2021-11-07xml: provide and use common interface-name building blocksChristian Poessinger
2021-08-29xml: add missing "u32:" value declarator on integer rangesChristian Poessinger
2021-04-20xml: T3488: when using regex one must use ^ and $ when checking string literalsChristian Poessinger
2020-12-27xml: fix valueHelp format stringsChristian Poessinger
A pre-defined list of common format strings to be used inside the <format> node of <valueHelp> is available from [1]. Adjust all currently in use <format> nodes to re-use the predefined strings over writing them on their own by even encapsulating the <> signs as &lt; and &gt;. [1]: https://github.com/vyos/vyatta-cfg/blob/5aec1a0429f2f/etc/bash_completion.d/vyatta-cfg#L515-L566
2020-12-17flow-accounting: T3132: enable egress traffic accountingJan-Philipp Benecke
2020-12-12xml: use "u32:" keyword when identifying port rangesChristian Poessinger
This will render the completion help more nicely.
2020-04-05flow-accounting: improve value help on ipfixChristian Poessinger
2019-12-26xml: remove leading carrot (^) from regex syntaxChristian Poessinger
... as the carrot is applied automatically when reading in the XML definition. Auto replaced by: $ find interface-definitions -type f | xargs sed -i 's/regex>^/regex>/'
2019-12-22flow-accounting: T1895: add restriction to syslog facilityAntonio Cuñat Alario
2019-12-18flow-accounting: T1890: flow-accounting rewritten with Python and XMLzsdc
This patch keep compatibility with old configuration and software, but now it is much easier to add a lot of other useful things Completely replaces vyatta-netflow package (except some outdated and not available via CLI parts)
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-07 00:40:21 +0000