| Age | Commit message (Collapse) | Author |
|---|
|
|
|
op-mode: T7540: move "clear interface connection" to "reset connection"
|
|
|
|
|
|
|
|
|
|
Leave hint if vyos-configd encounters an error in the generate/apply
stages: this only detects 'first-order' differences, meaning those
originating from the called config mode script, and not its
dependencies. This is useful for supporting automatic rollback for
certain cases of apply stage error.
|
|
dmbaturin/T7527-eliminate-embedded-op-mode-shell-snippets
op-mode: T7527: move assorted embedded shel snippets to script files
|
|
op-mode: T7538: remove the obsolete "show login level" command
|
|
T7492: Fix modem connection code
|
|
T7510: ospfd.frr.j2 ospf nssa translation error - fix template
|
|
|
|
T7365: add commit hooks and cli integration
|
|
|
|
|
|
|
|
|
|
For certain commands, notably 'commit', a python script is preferable to
the more responsive executable vyconf_cli. Criteria are (1) longer
running process, not benefiting from a compiled tool (2) convenience of
integration with the ecosystem, for example pre-/post-commit hooks.
|
|
|
|
|
|
|
|
T7532: container sysctl parameter values are quoted
|
|
conntrack: T7208: nf_conntrack_buckets defaults and behavior
|
|
T7523: firewall: Accepting invalid traffic for pppoe discovery and wol
|
|
To keep existing CLI behavior use a Warning() to prompt the user for an invalid
configuration. It is not possible to have more the one area-type defined per
area logically - the CLI does support it. In addition the backbone area cannot
be of type STUB or NSSA.
CLI configuration should be cleaned up using a migrator in the future.
|
|
|
|
|
|
|
|
Previously, we used a lower limit of 1 and a default value of 32768 for the
nf_conntrack_buckets (conntrack hash-size) sysctl option. However, the Linux
kernel enforces an internal minimum of 1024. A configuration migrator will now
adjust the lower limit to 1024 if necessary.
The former default value of 32768 was passed as a kernel module option, which
only took effect after the second system reboot. This was due to the option being
rendered but not applied during the first boot. This behavior has been changed so
that the value is now configurable at runtime and takes effect immediately.
Additionally, since VyOS 1.4 increased the hardware requirements to 4GB of RAM,
we now align the default value of nf_conntrack_buckets with the kernel's
default for systems with more than 1GB of RAM to 65536 entries. Previously, we
only supported half that amount.
|
|
|
|
T7524: Fix binary path for gwlbtun
|
|
Fix the gwlbtun binary path
```
r14 (gwlbtun)[8378]: aws-gwlbtun.service: Failed to locate executable /usr/bin/gwlbtun: No such file or directory
```
path
```
vyos@r14# sudo whereis gwlbtun
gwlbtun: /usr/sbin/gwlbtun
```
|
|
|
|
http-api: T3955: add commit-confirm to endpoints /configure /config-file
|
|
op-mode: T7509: add "detail" and "wide" modifier for BGP advertised-routes|received-routes
|
|
openconnect: T7511: bugfix invalid variable name
|
|
T7514: Fix smoketest QoS burst bytes replaced with kilobytes
|
|
op-mode: T7459: eliminate direct use of sudo in op mode commands
|
|
The `tc` output burst size was changed from bytes to kilobytes
|
|
nat: T7237: Remove expensive NAT address check
|
|
|
|
|
|
|
|
|
|
|
|
T7512: firewall: Modify accepting invalid traffic for VLAN aware bridge
|
|
|
|
Allow accepting invalid packets for ethernet types `8021q` and `8021ad`
in addition to ARP and UDP types so that stateful bridge firewall works
for VLAN-aware bridges in addition to regular bridges.
|
|
show ip bgp neighbors <ip> received-routes [detail [wide]|wide]
show bgp neighbors <ip> received-routes [detail [wide]|wide]
show bgp ipv4 neighbors <ip> received-routes [detail [wide]|wide]
show bgp ipv6 neighbors <ip> received-routes [detail [wide]|wide]
show bgp vrf <name> neighbors <ip> received-routes [detail [wide]|wide]
show bgp vrf <name> ipv4 neighbors <ip> received-routes [detail [wide]|wide]
show bgp vrf <name> ipv6 neighbors <ip> received-routes [detail [wide]|wide]
|
|
show ip bgp neighbors <ip> advertised-routes [detail [wide]|wide]
show bgp neighbors <ip> advertised-routes [detail [wide]|wide]
show bgp ipv4 neighbors <ip> advertised-routes [detail [wide]|wide]
show bgp ipv6 neighbors <ip> advertised-routes [detail [wide]|wide]
show bgp vrf <name> neighbors <ip> advertised-routes [detail [wide]|wide]
show bgp vrf <name> ipv4 neighbors <ip> advertised-routes [detail [wide]|wide]
show bgp vrf <name> ipv6 neighbors <ip> advertised-routes [detail [wide]|wide]
|
