[BUG] Subnet is not a correct CIDR

[Sigri44]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

After installation, the configuration export does not match the assigned IP and the authorized subnet, preventing VPN connection to the machine.

Expected Behavior

No response

Steps To Reproduce

1. Install dAppNode from scratch, with ISO img
2. Connect to SSH, and use "dappnode_wireguard" command
3. Get IP configuration

Environment

- OS: latest dAppnodeOS via ISO
- How docker service was installed: from ISO img

CPU architecture

x86-64

Docker creation

/

Container logs

[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────
  _____ __ __ _____ _____ _____ _____ 
 |     |  |  |   __|_   _|     |     |
 |   --|  |  |__   | | | |  |  | | | |
 |_____|_____|_____| |_| |_____|_|_|_|
       _____ __ __ _ __    ____  
      | __  |  |  | |  |  |    \ 
      | __ -|  |  | |  |__|  |  |
      |_____|_____|_|_____|____/ 

  Based on images from linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
WireGuard: https://www.wireguard.com/donations/

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────

Uname info: Linux 1b59c60018a3 6.1.0-15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09) x86_64 GNU/Linux
**** It seems the wireguard module is already active. Skipping kernel header install and module compilation. ****
**** As the wireguard module is already active you can remove the SYS_MODULE capability from your container run/compose. ****
**** Server mode is selected ****
**** Fetching DAppNode domain from my.dappnode...
**** Fetching DAppNode domain from dappmanager.dappnode...
**** Fetching DAppNode domain from 172.33.1.7...
**** Fetching DAppNode domain from my.dappnode...
**** Fetching DAppNode domain from dappmanager.dappnode...
**** Fetching DAppNode domain from 172.33.1.7...
**** Fetching DAppNode domain from 10.20.0.7...
**** Fetching DAppNode domain from my.dappnode...
**** Fetching DAppNode domain from my.dappnode...
**** Fetching DAppNode domain from my.dappnode...
**** Fetching DAppNode domain from my.dappnode...
**** Fetching DAppNode domain from my.dappnode...
**** Fetching DAppNode domain from my.dappnode...
**** Fetching DAppNode domain from my.dappnode...
**** Fetching DAppNode domain from my.dappnode...
**** External server port is set to 51820. Make sure that port is properly forwarded to port 51820 inside this container ****
**** Internal subnet is set to 10.24.0.0 ****
**** AllowedIPs for peers 172.33.0.0/16,10.20.0.0/24 ****
**** Peer DNS servers will be set to 172.33.1.2,10.20.0.2 ****
**** Server mode is selected ****
**** No changes to parameters. Existing configs are used. ****
[custom-init] No custom files found, skipping...
.:53
CoreDNS-1.10.1
linux/amd64, go1.20.11, 
**** Found WG conf /config/wg_confs/wg0.conf, adding to list ****
**** Activating tunnel /config/wg_confs/wg0.conf ****
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 10.24.0.1 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] ip -4 route add 10.24.0.2/32 dev wg0
[#] iptables -A FORWARD -i wg0 -j ACCEPT; iptables -A FORWARD -o wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth+ -j MASQUERADE
**** All tunnels are now active ****
[ls.io-init] done.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.