On 05-25-14, Sean Dennis said the following...
 
 SD> Hi, Darryl-
 SD> 
 SD> DP> This is interesting, in that g00r00 had implemented binkp for Mystic,
 SD> DP> it
 SD> DP> also had issues connecting to IREX uplinks.  That has been fixed now,
 SD> DP> have to wonder if it's a standard problem with IREX.
 SD> 
 SD> MBSE has its own binkd built-in.  I have heard that Rex 2.31 has a buggy
 SD> binkp implementation but I cannot verify that myself.  I have two nodes
 SD> in my own FTN that are running the Windows version of 2.31 and I get
 SD> this every time from them:
 SD> 
 SD> ! 25-May-2014 23:15:51 mbcico[12055] tty_read: error flag
 SD> ? 25-May-2014 23:15:51 mbcico[12055] Binkp: receiver status Error
 SD> + 25-May-2014 23:15:51 mbcico[12055] Binkp: session finished, rc=108
 SD> + 25-May-2014 23:15:53 mbcico[12055] Incoming call failed (rc=108)
 SD> + 25-May-2014 23:15:53 mbcico[12055] Terminated with error 108
 SD> 
 SD> That error 108 is a "file transfer error" according to
the MBSE docs.  I
 SD> did notice even on my OS/2 system that other systems running 2.31 would
 SD> very abruptly close the session and that would cause my 'Rex to complain.

This is interesting news and very relevant because this is almost the exact
behavior I see between Mystic binkp and Irex (on os/2).  I'll have to bring
this to g00's attention.  If he doesn't already know.

 "No matter where you go, there you are!" - B. Bonzai

--- Mystic BBS v1.10 A42 (Linux)