Hey DM,

Ive been playing with packet formats, and I cant seem to get a good 2.2 packet.

649783eb-997-2.2.pkt
00000000 04 00 e5 03 e7 07 05 00 19 00 0a 00 01 00 2b 00 |..............+.| 00000010 00 00 02 00 01 00 03 00 ff 03 4c 00 00 00 00 00 |..........L.....| 00000020 35 00 0a 00 0a 00 00 00 00 00 00 00 00 00 00 00 |5...............| 00000030 00 00 00 00 00 00 00 00 00 00 |..........|

For the domain part 0x26 and 0x2e, I was expecting "private" for the domain, not nulls.

Any ideas why I'm getting nulls?


...δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI

Re: Packet 2.2
By: deon to Digital Man on Sun Jun 25 2023 12:09 pm

For the domain part 0x26 and 0x2e, I was expecting "private" for the domain, not nulls.

Any ideas why I'm getting nulls?

My bad. I think I may have set it to v2 packet, not 2.2, I'll try again.


...δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI

Re: Packet 2.2
By: deon to Digital Man on Sun Jun 25 2023 08:57 pm

OK, I think I found a different problem with packet 2.2 format...

sbbsecho.log shows: (ie: packet to 3/997 - as defined - not to a point)

===
2023-06-25 20:59:39 Sending packet (/opt/sbbs/temp/sbbsecho/64981e1f.pkt, 0.5KB) from 10:1/4 to 10:3/997
2023-06-25 20:59:39 File (../fido/outbound.00a/64981e1f.pkt, 0.5KB) for 10:3/997 added to BSO/FLO file: ../fido/outbound.00a/000303e5.hlo
===

However packet dump says it is going to 3/997.5:

===
root@alterant:outbound.00a# pktdump 64981e1f.pkt
pktdump rev 1.18 - Dump FidoNet Packets

Opening 64981e1f.pkt
64981e1f.pkt Packet Type 2.2 (prod: FF, rev: 3) from 10:1/4@private to 10:3/997.5@private
===

Hexdump of the packet shows:

===
[root@a-2-1 outbound.00a]# hexdump -Cn 58 64981e1f.pkt
00000000 04 00 e5 03 e7 07 05 00 19 00 14 00 3b 00 27 00 |............;.'.| 00000010 02 00 02 00 01 00 03 00 ff 03 4c 00 00 00 00 00 |..........L.....| 00000020 00 00 0a 00 0a 00 70 72 69 76 61 74 65 00 70 72 |......private.pr| 00000030 69 76 61 74 65 00 00 00 00 00 |ivate.....|
===

Indeed:
0x04 should be zero (instead shows 2023 - Year?)
0x06 should be zero (instead shows 05 - Month?)
0x08 should be zero (? - reserved) but is probably the rest of the date from a type 2 packet?)


...δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI

Re: Packet 2.2
By: deon to Digital Man on Sun Jun 25 2023 09:17 pm

OK, I think I found a different problem with packet 2.2 format...

Thanks for the report! I just committed a fix to the SBBSecho type 2.2 packet header generation. Give that a try and let me know. Thanks,
--
digital man (rob)

Rush quote #33:
With the heart and mind united in a single, perfect sphere
Norco, CA WX: 71.6°F, 55.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs

Re: Packet 2.2
By: deon to Digital Man on Sun Jun 25 2023 09:17 pm

However packet dump says it is going to 3/997.5:

===
root@alterant:outbound.00a# pktdump 64981e1f.pkt
pktdump rev 1.18 - Dump FidoNet Packets

Opening 64981e1f.pkt
64981e1f.pkt Packet Type 2.2 (prod: FF, rev: 3) from 10:1/4@private to 10:3/997.5@private
===

Hexdump of the packet shows:

===
[root@a-2-1 outbound.00a]# hexdump -Cn 58 64981e1f.pkt
00000000 04 00 e5 03 e7 07 05 00 19 00 14 00 3b 00 27 00 |............;.'.|
00000010 02 00 02 00 01 00 03 00 ff 03 4c 00 00 00 00

Howdy,

(I know you've committed a fix to this.)

On a similiar topic, I thought pktdump should have reported that the packet was from 10:1/4.2023@private ?



...δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI

Re: Packet 2.2
By: deon to Digital Man on Tue Jun 27 2023 04:49 am

On a similiar topic, I thought pktdump should have reported that the packet was from 10:1/4.2023@private ?

Thanks - that should be fixed now too! :-)
--
digital man (rob)

Synchronet "Real Fact" #50:
JAM and Squish were considered before developing Synchronet Message Base format Norco, CA WX: 79.7°F, 37.0% humidity, 13 mph SSW wind, 0.00 inches rain/24hrs