NB> I don't plan to ever install a telnet mailer. Are you saying to just NB> poll you with binkd on that port? The mailer may answer, but the telnet NB> session won't be successful seeing as though binkd is a binkp mailer only.
Interesting thought but, no. BinkP won't work on that port here. We were talking telnet IAC, on the same port for both mailer & BBS.
PQ>> BTW, which program do you think answered your call? Clue: I have PQ>> never (not ever!) used the Mystic telnet server, nor any other.
NB> The version of Mystic you're using does not have a telnet server for NB> Linux. That I know. Then again, you mention using all these Linux NB> systems everywhere, yet you're running Argus? I guess I never paid much NB> attention if/when you've ever described your setup.
Three VirtualBox nodes: main node under Win98SE, running Radius/Mystic/JamNNTPd; this 'Pvt' node under Puppy 4.2.1 (multiuser) running binkD/Mystic/JamNNTPd (BBS is unused); and, a private node under Puppy 4.1.2 running binkD & JamNNTPd only. I also have a binkD job running as a point on my main PC in Ubuntu 10.04 LTS, doing non-Fido file transfers between the three nodes.
NB> Then again, when you telnet to port 10023 on your system. There is NB> nothing that states what telnet server is answering the call, either. So NB> "which program do you think answered your call?" I guess I can now NB> answer that it was Argus, but noone else would know that without you NB> saying so.
Yes, Radius answered and passed the task onto Mystic. Then it carried on looking for any further binkP, telnet, IFC callers, be they mailer or BBS as appropriate. OTOH, IFC callers don't get a look in since it isn't port-forwarded.
NB> Your port 23 answers, but hangs up right away without any NB> notification. I'm not sure if that's intended or not though.
Most likely dropped by the ADSL box.
Cheers, Paul.
--- Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 * Origin: Paul's Puppy 4.2.1 multiuser vBox - M'boro, Qld, OZ (3:640/1384)
