some nasty behaviour of ISPConfig 3.0.2.2.

[Hans]

Hi Till,
Today i dicovered some nasty behaviour of ISPConfig 3.0.2.2.
I try to tell you what i found out:

In ISPConfig3 on the master server, i added the new (additional) IP-addess 12.34.56.222 for an existing slave server.
Before i did that the slave server had the following content within /etc/network/interfaces:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 12.34.56.111
        netmask 255.255.255.0
        network 12.34.56.0
        broadcast 12.34.56.255
        gateway 12.34.56.129

After adding the additional IP-address on the master server, the content of /etc/network/interfaces on the slave changed into:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 12.34.56.222
        netmask 255.255.255.0
        network 12.34.56.0
        broadcast 12.34.56.255
        gateway 12.34.56.129

auto eth0:0
iface eth0:0 inet static
        address 12.34.56.111
        netmask 255.255.255.0
        network 12.34.56.0
        broadcast 12.34.56.255
        gateway 12.34.56.129

This is a problem, because of this automatic modification the slave server can not connect to the master anymore, because only root@12.34.56.111 is valid to connect to the master server, NOT root@12.34.56.222
So ISPConfig3 should not move 12.34.56.111 to eth0:0. but the new IP 12.34.56.222 instead!

So the right file content of /etc/networking/interfaces should be:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 12.34.56.111
        netmask 255.255.255.0
        network 12.34.56.0
        broadcast 12.34.56.255
        gateway 12.34.56.129

auto eth0:0
iface eth0:0 inet static
        address 12.34.56.222
        netmask 255.255.255.0
        network 12.34.56.0
        broadcast 12.34.56.255
        gateway 12.34.56.129

It would be nice if this behaviour can be changed in the next release of ISPConfig3.

[edge]

Today I locked myself out by doing something like you did.
I can not access my server anymore, and as it's a test server in Alphen a/d Rijn (grafix) I need to go there tomorrow and rewrite the file interfaces (add the correct info).

I'm using eth6 an eth7 in it, and ISPconfig changed it to eth0 and 0:0
(for some reason eth0 till eth5 do not work on my system).

Long car drive tomorrow :-(

[till]

@Hans: Please post it to the bugtracker so that we can check it.

@edge: I'am sorry that you have these problems. Thats the reason why the network configuration support is disabled by default. It can only be used for standard setups that use eth0. Other setups or network card names are not supported.

[Hans]

@Till,
I did that now.

@Edge, i feel sorry for you.

[till]

@edge. I've added a warning text to tthe network settings option to explain when it can not be used.

@hans: thanks for the bugtracker entry. Will fix that until 3.0.3 final.

[edge]

Thank you both.

After a +2 hr car drive I managed to fix the server again! (normally it only takes 50 minutes, but I got stuck in a 11 KM traffic jam)

On the way back I took a quick lunch at the Mcdonalds (the only fun part about the trip today).

I'm now talking to the DC about getting KVM over IP.

PS. I've seen a lot of DC's here in the Netherlands, and for sure the girl behind the desk at the DC where I was today is the best looking one!
Damn she was cute...