1. Forum
  2. fsxNet
  3. FSX BBS

  • Re: Mystic binkp poll logging

    From Avon@21:1/101 to Dumas Walker on Wed Apr 1 20:27:16 2020
    On 31 Mar 2020 at 06:13p, Dumas Walker pondered and said...

    Good evening,
    I have a new FTN node that is trying to connect with my system using mystic. When he attempts to poll here, he is getting the following log output on his end. On my end, I do not see any suggestion that there was ever a binkd connection to be lost.

    Is there an option in mystic to show more of the binkp output to the log so we can better trouble shoot this? I suspect he is never reaching the binkd on my end but cannot really tell from this output level.

    g00r00 recently added some logging options to later pre-alpha builds of 1.12 A46 such that you can set 'verbose' logging output for mis and mis poll

    That would be worth exploring if he is running a bleeding edge build.
    Otherwise it's probably a no until A46 is released.

    --- Mystic BBS v1.12 A46 2020/03/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Dumas Walker@21:1/175 to Al on Thu Apr 2 16:41:42 2020
    DM has suggested switching the ports on your BinkIT and Binkd mailers to
    see
    what changes.

    If you can do that I'll poll and see what happens.

    Let me know what ports to test.


    Actually, I have temporarily removed the filter files. You might try port 23 again and see what happens. On the basis of your nmap output it sure looks like it is open to you now!

    If that does not work, try port 2022. I am using a non-standard SSH port so maybe it won't be blocked if the block is outside my network.

    I would prefer not to try switching the binkit ports as it might fool my connections. I will try it if all else fails, though, but I think 2022 might be a similar test as it is not standard.

    Thanks!
    Mike
    --- SBBSecho 3.10-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)