Subj : all packets *.sec
To   : Michael Dukelsky
From : Rick Smith
Date : Mon Dec 05 2022 10:23 pm

Hello Michael!

Monday December 05 2022 18:26, you wrote to me:

 MD>  * Forwarded from area 'FIDOSOFT.HUSKY'
 MD> Hello Rick,

 MD> Friday December 02 2022, Rick Smith wrote to All:

 RS>> I am in the process of moving my hub setup to a VM in proxmox
 RS>> from a RPI.  VM is running ubuntu and I made a fresh build of HPT
 RS>> and BINKD on the VM.  Everything outbound seems to work just
 RS>> fine.  When I get pkts coming in according to the logs everything
 RS>> appears fine.  However messages never show up where I can see
 RS>> them in the editor, and my inbound dir has pkts with the name
 RS>> .sec I am using the EXACT config files from the working setup on
 RS>> the RPI, no password changes, only paths obviously.  I tried
 RS>> running pktinfo to see what I could see and this is the result.

 RS>> PktInfo/lnx 1.9 2022-07-03
 RS>> A 21:26:22   Invalid pkt version 2699!
 RS>> 00000153.th0: Corrupt packet

 RS>> so if I run hpt toss on that .th0 it gets renamed to .sec but I
 RS>> get no errors in the logs.  I have logs set to report everything.

 RS>> running pktinfo on the .sec

 RS>> A 21:26:10   Invalid pkt version 436!
 RS>> 88b7b400.sec: Corrupt packet

 RS>> any thoughts on what I could check?  When I switch back to RPI
 RS>> everything works as it should.

 MD> Did you use the same packet file both on RPI and on VM? Did you try
 MD> running pktinfo on the .sec packet both on RPI and on VM?

I think I sorted it out, I had the /in and protinbound reversed


Regards,

Rick

.... YKYHW: You consider BBSing better than sex.
--- GoldED+/LNX 1.1.5-b20220504
 * Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

.