Open Andsup opened 1 month ago
@Andsup you're using a standard debian image ? also wondering what the conversion steps were that you took if possible ...
For sure crash is linked to a mistake during the "manually" network file creation .
Fully out of the box debian image from my hoster with latest debian 12.5 setup (as many if not all virtual servers)
Today I back to the initial network setup with Cloud-init off : netplan (DHCP based) -> systemd-networkd.
The server is correctly secured with firewalld (firewall-cmd ...) but firewalld service have to be restart after each freepbx 17 (re)start. Killed by the freepbx "Intrusion Detection" service during the load.
My expectation is a config, that even in case of complete crash, could be easily reinstalled from a freepbx backup. Like the freepbx version 16 distro based version.
NB: message in admin "you'll need to disable systemd-networkd. " is quite incomplete and misleading
FreePBX Version
FreePBX 17
Improvement Description
Hi, I tried to switch from "networkd" network management to /etc/network/interfaces files based. Quite few help on internet to do this migration back to the former way of working.
End result : no network, KVM to repair and a lot of stress So a very bad experience.
I don't want to go in production with such kind of risk at support level.
Distro freepbx centos is based on "NetworkManager" with config files in /etc/sysconfig/network-scripts/ This is also easily manageable with tools like nmcli et nmtui,.
Why not let, in a first step, this possibility available next to the basic "/etc/network/interfaces" ?
This is not the best and uptodate but still more user friendly way to configure network
Thanks.