Subj : Radius/4.011/24.10.2013,17:38(Bzdeta)/Win32
To   : Paul Quinn
From : Tommi Koivula
Date : Mon Mar 26 2018 12:56:06

26 Mar 18 10:42, you wrote to me:

 PQ> On 21 Jan 18 11:14, you wrote to me:

 TK>> http://bakhvaloff.ru/Download/Taurus/

 PQ> After a series of much-needed backups yesterday afternoon I tried the
 PQ> subj Radius on my main node (~/384) for about two hours between
 PQ> 1600-1800, my time.  I couldn't figure out why traffic suddenly
 PQ> reduced, even for a Sunday.  Then I checked this node's log file,
 PQ> which was choked up with errors from attempts to contact that Radius,
 PQ> which all along, was still happily dealing with your node's polls
 PQ> together with those of a couple of other links.  It just didn't like
 PQ> _this_ node's (binkD?) polls, after the initial first or second
 PQ> successful polls.

 PQ> The error presented was like an old one involving a 2004/2005 Radius
 PQ> build.  It's an error reported in a _calling_ node's log as a "got
 PQ> M_BSY: Too many servers are running" entry, numerous times.  Oops.
 PQ> That was the only glitch seen during the test run.

 PQ> Needless to say, I've returned to using the trusty last official
 PQ> release, "Radius/4.010/21.01.2005,13:56(Final-Release)/Win32
 PQ> binkp/1.1".  No problems.

 PQ> Did your test node present any hiccups during your testing?

I never used that Radius/Beta in real business. Only in my test setup but I 
haven't noticed any hiccups.

Taurus from that website is running at 2:221/6. Not very much traffic there 
because binkd runs in port 24554 and Taurus binkp in secondary unlisted port 
24555.

'Tommi

---
 * Origin: ================================== (2:221/360)

.