Local network subnet mask change on Debian ISO 3CX Phone System

[CamphillGhent]

We recently expanded the local network our Debian ISO 3CX system is on from a /24 subnet to a /22 subnet. What is the proper way to update the Debian 3CX install with this new subnet? The official way of changing the IP address for this type of install seems to be: backup, reinstall and restore - is it the same for changing only the subnet?

 

[mcsphones]

I'm no Linux expert, but I would imagine you could just change the subnet on the applicable devices + your 3CX Linux box, and as long as the IPs don't change - or as long as devices can still register back to your PBX - you should be fine. At least this method would work on a Windows box.

 

[SnakeRiverWebDevelopment]

SSH in to your system, then make the change

if other user
sudo nano /etc/network/interfaces

if root user
nano /etc/network/interfaces

# The loopback network interface
auto lo
iface lo inet loopback
 
# The primary network interface
auto enp0s5
iface enp0s5  inet static
 address 192.168.2.236
 netmask 255.255.255.0
 gateway 192.168.2.254
 dns-domain sweet.home
 dns-nameservers 192.168.2.254

Restart networking

Non root user
sudo systemctl status networking.service

root user
systemctl status networking.service

 

[CamphillGhent]

SSH in to your system, then make the change

if other user
sudo nano /etc/network/interfaces

if root user
nano /etc/network/interfaces

# The loopback network interface
auto lo
iface lo inet loopback
 
# The primary network interface
auto enp0s5
iface enp0s5  inet static
 address 192.168.2.236
 netmask 255.255.255.0
 gateway 192.168.2.254
 dns-domain sweet.home
 dns-nameservers 192.168.2.254

Restart networking

Non root user
sudo systemctl status networking.service

root user
systemctl status networking.service

Thanks! This did the job.

In our case there were two differences... the subnet mask was combined with the address in the alternate form of: 192.168.2.236/24 (using the address in your example). And the commands to restart network did not get the interface using the new subnet, and instead I rebooted the server when it was not in use for that.