vyos-1x.git/smoketest/scripts, branch current

Merge pull request #5109 from statio/fix/vrf-aware-port-check

2026-05-28T14:39:35+00:00

T8454: fix VRF-bind port availability check in service_https

Merge pull request #5169 from jestabro/exclusive-mask-config-sync

2026-05-28T13:40:57+00:00

T8502: Add exclusion mask to config-sync

T8502: op-mode call needs to wait on completion of remote commit

2026-05-28T13:31:26+00:00

The added calculations were just enough to introduce a race between remote commit completion and show remote config.

T8454: fix VRF-bind port availability check in service_https

2026-05-27T20:15:40+00:00

When service https is configured with a listen-address on a VRF interface, adding or changing the vrf option causes the commit to fail with "TCP port 443 is used by another service!" even though no conflict exists. Root cause: check_port_availability() performs a socket.bind() in the default network namespace. When the listen-address belongs to a VRF interface the address is unreachable from the default namespace, so the bind fails with OSError which is misinterpreted as "port in use". The secondary check via is_listen_port_bind_service() also fails because psutil cannot see sockets bound inside a VRF. Fix: add an optional vrf parameter to check_port_availability(). When set, the test socket is bound to the VRF master device via SO_BINDTODEVICE before the bind() call, so that the address is resolved in the correct L3 domain. This is done in-process (no subprocess) and works for both IPv4 and IPv6. service_https verify() now passes the configured VRF (if any) to check_port_availability(). Non-VRF configurations are unaffected. Add smoke test for HTTPS with listen-address inside a VRF. Co-authored-by: Christian Breunig

Merge pull request #5208 from alexandr-san4ez/T8538-current

2026-05-27T19:42:01+00:00

snmp: T8538: Persist engineBoots counter across reboots

Merge pull request #5197 from alexandr-san4ez/T7555-current

2026-05-26T14:47:15+00:00

ipsec: T7555: Implement `ikev2-reauth` for site-to-site peers

Merge pull request #5179 from josephillips85/current

2026-05-26T06:34:20+00:00

Policy: T8823: validation of GE and LE according FRR instructions

Merge pull request #5119 from AppMana/T8480

2026-05-26T06:11:55+00:00

wan: T8480: add suppress_prefixlength ip rules for internal routing

snmp: T8538: Persist engineBoots counter across reboots

2026-05-22T14:50:22+00:00

Per RFC 3414 section 2.2 (Replay Protection), the `snmpEngineBoots` counter must be stored in non-volatile storage and incremented on every snmpd restart. VyOS was not persisting this value, causing it to reset to 1 after every reboot. SNMP managers cache the engineBoots value from previous sessions. When VyOS resets the counter to 1 after reboot, managers reject incoming SNMPv3 trap packets as "too old", producing errors such as: ``` usm: Message too old. reboot count invalid ``` This change introduces `/config/snmp/engineboots.count` as a disk-backed persist file and it uses to sync the counter into snmpd's conf before the daemon starts.

T8910: ipoe-server: expose accel-ppp idle-timeout option

2026-05-22T10:54:18+00:00

Add a CLI knob to terminate idle IPoE sessions after a configurable timeout: set service ipoe-server idle-timeout <0-86400> Today there is no way to age out stale IPoE sessions: clients that go silent (powered off, link down) leave a session record on the router indefinitely. accel-ppp natively supports idle-timeout in its [ipoe] section but VyOS did not expose it. The option is added as a shared accel-ppp include so it can be reused by other accel-ppp services in follow-up PRs.