Thanks for the in-depth reply. You replied to my note as follows...
>On Mon, 23 Dec 1996, CNSnet Tech Lib wrote:
>>
>> I have been encountering a memory leak that I believe I have traced to
>> the use of MLPPP ISDN connections from one of my users.
>
>[snip]
>
>> Seems to me there are two problems. 1) Why can't this user connect
>> consistently with two channels,
>
>Don't know. If you can run a logging or large scroll window do 'set
>console' and 'set beg 0x51' and watch the LCP negotiation. You might
>also check to see if his netuser or RADIUS profile has compression on,
>MPPP doesn't work with VJ header compression, make sure that compression
>is turned OFF.
Interesting. I have watched the LCP negotiation and have a captured
trace of it, some of which was supplied in previous note. That doesn't
mean I understand what I am seeing. :)
As for the compression, by default no users get VJ compression, and he
falls into this category. Interestingly enough, though, that most of my
LAN-to-LAN users, including some multi-channel ISDN clients using
Livingston or Farallon equipment, have VJ compression enabled. Is this a
problem, 'cause its been working for quite a while.
>I *THINK* you memory leak problem has been fixed in ComOS 3.5b17...yes that
>is BETA software. Read, READ, *READ* the release notes BEFORE you upgrade
>you machines!!!
Hmmm. Russian software roulette. Given the anguished cries I hear in
mail about the latest beta, I may hold on for a while. At least I have a
controlled crash cycle since I reboot on *my* terms before the machine
goes south.
>Feel free to call or email tech support concerning you issue. If you
>don't have a case open to track this problem PLEASE call in and get one
>open!
Err, I reported this via the web forms for problems
(<http://www.livingston.com/Tech/Support/supp-req-form.shtml>) and
(AFAICT) have not received any receipt or acknowldegment. I will call
Thurs (after a happy holiday to all) to see about it.
Thanks
Rusty Simmons
Cimarron Network Services, Inc.
http://www.CNSnet.net/