DA IP alias to bonded if

[caribk]

By default, DA seems to add virtual IP aliases to ETH_DEV = eth0

I am using a channel bonded interface bond0 with two interfaces eth0 and eth1.

Is it possible to have DA assign these IPs to the bonded interface instead?

eth0 seems hardcoded in some of the scripts, so which scripts would require change and is it as easy as changing eth0 to bond0 and restart network and DA?

 

[caribk]

ne1 have an input on this?

don't want to break dedicated IP hosting, but I'll like to keep the failover functionality on aliases IPs as well.

 

[jmstacey]

You might try just simply changing the ethernet device DirectAdmin uses to the bonded one.

In /usr/local/directadmin/conf/directadmin.conf
modify the "ethernet_dev=eth0" line as needed.
Not forgetting to restart when your done.

I don't know if this will work or not, but no harm in trying.

 

[caribk]

i would think this would be feasible, however, the IP modification scripts in /usr/local/directadmin/scripts seem to have eth0 hardcoded in there..

does anyone know (John, if you're reading this..) whether this will impose a problem if I change the ethernet_dev from eth0?

if not, which additional script need changing for this to work?

 

[DirectAdmin Support]

Hello,

That's what the setting is for

DA doesn't load the first server IP address. Lets say it was eth0, so set the ethernet_dev=eth1 for DA to use for the 2nd device IP.

Or alternatively you can just add them yourself using the ususal redhat scripts:

create:
/etc/sysconfig/network-scripts/ifcfg-eth1

from a copy of ifcfg-eth0, and setup the correct info in it. Since redhat's network setup happens before DA's the IP's will be loaded in by the system.. and when DA tries, it will complain it already there, but shouldn't cause any damage.

Getting into more detail, DA calls /usr/local/directadmin/scripts/addip and passes the IP, ethernet device netmask etc... to it. So you could also play around with that to customize what it does (only if you need to).

John