1. Forum
  2. RetroNet
  3. RTN_GENERAL

  • fsxnet

    From bcw142@FREEWAY to All on Wed Jun 6 12:54:00 2018
    FSXNet does seem to be down to Necronomicon. Didn't see the last message I
    sent here from Mystic Pi BBS either, though it seems to be up to here. I know Mystic Pi BBS had to kill some .bsy files at the end of May to get working
    with fsxnet again (was out a few days). Not sure totally what's up, but I suspect some .bsy files somewhere (echomail/in or echomail/out/fidonet if fsxnet is primary).
    I typed this on Necronomicon which is why it got though.

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/64)
    * Origin: Necronomicon BBS - necrobbs.strangled.net (80:774/0)
  • From Richard Menedetter@FREEWAY to bcw142 on Wed Jun 6 21:25:00 2018
    Hi bcw142!

    06 Jun 2018 12:54, from bcw142 -> All:

    FSXNet does seem to be down to Necronomicon. Didn't see the last
    message I sent here from Mystic Pi BBS either, though it seems to be
    up to here. I know Mystic Pi BBS had to kill some .bsy files at the
    end of May to get working with fsxnet again (was out a few days). Not
    sure totally what's up, but I suspect some .bsy files somewhere (echomail/in or echomail/out/fidonet if fsxnet is primary). I typed
    this on Necronomicon which is why it got though.

    No clue why you should delete busy files ...
    But he is reachable here:

    fido@odroid:~$ poll 21:1/100@fsxnet
    21:24 [7678] BEGIN, binkd/1.1a-75/Linux -p -P 21:1/100@fsxnet /usr/local/etc/binkd.cfg
    21:24 [7678] creating a poll for 21:1/100@fsxnet (`d' flavour)
    21:24 [7678] clientmgr started
    $ -h 2:310/31.1@fidonet
    -d 21:1/100@fsxnet
    + 21:24 [7679] call to 21:1/100@fsxnet
    21:24 [7679] trying agency.bbs.geek.nz [219.89.83.33]:24556...
    21:24 [7679] connected
    + 21:24 [7679] outgoing session with agency.bbs.geek.nz:24556 [219.89.83.33]
    - 21:24 [7679] OPT SSL CRAM-MD5-66a768b8812381eff018e91866c47e3a
    + 21:24 [7679] Remote requests MD mode
    - 21:24 [7679] SYS fsxHUB [fsxNet WHQ]
    - 21:24 [7679] ZYZ Paul Hayton
    - 21:24 [7679] VER Mystic/1.12A39 binkp/1.0
    + 21:24 [7679] addr: 21:1/100@fsxnet
    + 21:24 [7679] addr: 21:1/3@fsxnet
    + 21:24 [7679] addr: 21:1/2@fsxnet
    + 21:24 [7679] addr: 21:1/0@fsxnet
    + 21:24 [7679] addr: 21:0/0@fsxnet
    + 21:24 [7679] pwd protected session (MD5)
    + 21:24 [7679] done (to 21:1/100@fsxnet, OK, S/R: 0/0 (0/0 bytes))
    21:24 [7679] session closed, quitting...
    21:24 [7678] rc(7679)=0
    21:24 [7678] the queue is empty, quitting...

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: Error failed! Press any key to resume error. (80:774/18)
  • From bcw142@FREEWAY to bcw142 on Wed Jun 6 13:26:00 2018
    Repled from my end (a point off Mystic Pi BBS), but I guess it's working fine. So like I had thought before RetroNet is fine, it's FSXNet to Necronomicon
    that seems to have issues.

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Workpoint - You can't get here from there (80:603/0.3)
  • From Necromaster@FREEWAY to bcw142 on Fri Jun 8 07:50:00 2018
    On 06/06/18, bcw142 said the following...

    Repled from my end (a point off Mystic Pi BBS), but I guess it's working fine. So like I had thought before RetroNet is fine, it's FSXNet to Necronomicon that seems to have issues.

    Today i received quite a few messages on fsxnet seems to be a random thing.

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/64)
    * Origin: Necronomicon BBS - necrobbs.strangled.net (80:774/0)
  • From bcw142@FREEWAY to Necromaster on Mon Jun 11 14:24:00 2018
    On 06/08/18, Necromaster said the following...

    Today i received quite a few messages on fsxnet seems to be a random thing.

    Ya, I get that too. Mystic A39 release kills the busy flags daily, but they
    get recreated and hamper things again. Not sure what's really doing it, but
    in general your likely to get bursts due to that (me too).

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Workpoint - You can't get here from there (80:603/0.3)
  • From Necromaster@FREEWAY to bcw142 on Mon Jun 11 16:02:00 2018
    On 06/11/18, bcw142 said the following...

    On 06/08/18, Necromaster said the following...

    Today i received quite a few messages on fsxnet seems to be a random thing.

    Ya, I get that too. Mystic A39 release kills the busy flags daily, but they get recreated and hamper things again. Not sure what's really doing it, but in general your likely to get bursts due to that (me too).

    I figured it out :) I had deleted the polling event by accident :) All working normal again :)

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/64)
    * Origin: Necronomicon BBS - necrobbs.strangled.net (80:774/0)