Re: point system
By: Rick Smith to Alan Ianson on Sun Apr 30 2023 07:57 am

Hello Alan!

Saturday April 29 2023 18:28, you wrote to me:

* Forwarded from area 'FIDOSOFT.HUSKY'

A 08:41:35 Invalid pkt version 272!
47e8bc00.sec: Corrupt packet
rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 0069000a.sec
PktInfo/lnx 1.9 2023-01-07

I would check that that 0069000a.sec is a plain packet and not a compressed mail bundle as Carlos suggested. If it is a mail bundle you may need to decompress it.

I don't see that here. Here is what pktinfo says about a packet

Now I have no idea, I tried a new point on synchronet and I get the
same behavior...

I would suggest that you grab fresh husky source from github and rebuild just to be sure your husky tools are up to date.

I think that it is something to do with archivers perhaps? On the mystic system I unzipped all the .sec files and they were indeed pkt's and hpt tossed them just fine. On the synchronet test it renames them to .bad and I am unable to unarchive those to test.

If you're able to unzip the file, then it's not a packet, it's a bundle (which will usually contain one or more packets).

The latest builds of SBBSecho can include the *reason* a packet is bad when renaming it (configured in echocfg). Or you can just search the sbbsecho.log for "Bad packet detected" and the log lines before that msg will say *why* the packet file was considered bad.
--
digital man (rob)

This Is Spinal Tap quote #41:
Ian Faith: It says "Memphis show cancelled due to lack of advertising funds." Norco, CA WX: 61.2�F, 86.0% humidity, 8 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Greetings Alan!

Sunday April 30 2023 10:18, you wrote to me about an urgent matter!:

* Forwarded from area 'FIDOSOFT.HUSKY'

ok aftershock is working on the sbbs bbs, so the culprit must be my
mystic/hpt/binkd setup..

I think so yes.

Don't lose sight of the actual problem. Why are those packets not
tossed as expected?

The laptop setup is back pointing at mystic setup to try and sort this out.. I sent a netmail to areafix from laptop point which is also hpt/binkd/golded, on the mystic system in binkd log I see the netmail received it all looks normal with this exception;

? 30 Apr 18:00:41 [12766] unexpected password digest from the remote

However there is nothing in the hpt log indicating it ever tossed or processed the netmail. I am trying to find where the the packet went.



----
Regards,


Rick Smith (Nitro)

... You know you're hooked when: you consider BBSing better than chocolate
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

Greetings Rob!

Sunday April 30 2023 11:05, you wrote to me about an urgent matter!:

* Forwarded from area 'FIDOSOFT.HUSKY'
Re: point system
By: Rick Smith to Alan Ianson on Sun Apr 30 2023 07:57 am

Hello Alan!

Saturday April 29 2023 18:28, you wrote to me:

The latest builds of SBBSecho can include the *reason* a packet is bad when renaming it (configured in echocfg). Or you can just search the sbbsecho.log for "Bad packet detected" and the log lines before that
msg will say *why* the packet file was considered bad.

Thanks DM I was able to sort it out on SBBS and that point is now working as expected, oddly the system (hpt/binkd) I am way more familiar with I cannot get working.. I am sure it is something I am just overlooking.


----
Regards,


Rick Smith (Nitro)

... BBSing is a terminal disease and I have the ANSI strain.
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

Don't lose sight of the actual problem. Why are those packets not
tossed as expected?

The laptop setup is back pointing at mystic setup to try and sort this out.. sent a netmail to areafix from laptop point which is also hpt/binkd/golded, on the mystic system in binkd log I see the netmail received it all looks normal with this exception;

? 30 Apr 18:00:41 [12766] unexpected password digest from the remote

I think that is a password error in binkd. That would explain why the packets/bundles are renamed to .sec since the session is insecure.

However there is nothing in the hpt log indicating it ever tossed or processed the netmail. I am trying to find where the the packet went.

If I am right (I might not be) that happened when binkd received the file so check your binkd log. Session passwords are case sensitive so "password", "Password" and "PassWord" are all different. Be sure the same password is being used at both ends of the link.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Greetings Alan!

Sunday April 30 2023 11:22, you wrote to me about an urgent matter!:

* Forwarded from area 'FIDOSOFT.HUSKY'

Don't lose sight of the actual problem. Why are those packets not
tossed as expected?

The laptop setup is back pointing at mystic setup to try and sort
this out.. sent a netmail to areafix from laptop point which is also
hpt/binkd/golded, on the mystic system in binkd log I see the
netmail received it all looks normal with this exception;

? 30 Apr 18:00:41 [12766] unexpected password digest from the remote

I think that is a password error in binkd. That would explain why the packets/bundles are renamed to .sec since the session is insecure.

However there is nothing in the hpt log indicating it ever tossed or
processed the netmail. I am trying to find where the the packet
went.

If I am right (I might not be) that happened when binkd received the
file so check your binkd log. Session passwords are case sensitive so "password", "Password" and "PassWord" are all different. Be sure the
same password is being used at both ends of the link.

All passwords match, this is getting more weird tho... If I poll the mystic system from point I can deliver mail which I just found is in the bad area of golded stating I was not active for that area ( I checked my point is active in that area) if I poll the point from mystic machine it delivers mail normally and it gets tossed and auto adds areas not in fidoconfig etc? This is a real head scratcher...


----
Regards,


Rick Smith (Nitro)

... TAGLINE A bad day BBSing is better than a good day at school!
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

? 30 Apr 18:00:41 [12766] unexpected password digest from the remote

I think that is a password error in binkd. That would explain why the
packets/bundles are renamed to .sec since the session is insecure.

However there is nothing in the hpt log indicating it ever tossed or
processed the netmail. I am trying to find where the the packet
went.

If I am right (I might not be) that happened when binkd received the
file so check your binkd log. Session passwords are case sensitive so
"password", "Password" and "PassWord" are all different. Be sure the
same password is being used at both ends of the link.

All passwords match, this is getting more weird tho...

If that is so you need to figure out why you are getting the message "unexpected password digest from remote".

If I poll the mystic system from point I can deliver mail which I just found is in the bad area of golded stating I was not active for that area ( I checked my point is active i that area) if I poll the point from mystic machine it delivers mail normally and it gets tossed and auto adds areas not in fidoconfig etc?

Maybe the area is set to export to your point but your point is not setup with the area yet?

This is a real head scratcher...

Agreed.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)