On Wed, May 12, 2004 at 12:30:26PM +0200, Sebastien Petit wrote:
> There is a problem with freevrrpd and em drivers. em driver go down,wait 2
> seconds, and become up again when an SIOCIFLLADDR is used. So a flapping
> problem will appear. The last revision in CVS resolve this problem and a new
> p
> Do you have filtering turned on/are you allowing multicast out to
> the VRRP address? I'm a bit perplexed with "interface em0 is faulty". I
What do you mean speaking abount 'allowing multicast out'?
I'm having troubles with em0 and multicasts too (this time with RIPv2),
can't mak
Hi Tom,
There is a problem with freevrrpd and em drivers. em driver go down,wait 2
seconds, and become up again when an SIOCIFLLADDR is used. So a flapping
problem will appear. The last revision in CVS resolve this problem and a new
parameter called carrier_timeout (see the man with the new revisi
On May 11, 2004, at 6:38 PM, Tom Arnold wrote:
A bit more digging and I found that there was an em0 fix, so I cvsup'd
and
got it working. Failover is painfully slow ( read : not usable ) so I
think
my solution is to put fxp cards in these machines.
Interesting. Can you see why it's slow? And
On May 11, 2004, at 6:08 PM, Tom Arnold wrote:
Hardware is a Dell 650 with, of course, onboard Intel Pro/1000.
Also using freevrrp on other Dell650's, but they came with Pro/100's (
fxp )
and work fine, so I'm leaning towards hardware or driver quirks, but
any
ideas appreciated.
Do you have fil
On Tue, May 11, 2004 at 06:08:52PM -0700, Tom Arnold wrote:
> Having a problem with a very simple freevrrp config.
> This is FreeBSD 5.2.1p5
A bit more digging and I found that there was an em0 fix, so I cvsup'd and
got it working. Failover is painfully slow ( read : not usable ) so I think
my so
