NAPALM/napalm-device-types
1
0 Fork 0
Code Issues 12 Pull Requests 1 Actions Packages Projects Releases 2 Wiki Activity

feat: CARP addresses as virtual IPs, with their holder in the reading (4.10.0)
CI / test (3.10) (push) Successful in 27s
Details
CI / test (3.11) (push) Successful in 24s
Details
CI / test (3.12) (push) Successful in 27s
Details
CI / test (3.13) (push) Successful in 25s
Details
CI / test (3.10) (pull_request) Successful in 26s
Details
CI / test (3.11) (pull_request) Successful in 24s
Details
CI / test (3.12) (pull_request) Successful in 26s
Details
CI / test (3.13) (pull_request) Successful in 26s
Details

Browse Source 
A firewall pair's CARP addresses are a third virtual IP mechanism. Unlike
vip-manager and keepalived, a CARP reading says who holds the address: a
firewall's interface list need not show it, but CARP's state names the MASTER.

- VirtualIpsDict gains carp (NotRequired), VirtualIpDict gains holds
  (NotRequired; None leaves the holder to the interfaces).
- carp_virtual_ip() shapes one address bound to a VHID: MASTER holds, BACKUP
  stands by, INIT and DISABLED neither run nor hold, an unknown state says
  nothing. The same for OPNsense and pfSense; a driver supplies the fields.

netOrk #1121.
This commit is contained in:
christianmanivong committed 2026-10-16 11:06:43 +02:00
1 parent fde6d717a8
commit 4f3b88db0e
6 files changed
+195 -9
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

pyproject.toml
+1 -1
View File
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
[project]
name = "napalm-device-types"
version = "4.9.0"
version = "4.10.0"
description = "Abstract device-type base classes for NAPALM drivers"
readme = "README.md"
requires-python = ">=3.10"