| Age | Commit message (Collapse) | Author |
|---|
|
The previously "global" options actually were only relevant for the local
logging to /var/log/messages.
|
|
|
|
Move "global preserve-fqdn" one CLI level up, as it relates to all logging
targets (console, global and remote).
|
|
|
|
|
|
|
|
Should be added as runtime option similar to "terminal monitor" known from
other vendors.
|
|
|
|
|
|
T4930: Allow WireGuard peers via DNS hostname
|
|
T6641: Add vyos-network-event-logger Service
|
|
|
|
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 <event-type> <interface>`: Retrieve logs filtered by event type and interface.
- `show interfaces <type> <name> event-log <event-type>`: Display interface-specific logs filtered by event type.
|
|
* set interfaces wireguard wgXX peer YY hostname <fqdn>
|
|
nhrp: T2326: NHRP migration to FRR
|
|
NHRP migration to FRR
|
|
haproxy: T5222: Enable backend completion in service ruleset
|
|
xml: T5738: Reuse predefined regex constraint
|
|
|
|
Enable completion for backend in haproxy service ruleset like so:
```
set load-balancing haproxy service NAME rule 10 set backend
```
|
|
|
|
block
|
|
Improve config parsing for ZBF when using VRFs and interfaces attached to VRFs
|
|
interfaces attached to VRFs
|
|
T6994: Add textfile collector config option
|
|
srv6: T6984: add locator format configuration
|
|
|
|
* T6949: adds blackbox exporter
* T6949: adds basic config generation
* T6949: extract shared module config options
* T6949: switch to ipv4/6 literals
* T6949: moves config file to /run
* T6949: adds dns query name option
* T6949: adds dns query type values
* T6949: adds blackbox exporter to debian/control
|
|
|
|
Interface definition for pki has redundant `tagNode`
for `openssh`. Remove the redundant one.
|
|
xml: T5738: re-use XML building blocks for interfaces as much as possible
|
|
|
|
Change XML definitions to re-use already existing building blocks, or merge
two building block sinto one (e.g. static route interfaces).
|
|
T6013: Add support for configuring TrustedUserCAKeys for ssh service
|
|
T6936: PPPoE-server add option combined to interface
|
|
local and remote CA keys
|
|
T6953: merges node and frr exporter under prometheus section
|
|
Add option 'combined', it allows to listen to PPP requests on
both VLANs and the base parent interface (wihtout tag)
Before it was impossible to do it from our CLI
set service pppoe-server interface eth1 combined
set service pppoe-server interface eth1 vlan '10-122'
|
|
|
|
|
|
T6934: Add preshared key for zabbix-agent monitoring service
|
|
T6874: [QoS] Add class filter by ether
|
|
T6918: Accept invalid PPPoE Session in stateful bridge firewall.
|
|
Implement a command to configure QoS policy filters by ether properties.
The supported match types include:
- Destination: Specify the Ethernet destination address.
- Protocol: Define the Ethernet protocol.
- Source: Set the Ethernet source address.
`set qos policy <type> <name> class <id> match <match-id> ether <destination|protocol|source> <val>`
|
|
Co-authored-by: Daniil Baturin <daniil@baturin.org>
|
|
Migrate "set protocols static route <x.x.x.x/x> next-hop <y.y.y.y> bfd multi-hop
source <z.z.z.z> profile <NAME>" to: "set protocols static route <x.x.x.x/x>
next-hop <y.y.y.y> bfd profile bar"
FRR supports only one source IP address per BFD multi-hop session. VyOS
had CLI cupport for multiple source addresses which made no sense.
|
|
tagNode
This will save an entire level for the configuration and there is no need for a
parent "multicast" node, as it will only have "route" as tagNode below.
Move set protocols static multicast route <x.x.x.x/y> to:
* set protocols static mroute <x.x.x.x/y>
|
|
With FRR 10.0 daemons started to be migrated to integrated FRR mgmtd and a
northbound interface. This led to some drawbacks in the current state how
changes to FRR are handled. The current implementation will use frr-reload.py
and specifies excatly WHICH daemon needs a config update and will only replace
this part inside FRR.
With FRR10 and mgmtd when a partial configuration is sent to mgmtd, it will
remove configuration parts from other daemons like bgpd or ospfd which have
not yet been migrated to mgmtd.
It's not possible to call frr-reload.py with daemon mgmtd - it will error out.
This commit will also change the CLI for static routes:
CLI command "set protocols static route 10.0.0.0/8 next-hop 1.2.3.4 bfd multi-hop
source 1.1.1.1" will be split into:
* set protocols static route 10.0.0.0/8 next-hop 1.2.3.4 bfd source-address 1.1.1.1
* set protocols static route 10.0.0.0/8 next-hop 1.2.3.4 bfd multi-hop
To make the XML blocks reusable, and comply with the FRR CLI - this was actually
a wrong implementation from the beginning as you can not have multiple BFD
source addresses.
CLI command "set protocols static route 10.0.0.0/8 next-hop 1.2.3.4 bfd multi-hop
source 1.1.1.1 profile bar" is changed to:
* set protocols static route 10.0.0.0/8 next-hop 1.2.3.4 bfd profile bar
CLI commands "set protocols static multicast interface-route" is moved to:
* set protocols static multicast route <x.x.x.x/x> interface
To have an identical look and feel with regular static routes.
|
|
|
|
static: T4214: Allow several dhcp-interfaces to the same static rote
|
