hey, I found a bug in sbbsecho, a downlink did a areafix to turn on echos, should have been fidonet backbone ones only (the other two - r17 & n340 I turn on), he got every net I have in the areas.bbs file, before ask I have set so each net had it own code :
Address 1:340/101
Archive Type ZIP
Packet Type 2+
Packet Password ********
Areafix Password ********
Areafix Flags FN N340 R17
Status Crash
Direct Yes
Passive No
Send Notify List Yes
Route To Disabled
fn = fidonet
n340 = net 340 echo's
r17 = region 17 echo's
if you need a copy of my sbbsecho.cfg I can send it to you (by qwk networking) or if you need the sbbsecho log file can send the to you, after I take it out of message and move to a file (I have it set so every 24 hours it goes to a echo message) or my areas.bbs file (haven't fix it yet)
right now I am not home (on vaction)
ohh yes, before you ask sbbs 3.16b build date 4/13/15 (all files are current as of that date)
hey, I found a bug in sbbsecho, a downlink did a areafix to turn on echos, should have been fidonet backbone ones only (the other two - r17 & n340 I turn on), he got every net I have in the areas.bbs file, before ask I have set so each net had it own code :
Address 1:340/101
Archive Type ZIP
Packet Type 2+
Packet Password ********
Areafix Password ********
Areafix Flags FN N340 R17
Status Crash
Direct Yes
Passive No
Send Notify List Yes
Route To Disabled
fn = fidonet
n340 = net 340 echo's
r17 = region 17 echo's
So is "1:340/101" the downlink that requested the arefix to turn on echos?
What was the request, exactly? If the request was "+ALL" and the node as the AreaFix flags "FN N340 R17", then I would expect all the echoes for the echo lists matching those flags to have been added. So that doesn't sound like a bug to me.
if you need a copy of my sbbsecho.cfg I can send it to you (by qwk networking) or if you need the sbbsecho log file can send the to you, after I take it out of message and move to a file (I have it set so every 24 hours it goes to a echo message) or my areas.bbs file (haven't fix it yet)
right now I am not home (on vaction)
ohh yes, before you ask sbbs 3.16b build date 4/13/15 (all files are current as of that date)
I guess what i need is a better description of "the bug". I must be missing something.
Also, this messages seems better suited to Synchronet Discussion or Synchronet Sysops. It's not really a Synchronet Programming topic.
hey, I found a bug in sbbsecho, a downlink did a areafix to turn on echos, should have been fidonet backbone ones only (the other two - r17 & n340 I turn on), he got every net I have in the areas.bbs file, before ask I have set so each net had it own code :
Address 1:340/101
Archive Type ZIP
Packet Type 2+
Packet Password ********
Areafix Password ********
Areafix Flags FN N340 R17
Status Crash
Direct Yes
Passive No
Send Notify List Yes
Route To Disabled
fn = fidonet
n340 = net 340 echo's
r17 = region 17 echo's
So is "1:340/101" the downlink that requested the arefix to turn on echos?
yes
What was the request, exactly? If the request was "+ALL" and the node as the AreaFix flags "FN N340 R17", then I would expect all the echoes for the echo lists matching those flags to have been added. So that doesn't sound like a bug to me.
I don't know the command he used, the was the 3 nets plus the other ones, he wasn't set to get
Also, this messages seems better suited to Synchronet Discussion or Synchronet Sysops. It's not really a Synchronet Programming topic.
hmmm, I know one time this was fix being someone ask about it, read about it and then I set the flag up
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 326 |
Nodes: | 10 (0 / 10) |
Uptime: | 216:28:04 |
Calls: | 516 |
Messages: | 223254 |