On 2018 Sep 07 09:32:44, you wrote to me:   
      
    DG> Thats an indicator that it is a 2+ packet right?   
      
   yes...   
      
    DG> So does that mean my MBSE is not handling it correctly?   
      
   i see only that it is reporting and apparently using the 65535 net address   
   field and not pulling the true net address from the secondary field... i'm   
   curious to see what others of the MBSE community have to say... something tells   
    me this is a known problem that is being worked on but i do not know what the   
   status of that work is... i think andrew was working in this area...   
      
    DG> I recall somewhere a config about 4d packets, need to look for that,   
    DG> perhaps that is the problem?   
      
   i do not know... i have not (yet) installed and played with MBSE...   
      
    ml>> i was able to go back through my mail archive and find some posts   
    ml>> about the above document... draft 4 is available at   
    ml>> http://bbsdev.net/fsp/FSP-1040.txt and i think it is the last   
    ml>> draft... the details i speak of above are found in the notes portion   
    ml>> of the document's section "3. Type 2+ Packet"... the first paragraph   
    ml>> in that notes section explains why net 65535 is being seen in these   
    ml>> PKTs and how to properly handle it...   
      
    DG> Awesome, I'll take a look.   
      
    DG> Thanks...   
      
   you are welcome...   
      
   )\/(ark   
      
   Always Mount a Scratch Monkey   
   Do you manage your own servers? If you are not running an IDS/IPS yer doin' it   
   wrong...   
   ... while [ true ] ; do story ; done   
   ---   
    * Origin:  (1:3634/12.73)