Network - Add new address range don't work

Submitted by Blueforce on Wed, 05/24/2017 - 01:35 Pro Licensee

Hi,

I can's seem to add a IP range with Add a new address range" in Networking/Network Configuration/Network Interfaces The range gets installed in interfaces but never starts up! I have restarted network from command line and also rebooted server without interfaces starting up.

This works om CentOS 5 and 6 but not on CentOs 7.

If I add them manually one by one it works!

I use Virtualmin Pro and CentOS 7

Regards, Leffe

Status: 
Active

Comments

Submitted by JamieCameron on Wed, 05/24/2017 - 19:24

What is the range you entered exactly?

Submitted by Blueforce on Wed, 05/24/2017 - 22:13 Pro Licensee

Hi,

I entered a small range, only 5 of our public IP's this time, exactly as I have done before.

  • I selected the interface (eno1)
  • Added a range name (extra1)
  • Entered starting address (in format xxx.xxx.xxx.213)
  • Entered ending address (in format xxx.xxx.xxx.217)
  • Entered first virtual interface no. (The starting address last group, 213).

This has worked just fine on CentOS 5 and 6, I tried this yesterday on our local server running CentOS 6 just to make sure. At one point the network could not start after a restart in command line! And when network is unable to start I am VERY happy to have IPMI on our server! I had to connect via IPMI and remove the added ifcfg-eno1-rangeextra1 range file before I was able to start network and services again.

If I add the Virtual interfaces IP's one by one everything works fine.

//Leffe

Submitted by JamieCameron on Thu, 05/25/2017 - 18:25

What error message did you get when you tried to start the network from the command line?

IPMI is great - making network config changes remotely is always risky!

Submitted by Blueforce on Thu, 05/25/2017 - 20:41 Pro Licensee

Hi,

When I have added a range and then "Apply selected interfaces" I get this error

Failed to activate interfaces : RTNETLINK answers: Operation not supported

And the interfaces never becomes active.

//Leffe

Submitted by Blueforce on Thu, 05/25/2017 - 20:51 Pro Licensee

And I did forget to answer your question regarding error on network restart ;-)

I didn't get any error, just the "loading spinner" due to network shutting down! And I think this was caused by me, after trying to get range interface active for a while I edited the interface and added the netmask (the correct netmask) and then tried another network restart. And this time the network was unable to restart.

//Leffe

Submitted by JamieCameron on Thu, 05/25/2017 - 21:42

Is the primary IP for that interface on the same subnet as the range you added?

Submitted by Blueforce on Thu, 05/25/2017 - 21:47 Pro Licensee

Yes it is.

Submitted by JamieCameron on Thu, 05/25/2017 - 21:53

What if you just add a regular alias interface like eno1:1 .. does that work?

Submitted by Blueforce on Thu, 05/25/2017 - 22:04 Pro Licensee

Yes that works, I have added a few IP:s one by one.

But even if I have given the interfaces names like eno1:213 and eno1:214 in tab "Activated at boot" they get changed to eno1:0, eno1:1 and so on in "Activated now".

Submitted by Blueforce on Thu, 05/25/2017 - 22:11 Pro Licensee

If I do the same on a CentOS 6 server the interface name I enter in "Activated at boot" is preserved and same in "Activated now".

Submitted by JamieCameron on Fri, 05/26/2017 - 17:54

So adding a virtual IPs that cover the same range you're trying to add works OK, and can be activated?

Submitted by Blueforce on Fri, 05/26/2017 - 19:02 Pro Licensee

Yes adding them one by one works just fine, they are activated and accessible on our production server with CentOS 7, even if they don't keep their "name" as I said in #9.

Submitted by JamieCameron on Mon, 05/29/2017 - 17:00

Ok, let me see if I can re-produce this on a test CentOS 7 system.

Submitted by michaelfox on Fri, 11/24/2017 - 05:55

If range of added IP not satisfied by Network Interfaces, i can't do anything. I can advise you to visit our site, and say, what the problem? Thanks!