This is a project-as-a-tag.
Details
Tue, Mar 24
Mon, Mar 23
Sun, Mar 22
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
notify 0 {
match "system" "CARP";
match "subsystem" "[0-9]+@[0-9a-z.]+";
match "type" "(MASTER|BACKUP)";
action "/usr/local/scripts/carp-test.sh";
};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.
notify 0 {
match "system" "IFNET";
match "subsystem" "vmx1";
action "logger CARP state change detected";
};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.
Fri, Mar 20
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.
Tue, Mar 17
If we trigger the script through devd, we can provide a .conf configuration file in /usr/local/etc/devd.
Mar 4 2026
Mar 3 2026
resolved here
Ref T1695
Mar 2 2026
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)
Feb 26 2026
@yousra I think pip install salt==3006.8 should work, with dependencies.
Salt dependencies are reasonable enough to add to requirements.txt:
Feb 25 2026
If Salt dependencies are the issue, a possibility is to define requirements from https://github.com/saltstack/salt/tree/master/requirements
Feb 23 2026
I came up with this solution which seems to work as intended :
Feb 20 2026
Feb 19 2026
Nov 10 2025
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):