I can't say I'm particularly happy with the performance of the 3COM
Dual Link under Linux (and jetstart). Here's some info I extracted
from the logs for the period 11/03 - 17/03:

 - 45 disconnections.
 - 20 changes of IP address.
 - Average connect time 4 hours.

Most of the bad stuff happened during one 12 hour period when I was
dowloading lots and saturating the 128kb link. I was disconnected
28 times and had an average connect time of 25 minutes. When I wasn't
using the link much, it once stayed connected for 39 hours.

I was using the LCP thing to stop the modem disconnecting. Most of
the disconnections seemed to be because it didn't get responses from
its echo requests.

Things I might try:
  - Increase the number of tries before it fails
       LCP_FAILURE=6? 9? 42?
  - A comparison with the ping method under heavy usage.

Any suggestions are welcome. Is anybody interested in the results?

*********** REPLY SEPARATOR ***********

On 17-03-2001 at 10:38 Adam Warner wrote:

>Hi all,
>
>Could the early adopters of the 3COM Dual Link under Linux please comment on
>these questions:
>
>1. Is a 14 second ping necessary to keep the connection up? Or is there a
>different way that won't bother anyone?
>
>2. Has anyone had this modem going for days without the slightest problem?
>(This is just so I can know whether the modem is reliable in ideal conditions).
>If so is there anything you did to achieve this reliability (e.g. had your
>connection speed limited?)
>
>Thanks,
>Adam

This message is part of the NZ ADSL mailing list.
see http://unixathome.org/adsl/ for archives, FAQ,
and various documents.
To unsubscribe: send mail to majordomo@unixathome.org
with "unsubscribe adsl" in the body of the message
Received on Sat Mar 17 16:22:16 2001