• Synchronet Paths and Seen-By's?

    From Jeff Smith@1:282/1031 to All on Mon Nov 28 01:27:10 2016
    Hello There,

    I have done another recent fresh install of SBBS v3.17 for Linux. SBBS is setup
    in a FTN to use a point AKA. When a "Test" echomail message is generated SBBS looks to generate a AKA of 0/0 instead of using it's assigned point AKA address of 21:1/128.1.

    @TZUTC: -0600
    @MSGID: 1.fsx_gen@21:1/128.1 1c9e31f4
    @PID: Synchronet 3.17a-Linux Nov 25 2016 GCC
    @TID: SBBSecho 3.00-Linux r3.26 Nov 25 2016 GCC 5.4.0

    @PATH: 0/0 1/128 100

    I have SBBS setup to use the correct point AKA and it does include the correct AKA in the origin line but not in the individual message path. I have generated
    several test messages and all show of 0/0.

    Any thoughts?

    Jeff

    --- BBBS/Li6 v4.10 Dada-2
    * Origin: The OuijaBoard - Anoka, MN (1:282/1031)
  • From Digital Man@1:103/705 to Jeff Smith on Mon Nov 28 00:53:32 2016
    Re: Synchronet Paths and Seen-By's?
    By: Jeff Smith to All on Mon Nov 28 2016 01:27 am

    Hello There,

    I have done another recent fresh install of SBBS v3.17 for Linux. SBBS is setup
    in a FTN to use a point AKA. When a "Test" echomail message is generated SBBS looks to generate a AKA of 0/0 instead of using it's assigned point AKA address of 21:1/128.1.

    @TZUTC: -0600
    @MSGID: 1.fsx_gen@21:1/128.1 1c9e31f4
    @PID: Synchronet 3.17a-Linux Nov 25 2016 GCC
    @TID: SBBSecho 3.00-Linux r3.26 Nov 25 2016 GCC 5.4.0

    @PATH: 0/0 1/128 100

    I have SBBS setup to use the correct point AKA and it does include the correct AKA in the origin line but not in the individual message path. I have generated
    several test messages and all show of 0/0.

    Any thoughts?

    PATH lines only support 2D addresses, so point address aren't added PATHs. Most likely that 0/0 is coming from somewhere else (not your AKAs).

    What's your AREAS.BBS line look for this echo?

    digital man

    Synchronet/BBS Terminology Definition #4:
    BBS = Bulletin Board System
    Norco, CA WX: 47.8oF, 75.0% humidity, 3 mph W wind, 0.03 inches rain/24hrs
    --- SBBSecho 3.00-Win32
    * Origin: Vertrauen - vert.synchro.net (1:103/705)
  • From Jeff Smith@1:282/1031 to Digital Man on Mon Nov 28 07:15:14 2016
    Hello Digital Man,

    I have done another recent fresh install of SBBS v3.17 for Linux. SBBS is
    setup
    in a FTN to use a point AKA. When a "Test" echomail message is generated
    SBBS looks to generate a AKA of 0/0 instead of using it's assigned point >> AKA address of 21:1/128.1.

    @TZUTC: -0600
    @MSGID: 1.fsx_gen@21:1/128.1 1c9e31f4
    @PID: Synchronet 3.17a-Linux Nov 25 2016 GCC
    @TID: SBBSecho 3.00-Linux r3.26 Nov 25 2016 GCC 5.4.0

    @PATH: 0/0 1/128 100

    I have SBBS setup to use the correct point AKA and it does include the
    correct AKA in the origin line but not in the individual message path. I
    have generated several test messages and all show of 0/0.

    Any thoughts?
    PATH lines only support 2D addresses, so point address aren't added PATHs.

    Most likely that 0/0 is coming from somewhere else (not your AKAs).
    What's your AREAS.BBS line look for this echo?

    The test messages were sent in two different echos with corresponding AREAS.BBS
    entries of:

    FSX_GEN FSX_GEN 21:1/128
    FIDOTEST FIDOTEST 1:282/1031

    So, since I am using a point address SBBS isn't/can't adding that AKA as the origin AKA to the path?

    That conclusion is based on the fact that if I generate a test message using a non point Fido address then SBBS seems to add the correct origin AKA (1:282/1032) to the message path.

    As in:

    @PID: Synchronet 3.17a-Linux Nov 25 2016 GCC
    @TZUTC: -0600
    @TID: SBBSecho 3.00-Linux r3.26 Nov 25 2016 GCCFIDOTEST FIDOTEST
    1:282/1031FIDOTEST FIDOTEST
    1:282/1031FIDOTEST FIDOTEST 1:282/1031 5.4.0
    Hello There,

    Checking the correct message path.

    Jeff
    --- SBBSecho 3.00-Linux
    * Origin: The OuijaBoard Too - bbs2.ouijabrd.net (1:282/1032)

    @PATH: 282/1032 1031 261/38 393/68 770/1 280/464

    I am not trying to arbitrarily place responsibility but am looking to understand what is happening and why. Currently, SBBS is generating the message
    and sending it to BBBS who in turn sends the message onward.


    Jeff


    --- BBBS/Li6 v4.10 Dada-2
    * Origin: The OuijaBoard - Anoka, MN (1:282/1031)
  • From Digital Man@1:103/705 to Jeff Smith on Mon Nov 28 11:04:08 2016
    Re: Synchronet Paths and Seen-By's?
    By: Jeff Smith to Digital Man on Mon Nov 28 2016 07:15 am

    Hello Digital Man,

    I have done another recent fresh install of SBBS v3.17 for Linux. SBBS is >> setup
    in a FTN to use a point AKA. When a "Test" echomail message is generated >> SBBS looks to generate a AKA of 0/0 instead of using it's assigned point >> AKA address of 21:1/128.1.

    @TZUTC: -0600
    @MSGID: 1.fsx_gen@21:1/128.1 1c9e31f4
    @PID: Synchronet 3.17a-Linux Nov 25 2016 GCC
    @TID: SBBSecho 3.00-Linux r3.26 Nov 25 2016 GCC 5.4.0

    @PATH: 0/0 1/128 100

    I have SBBS setup to use the correct point AKA and it does include the
    correct AKA in the origin line but not in the individual message path. I >> have generated several test messages and all show of 0/0.

    Any thoughts?
    PATH lines only support 2D addresses, so point address aren't added PATHs.

    Most likely that 0/0 is coming from somewhere else (not your AKAs).
    What's your AREAS.BBS line look for this echo?

    The test messages were sent in two different echos with corresponding AREAS.BBS
    entries of:

    FSX_GEN FSX_GEN 21:1/128
    FIDOTEST FIDOTEST 1:282/1031

    So, since I am using a point address SBBS isn't/can't adding that AKA as
    the origin AKA to the path?

    Correct.

    That conclusion is based on the fact that if I generate a test message using a non point Fido address then SBBS seems to add the correct origin AKA (1:282/1032) to the message path.

    As in:

    @PID: Synchronet 3.17a-Linux Nov 25 2016 GCC
    @TZUTC: -0600
    @TID: SBBSecho 3.00-Linux r3.26 Nov 25 2016 GCCFIDOTEST
    FIDOTEST
    1:282/1031FIDOTEST FIDOTEST
    1:282/1031FIDOTEST FIDOTEST
    1:282/1031 5.4.0
    Hello There,

    Checking the correct message path.

    Jeff
    --- SBBSecho 3.00-Linux
    * Origin: The OuijaBoard Too - bbs2.ouijabrd.net (1:282/1032)

    @PATH: 282/1032 1031 261/38 393/68 770/1 280/464

    I am not trying to arbitrarily place responsibility but am looking to understand what is happening and why. Currently, SBBS is generating the message
    and sending it to BBBS who in turn sends the message onward.

    Is it possible that BBBS is adding those addresses to the PATH? Based on your areas.bbs file, SBBSecho should only be putting *one* address in the PATH.

    digital man

    Synchronet/BBS Terminology Definition #49:
    SyncTERM = The Synchronet Terminal Emulator/BBS-client program
    Norco, CA WX: 54.5oF, 75.0% humidity, 1 mph ESE wind, 0.01 inches rain/24hrs --- SBBSecho 3.00-Win32
    * Origin: Vertrauen - vert.synchro.net (1:103/705)