1. Forum
  2. fsxNet
  3. FSX MYS

  • Hello, World

    From nathanael@21:1/101 to Avon on Sat Dec 22 01:10:36 2018
    I must be barking up the wrong tree. It's gotta be some config issue with the Pi itself, not with Mystic.

    I've created two installations, on my Pi and on my desktop, installing them
    in tandem to make sure they're configured identically. AFAICS, the only difference is the package: mys112a39_pi.zip on the Pi, and mys112a39_l64.zip
    on the desktop.

    The desktop appears to poll successfully (although I don't get any mail), but the Pi fails. It's past my bedtime and I'm stumped :-(

    From my desktop:

    Dec 22 00:41:47 FIDOPOLL Version 1.12 A39 2018/04/21
    Dec 22 00:41:47 Scanning 21:1/100
    Dec 22 00:41:47 Queued 0 files (0 bytes) to 21:1/100
    Dec 22 00:41:47 Polling BINKP node 21:1/100 by IPV4
    Dec 22 00:41:47 Connecting to agency.bbs.nz:24556
    Dec 22 00:41:47 Using address 219.89.83.33
    Dec 22 00:41:47 Connected IPV4 to 219.89.83.33
    Dec 22 00:41:47 S: NUL SYS *HUMONGOUS* BBS
    Dec 22 00:41:47 S: NUL ZYZ nathanael
    Dec 22 00:41:47 S: NUL VER Mystic/1.12A39 binkp/1.0
    Dec 22 00:41:47 S: ADR 21:1/999@fsxnet
    Dec 22 00:41:48 C: NUL OPT SSL CRAM-MD5-6e12582955ddb0a98e997d0ca5df383d
    Dec 22 00:41:48 C: NUL SYS fsxHUB [fsxNet WHQ]
    Dec 22 00:41:48 System fsxHUB [fsxNet WHQ]
    Dec 22 00:41:48 C: NUL ZYZ Paul Hayton
    Dec 22 00:41:48 SysOp Paul Hayton
    Dec 22 00:41:48 C: NUL VER Mystic/1.12A39 binkp/1.0
    Dec 22 00:41:48 Mailer Mystic/1.12A39 binkp/1.0
    Dec 22 00:41:48 C: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
    Dec 22 00:41:48 S: PWD
    Dec 22 00:41:49 C: OK non-secure
    Dec 22 00:41:49 S: EOB
    Dec 22 00:41:49 C: EOB
    Dec 22 00:41:49 Session ended (0 sent, 0 rcvd, 0 skip)

    From the Pi:

    Dec 21 10:41:49 FIDOPOLL Version 1.12 A39 2018/04/21
    Dec 21 10:41:49 Scanning 21:1/100
    Dec 21 10:41:49 Queued 0 files (0 bytes) to 21:1/100
    Dec 21 10:41:49 Polling BINKP node 21:1/100 by IPV4
    Dec 21 10:41:49 Connecting to agency.bbs.nz:24556
    Dec 21 10:41:50 Using address 219.89.83.33
    Dec 21 10:41:51 Connected IPV4 to 219.89.83.33
    Dec 21 10:41:51 S: NUL SYS *HUMONGOUS* BBS
    Dec 21 10:41:51 S: NUL ZYZ nathanael
    Dec 21 10:41:51 S: NUL VER Mystic/1.12A39 binkp/1.0
    Dec 21 10:41:51 S: ADR 21:1/999@fsxnet
    Dec 21 10:41:51 RB Socket read status 104
    Dec 21 10:41:51 RB Socket read result 104
    Dec 21 10:41:52 C: NUL
    Dec 21 10:41:52 Connection lost
    Dec 21 10:41:52 Authorization failed

    --- Mystic BBS v1.12 A40 2018/12/22 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to g00r00 on Sun Dec 23 07:29:10 2018
    On 12/22/18, nathanael pondered and said...

    Dec 22 00:41:47 S: NUL SYS *HUMONGOUS* BBS
    Dec 22 00:41:47 S: NUL ZYZ nathanael
    Dec 22 00:41:47 S: NUL VER Mystic/1.12A39 binkp/1.0
    Dec 22 00:41:47 S: ADR 21:1/999@fsxnet
    Dec 22 00:41:48 C: NUL OPT SSL CRAM-MD5-6e12582955ddb0a98e997d0ca5df383d Dec 22 00:41:48 C: NUL SYS fsxHUB [fsxNet WHQ]
    Dec 22 00:41:48 System fsxHUB [fsxNet WHQ]
    Dec 22 00:41:48 C: NUL ZYZ Paul Hayton
    Dec 22 00:41:48 SysOp Paul Hayton
    Dec 22 00:41:48 C: NUL VER Mystic/1.12A39 binkp/1.0
    Dec 22 00:41:48 Mailer Mystic/1.12A39 binkp/1.0
    Dec 22 00:41:48 C: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet

    Hi there.

    Next time you're playing with this code would it be possible to please add in some remote/local date and time data from each system as a handshake occurs?

    It really helps me to find/confirm a specific polling event when I am trying
    to compare local logs here with logs with a date/time supplied by a node somewhere else in the world.

    BinkD example

    + 2018.12.23 01:48:13 BINKP 1-SysOp Tony Langdon
    + 2018.12.23 01:48:13 BINKP 1-S: NUL SYS fsxHUB [fsxNet WHQ]
    + 2018.12.23 01:48:13 BINKP 1-S: NUL ZYZ Paul Hayton
    + 2018.12.23 01:48:13 BINKP 1-S: NUL VER Mystic/1.12A39 binkp/1.0
    + 2018.12.23 01:48:13 BINKP 1-S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
    + 2018.12.23 01:48:13 BINKP 1-C: NUL LOC Bendigo, Australia
    + 2018.12.23 01:48:13 BINKP 1-Location Bendigo, Australia
    + 2018.12.23 01:48:13 BINKP 1-C: NUL NDL 115200,TCP,BINKP
    + 2018.12.23 01:48:13 BINKP 1-Info NDL 115200,TCP,BINKP
    + 2018.12.23 01:48:13 BINKP 1-C: NUL TIME Sat, 22 Dec 2018 23:48:12 +1100
    + 2018.12.23 01:48:13 BINKP 1-Info TIME Sat, 22 Dec 2018 23:48:12 +1100
    + 2018.12.23 01:48:13 BINKP 1-C: NUL VER binkd/1.1a-96/Linux binkp/1.1
    + 2018.12.23 01:48:13 BINKP 1-Mailer binkd/1.1a-96/Linux binkp/1.1

    BinkIT does this

    + 2018.12.23 02:00:46 BINKP 1-S: NUL SYS fsxHUB [fsxNet WHQ]
    + 2018.12.23 02:00:46 BINKP 1-S: NUL ZYZ Paul Hayton
    + 2018.12.23 02:00:46 BINKP 1-S: NUL VER Mystic/1.12A39 binkp/1.0
    + 2018.12.23 02:00:46 BINKP 1-S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
    + 2018.12.23 02:00:46 BINKP 1-C: NUL ZYZ Ian Segers
    + 2018.12.23 02:00:46 BINKP 1-SysOp Ian Segers
    + 2018.12.23 02:00:46 BINKP 1-C: NUL LOC Ashburton, Nz
    + 2018.12.23 02:00:46 BINKP 1-Location Ashburton, Nz
    + 2018.12.23 02:00:46 BINKP 1-C: NUL NDL 115200,TCP,BINKP
    + 2018.12.23 02:00:46 BINKP 1-Info NDL 115200,TCP,BINKP
    + 2018.12.23 02:00:46 BINKP 1-C: NUL TIME Sun Dec 23 2018 01:59:01 GMT+1200 (New Zealand Standard Time)
    + 2018.12.23 02:00:46 BINKP 1-Info TIME Sun Dec 23 2018 01:59:01 GMT+1200
    (New Zealand Standard Time)
    + 2018.12.23 02:00:46 BINKP 1-C: NUL VER BinkIT/2.12,JSBinkP/1.112,sbbs3.17a/Win32 binkp/1.1
    + 2018.12.23 02:00:46 BINKP 1-Mailer
    BinkIT/2.12,JSBinkP/1.112,sbbs3.17a/Win32 binkp/1.1
    + 2018.12.23 02:00:46 BINKP 1-C: ADR 21:1/115@fsxnet 316:64/1 719:570/2 3:770/330@fidonet 24:400/102@sportnet

    Thanks :)

    Best, Paul

    --- Mystic BBS v1.12 A40 2018/12/22 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to nathanael on Sun Dec 23 07:35:08 2018
    On 12/22/18, nathanael pondered and said...

    I must be barking up the wrong tree. It's gotta be some config issue
    with the Pi itself, not with Mystic.

    I've created two installations, on my Pi and on my desktop, installing them in tandem to make sure they're configured identically. AFAICS, the only difference is the package: mys112a39_pi.zip on the Pi, and mys112a39_l64.zip on the desktop.

    First things first, let's get you a reliable node number so we can test
    without any problems of packets going to another test node running the /999
    aka

    I will be in touch today with set up info via email.

    --- Mystic BBS v1.12 A40 2018/12/22 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From nathanael@21:1/999 to Avon on Sun Dec 23 05:29:50 2018
    Next time you're playing with this code would it be possible to please
    add in some remote/local date and time data from each system as a handshake occurs?

    I'd love to, but my newbness is showing. Is this a setting somewhere, or do I do it by hand?

    Meanwhile, I'm UTC+8, or five hours behind NZ.

    --nathanael

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: *HUMONGOUS* BBS (21:1/999)
  • From g00r00@21:1/112 to nathanael on Sat Dec 22 18:25:14 2018
    Dec 21 10:41:51 RB Socket read result 104

    This is a "connection reset by peer" error, and its an error not generated
    from within Mystic itself so this is a tough one to call.

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)
  • From g00r00@21:1/112 to Avon on Sat Dec 22 18:29:18 2018
    Next time you're playing with this code would it be possible to please
    add in some remote/local date and time data from each system as a handshake occurs?

    + 2018.12.23 01:48:13 BINKP 1-C: NUL TIME Sat, 22 Dec 2018 23:48:12
    + 2018.12.23 02:00:46 BINKP 1-C: NUL TIME Sun Dec 23 2018 01:59:01

    This sort of showcases one reason why I don't do it ^^

    There is no real format for the time that is used by everyone, so at least
    from a programmatic perspective it makes it sort of useless if we never know what they're really going to send.

    But anyway, sure I'll add it. It should only take me a couple of minutes.

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)
  • From vk3jed@21:1/109.1 to nathanael on Sun Dec 23 09:16:32 2018
    On 23-Dec-2018 16:29, nathanael wrote to Avon <=-

    I'd love to, but my newbness is showing. Is this a setting somewhere,
    or do I do it by hand?

    Meanwhile, I'm UTC+8, or five hours behind NZ.

    Western Australia or China or...? :D


    ... You did WHAT in my name? - God.
    --- MultiMail/Win
    * Origin: Bush Track BBS (21:1/109.1)
  • From nathanael@21:4/123 to vk3jed on Fri Dec 28 06:13:46 2018
    Western Australia or China or...? :D

    Neither. Taiwan.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: *HUMONGOUS* BBS (21:4/123)
  • From Vk3jed@21:1/109 to nathanael on Fri Dec 28 14:44:00 2018
    On 12-28-18 06:13, nathanael wrote to vk3jed <=-

    Western Australia or China or...? :D

    Neither. Taiwan.

    I was close with China - neighbours. :D


    ... Windows loading... Come back tomorrow.
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)