User Details
- User Since
- Jan 29 2026, 16:43 (6 w, 1 d)
- Availability
- Available
Today
changed syntax
public address
corrected syntax
Yesterday
ALigned ip adresses
- Added private_ipv4 to be able to display on the MOTD files
Using correct parameters to display IPs
Wed, Mar 11
Now using node.resolve_network
Fixed spaced
- Add Nginx directive to accept files less 100M
Added more details in README.md
Tue, Mar 10
Added software.sls and modified init.sls
Improved configuration files and headers
Updated config files to use node.resolve_gre_tunnels
Fri, Mar 6
Thu, Mar 5
Modified Ysul IP adress in network.sls
Added service.sls file
Updated strongswan config files and using a for loop for a more readable code
Wed, Mar 4
More detailed README.md
Tue, Mar 3
- Added an init.sls pour strongswan
resolved here
Ref T1695
Mon, Mar 2
$ sudo salt complector state.sls_id salt-node-cloudhugger roles/vault/policies test=True complector: ---------- ID: salt-node-cloudhugger Function: vault.policy_present Result: None Comment: Policy would be changed Started: 18:09:21.668208 Duration: 841.275 ms Changes: ---------- salt-node-cloudhugger: ---------- change: --- +++ @@ -10,3 +10,7 @@ path "ops/data/secrets/nasqueron/opensearch/infra-logs/internal_users/dashboards" { capabilities = [ "read" ] } + +path "ops/data/secrets/network/ipsec/key" { + capabilities = [ "read" ] +}
Thu, Feb 26
Added 1 blank line
testing arc diff
Removed unused imports
Added README.md file for installation steps
Added Nasqueron header in the plugin file
Wed, Feb 25
Tue, Feb 24
Updated hash resolver plugin for terminator
Mon, Feb 23
Moving to resolve-hash repository
Moving to resolve-hash repository
I came up with this solution which seems to work as intended :
Sun, Feb 22
Fri, Feb 20
FIx deployed.
Thu, Feb 19
Added alkane workflow scheme to its wiki documentation
Listen directives added for bots and users
yt-dlp package has been downloaded, but still needs to be tested
Will be deployed tonight on production servers
We want to change the "if" statement in php.sls for a proper map in order to support more OS
Wed, Feb 18
We chose to go with strongswan as it is native to FreeBSD and the most complete solution in terms of supported protocols. Strongswan has already been installed and tested on router-002 and router-003.
Tue, Feb 17
GRE tunnel and IPsec configurations work as intended between router-002 and router-003, GRE is reachable on both sides and traffic is encrypted in IPsec with an ESP header