• Nodelist Hatching

    From Avon@21:1/101 to All on Tue Feb 9 02:35:25 2021
    Hi there

    I have been working on getting the nodelist hatching working under the new systems I have in play at 1/100.. the first updated nodelist was sent out tonight. I think all should be fine but it may pay to check and see if it imported OK on your BBS and looks ok etc.. let me know :)

    I am still working on infopack updates in the coming days.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106.1 to Avon on Mon Feb 8 05:55:30 2021
    Re: Nodelist Hatching
    By: Avon to All on Mon Feb 08 2021 09:35 pm

    I have been working on getting the nodelist hatching working under the new systems I have in play at 1/100.. the first updated nodelist was sent out tonight. I think all should be fine but it may pay to check and see if it imported OK on your BBS and looks ok etc.. let me know :)

    It made it's way through here and did what it always does, no problems here.

    Ttyl :-),
    Al

    ... Is man one of God's blunders or is god one of Man's blunders?
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Zip@21:1/202 to Avon on Mon Feb 8 15:30:19 2021
    Hello Avon!

    On 08 Feb 2021, Avon said the following...
    I have been working on getting the nodelist hatching working under the
    new systems I have in play at 1/100.. the first updated nodelist was
    sent out tonight. I think all should be fine but it may pay to check and see if it imported OK on your BBS and looks ok etc.. let me know :)

    One thing I noticed is that the filename has changed from (e.g.) FSXNET.Z36 to FSXNET.z43, i.e. lowercase z now; updated my unpacking cron jobs here (I unpack them for ifcico) to accept both. :-)

    Best regards
    Zip

    --- Mystic BBS v1.12 A47 2021/01/24 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From Oli@21:3/102 to Avon on Mon Feb 8 16:43:01 2021
    Avon wrote (2021-02-08):

    Hi there

    I have been working on getting the nodelist hatching working under the new systems I have in play at 1/100.. the first updated nodelist was sent out tonight. I think all should be fine but it may pay to check and see if it imported OK on your BBS and looks ok etc.. let me know :)

    better change the lowercase z (NODELIST.z43) to an uppercase Z (NODELIST.Z43)

    ---
    * Origin: . (21:3/102)
  • From Warpslide@21:3/110 to Avon on Mon Feb 8 12:50:58 2021
    On 08 Feb 2021, Avon said the following...

    I have been working on getting the nodelist hatching working under the
    new systems I have in play at 1/100.. the first updated nodelist was
    sent out tonight. I think all should be fine but it may pay to check and see if it imported OK on your BBS and looks ok etc.. let me know :)

    Nodelist received and looks ok here:

    Archive: ./FSXNET.z43
    Length Date Time Name
    --------- ---------- ----- ----
    34891 2021-02-08 03:27 FSXNET.043
    --------- -------
    34891 1 file

    $ head -n1 FSXNET.043

    ;A fsxNet Nodelist for Friday, February 12, 2021 -- Day number 043 : 29454

    I know you're from the future, but this is getting ridiculous! ;)


    Kind of a strange oddity, I can't poll 21:1/100, 21:2/100, 21:4/100 & 21:5/100, I get the same invalid IP on each:

    --------------------- POLL v1.12 A47 2021/02/01 Mon, Feb 08 2021 (loglevel 3) + 2021.02.08 07:29:46 Poll BINKP node via address lookup: 21:1/100
    + 2021.02.08 07:29:46 1-Polling 21:1/100 on slot 1 via BINKP
    + 2021.02.08 07:29:46 1-Connecting to 24556 on port 24554
    + 2021.02.08 07:29:46 1-Using address 0.0.95.236
    + 2021.02.08 07:29:52 1-Unable to connect
    + 2021.02.08 07:29:54 Polled 1 systems

    It looks like Mystic is trying to connect to the port number as the host address, I am running the latest pre-alpha which may the the issue.

    I can poll 21:3/100 fine, but assuming that's because I have Deon setup as a node.

    Trying to poll 21:1/10 & /101 yield the same results, but I can poll 21:1/102 just fine:

    --------------------- POLL v1.12 A47 2021/02/01 Mon, Feb 08 2021 (loglevel 1) + 2021.02.08 07:49:17 Poll BINKP node via address lookup: 21:1/102
    + 2021.02.08 07:49:17 1-Polling 21:1/102 on slot 1 via BINKP
    + 2021.02.08 07:49:17 1-Connecting to error404bbs.ddns.net on port 24554
    + 2021.02.08 07:49:17 1-Using address 71.74.66.9
    + 2021.02.08 07:49:17 1-Connected by IPV4 to 71.74.66.9
    + 2021.02.08 07:49:17 1-System Error 404 BBS
    + 2021.02.08 07:49:17 1-SysOp Sysop Solaris
    + 2021.02.08 07:49:17 1-Mailer Mystic/1.12A46 binkp/1.0
    + 2021.02.08 07:49:17 1-Remote Queue: 0 files 0 bytes
    + 2021.02.08 07:49:18 1-Session ended (0 sent, 0 rcvd, 0 skip)
    + 2021.02.08 07:49:18 Polled 1 systems


    Jay

    --- Mystic BBS v1.12 A47 2021/02/01 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From Al@21:4/106.1 to Robert Wolfe on Mon Feb 8 10:18:02 2021
    Re: Nodelist Hatching
    By: Robert Wolfe to Al on Mon Feb 08 2021 07:12 am

    Ok, slowly rebuilding my system here. Moved it over to a VPS and it
    runs very nicely :)

    What VPS are you using? I was using a VPS (linode.com) about a year ago and found it to be quite good, I may go back to something like that at some point.

    Ttyl :-),
    Al

    ... For people who like peace & quiet - A phoneless cord!
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Robert Wolfe@21:2/136 to Al on Mon Feb 8 12:12:24 2021

    It made it's way through here and did what it always does, no problems here.

    Ok, slowly rebuilding my system here. Moved it over to a VPS and it
    runs very nicely :)
    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: Omicron Theta * Southaven MS * winserver.org (21:2/136)
  • From Alpha@21:4/158 to Robert Wolfe on Mon Feb 8 12:14:17 2021
    Ok, slowly rebuilding my system here. Moved it over to a VPS and it
    runs very nicely :)

    Just did the same. Had enough of power outages, accidental unplugs an my god-awful slow network. I'm on the Digital Ocean VPS $5/mo (USD) plan it
    works well.



    --- Talisman v0.10-dev (Linux/x86_64)
    * Origin: The Drunken Gamer BBS (21:4/158)
  • From Avon@21:1/101 to Zip on Tue Feb 9 18:32:33 2021
    On 08 Feb 2021 at 10:30a, Zip pondered and said...

    One thing I noticed is that the filename has changed from (e.g.) FSXNET.Z36 to FSXNET.z43, i.e. lowercase z now; updated my unpacking
    cron jobs here (I unpack

    Yeah I spotted that too.. I think it's a Linux MakeNL thing but not sure how
    to fix it.. thanks for the report

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Warpslide on Tue Feb 9 18:36:57 2021
    On 08 Feb 2021 at 07:50a, Warpslide pondered and said...

    ;A fsxNet Nodelist for Friday, February 12, 2021 -- Day number 043 :
    29454

    I know you're from the future, but this is getting ridiculous! ;)

    Yeah sorry about that :)

    Kind of a strange oddity, I can't poll 21:1/100, 21:2/100, 21:4/100 & 21:5/100, I get the same invalid IP on each:

    --------------------- POLL v1.12 A47 2021/02/01 Mon, Feb 08 2021 (loglevel 3) + 2021.02.08 07:29:46 Poll BINKP node via address lookup: 21:1/100 + 2021.02.08 07:29:46 1-Polling 21:1/100 on slot 1 via BINKP
    + 2021.02.08 07:29:46 1-Connecting to 24556 on port 24554
    + 2021.02.08 07:29:46 1-Using address 0.0.95.236
    + 2021.02.08 07:29:52 1-Unable to connect

    That's strange... if you try pinging the hubs domain names I wonder what you get.

    I do know that IPv6 connects to 21:1/100 will likely be down at the moment until I shift a few more things over to the new Linux box. But IPv4 will be fine.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Oli on Tue Feb 9 18:56:18 2021
    On 08 Feb 2021 at 11:43a, Oli pondered and said...

    better change the lowercase z (NODELIST.z43) to an uppercase Z (NODELIST.Z43)

    I wonder how to do this, it's MakeNL that's doing this. Guess it's a Linux thing?

    08-Feb-2021 21:27:21 makenl[26357] myfnmerge: drive='(null)' dir='/hub/makenl/fsxnet/out' name='FSXNET' ext='043'
    d 08-Feb-2021 21:27:21 makenl[26357] myfnmerge: drive='' dir='/hub/makenl/fsxnet/out' name='FSXNET' ext='$$$'
    + 08-Feb-2021 21:27:21 makenl[26357] Unchanged output file will be forced submitted
    d 08-Feb-2021 21:27:21 makenl[26357] myfnmerge: drive='(null)' dir='/hub/makenl/fsxnet/out' name='FSXNET' ext='360'
    d 08-Feb-2021 21:27:21 makenl[26357] myfnmerge: drive='' dir='/hub/makenl/fsxnet/out' name='FSXNET' ext='036'
    d 08-Feb-2021 21:27:21 makenl[26357] myfnmerge: drive='(null)' dir='/hub/makenl/fsxnet/out' name='FSXNET' ext='z43'
    + 08-Feb-2021 21:27:21 makenl[26357] Creating archive '/hub/makenl/fsxnet/out/FSXNET.z43' containing '/hub/makenl/fsxnet/out/FSXNET.043'
    d 08-Feb-2021 21:27:21 makenl[26357] os_spawn(): 'zip -jo /hub/makenl/fsxnet/out/FSXNET.z43 /hub/makenl/fsxnet/out/FSXNET.043'
    d 08-Feb-2021 21:27:21 makenl[26357] os_spawn(): system() rc=0
    d 08-Feb-2021 21:27:21 makenl[26357] /hub/temp/makenl/src/fileutil.c: cleanit(): cleanup no
    + 08-Feb-2021 21:27:21 makenl[26357] CRC = 29454

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106.1 to Avon on Mon Feb 8 21:56:47 2021
    Re: Re: Nodelist Hatching
    By: Avon to Warpslide on Tue Feb 09 2021 01:36 pm

    That's strange... if you try pinging the hubs domain names I wonder what you get.

    It is strange. I poll 21:1/100 from my Mystic BBS without adding 21:1/100 as an echomail link so the mailer was reading the nodelist and got the same result.

    I then added 21:1/100 as an echomail link with hostname info and the poll was good.

    I couldn't come to any conclusion why.

    Ttyl :-),
    Al

    ... I have a dream... C:\ 999,999,999,999 Megs free!
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Avon@21:1/101 to Al on Tue Feb 9 18:59:34 2021
    On 08 Feb 2021 at 04:56p, Al pondered and said...

    It is strange. I poll 21:1/100 from my Mystic BBS without adding
    21:1/100 as an echomail link so the mailer was reading the nodelist and got the same result.

    what domain is it polling Al?

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106.1 to Avon on Mon Feb 8 22:12:21 2021
    Re: Re: Nodelist Hatching
    By: Avon to Al on Tue Feb 09 2021 01:59 pm

    what domain is it polling Al?

    Here's my log. 21:1/100 is not listed in echomail nodes. I just ran "./mis poll 21;1/100".

    --------------------- POLL v1.12 A47 2021/02/01 Mon, Feb 08 2021 (loglevel 3) + 2021.02.08 17:04:36 Poll BINKP node via address lookup: 21:1/100
    + 2021.02.08 17:04:36 1-Polling 21:1/100 on slot 1 via BINKP
    + 2021.02.08 17:04:36 1-Connecting to 24556 on port 24554
    + 2021.02.08 17:04:36 1-Using address 0.0.95.236
    + 2021.02.08 17:04:42 1-Unable to connect
    + 2021.02.08 17:04:44 Polled 1 systems

    This is after adding 21:1/100 as an echoamil node..

    --------------------- POLL v1.12 A47 2021/02/01 Mon, Feb 08 2021 (loglevel 1) + 2021.02.08 17:08:32 Poll BINKP node via address lookup: 21:1/100
    + 2021.02.08 17:08:32 1-Polling 21:1/100 on slot 1 via BINKP
    + 2021.02.08 17:08:32 1-Connecting to net1.fsxnet.nz on port 24554
    + 2021.02.08 17:08:32 1-Using address 219.89.83.33
    + 2021.02.08 17:08:32 1-Connected by IPV4 to 219.89.83.33
    + 2021.02.08 17:08:32 1-System Agency + Risa HUB
    + 2021.02.08 17:08:32 1-SysOp Paul Hayton
    + 2021.02.08 17:08:33 1-Location Dunedin, New Zealand
    + 2021.02.08 17:08:33 1-Mailer binkd/1.1a-111/Linux binkp/1.1
    + 2021.02.08 17:08:33 1-Session ended (0 sent, 0 rcvd, 0 skip)
    + 2021.02.08 17:08:33 Polled 1 systems

    Ttyl :-),
    Al

    ... I tried to drown my problems.. they like beer too!
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Warpslide@21:3/110 to Avon on Tue Feb 9 01:21:26 2021
    On 09 Feb 2021, Avon said the following...

    That's strange... if you try pinging the hubs domain names I wonder what you get.

    $ ping -4 -n -c4 agency.bbs.nz
    PING agency.bbs.nz (219.89.83.33) 56(84) bytes of data.
    64 bytes from 219.89.83.33: icmp_seq=1 ttl=48 time=347 ms
    64 bytes from 219.89.83.33: icmp_seq=2 ttl=48 time=349 ms
    64 bytes from 219.89.83.33: icmp_seq=3 ttl=48 time=348 ms
    64 bytes from 219.89.83.33: icmp_seq=4 ttl=48 time=343 ms

    $ ping -4 -n -c4 net1.fsxnet.nz
    PING net1.fsxnet.nz (219.89.83.33) 56(84) bytes of data.
    64 bytes from 219.89.83.33: icmp_seq=1 ttl=48 time=324 ms
    64 bytes from 219.89.83.33: icmp_seq=2 ttl=48 time=315 ms
    64 bytes from 219.89.83.33: icmp_seq=3 ttl=48 time=331 ms
    64 bytes from 219.89.83.33: icmp_seq=4 ttl=48 time=322 ms

    $ ping -4 -n -c4 net2.fsxnet.nz
    PING error404bbs.ddns.net (71.74.66.9) 56(84) bytes of data.
    64 bytes from 71.74.66.9: icmp_seq=1 ttl=49 time=60.0 ms
    64 bytes from 71.74.66.9: icmp_seq=2 ttl=49 time=57.6 ms
    64 bytes from 71.74.66.9: icmp_seq=3 ttl=49 time=60.6 ms
    64 bytes from 71.74.66.9: icmp_seq=4 ttl=49 time=59.2 ms

    $ ping -4 -n -c4 net4.fsxnet.nz
    PING bbs.castlerockbbs.com (184.155.113.241) 56(84) bytes of data.
    64 bytes from 184.155.113.241: icmp_seq=1 ttl=55 time=99.8 ms
    64 bytes from 184.155.113.241: icmp_seq=2 ttl=55 time=98.9 ms
    64 bytes from 184.155.113.241: icmp_seq=3 ttl=55 time=97.7 ms
    64 bytes from 184.155.113.241: icmp_seq=4 ttl=55 time=102 ms


    Hub 5 doesn't like being ping'ed... :)

    $ ping -4 -n -c4 net5.fsxnet.nz
    PING rdfig.net (75.87.11.242) 56(84) bytes of data.

    --- rdfig.net ping statistics ---
    4 packets transmitted, 0 received, 100% packet loss, time 113ms


    Jay

    --- Mystic BBS v1.12 A47 2021/02/01 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From Avon@21:1/101 to Al on Tue Feb 9 19:27:48 2021
    On 08 Feb 2021 at 05:12p, Al pondered and said...

    --------------------- POLL v1.12 A47 2021/02/01 Mon, Feb 08 2021 (loglevel 3) + 2021.02.08 17:04:36 Poll BINKP node via address lookup: 21:1/100 + 2021.02.08 17:04:36 1-Polling 21:1/100 on slot 1 via BINKP
    + 2021.02.08 17:04:36 1-Connecting to 24556 on port 24554
    + 2021.02.08 17:04:36 1-Using address 0.0.95.236
    + 2021.02.08 17:04:42 1-Unable to connect
    + 2021.02.08 17:04:44 Polled 1 systems


    Yep that's strange... my router is directing 24556 traffic to 24554 as it
    comes in but it seems fine when you specify the domain name net1.fsxnet.nz or
    I imagine if you just used agency.bbs.nz also... although if you try IPv6 it will fail buy IPv4 will work.

    Hmm

    On my A46 I also saw something similar. I disabled by echomail node for 1/100 and tried a mis poll

    --------------------- POLL v1.12 A46 2020/08/26 Tue, Feb 09 2021 (loglevel 1) + 2021.02.09 14:21:15 Poll BINKP node via address lookup: 21:1/100
    + 2021.02.09 14:21:15 1-Polling 21:1/100 on slot 1 via BINKP
    + 2021.02.09 14:21:15 1-Connecting to 24556 on port 24554
    + 2021.02.09 14:21:18 1-Unable to connect
    + 2021.02.09 14:21:18 Polled 1 systems

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Warpslide on Tue Feb 9 19:29:45 2021
    On 08 Feb 2021 at 08:21p, Warpslide pondered and said...

    $ ping -4 -n -c4 agency.bbs.nz
    PING agency.bbs.nz (219.89.83.33) 56(84) bytes of data.
    64 bytes from 219.89.83.33: icmp_seq=1 ttl=48 time=347 ms
    64 bytes from 219.89.83.33: icmp_seq=2 ttl=48 time=349 ms
    64 bytes from 219.89.83.33: icmp_seq=3 ttl=48 time=348 ms
    64 bytes from 219.89.83.33: icmp_seq=4 ttl=48 time=343 ms

    $ ping -4 -n -c4 net1.fsxnet.nz
    PING net1.fsxnet.nz (219.89.83.33) 56(84) bytes of data.
    64 bytes from 219.89.83.33: icmp_seq=1 ttl=48 time=324 ms
    64 bytes from 219.89.83.33: icmp_seq=2 ttl=48 time=315 ms
    64 bytes from 219.89.83.33: icmp_seq=3 ttl=48 time=331 ms
    64 bytes from 219.89.83.33: icmp_seq=4 ttl=48 time=322 ms

    $ ping -4 -n -c4 net2.fsxnet.nz
    PING error404bbs.ddns.net (71.74.66.9) 56(84) bytes of data.
    64 bytes from 71.74.66.9: icmp_seq=1 ttl=49 time=60.0 ms
    64 bytes from 71.74.66.9: icmp_seq=2 ttl=49 time=57.6 ms

    thanks this all seems fine :) Agree?

    Hub 5 doesn't like being ping'ed... :)

    $ ping -4 -n -c4 net5.fsxnet.nz
    PING rdfig.net (75.87.11.242) 56(84) bytes of data.

    Not sure how Ruben is set up. Good to know though :)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106.1 to Avon on Mon Feb 8 22:42:54 2021
    Re: Re: Nodelist Hatching
    By: Avon to Al on Tue Feb 09 2021 02:27 pm

    Yep that's strange... my router is directing 24556 traffic to 24554 as it comes in but it seems fine when you specify the domain name net1.fsxnet.nz or I imagine if you just used agency.bbs.nz also... although if you try IPv6 it will fail buy IPv4 will work.

    It is. The nodelist looks OK though.. as far as I could tell. The issue must be something else.

    Ttyl :-),
    Al

    ... Sir, the Romulans do not take prisoners!
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Avon@21:1/101 to Al on Tue Feb 9 19:45:46 2021
    On 08 Feb 2021 at 05:42p, Al pondered and said...

    It is. The nodelist looks OK though.. as far as I could tell. The issue must be something else.

    I'm think I may tweak the nodelist to remove 24556 against 1/100 and then see how Mystic handles it then when it should be just trying to poll 24554

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Warpslide@21:3/110 to Avon on Tue Feb 9 01:44:58 2021
    On 09 Feb 2021, Avon said the following...

    thanks this all seems fine :) Agree?

    Yup, that all looks good. I got curious and removed IBN:24556 from the entry for 21:1/100 and I was then able to poll you:

    --------------------- POLL v1.12 A47 2021/02/01 Mon, Feb 08 2021 (loglevel 1) + 2021.02.08 20:41:13 Poll BINKP node via address lookup: 21:1/100
    + 2021.02.08 20:41:13 1-Polling 21:1/100 on slot 1 via BINKP
    + 2021.02.08 20:41:13 1-Connecting to net1.fsxnet.nz on port 24554
    + 2021.02.08 20:41:13 1-Using address 219.89.83.33
    + 2021.02.08 20:41:14 1-Connected by IPV4 to 219.89.83.33
    + 2021.02.08 20:41:14 1-System Agency + Risa HUB
    + 2021.02.08 20:41:14 1-SysOp Paul Hayton
    + 2021.02.08 20:41:14 1-Location Dunedin, New Zealand
    + 2021.02.08 20:41:14 1-Mailer binkd/1.1a-111/Linux binkp/1.1
    + 2021.02.08 20:41:15 1-Session ended (0 sent, 0 rcvd, 0 skip)
    + 2021.02.08 20:41:16 Polled 1 systems


    I recompiled which put the IBN:24556 back and I'm back to that weird IP address:

    --------------------- POLL v1.12 A47 2021/02/01 Mon, Feb 08 2021 (loglevel 1) + 2021.02.08 20:41:51 Poll BINKP node via address lookup: 21:1/100
    + 2021.02.08 20:41:51 1-Polling 21:1/100 on slot 1 via BINKP
    + 2021.02.08 20:41:51 1-Connecting to 24556 on port 24554
    + 2021.02.08 20:41:51 1-Using address 0.0.95.236
    + 2021.02.08 20:41:57 1-Unable to connect
    + 2021.02.08 20:41:58 Polled 1 systems


    Further investigation continues...


    Jay

    --- Mystic BBS v1.12 A47 2021/02/01 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From Avon@21:1/101 to Warpslide on Tue Feb 9 19:50:59 2021
    On 08 Feb 2021 at 08:44p, Warpslide pondered and said...

    Yup, that all looks good. I got curious and removed IBN:24556 from the entry for 21:1/100 and I was then able to poll you:

    Good stuff


    I recompiled which put the IBN:24556 back and I'm back to that weird IP address:

    OK, then it's something related to a mix of Mystic and my router redirects I think... but if I pull 24556 from my nodelist I think that should solve it
    for Mystic nodelist polling... for anyone using an explicit domain:port combo
    I think it will still be fine.

    So if you set up and echomail node with

    net1.fsxnet.nz:24556 that should work fine but be redirected via my router
    to the BinkD running on 24554 here...

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Oli on Wed Feb 10 01:04:32 2021
    On 09 Feb 2021 at 01:56p, Avon pondered and said...

    I wonder how to do this, it's MakeNL that's doing this. Guess it's a
    Linux thing?

    I think I found it, it was in MakeNL and in the zip command syntax. Next one should be uppercase again.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Oli@21:3/102 to Warpslide on Tue Feb 9 13:51:13 2021
    Warpslide wrote (2021-02-08):

    I recompiled which put the IBN:24556 back and I'm back to that weird IP address:

    --------------------- POLL v1.12 A47 2021/02/01 Mon, Feb 08 2021
    (loglevel 1)
    + 2021.02.08 20:41:51 Poll BINKP node via address lookup: 21:1/100
    + 2021.02.08 20:41:51 1-Polling 21:1/100 on slot 1 via BINKP
    + 2021.02.08 20:41:51 1-Connecting to 24556 on port 24554
    + 2021.02.08 20:41:51 1-Using address 0.0.95.236

    That's obviously a bug in the Mystic code that reads the nodelist. IBN:24556 is correct.

    0.0.95.236 expressed as an 32-bit integer is the same as 24556. The first byte of 24556 is 236, the second byte is 95.

    hex(24556)
    '0x5fec'
    0xec
    236
    0x5f
    95

    ---
    * Origin: . (21:3/102)
  • From Oli@21:3/102 to Avon on Tue Feb 9 14:02:26 2021
    Avon wrote (2021-02-09):

    On 08 Feb 2021 at 05:42p, Al pondered and said...

    It is. The nodelist looks OK though.. as far as I could tell. The
    issue must be something else.

    I'm think I may tweak the nodelist to remove 24556 against 1/100 and then see how Mystic handles it then when it should be just trying to poll 24554

    The bug needs to be fixed in Mystic. But I wonder why we need this INA:hostname,IBN[:port] combinations, when IBN:hostname[:port] would be shorter. Might be a workaround for the Mystic bug too.

    ---
    * Origin: . (21:3/102)
  • From Avon@21:1/101 to Oli on Wed Feb 10 02:09:24 2021
    On 09 Feb 2021 at 08:51a, Oli pondered and said...

    That's obviously a bug in the Mystic code that reads the nodelist. IBN:24556 is correct.

    0.0.95.236 expressed as an 32-bit integer is the same as 24556. The
    first byte of 24556 is 236, the second byte is 95.

    Ah, good catch.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Oli on Wed Feb 10 02:10:32 2021
    On 09 Feb 2021 at 09:02a, Oli pondered and said...

    The bug needs to be fixed in Mystic. But I wonder why we need this INA:hostname,IBN[:port] combinations, when IBN:hostname[:port] would be shorter. Might be a workaround for the Mystic bug too.

    without looking at all the old Fido specs I'm not sure of the answer to that one... I agree it would be good to test this option out.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Oli@21:3/102 to Avon on Tue Feb 9 14:16:56 2021
    Avon wrote (2021-02-09):

    On 09 Feb 2021 at 09:02a, Oli pondered and said...

    The bug needs to be fixed in Mystic. But I wonder why we need this
    INA:hostname,IBN[:port] combinations, when IBN:hostname[:port]
    would be shorter. Might be a workaround for the Mystic bug too.

    without looking at all the old Fido specs I'm not sure of the answer to that one... I agree it would be good to test this option out.

    You don't need to look it up. IBN:net1.fsxnet.nz:24556 without INA is valid according to FTS-5001:
    http://ftsc.org/docs/fts-5001.006

    ---
    * Origin: . (21:3/102)
  • From Avon@21:1/101 to Oli on Wed Feb 10 02:29:07 2021
    On 09 Feb 2021 at 09:16a, Oli pondered and said...

    You don't need to look it up. IBN:net1.fsxnet.nz:24556 without INA is valid according to FTS-5001:
    http://ftsc.org/docs/fts-5001.006

    Thanks, yep agreed.

    I manually edited the nodelist file Mystic compiles and added this to 1/100

    When attempting to poll it did resolve to my IPv6 address ... which at the moment is down... but at least it went looking to the correct location this time.

    21:26:59 Poll BINKP node via address lookup: 21:1/100
    21:26:59 1-Polling 21:1/100 on slot 1 via BINKP
    21:26:59 1-Connecting to net1.fsxnet.nz on port 24556
    21:26:59 1-Using address 2001:0470:000D:0123::0050
    21:27:05 1-Unable to connect
    21:27:06 Polled 1 systems

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Robert Wolfe@21:2/136 to Al on Fri Feb 19 00:11:22 2021
    Re: Nodelist Hatching
    By: Robert Wolfe to Al on Mon Feb 08 2021 07:12 am

    Ok, slowly rebuilding my system here. Moved it over to a VPS and it runs very nicely :)

    What VPS are you using? I was using a VPS (linode.com) about a year ago and found it to be quite good, I may go back to something like that at some poin

    Ttyl :-),
    Al

    ... For people who like peace & quiet - A phoneless cord!
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

    I am actually using InterServer for both my Linux and my Windows VPS.

    ... '\o.,@o.+:/~!v <------Tagline Debris
    --- Wildcat! v8.0.454.10 (May 26 2020), Editor Mod v2.1
    * Origin: Omicron Theta * Southaven MS * winserver.org (21:2/136)
  • From Robert Wolfe@21:2/136 to Alpha on Fri Feb 19 00:11:50 2021
    Ok, slowly rebuilding my system here. Moved it over to a VPS and it runs very nicely :)

    Just did the same. Had enough of power outages, accidental unplugs an my god-awful slow network. I'm on the Digital Ocean VPS $5/mo (USD) plan it works well.



    --- Talisman v0.10-dev (Linux/x86_64)
    * Origin: The Drunken Gamer BBS (21:4/158)

    Windows or Linux? And how much space?

    ... Ifyoucanreadthis,youspendtoomuchtimefiguringouttaglines!
    --- Wildcat! v8.0.454.10 (May 26 2020), Editor Mod v2.1
    * Origin: Omicron Theta * Southaven MS * winserver.org (21:2/136)
  • From Avon@21:1/101 to All on Sun Mar 7 19:56:52 2021
    Spent time today picking apart the scripts I use to hatch out the nodelist
    and infopack. The infopack went out twice today as I poked at the script and the nodelist once.

    Both should have landed in your inbound directories and been imported into
    your systems replacing the files that were in FSX_NODE and FSX_INFO file
    areas with the new versions.

    If anyone spotted an issue with this please let me know.

    Thanks!

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Warpslide@21:3/110 to Avon on Sun Mar 7 07:44:26 2021
    *** Quoting Avon from a message to All ***

    If anyone spotted an issue with this please let me know.

    One weird thing I noticed is that Allfix hung while trying to import the file_id.diz description on this file. I've not noticed that beofore, so just just told it to use the description in the .TIC file for that base and then it seemed to go through ok.

    Jay

    ... The nicest thing about growing older is that it takes such a long time.

    --- Telegard v3.09.g2-sp4/mL
    * Origin: Northern Realms | 289-424-5180 | bbs.nrbbs.net (21:3/110)
  • From Avon@21:1/101 to Warpslide on Wed Mar 10 12:40:20 2021
    On 07 Mar 2021 at 07:44a, Warpslide pondered and said...

    If anyone spotted an issue with this please let me know.

    One weird thing I noticed is that Allfix hung while trying to import the file_id.diz description on this file. I've not noticed that beofore, so just just told it to use the description in the .TIC file for that base and then it seemed to go through ok.

    Thanks for the report. When I used Allfix previously at 3:770/1 Fido HUB I sometimes hit that issue also when importing Fido stuff sent to me. Thing was it was not always a problem only on some files. I never figured out why but assume the version of zip used or something like that?

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)