Re: [Spread-users] unconfigured interfaces

Hi,

There is a Wackamole list, [email protected] .  I know 
this Linux issue comes up from time to time, but I'm not sure if anyone 
has solved it (except using the work-arounds you mentioned).  Be aware 
that running Spread on a different physical interface than Wackamole 
might cause some issues, because the two interfaces can fail independently.

Cheers,
Ryan

Kieren Hynd wrote:

> Hi,
> 
> More of a linux networking / Wackamole question really (is there a
> mailing list for Wackamole?), but maybe someone here has the answer :)
> 
> We'd like to let Wackamole have its Virtual IP's on an interface by
> itself (eth0), with Spread messages going over another interface (eth1)
> on a private network.
> 
> This works ok if we assign an address to eth0 in /etc/network/interfaces
> on the linux servers, but it also means that we have to statically bind
> one of the VIP's to each machine, or give it another address outside of
> the VIP range.
> 
> So, the question is: Does anyone know of a way to get Wackamole to
> manage its virtual interfaces on a 'real' interface under linux that has
> no address assigned to it (ie; down)?
> If we try to run Wackamole on an interface that isn't up, it has
> problems bringing up its virtual interfaces because the interface eth0
> wasn't up, and therefore had no routes in place.
> 
> I'd like not to have to assign one of the VIPs to eth0 to just get it
> configured (and also not to have to set preferred VIPs in wackamole).  
> I'd also not like to assign other addresses outside of the VIP range to
> eth0 just to get the interface up.
> 
> Is it possible to get Wackamole to create a default route when it brings
> up its virtual interfaces, or is this something that should be achieved
> in linux's IP functions (if so, could someone give me a clue how?).
> 
> Thanks,
> Kieren
> 
> _______________________________________________
> Spread-users mailing list
> [email protected]
> http://lists.spread.org/mailman/listinfo/spread-users
> 

-- 
Ryan W. Caudy
Center for Networking and Distributed Systems
Department of Computer Science
Johns Hopkins University