Can anyone point me somewhere that will tell me what 000ffe8 in FIDO HEX converts to? Yes, I know some smarty pants is going to say "FIDO HEX is HEX" but the translators on the web don't know what to do with it so I don't think so. Also, please don't point me to sbbs echo config as the values it is giving listing with the linked nodes do not match anything in my outbound.

Which brings me to why I am posting the message here. There is a discrepancy between the HEX value that sbbs echo config presents and the value that sbbsecho uses to create the packets. :) For example, it lists all of the 618:250/* nodes I connect with as starting with 00fa00 yet, in the outbound directory, all of the packets start with 0000ff.

I thought they were supposed to match so maybe I am mistaken?

Thanks!

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Convert FIDO HEX to node number
By: Dumas Walker to All on Tue Aug 13 2019 20:16:06

Can anyone point me somewhere that will tell me what 000ffe8 in FIDO HEX

converts to?

you're a digit short... there should be 8 of them... so i don't know if that's supposed to be 0000ffe8 (0/65512) or 000ffe80 (15/65152) or 000f0fe8 (15/4072) or something else...

Also, please don't point me to sbbs echo config as the values it is giving

listing with the linked nodes do not match anything in my outbound.

it certainly should for the ?lo and ?ut files...

Which brings me to why I am posting the message here. There is a

discrepancy between the HEX value that sbbs echo config presents and the value that sbbsecho uses to create the packets. :) For example, it lists all of

the 618:250/* nodes I connect with as starting with 00fa00 yet, in the

outbound directory, all of the packets start with 0000ff.

I thought they were supposed to match so maybe I am mistaken?

you are mistaken... the ?lo and ?ut files are the ones that follow the XXXXYYYY
hex format... mail bundles can also but PKTs cannot really follow this naming convention... this is why they are listed inside the ?lo files... same with TICs and their associated files...

so here's the thing... files can be named anything as long as they are listed in the ?lo file for the system they are addressed to... it really is that simple...

HTH


)\/(ark
--- SBBSecho 3.08-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Convert FIDO HEX to node number
By: Dumas Walker to All on Tue Aug 13 2019 08:16 pm

Can anyone point me somewhere that will tell me what 000ffe8 in FIDO HEX converts to?

It depends on the context. Which file or directory name are you referring to? And you only provided 7 digits... so are you missing something there?

Yes, I know some smarty pants is going to say "FIDO HEX is
HEX" but the translators on the web don't know what to do with it so I don't think so. Also, please don't point me to sbbs echo config as the values it is giving listing with the linked nodes do not match anything in my outbound.

The hexadecimal values shown in EchoCfg->Linked Nodes is the hexadecimal encoding of the <net><node> combination unless there's a wildcard in the node (e.g. 1:ALL) in which case, the hex value given is for the outbound zone extension.

Which brings me to why I am posting the message here. There is a discrepancy between the HEX value that sbbs echo config presents and the value that sbbsecho uses to create the packets. :)

EchoMail Packet filenames don't use hexadecimal encoding of the destination address. Perhaps you're thinking of bundles?

For example, it lists
all of the 618:250/* nodes I connect with as starting with 00fa00 yet, in the outbound directory, all of the packets start with 0000ff.

FA is hexadecimal for 250. That seems to be correct.

Please provide full examples of the filenames for which you have questions. An echomail packet whos name begins with "00000ff" may be totally valid, but I can't really tell with the lack of information provided.

I thought they were supposed to match so maybe I am mistaken?

Not necessarily. Here's the reference for FidoNet filenaming: http://wiki.synchro.net/ref:fidonet_files

digital man

This Is Spinal Tap quote #37:
David St. Hubbins: We are Spinal Tap from the UK - you must be the USA!
Norco, CA WX: 73.2øF, 61.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

you're a digit short... there should be 8 of them... so i don't know if that's >supposed to be 0000ffe8 (0/65512) or 000ffe80 (15/65152) or 000f0fe8 (15/4072) >or something else...

It was 4 leading zeroes... 0/65512 does not really translate to anything useful. :)

it certainly should for the ?lo and ?ut files...

Unfortunately, I did not see any of them.

you are mistaken... the ?lo and ?ut files are the ones that follow the XXXXYYYY
hex format... mail bundles can also but PKTs cannot really follow this naming >convention... this is why they are listed inside the ?lo files... same with >TICs and their associated files...

It was bundles not PKTs. It is confusing because the bundles are always
named the same before the '.' for each individual node so my assumption was that it should translate to something.

The issue is moot now. Figured out the issue and the node is getting mail
now. FWIW, all of the 0000ffe8 packets go to node 250/25.

---
þ SLMR 2.1a þ  Lifting Shadows Off a Dream
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

It depends on the context. Which file or directory name are you referring to? And you only provided 7 digits... so are you missing something there?

Sorry, typo, 0000ffe8. :)

EchoMail Packet filenames don't use hexadecimal encoding of the destination add
ess. Perhaps you're thinking of bundles?

Bundles. Like, 0000ffe8.SU0 containing multiple PKT files.

Not necessarily. Here's the reference for FidoNet filenaming: http://wiki.synchro.net/ref:fidonet_files

OK, thanks!

---
þ SLMR 2.1a þ Have an adequate day.
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Convert FIDO HEX to node
By: Dumas Walker to DIGITAL MAN on Wed Aug 14 2019 06:56 pm

It depends on the context. Which file or directory name are you referring to? And you only provided 7 digits... so are you missing something there?

Sorry, typo, 0000ffe8. :)

EchoMail Packet filenames don't use hexadecimal encoding of the destination add
ess. Perhaps you're thinking of bundles?

Bundles. Like, 0000ffe8.SU0 containing multiple PKT files.

A bundles are named with the hexadecimal *difference* between the source and destination net and node. So "0000" for the net means "no difference", so both the source and destination are the same network.

Not necessarily. Here's the reference for FidoNet filenaming: http://wiki.synchro.net/ref:fidonet_files

OK, thanks!

Yup, all explained there.

digital man

Synchronet/BBS Terminology Definition #38:
IBM437 = Code Page 437 (so-called IBM Extended ASCII)
Norco, CA WX: 74.4øF, 59.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

On 2019 Aug 14 19:11:00, you wrote to me:

you're a digit short... there should be 8 of them... so i don't know if
that's supposed to be 0000ffe8 (0/65512) or 000ffe80 (15/65152) or
000f0fe8 (15/4072) or something else...

It was 4 leading zeroes... 0/65512 does not really translate to anything useful. :)

ok :)

it certainly should for the ?lo and ?ut files...

Unfortunately, I did not see any of them.

depending on the tosser managing the BSO, this is possible...

you are mistaken... the ?lo and ?ut files are the ones that follow the
XXXXYYYY hex format... mail bundles can also but PKTs cannot really follow
this naming convention... this is why they are listed inside the ?lo
files... same with TICs and their associated files...

It was bundles not PKTs.

that explains it... i don't do bundles any more... mainly because of this... also because creating and extracting bundles in this day in time is kinda a waste of CPU cycles but that's just one perspective...

It is confusing because the bundles are always named the same before
the '.' for each individual node so my assumption was that it should translate to something.

yes, bundles are backwards from ?lo and ?ut files, IIRC... the first four are the net subtracted from your net... if you're both in the same net, then 0000 is the result... the destination node is also subtracted from your node... maybe i have the subtractions backwards but yeah... that's one reason why i use
my own naming convention and just list the files in the ?lo...

The issue is moot now. Figured out the issue and the node is getting
mail now. FWIW, all of the 0000ffe8 packets go to node 250/25.

excellent!

i was looking for a link to the origina BSO definitely/explanation but hadn't found anything that is easily understood... i did find this link in the wiki which is pretty straight forward regarding how bundles are named...

http://wiki.synchro.net/ref:fidonet_files

)\/(ark

Once men turned their thinking over to machines in the hope that this would set
them free. But that only permitted other men with machines to enslave them.
... I have flabby thighs, but fortunately my stomach covers them.
---
* Origin: (1:3634/12.73)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

A bundles are named with the hexadecimal *difference* between the source and de
tination net and node. So "0000" for the net means "no difference", so both the
source and destination are the same network.

Similarly, then, the ffe8 in the last four of the string is the difference between the two node numbers (in this case, 1 and 25)?

Neat!

---
þ SLMR 2.1a þ Phone Farr: the Vulcan 900 number for phone sex
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

The issue is moot now. Figured out the issue and the node is getting mail now. FWIW, all of the 0000ffe8 packets go to node 250/25.

excellent!

i was looking for a link to the origina BSO definitely/explanation but hadn't found anything that is easily understood... i did find this link in the wiki which is pretty straight forward regarding how bundles are named...

http://wiki.synchro.net/ref:fidonet_files

Mark,
thanks! DM also pointed out that link (or another like it). I need to
read up next time before getting myself confused and reporting non-issues.
:)

---
þ SLMR 2.1a þ Eschew Obfuscation!
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Convert FIDO HEX to node
By: Dumas Walker to DIGITAL MAN on Thu Aug 15 2019 06:47 pm

A bundles are named with the hexadecimal *difference* between the source and de
tination net and node. So "0000" for the net means "no difference", so both the
source and destination are the same network.

Similarly, then, the ffe8 in the last four of the string is the difference between the two node numbers (in this case, 1 and 25)?

Right. If you enter ffe8 into a hex calculator (e.g. https://www.rapidtables.com/convert/number/hex-to-decimal.html) it'll report that value as -24 decimal (as a signed 16-bit integer).

digital man

Synchronet "Real Fact" #61:
How to get Synchronet technical support: http://wiki.synchro.net/howto:support Norco, CA WX: 71.6øF, 61.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Right. If you enter ffe8 into a hex calculator (e.g. https://www.rapidtables.co
/convert/number/hex-to-decimal.html) it'll report that value as -24 decimal (as
a signed 16-bit integer).

Hmmmm, I put the whole string... 0000ffe8.... into an online hex converter
and it returned mostly garbage characters. I did that before I asked here.
:D Must need to use a better one!

---
þ SLMR 2.1a þ !enilgat cinataS !eraweB
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Convert FIDO HEX to node
By: Dumas Walker to DIGITAL MAN on Fri Aug 16 2019 04:33 pm

Right. If you enter ffe8 into a hex calculator (e.g. https://www.rapidtables.co
/convert/number/hex-to-decimal.html) it'll report that value as -24 decimal (as
a signed 16-bit integer).

Hmmmm, I put the whole string... 0000ffe8.... into an online hex converter and it returned mostly garbage characters. I did that before I asked here.

Also, 0000ffe8 and ffe8 are different numbers when treated as a signed (possibly negative) values. Any number beginning with 0 will not be negative. I know, it's complicated.

digital man

Synchronet "Real Fact" #49:
Synchronet program was named 'sbbs' instead of 'sync' to avoid conflict w/Unix. Norco, CA WX: 85.9øF, 43.0% humidity, 12 mph E wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net