• Prealphas Jan 28

    From g00r00@21:1/108 to All on Tue Jan 28 00:17:44 2020
    Updated the prealpha again with a fix for an obscure bug, a change to remove the node/OS from the connection banner, and...

    A change to the node calculation. I was DDOSing the Windows version with 25 concurrent telnet nodes in a WinXP vmware. I was able to get the occasional node calculation conflict which resulted in a ghost node.

    I made a change and DDOSed the it for quite a while and it was flawless after the change. Hopefully there will be some improvement in that area.

    --- Mystic BBS v1.12 A44 2020/01/28 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Avon@21:1/101 to g00r00 on Tue Jan 28 20:40:50 2020
    On 28 Jan 2020 at 12:17a, g00r00 pondered and said...

    Updated the prealpha again with a fix for an obscure bug, a change to remove the node/OS from the connection banner, and...

    OK have applied this one at NET 1 HUB (21:1/100) and it's now tossing all traffic for those nodes. I did my usual test post to Agency first and the SEEN-BYs seem to be correct (thank you :))

    Here's what I see

    [snip]

    From: Paul Hayton
    To: All
    Subj: NET 1 HUB
    Date: 01/28/20 20:23
    Base: General Chat

    @TID: Mystic BBS 1.12 A44
    @MSGID: 21:1/100 b839b747
    @TZUTC: 1300
    @SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 1/116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 133 @SEEN-BY: 1/134 136 137 138 139 140 141 143 144 145 146 147 148 149 150 152 153 @SEEN-BY: 1/154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 171 @SEEN-BY: 1/172 173 174 175 176 177 178 180 181 182 183 184 185 186 187 188 189 @SEEN-BY: 1/190 191 192 193 194 195 197 199 200 201 202 203 204 205 995 999 @SEEN-BY: 2/100 3/100 4/100 5/100
    @PATH: 1/100
    Has been updated to v1.12 A44 Windows/32 Compiled 2020/01/28 00:37:48

    --- Mystic BBS v1.12 A44 2020/01/28 (Windows/32)
    * Origin: fsxNet HUB (21:1/100)

    [snip]

    So I'm leaving this build in place to give it a good test :)

    I noticed the stats when I checked the echomail nodes are all out of whack

    [snip]

    22 Yes Darryl Perry / Cyberia BB Darryl Perry 21:1/120
    ───────────────────────────────────────────────────────────────────────────
    Inactive: 2,858 days Last In: Never
    Received: 0 (0KB) Last Out: 01 Apr 2012 18:09
    Sent: 0 (0KB) Reset: Never

    lots looking like this.

    The reset option only seems to be per node, you can't reset all or tag nodes
    to apply a selected global style reset. Do you think this could or should be done?

    Best, Paul

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to g00r00 on Tue Jan 28 20:57:23 2020
    On 28 Jan 2020 at 08:40p, Avon pondered and said...

    21:1/120 ──────────────────────────────────────────────────────────────────────────
    Received: 0 (0KB) Last Out: 01 Apr 2012 18:09 Sent: 0 (0KB) Reset: Never

    of course this could probably be ignored as I have not been using MIS nor FIDOPOLL lately for BinkP duties... so ignore my late night ramblings on this one :)

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Captain Obvious@21:1/157 to g00r00 on Tue Jan 28 05:46:37 2020
    It may already be possible to do this but I was not able to find anything in the docs.

    Would it be possible for Mutil to autocreate message bases based on the HUB network address rather than or as well as the node net address?

    Not sure about other folks but I receive two different Fido feeds (zone 1 and 2) as well as two in fsx (normal network and gated usenet).

    Not a huge deal to move stuff to a different group manually as once they are added I don't guess many people change that stuff a lot but I can see where
    if someone were using Mystic as a hub it could be useful.

    Not sure if I actually got my point across but there it is <g>

    -=>Richard Miles<=-
    -=>Captain Obvious<=-
    -=>bbs.shadowscope.com<=-

    --- Mystic BBS v1.12 A44 2020/01/27 (Windows/32)
    * Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)
  • From g00r00@21:1/108 to Avon on Tue Jan 28 13:36:41 2020
    The reset option only seems to be per node, you can't reset all or tag nodes to apply a selected global style reset. Do you think this could or should be done?

    You can tag and reset it in the next build. I suspect mostly they will be
    reset via MUTIL once we figure out what we want to build into it to work with this stuff!

    The dates being messed up is an artifact from previous upgrades because I changed the format of the date between the time I started and now.

    --- Mystic BBS v1.12 A44 2020/01/28 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Avon@21:1/101 to g00r00 on Wed Jan 29 10:26:34 2020
    On 28 Jan 2020 at 01:36p, g00r00 pondered and said...

    You can tag and reset it in the next build. I suspect mostly they will be reset via MUTIL once we figure out what we want to build into it to work with this stuff!
    The dates being messed up is an artifact from previous upgrades because I changed the format of the date between the time I started and now.

    All noted.. Thanks!

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)