RE: Problem with 'worst' conn method reporting

["Schwimmer, Eric E *HS" <EES2Y (at) hscmail.mcc.virginia.edu>]

Doesn't look like this made its way into the current alfa code.
(We must migrated to a new servers and this bit me again, so
I thought I'd give it a bump).

-Eric Schwimmer
Network Engineer
UVA HSCS Network Engineering  

> -----Original Message-----
> From: Schwimmer, Eric E *HS 
> Sent: Friday, November 04, 2005 9:40 AM
> To: hobbit (at) hswn.dk
> Subject: Problem with 'worst' conn method reporting
> 
> 
> Hi Henrik,
> 
> We've had a problem with the 'worst' conn method for a while now,
> and I've never got around to reporting or looking into it.  Basically
> what happens is that a host with multiple IP addresses and the 'worst'
> conn method wont report any status changes (it will always be 
> green, even
> if one or all of its ips are unpingable).
> 
> I think I've fixed this, it was a pretty simple bug;  on line
> 1383 of bbtest-net.c, I changed 'countasdown = 0;' to 
> 'countasdown = 1;'.
> I didn't really investigate the ramifications of what this 
> change might
> have on the rest of the code, so let me know if I'm way off base.
> (I know it did fix the worst issue, though, because 3 of our 
> multi-interface
> sites with unpingable ifcs immediately went red).
> 
> Regards,
> -Eric Schwimmer
> Network Engineer
> UVA HSCS Network Engineering 
>