I wrote new failure detection algorithm based on heartbeat signal for
ng_one2many node. Features:
- automatic detection of failures;
- automatic detection of recoveries;
- detection of point of failure (see diagnostics in man page);
- configurable timing parameters of failure and recovery detectio
On Sat, 11 Dec 2004, 11:58+0100, Andre Oppermann wrote:
> Edwin Groothuis wrote:
> >
> > On Sun, Dec 05, 2004 at 01:14:49AM +0300, Gleb Smirnoff wrote:
> > > On Sun, Dec 05, 2004 at 12:53:52AM +0300, Maxim Konovalov wrote:
> > > M> IMHO restoring the historic behaviour (even broken in some respect
On Wed, Jan 12, 2005 at 01:26:52PM +0300, Maxim Konovalov wrote:
> On Sat, 11 Dec 2004, 11:58+0100, Andre Oppermann wrote:
>
> > Edwin Groothuis wrote:
> > >
> > > On Sun, Dec 05, 2004 at 01:14:49AM +0300, Gleb Smirnoff wrote:
> > > > On Sun, Dec 05, 2004 at 12:53:52AM +0300, Maxim Konovalov wrote
> Date: Wed, 12 Jan 2005 12:31:19 +0900
> From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <[EMAIL
> PROTECTED]>
>
> > On Tue, 11 Jan 2005 14:01:29 -0800,
> > "Kevin Oberman" <[EMAIL PROTECTED]> said:
>
> > I think I have found a problem with TCP when run over IPv6.
> > I se
Evgeny Dolgopiat:
I wrote new failure detection algorithm based on heartbeat signal for
ng_one2many node. Features:
- automatic detection of failures;
- automatic detection of recoveries;
- detection of point of failure (see diagnostics in man page);
- configurable timing parameters of failure and
Tatuya-san,
I think this is almost certainly a network issue. I suspect that the MTU
is really NOT 1500. It's probably a couple of bytes less due to
tunneling or something similar. Unfortunately when I tried ping6 to test
with various packet sizes, my FreeBSD 5.3-Stable box did a reboot. (No
panic
I have a link which is provided by someone else that is 7 x E1s aggregated.
At leat it looks that way to me when I get to see it. however I have
only been able to get
60kB.sec across this, despite having a tcp window size of 131072 bytes..
After investigation it appears that the link is massively
In reply to Julian Elischer <[EMAIL PROTECTED]> :
> I have no control over or access to the link.. all I have is a promise
> that they will deliver
> 14Mb/Sec. with approc 300mSec. RTT to me but there is no promise about
> packet order.
My guess is that they are doing round-robin load balanci
Eli Dart wrote:
In reply to Julian Elischer <[EMAIL PROTECTED]> :
I have no control over or access to the link.. all I have is a promise
that they will deliver
14Mb/Sec. with approc 300mSec. RTT to me but there is no promise about
packet order.
My guess is that they are doing round-robin
On Wed, Jan 12, 2005 at 05:07:36PM -0800, Julian Elischer wrote:
>
> I have a link which is provided by someone else that is 7 x E1s aggregated.
> At leat it looks that way to me when I get to see it. however I have
> only been able to get
> 60kB.sec across this, despite having a tcp window size
Hi
We have pppoe server running on FreeBSD 4.9 and 90% of our wireless clients
are using MS Windows OS to access the service. I have noticed that when ever
there is some problem in the link ( due to AP or SM reboot, switch reboot etc
etc ) the pppoe connection closes. I have also noticed that t
Open up your registry editor and go to
HEKY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Modem\\Set
tings where is the number of your modem (example: 0001). On the
right pane search for a string value named InactivityTimeout. Enter the
new timeout rate in minutes. For example ente
12 matches
Mail list logo
