Okay, a more serious nodelist question...

What is a nodelist parser supposed to do with a line that has two INA addresses? Right now, I am taking the second, mainly because one line just has INA:9600, which totally tripped up my address validation code. [fixed].

There are a couple lines that have for example ITN:domain.address, no IBN, no INA, and phone is -Unpublished-, however, it is not marked as Pvt or Down. What
rule of thumb should be applied?

I have Rhenium polling every node right now in the background - just so I can validate my nodelist parser. Finding a lot of systems that are IP based are not
available - I know someone is going to defend this with ZMH... however, I haven't gotten to implement XM,CM,etc. logic. Rhenium is doing this so I can collect VER information (what systems are running what, along with collecting M_ADR list for what networks others are in around the world).

* This is running in single thread poll - so I would not mess up anyone, including my ISP if I spawned off a few thousand threads.
Regards,
Ozz

--- dBridge & Rhenium
* Origin: RVA Fido Support - ExchangeBBS.com, ModernPascal.com (1:275/362)

Hi Ozz,

On 2018-06-27 17:16:37, you wrote to All:

Okay, a more serious nodelist question...

What is a nodelist parser supposed to do with a line that has two INA addresses?

A node can have multiple domains. binkd.config can handle that too. So it depends on what your nodelist parser is producing, what you do with it...

Right now, I am taking the second, mainly because one line just
has INA:9600, which totally tripped up my address validation code. [fixed].

That's a bug in the nodelist. An INA: is not supposed to specify a port number!

There are a couple lines that have for example ITN:domain.address, no
IBN, no INA, and phone is -Unpublished-, however, it is not marked as
Pvt or Down. What rule of thumb should be applied?

So they are connectable by telnet. So the lack of Pvt or Down is correct.

I have Rhenium polling every node right now in the background - just so I can validate my nodelist parser. Finding a lot of systems that are IP

based

are not available - I know someone is going to defend this with ZMH... however, I haven't gotten to implement XM,CM,etc. logic. Rhenium is doing this so I can collect VER information (what systems are running what,

along

with collecting M_ADR list for what networks others are in around the world).

* This is running in single thread poll - so I would not mess up anyone, including my ISP if I spawned off a few thousand threads. Regards, Ozz

It would be interesting to see the statistics of the result, when you are done!
;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

On 2018 Jun 27 17:16:36, you wrote to All:

Okay, a more serious nodelist question...

What is a nodelist parser supposed to do with a line that has two INA addresses?

treat them as multiple connection numbers... if you can't connect on one, try the next one... do that for how ever many loops you designate as your retry attempt count...

Right now, I am taking the second, mainly because one line just has INA:9600, which totally tripped up my address validation code.
[fixed].

that's an invalid entry and it should have been fixed months ago... the two entries i know of do not appear any more since nodelist.131 of 2018 (this year)... sounds like you should get a new nodelist ;)

There are a couple lines that have for example ITN:domain.address, no
IBN, no INA, and phone is -Unpublished-, however, it is not marked as
Pvt or Down. What rule of thumb should be applied?

that's a normal telnet only connection... analogue modem mailers have no number
to dial (-Unpublished-) so no danger for them there... the system is not PVT so
other internet capable nodes that can perform telnet mailer connections can connect...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Why are Christians persecuted? Because everyone's sick of them.
---
* Origin: (1:3634/12.73)

Hi Ozz!

27 Jun 2018 17:16, from Ozz Nixon -> All:

What is a nodelist parser supposed to do with a line that has two INA addresses?

If you can have multiple addresses, then use both. (eg. backup address, if first is unreachable).
Otherwise use either of them.

There are a couple lines that have for example ITN:domain.address, no
IBN, no INA, and phone is -Unpublished-, however, it is not marked as
Pvt or Down. What rule of thumb should be applied?

I would assume that you can somehow reach that node via telnet on the address from the ITN flag.
If you do not support that protocol you have to treat that node as unrechable.

I have Rhenium polling every node right now in the background -
just so I can validate my nodelist parser.

It would be nice if you could post your findings here.

Rhenium is doing this so I can collect VER information (what systems
are running what, along with collecting M_ADR list for what networks others are in around the world).

Again ... would be nice if you could share this.

CU, Ricsi

--- GoldED+/LNX
* Origin: After us the SYN flood! (2:310/31)

addresses?

If you can have multiple addresses, then use both. (eg. backup address,
if first is unreachable).

Thanks - that makes sense (to all have pointed out multi-homed).

There are a couple lines that have for example ITN:domain.address, RM>ON> no IBN, no INA, and phone is -Unpublished-, however, it is not
marked as Pvt or Down. What rule of thumb should be applied?

I would assume that you can somehow reach that node via telnet on the address from the ITN flag.
If you do not support that protocol you have to treat that node as unrechable.

* My interpretation:
INA - is reserved to be the address of the destination machine w/o PORT
INB - says BinkP
ITN - says Telnet (does that mean Wazoo/YooHoo over TCP?)

If I understood the above, then the INA should have had the address, w/o a INB and does have ITN as a flag, as port 23 is assumed.

It would be nice if you could post your findings here.

I will be posting my finding (who was up, who was not), binkp extentions and versions, along with software and what networks everyone is sharing.

I held off on sharing my last results, as I found a bug in my M_ADR parser, only reporting the first 255 bytes (oops). That has been fixed... now I am going to run again this week and I will collect into a DB so I can make some useful reports... thanks for the interest!

Ozz

--- dBridge & Rhenium
* Origin: RVA Fido Support - ExchangeBBS.com, ModernPascal.com (1:275/362)

On 2018 Jul 09 14:13:40, you wrote to Richard Menedetter:

* My interpretation:
INA - is reserved to be the address of the destination machine w/o PORT

INA was created because there was someone who was trying to push a lot of buttons and piss a lot of people off... at that time, there was a 157 (IIRC) limit on the length of a nodelist line so this individual was putting their domain on all of the flags that applied to their node... the same domain... INA
was created as a generic one place flag to list the domain if it was the same for all the flags...

INB - says BinkP

IBN... yes, that's binkp protocol...

ITN - says Telnet (does that mean Wazoo/YooHoo over TCP?)

yes, it means all the standard FTN protocols used on a POTS line are available on telnet... FTS-0001 and up through EMSI...

If I understood the above, then the INA should have had the address,
w/o a INB and does have ITN as a flag, as port 23 is assumed.

i'm not sure which nodelist line you are referencing now but yes, if there's no
port, the default port is assumed...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... A Canadian is someone who knows how to make love in a canoe.
---
* Origin: (1:3634/12.73)

i'm not sure which nodelist line you are referencing now but yes, if there's no port, the default port is assumed...

Thanks Mark! I am running all node lists since 1/1/2017 - just so I can make sure my nodelist.xxx indexer is error proof. Evertime I think I have it, I will
find an address and flag combination that I need a rule for ;-)

Ozz

--- dBridge & Rhenium
* Origin: RVA Fido Support - ExchangeBBS.com, ModernPascal.com (1:275/362)

Hi Ozz!

10 Jul 2018 09:57, from Ozz Nixon -> mark lewis:

I am running all node lists since 1/1/2017 - just so I can make sure
my nodelist.xxx indexer is error proof. Evertime I think I have it, I
will find an address and flag combination that I need a rule for ;-)

Holding my fingers crossed ;)

BTW did you receive my netmail with the othernet zone numbers?

I tried to send it directly but it seems it could not be sent. (it was still in
my outbound, so I sent it routed ... hope you received it)

CU, Ricsi

--- GoldED+/LNX
* Origin: Friendship is like money, easier made than kept. (2:310/31)

BTW did you receive my netmail with the othernet zone numbers?

Yes, thank you! I am still running routed netmail only. I have like 18 projects
in the air, and try to give each project a day or two of effort. So, I have circled back around today to the Nodelist stuff...

Ozz

--- dBridge & Rhenium
* Origin: RVA Fido Support - ExchangeBBS.com, ModernPascal.com (1:275/362)