Although my data was save, the server wouldnt connect to the network anymore because it had a new MAC address.

CentOS stores this value in two of its files, and when it changes (which is hardly ever the case), those files need to be updated.

I did this on a CentOS 6 server, but it looks like the procedure is the same for CentOS 7.

We know why: because our MAC address has changed, and CentOS is trying to talk to hardware that doesnt respond.

In it well find sub-folders corresponding to our connections (such as eth0, lo, wlan, etc).

Each of these contains a file called address in which we can see our current MAC address.

Those are updated on the fly and should always be up to date with whatever hardware were using.

SUBSYSTEMnet, ACTIONadd, DRIVERS, ATTRaddress8c:89:a5:1e:38:3d, ATTRtype1, KERNELeth, NAMEeth1.

SUBSYSTEMnet, ACTIONadd, DRIVERS, ATTRaddress8c:89:a5:1e:38:3e, ATTRtype1, KERNELeth, NAMEeth2.

Those are stored during the initial network setup and as it seems are not updated on the fly when a change in hardware occurs.

Among many other things (depending on our hardware and setup), mine contained something like this.

Now a server restart should do the trick of connecting us to the network again.

There are many other ways to support me too, like shopping via my Amazon links, YouTube Super Chats or PayPal donations.

Where To Find Discord Files For Mac -Download -Bot -Alternative