13 Nov 16 17:35, you wrote to me:

 NB>>> They were stopped here, most likely because they were type 2.2
 NB>>> packets. At the moment my node is expecting type 2+ packets. If I
 NB>>> can find something in the documentation that states I can change
 NB>>> that, I will most definitely let you know.

 ml>> unless i'm mistaken, HPT recognises all three Type 2 PKT formats...
 ml>> i'm fairly certain i've thrown all three types at it over here but
 ml>> that was a while back :?

 NB> From hpt.texi:

 NB> "tossing packets of 2, 2.0 & 2+ types"

i suspect that's a typo as 2 and 2.0 are the same...

 NB> and..

 NB> "PKT password is limited to 8 characters, this is PKT 2+ limit."

it is a Type 2 limitation that covers all Type 2 variants... in pascal, we
define them as

  password : array[0..7] of char;

or some might define them as

  password : array[1..8] of char;

if they don't start counting from zero... in either case, it is eight
characters max...

 NB> That is all I found in that document regarding packet header types. A
 NB> search for "2.2" returns nothing, and a search for "2+" returns the
 NB> two above lines. That was all I could see on the matter.

 NB> hpt does come with a "pktinfo" program I may be able to run on one of
 NB> his packets that fails here. That may lead to more clues.

that would be one thing to do... if you like, you can also send it to me and i
can look at it with my READPKT tool...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Out of body, be back in five minutes.
---