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?
I'm going to dive into a Mystic upgrade from A45 to A47.
Is there anything I should watch out for/do?
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.
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 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.
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.
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.
You would also want your HUB to set your node to CRASH so it tries to
push packets to your BinkP server
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.
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..?
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
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,045 |
Nodes: | 15 (0 / 15) |
Uptime: | 11:27:12 |
Calls: | 500,414 |
Files: | 95,210 |
D/L today: |
5,607 files (565M bytes) |
Messages: | 465,161 |