vyos-1x.git/src/services, branch sever-sever-patch-1

configd: T7119: fix misleading debug messages

2025-01-31T18:06:46+00:00

An artifact of T6899 included a report of 'error_code 1' on success: for consistency with shim error codes 1 == SUCCESS, however, the debug message is misleading and is here corrected.

configd: T7119: normalize formatting

2025-01-31T18:06:46+00:00

wireguard: T7087: Fix vyos-domain-resolver failing if no wireguard interfaces defined

2025-01-25T12:39:43+00:00

Merge pull request #4200 from sskaje/T4930-1

2025-01-24T18:13:08+00:00

T4930: Allow WireGuard peers via DNS hostname

T6641: Add vyos-network-event-logger Service

2025-01-21T04:17:26+00:00

The service parses and logs network events for improved monitoring and diagnostics. Supported event types include: - `RTM_NEWROUTE`, `RTM_DELROUTE` - `RTM_NEWLINK`, `RTM_DELLINK` - `RTM_NEWADDR`, `RTM_DELADDR` - `RTM_NEWNEIGH`, `RTM_DELNEIGH`, `RTM_GETNEIGH` - `RTM_NEWRULE`, `RTM_DELRULE` Added operational mode commands for filtered log retrieval: - `show log network-event `: Retrieve logs filtered by event type and interface. - `show interfaces event-log `: Display interface-specific logs filtered by event type.

wireguard: T4930: fix dict key (-/_) when working with config dict

2025-01-18T23:17:12+00:00

Retrieving the config dict sets key_mangling(), thus we need to look for host_name instead of host-name.

wireguard: T4930: add mnemonic for WIREGUARD_REKEY_AFTER_TIME

2025-01-18T23:17:12+00:00

WireGuard performs a handshake every WIREGUARD_REKEY_AFTER_TIME if data is being transmitted between the peers. If no data is transmitted, the handshake will not be initiated unless new data begins to flow. Each handshake generates a new session key, and the key is rotated at least every 120 seconds or upon data transmission after a prolonged silence.

wireguard: T4930: allow peers via FQDN

2025-01-18T23:17:12+00:00

* set interfaces wireguard wgXX peer YY hostname

configd: T6747: use one long-lived instance of FRRender (#4274)

2025-01-06T17:05:06+00:00

* smoketest: T6747: call wait after commit() only for FRR related tests Commit 702a60a8de28 ("smoketest: T6746: wait after commit() until frr-reload is no longer running") added a guard timeout for every commit executed via CLI smoketests. This commit changes the bahavior to only add the guard timeout for FRR related testscases. This improves the overall smoketest time. * configd: T6747: use one long-lived instance of FRRender Previously there was one FRRender() instance per config session. This resulted in re-rendering the FRR configuration every time a new config session was created. Example: vyos@vyos:~$ configure vyos@vyos# set interfaces dummy dum0 description foo vyos@vyos# commit vyos@vyos# exit vyos@vyos:~$ configure vyos@vyos# set interfaces dummy dum0 description bar vyos@vyos# commit vyos@vyos# exit In the past this caused a re-render of the FRR configuration as the delta check added in commit ec80c75d6776 ("frrender: T6746: only re-render FRR config if config_dict did change") evaluated to false, as it operated on a new instance of the FRRender class. With this change there is no FRR re-render, as there is nothing to update in FRR.

frr: T6746: additional improvements after 10.2 upgrade (#4259)

2024-12-30T19:35:08+00:00

* smoketest: T6746: add substring search in getFRRconfig() Some daemons (e.g. bgpd) have several nested substrings/sections like router bgp 100 address-family ipv4 unicast .. exit-address-family exit We can now use getFRRconfig() with the substring option to extract only address-family ipv4 unicast .. exit-address-family Making config validation more granular * frrender: T6746: only re-render FRR config if config_dict did change * frrender: T6746: fix naming glitch isis/eigrp * frrender: T6746: add --stdout option when running with debug flags * smoketest: T6746: remove unneeded commit_guard time It was an invalid workarround as the underlaying issue seems to be a race condition in CStore. The commit process is not finished until all pending files from VYATTA_CHANGES_ONLY_DIR are copied to VYATTA_ACTIVE_CONFIGURATION_DIR. This is done inside libvyatta-cfg1 and the FUSE UnionFS part. On large non-interactive commits FUSE UnionFS might not replicate the real state in time, leading to errors when querying the working and effective configuration. TO BE DELETED AFTER SWITCH TO IN MEMORY CONFIG