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 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 :)
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 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 :)
Ok, slowly rebuilding my system here. Moved it over to a VPS and it
runs very nicely :)
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 :)
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
;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
better change the lowercase z (NODELIST.z43) to an uppercase Z (NODELIST.Z43)
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.
what domain is it polling Al?
That's strange... if you try pinging the hubs domain names I wonder what you get.
--------------------- 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
$ 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
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.
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.
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:
I recompiled which put the IBN:24556 back and I'm back to that weird IP address:
I wonder how to do this, it's MakeNL that's doing this. Guess it's a
Linux thing?
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
'0x5fec'hex(24556)
2360xec
950x5f
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
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.
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.
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
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)
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)
If anyone spotted an issue with this please let me know.
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.
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 15:17:04 |
Calls: | 14,143 |
Files: | 295 |
Messages: | 551,312 |