Re: loopback

On Sep 28, 2006, at 6:37 AM, Ian Eiloart wrote:
> --On 22 September 2006 17:04:13 +0100 Ian Eiloart  
> <[email protected]> wrote:
>
>>  Sometimes, when I use wackatrl -l, I get output like this:
>>
>> Owner: 127.0.0.1
>>         *     lo0:139.184.14.101/32
>>          ->   lo0:139.184.14.70/32
>>
>> Implying that the loopback interface (on some host) has control of  
>> one of
>> my VIFs. My guess is that this happens because spread and  
>> wackamole are
>> starting before en0 is up.
>
> Actually, if I restart wackamole, but leave spread alone, then the  
> problem goes away, so this must be a wackamole issue, not a spread  
> issue.

Wackamole requires a few things to be configured/running when it is  
started:

o IP networking and static IPs with established routes on the  
interfaces that will host the VIFs.
o It's hostname to be set and the IP address to which that resolves  
(gethostbyname) should be an identifying IP address (not 127.0.0.1)
o Spread must be running.

Wackamole doesn't ship with startup scripts for Mac OS X, so you are  
on your own to implement the startup procedure and satsisfy the above  
requirements.

It's worth noting that I think the issue is that the hostname is  
referring to localhost (or at least resolving there) when wackamole  
starts which means host level networking has not yet been completely  
configured and you are trying to start a networked service that needs  
it.

// Theo Schlossnagle
// CTO -- http://www.omniti.com/~jesus/
// OmniTI Computer Consulting, Inc. -- http://www.omniti.com/