Hello Paul!

 JS>> with only allowing a IP4 connection. Unfortunately Mystic doesn't
 JS>> currently connect to many remote systems so I have only your
 JS>> BinkD and my BBBS connections to go by. And I haven't seen any of
 JS>> the same issue in connecting to BBBS. I will setup a BinkD based
 JS>> point

 PH> You're more than welcome to test by connecting to 3:770/1 also Jeff.
 PH> We can liaise to set up some session details if you like.

I will keep that in mind Paul. In exploring the HTTP capabilities of
Mystic this morning. I noticed that if I enable both IP4 and IP6 on
the HTTP server. I get an immediate "IP Blocked" when connecting locally.
If I make the HTTP server to IP4 only then I can connect fine. That is with
all local IP's already setup in Mystic's whitelist file. Currently I have a
IP6toIP4 tunnel from HE.NET installed and it seemds to work ok otherwise.

Mystic's FQDN resolves correctly to both IP4 and IP6 IP's.

Log snippets in next message.

Jeff


--- Mystic v1.12 A43 (2019/03/02) GoldED+/LNX 1.1.5-b20170303