TIP: Click on subject to list as thread! ANSI
echo: linux
to: MAURICE KINAL
from: NICHOLAS BOEL
date: 2016-11-13 12:14:00
subject: Re: two steps back

Hello Maurice,

On 13 Nov 16 17:35, Maurice Kinal wrote to Nicholas Boel:

 NB>> If you insist on using type 2.2 packets

 MK> I don't use any of them.  I was/am only tacking them onto the
 MK> outbound.  If you insist on a different format than what was working
 MK> just fine then you should have let me know beforehand.  I haven't
 MK> changed anything as far as outbound is concerned but am willing to try
 MK> something different if it will help.

I can not let you know beforehand what I did not know or realize until actually
became an issue. I let you know as soon as I was aware of it.

 NB>> At the moment my node is expecting type 2+ packets.

 MK> I tried that with one direct netmail to you and you never responded or
 MK> acknowledged it so I assumed it was broken as well.  Beats me why but
 MK> I haven't been dealing with netmail so it could easily be something
 MK> there.  I am seeing yours just fine but then again no matter what type
 MK> the pkt header is it ends up being ignored at this end.  Near as I can
 MK> tell the first 58 bytes of pkt's are utter crap and always have been.

 MK> What do you see in them?

All I know is that a couple fields are definitely changed in length. So when
you send me a type 2.2 packet header, my system seems to think it's addressed
to a point system that doesn't exist. I can only guess that it's taking numbers
from another field and adding them to the original TO address. Unfortunately,
this doesn't seem to be able to be fixed or changed in hpt's configuration.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.