I was playing around with setting up MysticBBS under Ubuntu on another computer. I have it set up as a point off of my main BBS. When I post an echomail message on the point system, SBBSEcho will receive it and send it to my uplink, but will also send another copy of it back to the point system.
I was playing around with setting up MysticBBS under Ubuntu on
another computer. I have it set up as a point off of my main BBS.
When I post an echomail message on the point system, SBBSEcho will
receive it and send it to my uplink, but will also send another copy
of it back to the point system.
what version of mystic?
what version of sbbsecho? looks like you're using 3.00 compiled 2016 Nov
17... you might want to update again... there has been discussion about this problem in a few areas and i think, too early for that really, that it was fixed since then...
Hi there,
I was playing around with setting up MysticBBS under Ubuntu on another computer. I have it set up as a point off of my main BBS. When I post an echomail message on the point system, SBBSEcho will receive it and send it to my uplink, but will also send another copy of it back to the point system.
Is there a setting that I messed up somewhere in SBBSEcho? I just went through them, and everything looks right to me.
Any suggestions?
computer. I have it set up as a point off of my main BBS. When I post
an echomail message on the point system, SBBSEcho will receive it and
send it to my uplink, but will also send another copy of it back to
the point system.
What does your areas.bbs line look like for the echo in question?
What does your sbbsecho.log file report when importing the post from the point system?
Re: Mystic point and SBBS
By: Digital Man to Black Panther on
Fri Dec 30 2016 16:27:34
computer. I have it set up as a point off of my main BBS. When I post
an echomail message on the point system, SBBSEcho will receive it and
send it to my uplink, but will also send another copy of it back to
the point system.
What does your areas.bbs line look like for the echo in question?
It is actuall happening in multiple echos, which all look like:
FSCHATTEST FSX_GEN 21:1/100 21:1/186.1
What does your sbbsecho.log file report when importing the post from the point system?
2016-12-28 18:38:07 SBBSecho 3.00-Win32 r3.27 Dec 8 2016 MSC 1800 invoked with options: -linf
2016-12-28 18:38:07 Exporting fsmysticbb message #409 from Dan Richter to Vk3jed in area: FSX_MYS
2016-12-28 18:38:07 Creating outbound packet from 21:1/186 to 21:1/100: C:\BBS\SBBS\temp\sbbsecho\586468ff.pkt
2016-12-28 18:38:07 Adding FSX_MYS message from Dan Richter (21:1/186) to packet for 21:1/100: C:\BBS\SBBS\temp\sbbsecho\586468ff.pkt
2016-12-28 18:38:07 Creating outbound packet from 21:1/186 to 21:1/186.1: C:\BBS\SBBS\temp\sbbsecho\58646900.pkt
2016-12-28 18:38:07 Adding FSX_MYS message from Dan Richter (21:1/186) to packet for 21:1/186.1: C:\BBS\SBBS\temp\sbbsecho\58646900.pkt
2016-12-28 18:38:08 Exported: 1 msgs fsmysticbb -> FSX_MYS 2016-12-28 18:38:08 Exported: 1 msgs total
2016-12-28 18:38:08 Finalizing outbound packet from 21:1/186 to 21:1/186.1: C:\BBS\SBBS\temp\sbbsecho\58646900.pkt
2016-12-28 18:38:08 Node (21:1/186.1) successfully locked via: /bbs/sbbs/data/outbound.015\000100ba.pnt\00000001.bsy
2016-12-28 18:38:08 Sending packet (C:\BBS\SBBS\temp\sbbsecho\58646900.pkt, 1.0KB) from 21:1/186 to 21:1/186.1
2016-12-28 18:38:08 Moving packet for 21:1/186.1: C:\BBS\SBBS\temp\sbbsecho\58646900.pkt to /bbs/sbbs/data/outbound.015\000100ba.pnt\58646900.pkt
2016-12-28 18:38:08 Deleting C:\BBS\SBBS\temp\sbbsecho\58646900.pkt (from line 2160)
2016-12-28 18:38:08 Packing packet (/bbs/sbbs/data/outbound.015\000100ba.pnt\58646900.pkt) into bundle (/bbs/sbbs/data/outbound.015\000100ba.pnt\0000p001.WE0) for 21:1/186.1 using ZIP
2016-12-28 18:38:08 Executing: /bbs/pb/zip /bbs/sbbs/data/outbound.015\000100ba.pnt\0000p001.WE0 /bbs/sbbs/data/outbound.015\000100ba.pnt\58646900.pkt
2016-12-28 18:38:09 Deleting /bbs/sbbs/data/outbound.015\000100ba.pnt\58646900.pkt (from line 1983)
Sorry, it ended up a bit messy with the word wrapping.
Re: Mystic point and SBBS
By: Digital Man to Black Panther on
Sat Dec 31 2016 00:48:40
Ok, I just sent a message from my point system, and had it send through the main SBBS node. Here is a full sbbsecho.log snapshot of what happened. I do appologize for the length, but I wanted to make sure that everything was included. The only thing that looked odd, was the circular path detected.
The log says the packet was "from 24:150/2.2". I thought you said your point node was 24:150/2.1? It makes sense that when importing a packet from /2.2 that SBBSecho would echo the messages to /2.1.
Re: Mystic point and SBBS
By: Digital Man to Black Panther on
Sun Jan 01 2017 14:24:29
The log says the packet was "from 24:150/2.2". I thought you said your point node was 24:150/2.1? It makes sense that when importing a packet from /2.2 that SBBSecho would echo the messages to /2.1.
/2.1 is a point for my hotdoged tablet. /2.2 is the other computer. The message was sent from /2.2, but then was sent back to /2.2 after processing through SBBSEcho.
In any case, the likely issue is that PATH and SEENBY lines don't contain point numbers, so they can't be used for msg loop detection (with point nodes). The message header could be used to prevent a msg loop, but it appears the message headers in these packets from your /2.2 point do not contain point information:
In any case, the likely issue is that PATH and SEENBY lines don't
contain point numbers, so they can't be used for msg loop detection
(with point nodes). The message header could be used to prevent a msg
loop, but it appears the message headers in these packets from your
/2.2 point do not contain point information:
Thank you. I took a look at a .pkt from the point system, and you are correct. It is not showing the point in the address in either the path
or the seenby lines. I'll ask in the MysticBBS echos to see if there
is a work-around for this.
In any case, the likely issue is that PATH and SEENBY lines don't
contain point numbers, so they can't be used for msg loop detection
(with point nodes). The message header could be used to prevent a
msg loop, but it appears the message headers in these packets from
your /2.2 point do not contain point information:
Thank you. I took a look at a .pkt from the point system, and you
are correct. It is not showing the point in the address in either
the path or the seenby lines. I'll ask in the MysticBBS echos to see
if there is a work-around for this.
there is no workaround... the processing system has to take into account the information in the PKT header when processing messages from point systems... hopefully there's also MSGIDs in the messages along with proper origin lines that also contain that point information...
Re: Mystic point and SBBS
By: Digital Man to Black Panther on
Mon Jan 02 2017 04:08:59
In any case, the likely issue is that PATH and SEENBY lines don't contain point numbers, so they can't be used for msg loop detection (with point nodes). The message header could be used to prevent a msg loop, but it appears the message headers in these packets from your /2.2 point do not contain point information:
Thank you. I took a look at a .pkt from the point system, and you are correct. It is not showing the point in the address in either the path or the seenby lines. I'll ask in the MysticBBS echos to see if there is a work-around for this.
Re: Mystic point and SBBS
By: Black Panther to Digital Man on Mon Jan 02 2017 12:17 pm
Re: Mystic point and SBBS
By: Digital Man to Black Panther
on Mon Jan 02 2017 04:08:59
In any case, the likely issue is that PATH and SEENBY lines don't contain point numbers, so they can't be used for msg loop detection (with point nodes). The message header could be used to prevent a msg loop, but it appears the message headers in these packets from your /2.2 point do not contain point information:
Thank you. I took a look at a .pkt from the point system, and you are correct. It is not showing the point in the address in either the path or the seenby lines. I'll ask in the MysticBBS echos to see if there is a work-around for this.
It is normal and expected that point information is not included in PATH and SEEN-BY lines (the FTN standards don't allow for it). However, there should be a "FMPT" kludge line indicating the point number or the Origin line should include the full address (with point information). What is the origin line on these messages?
It is normal and expected that point information is not included in PATH and SEEN-BY lines (the FTN standards don't allow for it). However, there
should be a "FMPT" kludge line indicating the point number or the Origin line should include the full address (with point information). What is the origin line on these messages?
there is no workaround... the processing system has to take into
account the information in the PKT header when processing messages
from point systems... hopefully there's also MSGIDs in the messages
along with proper origin lines that also contain that point
information...
Yes, the MSGID and the origin lines indicate the correct point
address. It was just in the PATH and SEENBY lines which did not.
I guess it's something I can live with, as it is just an annoyance.
Thanks
Re: Mystic point and SBBS
By: Digital Man to Black Panther on
Mon Jan 02 2017 15:35:59
It is normal and expected that point information is not included in PATH and SEEN-BY lines (the FTN standards don't allow for it). However, there
I did just find that out. I didn't realize it was only 2D for the PATH and SEEN-BY lines.
should be a "FMPT" kludge line indicating the point number or the Origin line should include the full address (with point information). What is the origin line on these messages?
The only kludge lines that I'm seeing in the outgoing messages are the MSGID and TZUTC lines. When they come back to the point system, they contain TID, MSGID, TZUTC, SEEN-BY and PATH.
The origin lines show the correct point address. For example:
* Origin: Castle Rock BBS 2 - Test Point (24:150/2.2)
I do have an example outbound packet that I captured and zipped up. Would you like me to send it to you? If so, what method would be the best?
Thanks again for the assistance.
I see in your follow-up email to Mark that your origin line apparently contains the full address (with point). I just commited a change in CVS to SBBSecho which I would appreciate if you would try (if you need a build for Windows, you'll have to get tomorrow morning's daily dev-build). This change *should* avoid this message loop-back, but I don't have any immediate method of testing, so I'd appreciate your feedback. Thanks,
I do have an example outbound packet that I captured and zipped up.
Would you like me to send it to you? If so, what method would be the
best?
Upload to Vertrauen (e.g. FTP to vert.synchro.net /incoming) or just email to rob {at} synchro {dot} net.
It is normal and expected that point information is not included in PATH and SEEN-BY lines (the FTN standards don't allow for it). However, there should be a "FMPT" kludge line indicating the point number or the Origin line should include the full address (with point information). What is the origin line on these messages?
You're welcome. Hopefully my latest change to SBBSecho v3.0 fixes this for ya.
On 2017 Jan 02 15:35:58, you wrote to Black Panther:
It is normal and expected that point information is not included in PATH and SEEN-BY lines (the FTN standards don't allow for it). However, there should be a "FMPT" kludge line indicating the point number or the Origin line should include the full address (with point information). What is the origin line on these messages?
ummm... FMPT and TOPT are for netmail... not echomail ;)
Re: Mystic point and SBBS
By: Digital Man to Black Panther on
Mon Jan 02 2017 23:01:39
You're welcome. Hopefully my latest change to SBBSecho v3.0 fixes this for ya.
Rob,
That seemed to take care of the issue. I just sent out a test message from the point system, and didn't get a copy sent back.
ummm... FMPT and TOPT are for netmail... not echomail ;)
Thanks, I realized that after I wrote the message.
| Sysop: | Ragnarok |
|---|---|
| Location: | Dock Sud, Bs As, Argentina |
| Users: | 136 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 57:59:35 |
| Calls: | 15,174 |
| Calls today: | 1 |
| Files: | 19,862 |
| D/L today: |
62 files (12,245K bytes) |
| Messages: | 1,693,707 |