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.
ftp://vert.synchro.net.main/BBS/pktdump.exe
Correction..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.
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 t other way around.
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
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
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.
It may be that D'Bridge needs to be updated to support PKT2+ for point suppo for this to work.
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.
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?
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
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,036 |
Nodes: | 15 (0 / 15) |
Uptime: | 17:40:53 |
Calls: | 860 |
Calls today: | 11 |
Files: | 95,180 |
D/L today: |
702 files (118M bytes) |
Messages: | 465,053 |
Posted today: | 1 |