• Re: Zone Blind...

    From Nicholas Boel@1:154/701 to Bill McGarrity on Tue May 6 20:08:00 2014
    @MSGID: <5369862B.33570.sync_sys@vert.synchro.net>
    On 05-06-14, Bill McGarrity said the following...

    Quick question if Imay.

    Quick answer if I might!

    The issue is with Zone Blind toggle. If I don't want one network's addresses to appear in the seen-by and path lines of another, should
    that toggle be "enabled" or "disabled"? If enabled, that brings us to another issue that I was told to add a 4 at the end of the Zone_Blind in the sbbsecho.cfg file. I am assuming that means the first 4 zones
    should be considered as one. Over the past few weeks with the issues of the INTL kludge line in echomail (which was determined sbbsecho was not
    to blame) my head is spinning.... not that it doesn't normally spin anyway.

    No need for your head to spin.

    Here's the deal, for ages, Fidonet has stripped SEEN-BYs across zones so that everyone would still get their echomail if there were duplicate nets.

    For example, the last duplicate net was 250. There was a 1:250 anda 2:250.
    If 250/0 was kept in the SEEN-BYs from zone 1 to zone 2, 2:250/0 wouldn't get the echomail, and vice versa.

    Since there are no more duplicate nets in Fidonet, some have asked top stop stripping SEEN-BYs across zones. To accomodate this, we askedRob for some
    help in the matter. What he did was create the ZONE BLIND option. At first
    this caused trouble if you carried multiple networks because any echomail for any network would include ALL of your AKAs in the SEEN-BYs. So my Agoranet
    node number, my Zeronet node number, etc, were all being stuffed into Fidonet echomail, which wasn't good (just in case) there was a matching net/node combination between Fidonet and one of those other networks.

    So, going back to Rob.. he added an optional number afterthe ZONE_BLIND
    option. This way you can do ZONE_BLIND 4 and zones 1 through 4 will keep all SEEN-BYs in those zones, but anything AFTER 4 will not.

    In all reality, you *could* put ZONE_BLIND 6 but it really doesn't matter anymore since there are no zones5 and 6 in Fidonet. Any other zones above 4
    in our case will be treated normally, and WILL strip SEEN-BYs. For example, Agoranet is zone 46. Only zone 46 net/node combinations will be put into
    the SEEN-BYs in zone 46 echomail. Zone 46 will not be stuffed into Fidonet echomail.

    Also, The ZONE_BLIND 4 option helps those same people in Fidonet with dupe detection. If all 4 zones worth of SEEN-BYs are kept in echomail, there will
    be less dupes. By now you've probably gotten a chance to see what the
    "fidoweb" is all about. Everyone links to everyone for the same echos, and
    let the dupe detection sort everything out. This is why they'reasking to
    keep all SEEN-BYs in echomail now, as it would actually cause less dupes
    across zones.

    I'm sure Rob could have done it a better way, but this was a quick fix to
    make the very few people in Fidonet happy, while noone else in other networks have any issues sticking to the old ways of doing things.

    Either way, it's tried and tested here, working great for Fidonet, and the
    rest of the networks separately.

    BTW, the INTL kludge stuffing wasn't any kind of scare except to the original person that posted about it when they realized it was their own system. LOL!

    --- Mystic BBS v1.10 A39 (Linux)
    * Origin: Dark Sorrow | telnet://bbs.darksorrow.us (1:154/701)
  • From Joe Delahaye@1:249/303 to Bill McGarrity on Tue May 6 21:07:00 2014
    @MSGID: <5369941B.33572.sync_sys@vert.synchro.net>
    @TZ: 40f0
    Re: Zone Blind...
    By: Bill McGarrity to All on Tue May 06 201416:05:00

    The issue is with Zone Blind toggle. If I don't want one network's addresses to appear in the seen-by and path lines of another, should that toggle be "enabled" or "disabled"? If enabled, that brings us to another issue thatI was told to add a 4 at the end of the Zone_Blind in the sbbsecho.cfg file. I am assuming that means the first 4 zones should be considered as one. Over the past few weeks with the issues of the INTL kludge line in echomail (which was determined sbbsecho was not to blame) my head is spinning.... not that it doesn't normally spin anyway.


    The way to use it as we have for international traffic Bill, is how I mentioned
    it to you. If you toggle Zone Blind on again, you will run into seen by problems again.
    --- SBBSecho 2.27-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Bill McGarrity@1:266/404 to Joe Delahaye on Tue May 6 23:08:00 2014
    @MSGID: <5369B042.33574.sync_sys@vert.synchro.net>
    @REPLY: <5369941B.33572.sync_sys@vert.synchro.net>
    @TZ: 40f0
    Joe Delahaye wrote to Bill McGarrity <=-

    Hiya Joe...


    The issue is with Zone Blind toggle. If I don't want one network's addresses to appear in the seen-by and path lines of another, should that toggle be "enabled" or "disabled"? If enabled, that brings us to another issue that I was told to add a 4 at the end of the Zone_Blind in the sbbsecho.cfg file. I am assuming that means the first 4 zones should be considered as one. Over the past few weeks with the issues of the INTL kludge line in echomail (which was determined sbbsecho was not to blame) my head is spinning.... not that it doesn't normally spin anyway.


    The way to use it as we have for international traffic Bill, is how I mentioned it to you. If you toggle Zone Blind on again, you will run
    into seen by problems again.

    Nick just told me differently... and I edited sbbsecho.cfg to Zone_Blind 4. I'll make one more test... this is nuts... lol!!

    Thanks..


    Bill

    Telnet: bbs.tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Motorcycles are everywhere... Look twice, save a life!!
    --- MultiMail/Win32 v0.50
    --- SBBSecho 2.27-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Nicholas Boel@1:154/701 to Bill McGarrity on Wed May 7 20:36:00 2014
    @MSGID: <536AD76B.33580.sync_sys@vert.synchro.net>
    @REPLY: <536A7501.33578.sync_sys@vert.synchro.net>
    EEN-BY: 154/10 203/0124 221/1 249/303 266/404 280/5003 320/119 123/500 EEN-BY: 227/201 154/701 10 0
    ATH: 203/0 154/10
    I did all you said in adding ZONE_BLIND 4 to the cfg and it still sent
    out my aka's in the seen-by's. I disabled the ZONE Blind optionand now
    it strips my aka's. Cound Rob have done some other coding for this?
    This message has the toggle set to disable and there in no ZONE_BLIND statement in the cfg. Check the paths and seenbys to see if 100/24 and 973/2 are still there.

    It strips your AKAs, as well as any other nodes in other zones other than zone 1 out of the PATH statement. See the PATHI have here for this message as evidence. Bjorn in Zone 2 to me in Zone 1. The system it passed before
    Bjorn's system stripped SEEN-BYs across zones. Do you see where the issues
    lie in regards to their experiment?

    Using ZONE_BLIND by itself would includeevery one of your addresses listed
    on your system in the SEEN-BYs (I'm not sure about PATH).

    The "ZONE_BLIND 4" option should only include your fidonet addresses, and not any other networks into SEEN-BYs.

    If you had ZONE_BLIND 4 as the first line in your sbbsecho.cfg, you shouldn't have sent out any other addresses besides your 1:* ones. If you did, then something wasn't done properly. Did you try recycling Synchronet?

    Joe is using this same feature on Win32, and it seems to be working fine for him. I'mnot sure what the deal is seeing as though I'm running Linux here.

    I can't really get the facts out of your message currently,because someone between you and I are also stripping zones out of the PATH line (Probably
    Ross, since HPT doesn't have an option to change that, but hopefully it will
    in the future).

    Regards,
    Nick

    --- Mystic BBS v1.10 A39 (Linux)
    * Origin: Dark Sorrow | telnet://bbs.darksorrow.us (1:154/701)
  • From Bill McGarrity@1:266/404 to Nicholas Boel on Wed May 7 23:06:00 2014
    @MSGID: <536B01AC.33581.sync_sys@vert.synchro.net>
    @REPLY: <536AD76B.33580.sync_sys@vert.synchro.net>
    @TZ: 40f0
    Hiya Nick...

    Nicholas Boel wrote to Bill McGarrity <=-

    I did all you said in adding ZONE_BLIND 4 to the cfg and it still sent
    out my aka's in the seen-by's. I disabled the ZONE Blind option and now it strips my aka's. Cound Rob have done some othercoding for this?
    This message has the toggle set to disable and there in no ZONE_BLIND statement in the cfg. Check the paths and seenbys to see if 100/24 and 973/2 are still there.

    It strips your AKAs, as well as any other nodes in other zones other
    than zone 1 out of the PATH statement. See the PATH I have here for
    this message as evidence. Bjorn in Zone 2 to me in Zone 1. The system
    it passed before Bjorn's system stripped SEEN-BYs across zones. Do you
    see where the issues lie in regards to their experiment?

    Using ZONE_BLIND by itself would include every one of your addresses listed on your system in the SEEN-BYs (I'm not sure about PATH).

    The "ZONE_BLIND 4" option should only include your fidonetaddresses,
    and not any other networks into SEEN-BYs.

    If you had ZONE_BLIND 4 as the first line in your sbbsecho.cfg,you shouldn't have sent out any other addresses besides your 1:* ones. If
    you did, then something wasn't done properly. Did you try recycling Synchronet?

    Joe is using this same feature on Win32, and it seems to be working
    fine for him. I'm not sure what the deal is seeing as though I'm
    running Linux here.

    I can't really get the facts out of your message currently, because someone between you and I are also stripping zones out of the PATH line (Probably Ross, since HPT doesn't have an option to change that, but hopefully it will in the future).

    OK, I reconfigured it as your said, ZONE_BLIND 4 and completely restarted the server. I'll try and capture this message on the way out in my outbound folder
    and see what seen-bys and path statements are in the message. I will post said
    results in next message...


    Bill

    Telnet: bbs.tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Motorcycles are everywhere... Look twice, save a life!!
    --- MultiMail/Win32 v0.50
    --- SBBSecho 2.27-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)