Hello All!

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

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

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

running pktinfo on the .sec

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

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

Regards,

Rick

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

Hello Rick,

Friday December 02 2022, Rick Smith wrote to All:

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

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

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

running pktinfo on the .sec

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

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

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

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Moscow, Russia (2:5020/1042)

Hello Michael!

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

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

Friday December 02 2022, Rick Smith wrote to All:

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

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

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

running pktinfo on the .sec

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

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

Did you use the same packet file both on RPI and on VM? Did you try 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)