Hello everyone,

I've been having some problems with my echomail packets being sent from me to my bossnode. When he receives the packets, his system says they are coming from 1:-1/426 (not even including my point) because it appears that my system is unlinked. I've checked everything I should be checking (I think) and I don't see anything out of place. Does anyone have any thoughts on what I can check? When I look at the packet on my end, it looks correct to me.

Thanks,
Andy

... I tried being reasonable once, I didn't like it.

--- Renegade v1.22/DOS
* Origin: PB Renegade (gapbbs.rdfig.net:2424) Mesquite, Tx (1:124/5014.2)

Re: Packets being sent from a point
By: Andy Gorman to All on Mon Apr 12 2021 09:27 pm

I've been having some problems with my echomail packets being sent from me to my bossnode. When he receives the packets, his system says they are coming from 1:-1/426 (not even including my point) because it appears that my system is unlinked. I've checked everything I should be checking (I think) and I don't see anything out of place. Does anyone have any thoughts on what I can check? When I look at the packet on my end, it looks correct to me.

The old stone age packet format doesn't support points so you and your boss will want to stay away from those. I'd be surprised if that's the problem though. If you and your boss are generating 2+ packets, or 2e you should be OK.

You can grab a packet inspector at Vertrauen and it'll tell you about the packets that cause problems.

ftp://vert.synchro.net.main/BBS/pktdump.exe

Ttyl :-),
Al

... Should I or shouldn't I?... Too late, I did!
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

On 12 Apr 2021, Al said the following...

ftp://vert.synchro.net.main/BBS/pktdump.exe

Correction..

ftp://vert.synchro.net/main/BBS/pktdump.exe

If you are generating those packets with Mystic there is no need to worry. Mystic does not create type 2 stone age packets. It creates 2+ or 2e. My mailer has no problem reading packets created by this point on Mystic or the other way around.

Ttyl :-),
Al

--- Mystic BBS v1.12 A47 2021/04/08 (Linux/64)
* Origin: Equinox BBS - Penticton, BC Canada (1:153/757.3)

Correction..

ftp://vert.synchro.net/main/BBS/pktdump.exe

I tried to get this and the server just timed out but I'll try to find it other ways. Thanks for the assist there.

If you are generating those packets with Mystic there is no need to worry. Mystic does not create type 2 stone age packets. It creates 2+ or 2e. My mailer has no problem reading packets created by this point on Mystic or t other way around.

I am using Mystic to create the packets and he is using D'Bridge to read them.
I'll see what the packet dump looks like.

Thanks,
Andy

... My opinions are not those of my employer

--- Renegade v1.22/DOS
* Origin: PB Renegade (gapbbs.rdfig.net:2424) Mesquite, Tx (1:124/5014.2)

On 12 Apr 21 21:27:20, Andy Gorman said the following to All:

I've been having some problems with my echomail packets being sent from me my bossnode. When he receives the packets, his system says they are coming from 1:-1/426 (not even including my point) because it appears that my syst

Everyone,

I am the hub in question, and heres what I see:

- I download and install Mystic from the Mystic website... A46 I think.
- Configured it with primary address 1:229/426.93 and the uplink 1:229/426.
- Configured a dummy echomail area between the two systems.
- Post a local message from .93 and have MUTIL export, MIS POLL SEND to me.

When I use Pktview (util from '94) to view the packet sitting in Mystic's outbound before its sent here, the packet header is showing as being from
the address 1:65535/426.93.

The negative Net display here is simply a cosmetic problem for me to deal with but the unusual Net-value generated by Mystic in the packet header is not.

I am not a Mystic expert or even aware if I am using the latest version but this is what I have discovered in less than a half-hour of testing.

This system feeds over a hundred downlinks; many are Mystic systems trading packets here like clockwork. This is the first time I've seen this problem but do not believe I have any Points running Mystic.

Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Re: Re: Packets being sent from a point
By: Nick Andre to All on Tue Apr 13 2021 01:25 am

I am not a Mystic expert or even aware if I am using the latest version but this is what I have discovered in less than a half-hour of testing.

I am not either but I have been using mystic as a point off my node without issues. I generated this packet at 153/757.3

http://trmb.synchro.net/07a436d5.pkt

I wonder if there is something different about it from the ones your .93 is generating?

I hope it will provide a clue.

Ttyl :-),
Al

... Everybody lies, but it doesn't matter, cuz nobody listens.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

On 12 Apr 21 23:28:10, Al said the following to Nick Andre:

I am not either but I have been using mystic as a point off my node without issues. I generated this packet at 153/757.3

http://trmb.synchro.net/07a436d5.pkt

Interesting. With Pktview the Net shows 65535 on this one.

More interesting is when the Point is set to zero in Mystic -Cfg, the
resulting test run has a correct Net in the packet.

Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

When I use Pktview (util from '94) to view the packet sitting in Mystic's outbound before its sent here, the packet header is showing as being from the address 1:65535/426.93.

The negative Net display here is simply a cosmetic problem for me to
deal with but the unusual Net-value generated by Mystic in the packet header is not.

I am not a Mystic expert or even aware if I am using the latest version but this is what I have discovered in less than a half-hour of testing.

This is not an unusual net value within a PKT2+ packet.

In a PKT 2+ format if the origNet is $FFFF it indicates that the origin is a point system and the net is found in the auxNet field.
Here's a paste from the PKT2+ FSC-0048 documentation:

auxNet field:
When parsing a Type 2+ packet, if origNet is 65535, the software MUST use
the value from the auxNet field. When creating a packet, if the
originating system is a point, it SHOULD set origNet to 65535 and
put the net number in this field.

The reason for this kludge is so that PKT2+ maintains backwards compatibility with PKT2 while also allowing for 4D addressing that was missing in the PKT2 format.

It may be that D'Bridge needs to be updated to support PKT2+ for point support for this to work.

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

On 13 Apr 21 02:11:56, G00R00 said the following to Nick Andre:

It may be that D'Bridge needs to be updated to support PKT2+ for point suppo for this to work.

I just did this now and was able to toss succesfully from a Mystic Point.

Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

It may be that D'Bridge needs to be updated to support PKT2+ for point for this to work.

I just did this now and was able to toss succesfully from a Mystic Point.

Glad its been sorted out! Crazy how long some things can co-exist without anyone running into a problem like that isn't it?

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

On 13 Apr 21 03:13:15, G00R00 said the following to Nick Andre:

It may be that D'Bridge needs to be updated to support PKT2+ for poi for this to work.

I just did this now and was able to toss succesfully from a Mystic Poin

Glad its been sorted out! Crazy how long some things can co-exist without anyone running into a problem like that isn't it?

I know eh, I've NEVER come across this until now. The D'Bridge code actually has elements of 2+ in there (hence the quick-fix) but just as random names so it appears it was likely started but abandoned for whatever reason.

Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

On 13 Apr 2021, Nick Andre said the following...

On 13 Apr 21 03:13:15, G00R00 said the following to Nick Andre:

It may be that D'Bridge needs to be updated to support PKT2+ fo for this to work.

I just did this now and was able to toss succesfully from a Mystic

Glad its been sorted out! Crazy how long some things can co-exist with anyone running into a problem like that isn't it?

I know eh, I've NEVER come across this until now. The D'Bridge code actually has elements of 2+ in there (hence the quick-fix) but just as random names so it appears it was likely started but abandoned for whatever reason.

Nick

Thanks Nick and everyone else for helping get this sorted out. I just posted to Fido Test from my system and it showed up.

Andy

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: The Pot O'Gold - bbs.thepotogold.net:4888 (1:229/426.52)