Re: Is bonding supported ?

On Tue, Oct 04, 2005 at 01:35:43AM +0000, Eric Chan wrote:
> Horms <horms <at> verge.net.au> writes:
> 
> > 
> > On Thu, Sep 29, 2005 at 01:00:58PM -0600, Terry, Jason wrote:
> > > I've got my cluster setup on bond0 and working fine.
> > > 
> > >  
> > > 
> > > However I did find a few scripts that were setup specifically for eth0.
> > > Simply changing these to bond0 worked.
> > > 
> > >  
> > > 
> > > This was the file that had eth0 hardcoded
> > > 
> > > /usr/sbin/arptables-noarp-addr
> > 
> > Thanks for pointing that out, I'll fix that up for the next release.
> > Please let me know if you find any others.
> > 
> 
> Hi, 
> 
> I have a server with 4 ethernet card, bond0 is binded to eth0 and eth1, bond1 
> is binded to eth2 and eth3. bond0 and bond1 are connected to 2 different 
> network segment. I want to set up 2 virtual ip, one for bond0 and one for 
> bond1. To build the arptables, arptables-noarp-addr is modified 2 times and 
> executed for bond0 and bond1 respectively.
> 
> Follow after, there are the below steps:
> 
> cd /etc/ha.d/rc.d && ln -s arptables-noarp-addr_takeip local_takeip;
> cd /etc/ha.d/rc.d && ln -s arptables-noarp-addr_giveip local_giveip;
> 
> I find that arptables-noarp-addr_takeip and arptables-noarp-addr_giveip are 
> calling to 
> 
> arptables-noarp-addr_takegiveip 
> 
> which in turn will call /usr/sbin/arptables-noarp-addr
> 
> However, arptables-noarp-addr is either configured with bond0 or bond1. How 
> should I modify arptables-noarp-addr ? Thx a lot for your reply. 

As I mentioned before, the hardcoding of the interface is wrong, it
is a bug, it should not be there, it shold be fixed. 

If in the mean time you want to hack it to hardcode in different
interfaces, I'd recommend just making multiple copies of
/usr/sbin/arptables-noarp-addr and having
arptables-noarp-addr_takegiveip call all of them.

-- 
Horms


-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.