• check for leaks

    From Maurice Kinal@1:153/7001 to Hot Damn on Wed Jun 8 06:25:34 2016
    -={ mercredi, 08 juin 2016, 06:25:35 +0000 }=-

    Hey Hot!

    Another type 2.2 test. This should be it other than a follow up reply just to make double sure.

    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)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001.0)
  • From Maurice Kinal@1:261/38 to Maurice Kinal on Wed Jun 8 02:43:44 2016
    -={ mercredi, 08 juin 2016, 06:25:35 +0000 }=-
    Hey Hot!
    Another type 2.2 test. This should be it other than a follow up reply just to
    make double sure.
    Life is good,
    Maurice
    ... Don't cry for me I have vi.

    Yes and no.

    --- BBBS/Li6 v4.10 Dada-2
    * Origin: Prism bbs (1:261/38)
  • From Alan Ianson@1:153/757 to Maurice Kinal on Tue Jun 7 23:40:14 2016
    On 06/08/16, Maurice Kinal said the following...

    Another type 2.2 test. This should be it other than a follow up reply just to make double sure.

    It made it this far.. :)

    Ttyl :-),
    Al

    --- Mystic BBS v1.12 A17 (Linux)
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Maurice Kinal@1:153/7001 to Maurice Kinal on Wed Jun 8 06:55:56 2016
    -={ Tuesday, 07 June 2016, 23:55:56 -0700 }=-

    Hey Maurice!

    This should be it other than a follow up reply just to make double
    sure

    Let's make it a triple threat.

    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)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001.0)
  • From Maurice Kinal@1:153/7001 to Alan Ianson on Wed Jun 8 07:04:06 2016
    -={ Wednesday, 08 June 2016, 00:04:07 -0700 }=-

    Hey Alan!

    It made it this far.. :)

    It also made it to NYS which is WAY further. ;-)

    Thanks and have you had a chance to run the test pktool? The pkt with the triple threat reply shows;

    -------------- ye olde cut `n paste starts
    fidonet@mikey [ ~/testing ]$ ./pkttool 5757c1c8.pkt
    5757c1c8.pkt: Type 2.2 pkt header 7001,7715,0,0,,2,2,153,153,255,0,,1,1,fidonet,fidonet,0
    -------------- ye olde cut `n paste ends

    I like the output as the column delimited fields make it super easy for a bash 'read' or 'gawk -F,' dealie if one prefers. Getting rid of the binary crap is ALWAYS a good idea but to be honest I really don't see much use to the pkt headers information no matter what type, although 2.2 is best of the three choices.

    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)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001.0)
  • From Alan Ianson@1:153/757 to Maurice Kinal on Wed Jun 8 01:02:36 2016
    On 06/08/16, Maurice Kinal said the following...

    Thanks and have you had a chance to run the test pktool? The pkt with
    the triple threat reply shows;

    I just took a look through my in/out dirs and there is nothing in there. Once this goes I'm going to stop tossing pkts for a times so I have some stuff to look at.

    I like the output as the column delimited fields make it super easy for
    a bash 'read' or 'gawk -F,' dealie if one prefers. Getting rid of the binary crap is ALWAYS a good idea but to be honest I really don't see
    much use to the pkt headers information no matter what type, although
    2.2 is best of the three choices.

    It looks helpfull, it'll answer the question about what pkt type we are looking at which will help us get to the trouble.

    Thanks again.. :)

    Ttyl :-),
    Al

    --- Mystic BBS v1.12 A17 (Linux)
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From mark lewis@1:3634/12.73 to Maurice Kinal on Wed Jun 8 09:54:54 2016

    08 Jun 16 07:04, you wrote to Alan Ianson:

    but to be honest I really don't see much use to the pkt headers information no matter what type, although 2.2 is best of the three choices.

    think of a PKT as a bag of postal mail... the PKT header is the shipping tag on
    the bag's closure which tells the origination and destination of the bag for shipping purposes...

    )\/(ark

    Always Mount a Scratch Monkey

    ... Bread that must be sliced with an ax is bread that is too nourishing.
    ---
    * Origin: (1:3634/12.73)
  • From Maurice Kinal@1:153/7001 to Alan Ianson on Wed Jun 8 18:04:24 2016
    -={ Wednesday, 08 June 2016, 11:04:25 -0700 }=-

    Hey Alan!

    It looks helpfull, it'll answer the question about what pkt type
    we are looking at which will help us get to the trouble.

    Excellent. For now I plan to add something extra to it which I'll get more into in the reply to mark lewis. Please stay tuned.

    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)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001.0)
  • From Maurice Kinal@1:153/7001 to mark lewis on Wed Jun 8 18:06:58 2016
    -={ Wednesday, 08 June 2016, 14:06:58 -0400 }=-

    Hey mark!

    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)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001.0)
  • From Alan Ianson@1:153/757 to Maurice Kinal on Wed Jun 8 14:16:40 2016
    On 06/08/16, Maurice Kinal said the following...

    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?

    We were having problems that I was thinking but don't know could be related
    to the pkt type in use. The node in question seems to have given up the fight but may reappear (I hope).

    I find a tool that can identify pkt type usefull but I'm not sure where a
    type 2 pkt can be found today. Having a look through the pkts that arrive
    here and what I am sending out it looks like it is all 2+.

    I still don't know what the problem was or if it'll ever be a problem again
    but the pkt type you are working with is good to know.

    Ttyl :-),
    Al

    --- Mystic BBS v1.12 A17 (Linux)
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Maurice Kinal@1:153/7001 to Alan Ianson on Wed Jun 8 21:37:32 2016
    -={ Wednesday, 08 June 2016, 14:37:32 -0700 }=-

    Hey Alan!

    I find a tool that can identify pkt type usefull

    Probably although speaking for myself I've been just heave-ho-ing the pkt header and the first 14 bytes of the msg headers as they are just getting in the way of anything meaningful, especially development.

    it looks like it is all 2+

    Other than the recent 2.2's I've been creating, it is all 2+ from what I've seen in the last decade or so, although I've heard horror stories about type 2 ones rearing their ugly heads every now and then.

    the pkt type you are working with is good to know

    For sure, but for decades now *NO STINKIN' BINARY IN HEADERS* has been on my wish list. Perhaps that could happen in type 3 pkt headers? ;-)

    Speaking of which, I like the idea of utf-8 headers. :::evil grin:::

    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)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001.0)
  • From mark lewis@1:3634/12.73 to Maurice Kinal on Thu Jun 9 12:40:00 2016

    08 Jun 16 18:06, you wrote to me:

    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?

    yes, the original Type 2 (aka 2.0) format is still used... i have at least one here if you would like it for testing... it is from 1994, is 233782 bytes and appears to be created by George Peace's QM packer for MS-DOS ;)

    )\/(ark

    Always Mount a Scratch Monkey

    ... It ain't over, but the fat lady is clearing her throat.
    ---
    * Origin: (1:3634/12.73)
  • From mark lewis@1:3634/12.73 to Maurice Kinal on Thu Jun 9 12:46:08 2016

    08 Jun 16 21:37, you wrote to Alan Ianson:

    For sure, but for decades now *NO STINKIN' BINARY IN HEADERS* has been
    on my wish list. Perhaps that could happen in type 3 pkt headers? ;-)

    there was a proposal or two for pure text PKTs... i don't remember if it was one of the type 3s or one of the type 10s, though...

    )\/(ark

    Always Mount a Scratch Monkey

    ... You will get a fair trial, after which you will be shot.
    ---
    * Origin: (1:3634/12.73)