Repository move

Not for the operations repository, it's for rRESOLVEHASH.

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

Add the flag ipv6_dhcp_duid for windriver

Fix : when an IPv6 address belongs to the Scaleway tenant, add the
ipv6_dhcp_duid flag in the pillar

Remove an incorrect character from the code (star that shouldn't be there).

I removed the priority and name entries from the generated pillar, as they are not used by Salt in our current setup.
Keeping only the fields actually consumed by the states makes the pillar cleaner and avoids maintaining redundant data.

Use True and False (capitalized) to follow Salt's Python boolean conventions.

Increase the SOA serial so secondary name servers detect the changes and perform a zone transfer.
Ensure DNS records are placed in alphabetical order within the zone file.

Fix priority for CARP in NetBox, and then in the file nodes.sls

Add functions to get the CARP configiruation in NetBox

For (1), it was disabled between March 2022 (D2569) and August 2024 (forum thread reporting the issue).

This revision should only contain the NotFound.vue page and its catch-all route — that's the task. Please strip out the unrelated changes (navbar logo rework, SubscribeForm restyling, logo.svg replacement, package-lock.json removals) into their own separate revisions. See inline comments for specific fixes needed on indentation and missing newlines.

FIx deployed.

Avoid to include nodes.sls on the review

Fix OVH + IPv6 /64 => netmask gateway /56

1. Fix duplicate primary IP in aliases

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

19:21 < Yousra> Dereckson router-003: IP= 178.32.70.111/30, en fait .111 c'est la broadcast

Copying from Discord:

A new bloc IPV4 was added in NetBox : The 172.27.27.0/28 subnet was fully allocated and currently used by VMs on Hyper-1, so I expand it to a larger prefix by combining 172.27.27.0/28 and 172.27.27.16/28 into a single 172.27.27.0/27 subnet to allow better address utilization in the future.

The additional public IPv4 address has been received and is ready to be used for the CARP setup : IP=51.68.252.230/32

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.

That's a good idea, you can add it as low priority in Frontend and assign it to @Chenani-MohamedAmine

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

Clean and straightforward.

{F24385587}