Age | Commit message (Collapse) | Author |
|
|
|
|
|
settings
|
|
Feature detection is used to see if certain offload settings are available on
the given NIC.
|
|
ospfv3: allow metric and metric-type on redistributed routes
|
|
vyos.ethtool: T6083: use JSON input data for ring-buffer methods
|
|
banner: T6077: dehardcode URLs in MOTD template
|
|
|
|
Example:
vyos@vyos# set protocols ospfv3 redistribute bgp
Possible completions:
metric OSPF default metric
metric-type OSPF metric type for default routes (default: 2)
route-map Specify route-map name to use
|
|
|
|
qos: T6081: QoS policy shaper target and interval wrong calcuations
|
|
Use URLs provided by flavor build system and version.json file
|
|
|
|
dhcp-server: T6079: Disable duplicate static-mappings on migration
|
|
|
|
|
|
Added health-check to sync-group in CLI
Don't use instance health-check when instance in sync group member
Disallow wrong healtch-check configurations
New smoke test
|
|
vyos-hostsd: T4270: resolve only hostname without domain name to 127.0.1.1
|
|
This is a fix for commit 665ae50729 ("vyos-hostsd: T4270: do not resolve local
router FQDN to 127.0.1.1") as it made calls to sudo super slow due to:
sudo: unable to resolve host vyos: System error
To avoid the initial issue we only add the hostname without domain name, thus
the FQDN is not resolved by powerdns.
|
|
configdep: T5839: remove trivially redundant config dependency calls
|
|
vyos.ethtool: T6070: fix EEE reading the incorrect status line
|
|
T5504: Keepalived VRRP ability to set more than one peer-address
|
|
banner: T6077: implement ASCII contest winner default logo
|
|
|
|
Added health-check to sync-group in CLI
Don't use instance health-check when instance in sync group member
Disallow wrong healtch-check configurations
New smoke test
|
|
|
|
|
|
|
|
|
|
Implement VyOS ASCII art contest winners logo as the default for our MOTD
|
|
vrf: conntrack: T6073: Populate VRF zoning chains only while conntrack is required
|
|
vyos-hostsd: T4270: do not resolve local router FQDN to 127.0.1.1
|
|
container: T6074: do not allow deleting images which have a container running
|
|
|
|
required
|
|
Clients using VyOS as their DNS server and trying to resolve the FQDN of the
router will receive 127.0.1.1 as answer.
set service dns forwarding allow-from '172.16.0.0/12'
set service dns forwarding listen-address '172.31.0.254'
set service dns forwarding negative-ttl '60'
set system domain-name 'vyos.net'
set system host-name 'R1'
Will return:
$ host R1.vyos.net 172.31.0.254
Using domain server:
Name: 172.31.0.254
Address: 172.31.0.254#53
Aliases:
R1.vyos.net has address 127.0.1.1
When it should rather return the real IP address assigned via DNS.
|
|
The current VyOS container image manipulation "delete container image" command
allows force removal of container images - even if they still have a container
running.
Drop the --force option from the op-mode script.
vyos@vyos:~$ delete container image 2636705a815a
Error: image used by 6adb0175d47f.. image is in use by a container: consider
listing external containers and force-removing image
|
|
remove obsolete imports
|
|
EEE enabled status is on the 2nd line of ethtool output and not the 3rd. Subsequently, reading the 3rd line was causing an out-of-bounds access for the bnx2x driver as well.
|
|
dhcp-server: T6063: Add `ignore-client-id` to relax client identifier checks for leases
|
|
for leases
|
|
container: T6060: support removing all container images at once via op-mode
|
|
cpo@LR1.wue3:~$ show container image
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/library/busybox latest 3f57d9401f8d 5 weeks ago 4.5 MB
docker.io/jacobalberty/unifi v7.5 f6df690d6c67 4 months ago 827 MB
docker.io/jacobalberty/unifi v7.4 7838b75ef7b9 7 months ago 786 MB
cpo@LR1.wue3:~$ delete container image
Possible completions:
3f57d9401f8d Delete container image
7838b75ef7b9
all
f6df690d6c67
cpo@LR1.wue3:~$ delete container image all
cpo@LR1.wue3:~$ show container image
REPOSITORY TAG IMAGE ID CREATED SIZE
|
|
container: T5909: move registry login to op-mode
|
|
It does not make sense to perform the "podman login" command when setting up
containers, as images are not automatically pulled in from the registry - due
to issues with the default route during startup.
The same issue manifests in "podman login" where we can not login to a registry
unless there is a default route present.
This commit changes the behavior that the container registry is part of the
configuration, but it is only referenced during "add container image" and thus
never during system boot.
|
|
T6054: WLB: fix rules parsing when using multiple ports in one rule
|
|
|
|
pki: T6055: Cleanup unnecessary sudo, preserve env when sudo is needed
|
|
|
|
|