* Replying to a msg in ipv6 (ipv6)
I found an interesting thing.. I polled with Taurus your port 60179,
IFC, but the connection was established as binkp.
On 01/20/2018 05:03 PM, you wrote to Alex Shuman:
* Replying to a msg in ipv6 (ipv6)
I found an interesting thing.. I polled with Taurus your port 60179, IFC, but the connection was established as binkp.
Oh, your Taurus probably had a brain fart.
But I have to admit that once upon a time my Radius made an accidental
POTS call to Kiev and getting a hydra connection, and being offered a
chat option on the back channel. :-D
Does Alex read here (now?). Hi Alex!
Or two argus clones were smart enough to handshake the best common protocol? I haven't used Argus/Radius/Taurus so much in the past so I wouldn't know.
This was Argus-related thing, not Alex-related thing, so I posted it
only here. :)
connectsOr two argus clones were smart enough to handshake the best common
protocol? I haven't used Argus/Radius/Taurus so much in the past so I
wouldn't know.
My node connects with Scott Little's Argus system many, many times a day but always on the binkP port, though there were some recent telnet
as I think Scott was experimenting. I don't know much either.
Radius-to-Radius connection to your ifc port 60179:
=== Cut ===
21-Jan-2018 09:04:37 Running under: Windows NT 6.1 (build: 7601, Service
21-Jan-2018 09:04:37 Connect To 122.148.59.26 #60179
21-Jan-2018 09:04:38 EMSI data send
21-Jan-2018 09:04:38 Nothing for them
21-Jan-2018 09:04:38 Establishing BinkP transfer protocol
=== Cut ===
Binkp. :)
But the connection to your telnet port was EMSI/Hydra:
: 21-Jan-2018 17:11:41 Mailer :Radius/4.011/24.10.2013,17:38(Bzdeta)/Win32
I also see...
: Mailer : Radius/4.011/24.10.2013,17:38(Bzdeta)/Win32
Is that a private edit? Or, could you drop me a copy if you would
recommend it... please?
Take a look at this website:
http://bakhvaloff.ru/Download/Taurus/
There you can find "Radius rebuilded".
TK> Take a look at this website:
TK> http://bakhvaloff.ru/Download/Taurus/
TK> There you can find "Radius rebuilded".
Mmm... nice. Thank you, kindly.
Not much of a picture gallery. He needs to travel more.
Oops, now I'm on his 'map'. :)
http://bakhvaloff.ru/Download/Taurus/
On 21 Jan 18 11:14, you wrote to me:
http://bakhvaloff.ru/Download/Taurus/
After a series of much-needed backups yesterday afternoon I tried the
subj Radius on my main node (~/384) for about two hours between
1600-1800, my time. I couldn't figure out why traffic suddenly
reduced, even for a Sunday. Then I checked this node's log file,
which was choked up with errors from attempts to contact that Radius, which all along, was still happily dealing with your node's polls
together with those of a couple of other links. It just didn't like _this_ node's (binkD?) polls, after the initial first or second
successful polls.
The error presented was like an old one involving a 2004/2005 Radius build. It's an error reported in a _calling_ node's log as a "got
M_BSY: Too many servers are running" entry, numerous times. Oops.
That was the only glitch seen during the test run.
Needless to say, I've returned to using the trusty last official
release, "Radius/4.010/21.01.2005,13:56(Final-Release)/Win32
binkp/1.1". No problems.
Did your test node present any hiccups during your testing?
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.
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.
You won't on that node. And may never ever notice as there is no indication there's a problem. It will be other nodes calling it that
may have trouble(s). I put it on my production node and wham-bam!
Oops. Some nodes worked but mine didn't (this one).
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.
Mmm... I've found that binkD still monitors 24554 even when pointed at 24555.
Do you use some other facilities of Taurus, special enough to keep
running it?
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 510 |
Nodes: | 10 (1 / 9) |
Uptime: | 134:16:49 |
Calls: | 8,200 |
Calls today: | 2 |
Files: | 15,446 |
Messages: | 913,903 |