Changed LAN address and bad things happened

[bobtskutter (bob)]

Version 7.4 (Fully configured)

I changed the LAN IP address last night, and broke the system
but thanks to ZFS and snapshots, I recovered the system

The system is running OpenLDAP with 5 users, webtop and normal gateway type systems. WebTop “died” and the system was very unresponsive.

I wish I’d seen this post before I started:

Can't change AD IP address

NethServer Version: 7.3 RC3 with all updates **Module:**sssd and AD? Folks, we changed red to our ISP and the green to from 192.168.2.x to 192.168.1.1 to match our machines. We can’t change Accounts provider bridge IP address. Please help. We are so close on this. Thanks all! Jonah

My guess is that I’d broken the LDAP server and that took WebTop down with it.

Should we be able to change the LAN IP address once the system is configured?

If not, please can a big label be added to the network tab saying “don’t change the LAN address”.

For those who are wondering, I’ve set up NethServer in a fully virtualised environment using 192.168.1.1 as it’s LAN address. The NethServer is to replace another CentOS server, which also has LAN address of 192.168.1.1. I changed the NethServer LAN IP to 192.168.1.150 so I could run both gateways on the same network and then transfer the IMAP data across using imapsync. Once I’d moved the IMAP data across I was planning to shutdown the old gateway and move the NethServer LAN IP back to 192.168.1.1.

Regards
Bob

[giacomo (Giacomo Sanchietti)]

Hi bob,

@bobtskutter

I wish I’d seen this post before I started:

the linked thread talks about Samba 4, which is not your case.
Also, this operation can now be done using the UI even for the DC.

@bobtskutter

Should we be able to change the LAN IP address once the system is configured?

Of course! Changing the green IP address of a machine is a common operation. From my experience, I can say that problems are usually network-related, like duplicate IPs in the LAN.

After changing the IP, make sure no other host as the same address using the arping command.
Check also /var/log/firewall.log and /var/log/messages to find martian packets.

Also make sure that the DNS is correctly configured since some services could use it to access the resources.

[bobtskutter (bob)]

@giacomo I think it was probably the DNS. I’ll go through the logs and see what I can find.

All I was trying to do was move the IMAP data from one server to the other. I can do that via the red interface since there is another firewall between that and the internet.

Thank goodness for ZFS snapshots!

Regards
Bob

[m.traeumner (Michael Träumner)]

@bobtskutter

I think it was probably the DNS. I’ll go through the logs and see what I can find.

If it is solved, could you mark the topic as solved please.

Howto mark a topic as solved

Now we have an amazing feature on our community platform which helps to mark a topic as SOLVED As the OP (topic creator) you will have a button that allows you to accept an answer [image] Accepted answers are highlighted in the topic list: [image] Accepted answers are highlighted on the initial topic: [image] This kind of action is enabled only for topic into the Support category Happy support!

[bobtskutter (bob)]

Sorry, I was writing up my final comments, but forgot to send them.

I don’t know exactly what happened. I recovered the system from a snapshot backup and everything is OK.

I transferred the IMAP data via the red interface (should have done that all along!!).