In a situation where there was issue, bug, exploit, in the tcp/ip stack
which caused ip communication to go dead then serial line communication
may also be affected, because the Heartbeat Package uses an UDP
Heartbeat over ppp when a serial connection is used.
I don't really know if this is the case or not. I have no knowledge of
the inner working of the linux tcp/ip code.
JDF
>Derek Martin wrote:
>
> On Mon, 17 Jul 2000, Paul Lussier wrote:
>
> >
> > In a message dated: Mon, 17 Jul 2000 01:27:31 EDT
> > Derek Martin said:
> >
> > >What makes you think this? Heartbeat specifically states that heartbeat
> > >ethernets should be *dedicated* (as does our documentation, I believe)
> > >which should prevent that scenario, so if you failed miserably to follow
> > >directions and not do that, you deserve what you get...
> >
> > It doesn't matter if their dedicated or not, it's the same IP stack that's
> > getting hammered! The only thing that will help in this case is NON-ethernet
> > heartbeat. Serial line, quorum disk, or telepathic mind-melding, as long as
> > it's not ethernet!
>
> Not likely to be a problem, unless you've got a seriously FAT pipe. a T1
> or T3 can't even saturate your ethernet. If you can afford a fatter pipe,
> you're not using redundant Linux firewalls. :)
>
> --
> Derek Martin
> System Administrator
> Mission Critical Linux
> [EMAIL PROTECTED]
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
