Hello Digital,

I think I may have noticed something (which was caught by my point system) odd since upgrading to 3.17. It seems with the circular path detection enabled, now
it detects everything from the one point system I have as circular path dupes. Here's a snip from the logs:

Importing (secure e7bea400.pkt (Type 2+) from 1:154/10.11
FIDOTEST: Circular path detected for 1:154/10

Notice the 2nd line doesn't have the point number, and everything he's posting to Fidonet isn't going through. Is this the right behavior?

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20150715
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (723:1/701)
þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)

Re: Circular path detection..
By: Accession to Digital Man on Thu Sep 03 2015 05:15 pm

Hello Digital,

I think I may have noticed something (which was caught by my point system) odd since upgrading to 3.17. It seems with the circular path detection enabled, now
it detects everything from the one point system I have as circular path dupes. Here's a snip from the logs:

Importing (secure e7bea400.pkt (Type 2+) from 1:154/10.11
FIDOTEST: Circular path detected for 1:154/10

Notice the 2nd line doesn't have the point number, and everything he's posting to Fidonet isn't going through. Is this the right behavior?

1.154/10 is one of *your* AKAs and the message being imported has this address already listed in the "PATH" kludge line of the message, so it's detected as "circular" and ignored. This logic hasn't changed.

What *has* changed is that (optionally), circular messages aren't fowarded to other links for that echo. In previous versions, other links would still receive the circular message even if it was not imported (and reported as circular in the log). This is actually still the default behavior unless you have "NOCIRCULARFWD" set in your sbbsecho.cfg file.

So if you check your logs, I suspect you'll find that your point's messages were detected as circular in previous versions of SBBSecho as well (and not imported in your message base as a result).

If you do not have NOCIRCULARFWD set, then I would expect the behavior to be the same as earlier versions.

It sounds like your point node needs to stop adding your address to the PATH of messages being sent to you.

digital man

Synchronet "Real Fact" #48:
Synchronet program was named 'sbbs' instead of 'sync' to avoid conflict w/Unix. Norco, CA WX: 61.5øF, 87.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Hello Digital,

On 04 Sep 15 01:54, Digital Man wrote to Accession:

1.154/10 is one of *your* AKAs and the message being imported has this address already listed in the "PATH" kludge line of the message, so
it's detected as "circular" and ignored. This logic hasn't changed.

What *has* changed is that (optionally), circular messages aren't
fowarded to other links for that echo. In previous versions, other
links would still receive the circular message even if it was not
imported (and reported as circular in the log). This is actually still
the default behavior unless you have "NOCIRCULARFWD" set in your sbbsecho.cfg file.

So if you check your logs, I suspect you'll find that your point's messages were detected as circular in previous versions of SBBSecho as well (and not imported in your message base as a result).

If you do not have NOCIRCULARFWD set, then I would expect the behavior
to be the same as earlier versions.

It sounds like your point node needs to stop adding your address to
the PATH of messages being sent to you.

Now that I was able to take a deeper look into it, you're exactly right. For some reason his messages are being sent to me with MY node number, and not his point number which it should be using. I'll have to take a look over his setup when I get a chance and see if he's got a typo somewhere.

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20150715
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (723:1/701)
þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)