summaryrefslogtreecommitdiff
path: root/smoketest
AgeCommit message (Collapse)Author
2021-12-30smoketest: snmp: T4124: locally connect to SNMP service and retrieve dataChristian Poessinger
2021-12-27smoketest: snmp: T4093: v3 user requires a groupChristian Poessinger
2021-12-26smoketest: ospf: use setUpClass()/tearDownClass() for route-mapsChristian Poessinger
2021-12-26ospfv3: T4107: add support for "default-information originate"Christian Poessinger
2021-12-26ospfv3: T4102: nssa area support both no-summary and default-originateChristian Poessinger
2021-12-26flow-accounting: T4097: move configuration file to /runChristian Poessinger
2021-12-26smoketest: flow-accounting: adjust to CLI change (source-address)Christian 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: T4097: move to get_config_dict()Christian Poessinger
2021-12-25ospfv3: T4102: add support for NSSA area-typeChristian Poessinger
2021-12-24smoketest: ospf: enable FRR debuggingChristian Poessinger
2021-12-24smoketest: flow-accounting: add sflow and netflow testcasesChristian Poessinger
2021-12-17Merge pull request #1103 from zdc/T3774-sagittaChristian Poessinger
logs: T3774: Added CLI options to control atop logs rotation
2021-12-13logs: T3774: Added new CLI itemzsdc
Added the ability to control the `/var/log/messages` rotation. Renamed the option `maxsize` to `max-size`.
2021-12-13configd: T2582: add smoketest for vyos-configd initializationJohn Estabrook
2021-12-12bgp: T3967: add support for conditional advertisementChristian Poessinger
The BGP conditional advertisement feature uses the non-exist-map or the exist-map and the advertise-map keywords of the neighbor advertise-map command in order to track routes by the route prefix. non-exist-map ============= * If a route prefix is not present in the output of non-exist-map command, then advertise the route specified by the advertise-map command. * If a route prefix is present in the output of non-exist-map command, then do not advertise the route specified by the addvertise-map command. exist-map ========= * If a route prefix is present in the output of exist-map command, then advertise the route specified by the advertise-map command. * If a route prefix is not present in the output of exist-map command, then do not advertise the route specified by the advertise-map command. This feature is useful when some prefixes are advertised to one of its peers only if the information from the other peer is not present (due to failure in peering session or partial reachability etc). The conditional BGP announcements are sent in addition to the normal announcements that a BGP router sends to its peer. CLI nodes can be found under: * set protocols bgp neighbor <ip> address-family <afi> conditional-advertisement * set protocols bgp peer-group <p> address-family <afi> conditional-advertisement
2021-12-12bgp: smoketest: add proper peer-group assignment testsChristian Poessinger
In the past a peer-group was only assigned to the BGP process but not bound to any neighbor. This has been changed.
2021-12-12bgp: T4069: add "parameters suppress-fib-pending" CLI optionChristian Poessinger
This command is applicable at the global level and at an individual bgp level. If applied at the global level all bgp instances will wait for fib installation before announcing routes and there is no way to turn it off for a particular BGP vrf.
2021-12-12bgp: T4069: add "parameters shutdown" CLI optionChristian Poessinger
Administrative shutdown of all peers of a bgp instance. Drop all BGP peers, but preserve their configurations. The peers are notified in accordance with RFC 8203 by sending a NOTIFICATION message with error code Cease and subcode Administrative Shutdown prior to terminating connections. This global shutdown is independent of the neighbor shutdown, meaning that individually shut down peers will not be affected by lifting it.
2021-12-12bgp: T4069: add "parameters reject-as-sets" CLI optionChristian Poessinger
This command enables rejection of incoming and outgoing routes having AS_SET or AS_CONFED_SET type.
2021-12-12bgp: T4069: add "parameters minimum-holdtime <n>" CLI optionChristian Poessinger
This command allows user to prevent session establishment with BGP peers with lower holdtime less than configured minimum holdtime. When this command is not set, minimum holdtime does not work.
2021-12-12bgp: T4069: add "parameters fast-convergence" CLI optionChristian Poessinger
Whenever BGP peer address becomes unreachable we must bring down the BGP session immediately. Currently only single-hop EBGP sessions are brought down immediately. IBGP and multi-hop EBGP sessions wait for hold-timer expiry to bring down the sessions. This new configuration option helps user to teardown BGP sessions immediately whenever peer becomes unreachable. This configuration is available at the bgp level. When enabled, configuration is applied to all the neighbors configured in that bgp instance.
2021-12-12bgp: T3967: add "parameters conditional-advertisement timer <n>" optionChristian Poessinger
Set the period to rerun the conditional advertisement scanner process. The default is 60 seconds.
2021-12-11smoketest: bfd: only read in FRR configuration from bfddChristian Poessinger
2021-12-11bfd: T3310: bugfix on profile names using hyphensChristian Poessinger
2021-12-10vxlan: T3700: can not specify both "external" and "VNI"Christian Poessinger
2021-12-10vxlan: T3700: add support for external controlled FDBChristian Poessinger
Background information [1]. Specifies whether an external control plane (e.g. ip route encap/EVPN) or the internal FDB should be used. [1]: https://legacy.netdevconf.info/2.2/slides/prabhu-linuxbridge-tutorial.pdf
2021-12-10smoketest: interfaces: bugfix loop iteration - same config set multiple timesChristian Poessinger
2021-12-09ospf(v3): T4058: add support for BFD profilesChristian Poessinger
2021-12-09isis: T4058: add support for BFD profilesChristian Poessinger
2021-12-09bgp: T4058: add support for BFD profilesChristian Poessinger
2021-12-09smoketest: vlan: T4064: verify IP addresses do not stick after deletionChristian Poessinger
(cherry picked from commit 1a814661a0ade01f144398b91dd6998e42018fdd)
2021-12-07logs: T3774: Added CLI options to control atop logs rotationzsdc
Added CLI options to generate logrotate configuration file for atop logs
2021-12-06smoketest: bfd: T4054: verify peer -> profile assignmentChristian Poessinger
2021-12-06Merge pull request #1077 from sever-sever/T3829Christian Poessinger
netns: T3829: Ability to configure network namespaces
2021-12-06smoketests: mpls: add initial basic testcaseChristian Poessinger
2021-12-04smoketest: vrrp: passwords are only allowed 8 characters longChristian Poessinger
(cherry picked from commit 55f6c1352fc5b2b8d051497e7fe97a4e62caf1fe)
2021-12-04smoketest: vrrp: delete VLAN interfaces in tearDown()Christian Poessinger
(cherry picked from commit 3fb6f5a966c57cb0936b35c13655f0b3f36483c4)
2021-12-04bfd: T4043: add support for passive modeChristian Poessinger
Mark session as passive: a passive session will not attempt to start the connection and will wait for control packets from peer before it begins replying. This feature is useful when you have a router that acts as the central node of a star network and you want to avoid sending BFD control packets you don't need to. The default is active-mode
2021-12-04bfd: T4044: add VRF support for peersChristian Poessinger
2021-11-29Merge pull request #1076 from DmitriyEshenko/current-22112021-01Christian Poessinger
tftp: T4012: Add TFTP VRF support
2021-11-29smoketest: tftp: T4012: Add smoketest for TFTP in VRF contextDmitriyEshenko
2021-11-28ospfv3: T3928: add VRF supportChristian Poessinger
set vrf name foo protocols ospfv3
2021-11-28smoketest: ospf: rearrange testcases - place vrf lastChristian Poessinger
2021-11-27isis: T3753: adjust to new FRR 8.1 syntaxChristian Poessinger
2021-11-27rpki: T3753: adjust to new FRR 8.1 syntaxChristian Poessinger
2021-11-27ripng: T3753: adjust to new FRR 8.1 syntaxChristian Poessinger
2021-11-27policy: T3753: adjust to new FRR 8.1 syntaxChristian Poessinger
Every node in running config now has an explicit "exit" tag
2021-11-27ospf: T3753: adjust to CLI options new in FRR 8.0Christian Poessinger
FRR 7.5 router ospf passive-interface default no passive-interface eth0.202 Changed int FRR 8 to interface eth0.202 no ip ospf passive ! router ospf ospf router-id 172.18.254.202 log-adjacency-changes detail passive-interface default
2021-11-27ospfv3: T3753: adjust to CLI options new in FRR 8.0Christian Poessinger
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-12 15:11:07 +0000