So, I learned today that... SMH;

I didn't have BINKP set to active in my Mystic config.
Yea.

So, what was I missing?; the ability to receive incoming connections? Like netmail?
I suppose, tG & BP, that would explain a bit...

I left the settings to stock, AND have been telling my message nets that the port is standard, so... I *think* I should be ok - do I need to test
anything?
-----
#33;
I'm going to dive into a Mystic upgrade from A45 to A47.

Is there anything I should watch out for/do?

Thanks all... yay for me. :/



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

So, I learned today that... SMH;

I didn't have BINKP set to active in my Mystic config.
Yea.

So, what was I missing?; the ability to receive incoming connections? Like netmail?

Yes, you were missing inbound connections. In the case of your hubs you would poll them and pick stuff up so no worries. If anyone tried to send anything to you directly that would not have been possible.

I suppose, tG & BP, that would explain a bit...

If you want to be contactable/pollable directly you need the binkp server active.

I left the settings to stock, AND have been telling my message nets that the port is standard, so... I *think* I should be ok - do I need to test anything?

For your server to be contactable by anyone I would leave off "force CRAM-MD5" so mailers like BBBS (BBBS doesn't support CRAM-MD5) can poll. Also leave on "Allow Unsecure" so you can accept polls from nodes that are not in your config, and so there is no password for those connections.

I'm going to dive into a Mystic upgrade from A45 to A47.

Is there anything I should watch out for/do?

I have noticed a small problem with the TZUTC kludge that will probably be fixed soon and is really nothing to worry about. I noticed this problem with the linux64 version and it may not even affect the others.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 17 Oct 2020 at 02:14p, Al pondered and said...

Yes, you were missing inbound connections. In the case of your hubs you would poll them and pick stuff up so no worries. If anyone tried to send anything to you directly that would not have been possible.

You would also want your HUB to set your node to CRASH so it tries to push packets to your BinkP server

For your server to be contactable by anyone I would leave off "force CRAM-MD5" so mailers like BBBS (BBBS doesn't support CRAM-MD5) can poll. Also leave on "Allow Unsecure" so you can accept polls from nodes that
are not in your config, and so there is no password for those
connections.

good advice :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 17 Oct 2020, Al said the following...

I have noticed a small problem with the TZUTC kludge that will probably befixed soon and is really nothing to worry about. I noticed this
problem withthe linux64 version and it may not even affect the others.

Let's see if it affects others running Linux64..?

Regards,
Nick

--- Mystic BBS v1.12 A47 2020/10/17 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

So, what was I missing?; the ability to receive incoming connections? Li netmail?

Yes, you were missing inbound connections. In the case of your hubs you would poll them and pick stuff up so no worries. If anyone tried to send anything to you directly that would not have been possible.

Makes sense as to why I'd get netmails a bit late. :/ I understand now, and
its obvious that when I was BBSing back in the day, I wasn't networked. My board wasn't one I wanted to be a part of the broader community.

For your server to be contactable by anyone I would leave off "force CRAM-MD5" so mailers like BBBS (BBBS doesn't support CRAM-MD5) can poll. Also leave on "Allow Unsecure" so you can accept polls from nodes that
are not in your config, and so there is no password for those
connections.

Thanks; I had all of this setup correctly, from when I joined fsxNet - but I just never tacked the 'yes' option on the BINKP network tab. Stupid... but my FTNs were working so.... anyway, glad I *think* I have it running smoothly
now.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

You would also want your HUB to set your node to CRASH so it tries to
push packets to your BinkP server

Yes, solaris mentioned this in the first email he sent me with my details. Guess I'd better send him off an email so I can be all up in fsx correctly.
:P



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 18 Oct 2020, paulie420 said the following...

Thanks; I had all of this setup correctly, from when I joined fsxNet -
but I just never tacked the 'yes' option on the BINKP network tab. Stupid... but my FTNs were working so.... anyway, glad I *think* I have
it running smoothly now.

You can always use a port scanner to make sure it's actually open to the outside:

GRC's Shields Up:
https://www.grc.com/x/ne.dll?rh1dkyd2

IP Fingerprints:
https://www.ipfingerprints.com/portscan.php


Jay

... Waking up this morning was an eye-opening experience

--- Mystic BBS v1.12 A47 2020/10/13 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

On 18 Oct 2020, Accession said the following...

I have noticed a small problem with the TZUTC kludge that will probab befixed soon and is really nothing to worry about. I noticed this problem withthe linux64 version and it may not even affect the others

Let's see if it affects others running Linux64..?

Yes, and your version is very close to mine and yet I see your time is accurate and includes a TZUTC of -0500.

My time is accurate too.. it's just UTC.

Ttyl :-),
Al

--- Mystic BBS v1.12 A47 2020/10/17 (Linux/64)
* Origin: Equinox BBS - Penticton, BC Canada (21:4/106.2)

Thanks; I had all of this setup correctly, from when I joined fsxNet but I just never tacked the 'yes' option on the BINKP network tab. Stupid... but my FTNs were working so.... anyway, glad I *think* I ha it running smoothly now.

You can always use a port scanner to make sure it's actually open to the outside:
GRC's Shields Up:
https://www.grc.com/x/ne.dll?rh1dkyd2
IP Fingerprints:
https://www.ipfingerprints.com/portscan.php
Jay

Thanks, fingerprints found the port - appreciate the tip.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)