We noticed that Windriver is unable to ping the public IP addresses of router-002 and router-003. However, GRE tunnel creation is successful, and tunnel connectivity works with router-002, although pinging its public IP is still unsuccessful.

When creating a GRE tunnel to the alias IP of ysul as an endpoint the tunnel is unpingable however when creating the GRE tunnel using the public IP of ysul, GRE tunnel responds well to ping.
I suspect that the problem might come from using an alias IP as GRE endpoint that might cause this as it suggest encapsulation/decapsulation issues

I created and tested a Salt reactor that listens for the carp/master event sent by the routers. For now, the reactor only runs a test command on Ysul and Windriver to confirm that the event is correctly received and that the master can trigger actions on those hosts.

Test to validate Salt event emission and reception on the master :

Ah, that's now what we need, nice for the script!

The file /usr/local/etc/devd/carp.conf :

You can directly use variables in the action to pass interface and state with $subsystem and $type

For all CARP external documentation, I think I've found the threshold where information is outdated in that man page:

According carp(4) (man carp) examples section, the name has changed.

@dereckson I first tried to redefine the devd rule by matching specific IFNET event types such as LINK_UP, LINK_DOWN, UP and DOWN, but none of them were triggered during CARP state changes in my tests.

A dedicated devd file was placed in /usr/local/etc/devd because this directory is usually used for custom configurations added by administrators, while /etc/devd contains the default system rules from FreeBSD. It makes the setup cleaner, avoids mixing custom logic with system configuration, and makes future maintenance or upgrades easier.

OVH API credentials published to apps/network/carp-hyper-001-switch path,
under application_key, application_secret, consumer_key keys.

@Duranzed Can you open the issue with Terminator maintainers, so we can determine the best course of action for the plugin to load our resolve-hash library?

Discussion to have with the upstream to understand how to safely load a Python library.

If we trigger the script through devd, we can provide a .conf configuration file in /usr/local/etc/devd.

resolved here
Ref T1695

I tried pip install salt==3006.8, but it brings the same strange issue : AttributeError: cannot access submodule 'cmdmod' of module 'salt.modules' (most likely due to a circular import)
(same in WindRiver)

@yousra I think pip install salt==3006.8 should work, with dependencies.

Salt dependencies are reasonable enough to add to requirements.txt:

If Salt dependencies are the issue, a possibility is to define requirements from https://github.com/saltstack/salt/tree/master/requirements

I came up with this solution which seems to work as intended :

Bruteforce attack scenario possible, so we're only interested by usernames defined in users.sls, not by "root" (can't login by SSH) or generic accounts like "docker" (doesn't exist):

Updated P297, we've still lot of branches to rename. Fixed one repo without call sign.