So I loaded the new 3.3.1c1 code, made sure the additions required were
placed in the dictionary, and wanted for one of my annoying disconnects.
Well the unit didn't let me down, and within hours my line dropped. So
now it was time to play detective and find out why. I started browsing
the radius accounting logs to find that all the Async connections (to the
PM2's serial ports) seemed to work fine, but any connections to the ISDN
ports (It didn't matter if it was PPP or V.120) didn't log the Termination
reason. I ran multiple tests, from just handing up the connection, and
normal host disconnects, still nothing!
Finally the other day I decided to just grab the new 3.3.2b3 from the
ftp site and see how it worked. As soon as I uploaded this into the
PM's the ISDN termination logging started working. So I suspect that
the ISDN termination logging is NOT WORKING in the 3.3.1c1 update, but
is OK in the 3.3.2b3 beta software. Just thought I would share this
with everyone..
FYI, I have only had the BETA code running about a day, but so far it
seems OK. The only strangeness I have noted on my ISDN connection is
that when I perform a remote logout (Shell using V.120 Async) the PM2
reports connection closed, but sits for about 30 seconds before actually
dropping the circuit. Under the 3.3.1c1 and earlier releases, when it
said connection closed, the line was dropped instantly...
-------------------------------------------------------------------------------
Internet : howardl@abs.net | Howard D. Leadmon
UUCP : wb3ffv!howardl | ABSnet Internet Services
PHONE : (410)-361-8160 | 200 E. Lexington Street
FAX : (410)-361-8162 | Suite-1602
PACKET : WB3FFV @ WB3FFV.MD.USA.NA | Baltimore, MD 21202
WWW : http://www.abs.net |