Prealpha again to fix some IP & country blocking/IPV6 wierdness.
Getting close to A36 full release I think! And A37 should get rid of MIS entirely.
Getting close to A36 full release I think! And A37 should get rid of entirely.
Did you happen to see my message on Failed to Create Node: 740
when I run Telnet under MIS2?
Prealpha again to fix some IP & country blocking/IPV6 wierdness.
Getting close to A36 full release I think! And A37 should get rid of MIS entirely.
--- Mystic BBS v1.12 A36 2017/11/21 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
Prealpha again to fix some IP & country blocking/IPV6 wierdness.
Getting close to A36 full release I think! And A37 should get rid of MIS entirely.
Prealpha again to fix some IP & country blocking/IPV6 wierdness.
Getting close to A36 full release I think! And A37 should get rid of MIS entirely.
Did you happen to see my message on Failed to Create Node: 740
when I run Telnet under MIS2?
What operating system and version?
740 is a Windows error saying that the user you're running the BBS with doesn't have administration rights to spawn the node. The actual error
is "Elevated permissions are required to execute".
Did you happen to see my message on Failed to Create Node: 740
when I run Telnet under MIS2?
What operating system and version?
740 is a Windows error saying that the user you're running the BBS with doesn't have administration rights to spawn the node. The actual error
is "Elevated permissions are required to execute".
Prealpha again to fix some IP & country blocking/IPV6 wierdness.
Getting close to A36 full release I think! And A37 should get rid of MIS entirely.
On 11/21/17, g00r00 pondered and said...
Prealpha again to fix some IP & country blocking/IPV6 wierdness.
Getting close to A36 full release I think! And A37 should get rid of entirely.
I'm uncertain if to update the HUB the reason being I really want to retain the custom bsy logging you created for me. The hope being when
the day arrives again for the lockups (which frustratingly have not happened since putting in the modified .exe files) then the issue can be caught.
Prealpha again to fix some IP & country blocking/IPV6 wierdness.
Getting close to A36 full release I think! And A37 should get rid of MIS entirely.
On 11/21/17, g00r00 said the following...
Prealpha again to fix some IP & country blocking/IPV6 wierdness. Getting close to A36 full release I think! And A37 should get rid of entirely.
no crash from 11/20/17 compile ;)
Pfft now get 11/21!
Will give this a try as I am eager to see if this fixes the issues was seeing, also g00r00 should we still be using the blacklist.txt and the ip blocking that is under internet servers? I was under the impression we use both. =)
I'm uncertain if to update the HUB the reason being I really want to retain the custom bsy logging you created for me. The hope being when
the day arrives again for the lockups (which frustratingly have not happened since putting in the modified .exe files) then the issue can be caught.
Prealpha again to fix some IP & country blocking/IPV6 wierdness.
Getting close to A36 full release I think! And A37 should get rid of MIS >entirely.
--- Mystic BBS v1.12 A36 2017/11/21 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
Its in all of the prealpha versions. Everyone has those busy logs so
you are safe to upgrade freely.
Its in all of the prealpha versions. Everyone has those busy logs so
you are safe to upgrade freely.
g00r00 wrote to Pequito <=-
I haven't figured out what to do about blacklist DNS yet, but that will
be more important when I enable outside e-mail via SMTP.
Pequito wrote to g00r00 <=-
Also telnet when connected shows like this, is this maybe the reason unable to know what country?
19:07:39 TELNET 2-Address ::FFFF:BB90:9A0B
SSH shows the entire ipv6 address:
19:07:01 SSH 1-Address 2601:08C0:4280:1C81:020C:29FF:FE10:ADC3
I haven't figured out what to do about blacklist DNS yet, but that wi be more important when I enable outside e-mail via SMTP.
Blacklist DNS is fraught with issues, while useful as an input to
systems like SpamAssassin, I've seen too many issues with the RBLs being too overxealous in blocking domains.
g00r00 wrote to vk3jed <=-
For now I am just not going to worry about it in MIS2 - most people
seemed only really interested in the country blocking anyway, and I
have that covered now.
I think country blocking is the main thing. And also the ability to
block IP address ranges might be useful.
g00r00 wrote to vk3jed <=-
I think country blocking is the main thing. And also the ability to
block IP address ranges might be useful.
You can wildcard them to block entire subnets already. Its not the
same thing as a range and it doesn't use standard notation but it
should give you the ability to do some wildcarding.
I am updating pre-alphas again.
This built has changed to the FS editor template to allow users to save draft messages so they can continue them later. Mystic already creates drafts if a user times out or loses connection, or if Mystic errors when saving a message, but now users can do it too.
Also, the beginnings of the echomail ACS system are active, although
only one part of it is enabled. I added the "subscribe/read ACS" to message bases first only because it was by far the easiest to do. More
to come though!
I also made some changes to the default install to include an option on the message menu for draft messages.
This built has changed to the FS editor template to allow users to save draft messages so they can continue them later. Mystic already creates drafts if a user times out or loses connection, or if Mystic errors when saving a message, but now users can do it too.
Ok, just re-ran my update script and it got "2018/12/14 13:43:05" so I'm good it seems {chuckle} belay that last post please :)
I did spot a little thing. There is a one second difference in the
time stamp displayed within mystic -cfg vs. using mystic -ver from the command line.
v1.12 A40 Windows/32 Compiled 2018/12/14 13:43:05
Û Mystic BBS v1.12 A40 compiled 2018/12/14 13:43:04 Û
:)
Uh-oh, now we're in BIG trouble {chuckle} thanks for the heads up :)
I downloaded the latest Win32 1.12 A40 (on 12/13/2018) and it has the
same timestamp as the last one (2018/12/11 00:00:45 generated from "mystic.exe -ver") even though the file itself was newer than the last
It's me being too detailed. Heh, shows me the var is stored in different locations at well different times I guess :)
I downloaded the latest Win32 1.12 A40 (on 12/13/2018) and it hasAre you sure there wasn't a user error where the file wasn't copied
the same timestamp as the last one (2018/12/11 00:00:45 generated
from "mystic.exe -ver") even though the file itself was newer
than the last
over?
Hi G00r00,
Just d/l'd and installed the latest prealpha, and it can't transfer
files (working fine before) see tear for version :)
=== snip ===
Dec 30 12:24:43 Polling BINKP node 3:770/1 by IPV4
Dec 30 12:24:43 Connecting to agency.bbs.nz
Dec 30 12:24:44 Using address 219.89.83.33
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 132:21:41 |
| Calls: | 2,073 |
| Files: | 11,136 |
| Messages: | 947,549 |