Change Details

When the CARP device becomes active, the upstream router needs to be notified of the address MAC of the device where to route traffic for the shared address. For dedicated servers, the router is managed by our provider, not by us. The first implementation is for hyper-001, hosted at OVH. An API is available to update the MAC address. We develop a Python script solution to trigger the API. Credentials are stored in Vault. References: - https://pypi.org/project/ovh/ - https://docs.nasqueron.org/secretsmith/ Ref T2276

When the CARP device becomes active, the upstream router needs to be notified of the address MAC of the device where to route traffic for the shared address. For dedicated servers, the router is managed by our provider, not by us. The first implementation is for hyper-001, hosted at OVH. An API is available to update the MAC address. We develop a Python script solution to trigger the API. Credentials are stored in Vault. References: - https://pypi.org/project/ovh/ - https://docs.nasqueron.org/secretsmith/ Ref T2276

When the CARP device becomes active, the upstream router needs to be notified of the address MAC of the device where to route traffic for the shared address. For dedicated servers, the router is managed by our provider, not by us. The first implementation is for hyper-001, hosted at OVH. An API is available to update the MAC address. We develop a Python script solution to trigger the API. Credentials are stored in Vault. References: - https://pypi.org/project/ovh/ - https://docs.nasqueron.org/secretsmith/ Ref T2276