Want to change subnet in Directadmin.

[masaomi]

We want to extend subnet ip from 255.255.255.248 to 255.255.255.192
But we can't change in directadmin. How to change subnet?
If I change Subnet in Server OS, the license will be problem? And after that, how to change subnet in directadmin? :confused:



Thanks for help:)

[SeLLeRoNe]

i dont think will cause problem to license, but, after changed the subnet to os be sure to change this file aswell /usr/local/directadmin/data/admin/ips/YOUR_IP

inside this file there are information about this IP, so, there you can change directadmin subnet aswell.

Restart OS (or just network) and directadmin

Regards

[zEitEr]

Restart OS (or just network) and directadmin

Restarting directadmin won't help you to update network settings. With network restart, if none changes are done in network configs, you'll not get, what you expect.

For main IP (i.e. eth0) update configs in shell. Other IPs can be updated in directadmin.

So as I as know, you'd better restart (shutdown -r now) your server.

[SeLLeRoNe]

ofc you need to edit eth0 configs in ssh (for that restart network) and change the file i menthioned for directadmin (for that directadmin restart i thot was enough)

ofc, a total reboot is the total best way ;)

[nobaloney]

You don't need to restart the server; all you need to do is restart networking and run the DirectAdmin startips script.

If possible, before you do that make sure you have a way to contact the server if you've made a mistake and the network doesn't restart properly. We use a separate NIC to a private network; we can log into one of our other servers, and shell into the broken one through the private IP#, and fix it without a trip to the datacenter.

Jeff

[masaomi]

I change /usr/local/directadmin/data/admin/ips/YOUR_IP and restart service directadmin.

[zEitEr]

ofc, a total reboot is the total best way ;)

And to get downtime while disk checking is running, if you had a high uptime and none reboot since months.

[SeLLeRoNe]

well, fsck is suggested after 1 month of use, but, if you dont wanna that check on reboot.. just disable it in fstab...

[nobaloney]

Still best to not reboot if unnecessary. On my desktops running KDE I find it often necessary, KDE isn't good at conserving resources. But I've not had the problem on any of my servers.

The only reasons I can think of for rebooting a server are:

When updating a kernel (but there's now a project out there which hot-updates kernels, to avoid this).

When some libraries are updated, if you're not sure which daemons use them, and if your package manager doesn't manage that for you.

Jeff

[zEitEr]

but there's now a project out there which hot-updates kernels, to avoid this

Do you talk about Ksplice? Did you personally try that?

[nobaloney]

Yes.

No.

Jeff