On 21 Oct 2020 at 08:54p, Black Panther pondered and said...

Hi Paul,

I'm not sure if this would be useful for you or fsxNet. I had been
playing around with the code, and made some updates. It analyzes the nodelists.

Yes, this would be a great addition to have each week, much like they post to Fido (as far as I can tell?)

The Input Nodelist file has 219 Nodes in it
and a total of 249 non-comment entries.

The list has 1 Zones listed.
1 Region Coordinators listed.
5 Network Hosts listed.

Could the info be displayed in a different order?

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

On 24 Oct 2020 at 02:12a, Black Panther pondered and said...

How would you like it arranged?

Perhaps something like this...

[snip]

NetStats 4.1(RCS) 21 Oct 2020

INPUT NODELIST FILE : FSXNET.297

File has a Date Stamp of : 10/18/2020
File Size (uncompressed) : 30.18 KBytes

Nodes : 219
Non-comment entries : 249

FSXNET.297 Analysis
===================

Zones : 1
Region Coordinators : 1
Network Hosts : 5
Hubs : 0
DOWN Nodes : 2
PRIVATE Nodes : 21 ( 9.59 %)
HOLD Nodes : 0

Admin Overhead : 7 ( 3.20 %)
MailOnly Nodes : 4 ( 1.83 %)
CrashMail Capable : 219 (100.00 %)

Nodelist Flag Analysis
======================

------------------------------------------------------
IP Flags Protocol Number of systems
IBN Binkp 213 ( 97.26 %)
IFC Raw ifcico 2 ( 0.91 %)
IFT FTP 1 ( 0.46 %)
ITN Telnet 45 ( 20.55 %)
IVM Vmodem 5 ( 2.28 %)
IP Other 0 ( 0.00 %)
INO4 IPv6 only 0 ( 0.00 %) ------------------------------------------------------

[ This report produced by NETSTATS - Redesigned and Updated 1:317/3 ]
[ NetStats 4.1(RCS) 21 Oct 2020 - Black Panther(RCS) - Castle Rock BBS ]

[snip]

It would be good to see the % figures against the admin section, I added in
the PVT one.

Also good to understand what Flags the systems tracks individually, so we
could add to this and put in some custom ones, for Onion addresses etc.

:)

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

On 24 Oct 2020 at 03:23a, Black Panther pondered and said...

NetStats 4.2(RCS) 24 Oct 2020

INPUT NODELIST FILE : FSXNET.304
File has a Date Stamp of : 10/24/2020
File Size (uncompressed) : 30.38 KBytes.

This looks nice Dan. I think it would also be good to have the local time the report was run as well, so if it's generated different times on the same day you can tell. Perhaps add that to the header too?

This exercise also got me thinking about ways of using the nodelist to track numerically and graphically things like

- number of nodes per net

- week to week stats changes in nets as well as across a zone.

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

On 24 Oct 2020 at 01:26p, Black Panther pondered and said...

I've got the current RunTime date and time listed now. Although I would think this program would only be run once per week.

Thanks :) Yes, or when the nodelist was updated as well?

- number of nodes per net

That can be added. It wouldn't be too difficult to count each net individually.

I figured not, but it would be an interesting stat to watch ebb and flow.

- week to week stats changes in nets as well as across a zone.

This is something I'm already working on. The program right now, is also generating a comma delimited file with the information. I still need to update the fields. There could be an addition to the program which could generate numbers over time using that file.

sounds good :)

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

On 25 Oct 2020 at 10:00a, deon pondered and said...

I think it would be great, if we could plug out the city/country from the nodelist and do some stats based on that too...

So, if there was a standard format in the nodelist, eg: Melbourne_AU
(IIRC mostly it is this way), it would be nice to know the distribution
of where folks are from (country wise).

Good suggestion :)

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

On 25 Oct 2020 at 10:51p, Black Panther pondered and said...

the nodelist. Before you ask, the 'XXX' was added to the listing you
have for 1/999.

Ahh..

This report is showing the last three characters of the city/state field of the nodelist, so we will need to double check to make sure they are
all set up in that format. When I originally ran it, I had a node in 'NLD', and another one in 'Netherlands'.

My reference guide for using country codes in the fsxNet nodelist has been
this web page https://en.wikipedia.org/wiki/ISO_3166-1#Current_codes
I use the Alpha 3 codes - hope that helps.

Your comment made me realise as we get closer to having regular segments
being incorporated into the nodelist from HUBs it's important we are all
using the same song sheet.

I'll keep you posted as to making it look better. :)

You're doing great :)

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