Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 3 > General

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #1  
Old 27th September 2010, 23:22
Hans Hans is offline
Moderator
 
Join Date: Dec 2005
Location: Montfoort, The Netherlands
Posts: 2,263
Thanks: 216
Thanked 649 Times in 295 Posts
Exclamation some nasty behaviour of ISPConfig 3.0.2.2.

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:


Code:
# 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:

Code:
# 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:

Code:
# 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.
__________________
Hans

MrHostman | Managed Hosting

Last edited by Hans; 28th September 2010 at 00:49.
Reply With Quote
Sponsored Links
 

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ISPConfig certificate expired, followed instructions, now can't access ISPConfig DennyCrane General 1 22nd November 2009 19:34
Install a Comodo InstantSSL Certificate for ISPconfig Apache, Postfix, Imap & Pop gwa7 Tips/Tricks/Mods 1 30th September 2009 19:08
Resources/additions for ISPConfig 3 khayjake General 3 2nd May 2009 10:40
Install a Comodo InstantSSL Certificate for ISPconfig Apache, Postfix, Imap & Pop gwa7 Installation/Configuration 0 10th April 2009 05:54
ISPConfig 3.0.0.7 Beta released till General 78 24th December 2008 12:47


All times are GMT +2. The time now is 12:29.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.