MSGID: 1:153/7001.0 57585ec2
-={ Wednesday, 08 June 2016, 14:06:58 -0400 }=-

Hey mark!

 ml> think of a PKT as a bag of postal mail

I am assuming that something like origAddr -> destAddr might be something
useful.  In awkSpeak it could look like the below:

Type 2:
awk -F, '{printf("%d:%d/%d -> %d:%d/%d", $16, $11, $1, $17, $12, $2)}'

Type 2+:
awk -F, '{printf("%d:%d/%d.%d -> %d:%d/%d.%d", $16, $11, $1, $25, $17, $12, $2,
$26)}'

Type 2.2:
awk -F, '{printf("%d:%d/%d.%d -> %d:%d/%d.%d", $13, $8, $1, $3, $14, $9, $2,
$4)}'

I added the above to the current pkttool and it produced the following;

-------------- ye olde cut `n paste starts
fidonet@mikey [ ~/testing ]$ ./pkttool 5754c356.pkt
5754c356.pkt: Type 2.2 pkt header
1:153/7001.0 -> 1:153/7715.0
fidonet@mikey [ ~/testing ]$ ./pkttool 5722a447.pkt
5722a447.pkt: Type 2+ pkt header
1:153/7715.0 -> 1:153/7001.0
-------------- ye olde cut `n paste ends

Note the above includes both a types 2+ and 2.2, where the 2.2 originated at
this node.  Since both of them have something to do with Little Mikey's Brain I
can speak favourably as to the accuracy of the above information.

What would be handy to have is a type 2 pkt for checking.  I may have to do
something about that if it matters any.  Does it?

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.3.42(1)-release (x86_64-atom-linux-gnu)