Hello Paul,


> Jeff, just reaching out here. I can see problems with you polling the Z21 NET
> 1 HUB looks like no correct AKAs are being presented?
> [snip]
> + 2019.03.14 18:23:54  BINKP > Connect on slot 1/25 (65.103.12.161)
> + 2019.03.14 18:23:54  BINKP 1-HostName Unknown
> + 2019.03.14 18:23:54  BINKP 1-S: NUL OPT
> CRAM-MD5-f66e688ea332a93cb8dbb22a174cf960
> + 2019.03.14 18:23:54  BINKP 1-S: NUL SYS fsxHUB Risa [NET1]
> + 2019.03.14 18:23:54  BINKP 1-S: NUL ZYZ Avon
> + 2019.03.14 18:23:54  BINKP 1-S: NUL TIME Thu, 14 Mar 2019 18:23:54 1300
> + 2019.03.14 18:23:54  BINKP 1-S: NUL VER Mystic/1.12A43 binkp/1.0
> + 2019.03.14 18:23:54  BINKP 1-S: NUL BUILD 2019/03/03 01:35:01 Windows/32
> + 2019.03.14 18:23:54  BINKP 1-S: ADR 21:1/100@fsxnet 21:1/3@fsxnet

That is because I switched 21:1/128 over to Mystic at bbs.twisted-balloon.org  
(65.103.12.163) and now BBBS bbs.ouijabrd.net (65.103.12.161) is now 
21:1/128.1. 
I have been polling you from Mystic and can connect to you fine. I had just 
completed 
the actual switch over and was testing the connection. I sent you an email 
regarding 
the switchover so that you could make any necessary adjustments on your end.

The polling loop situation currently exists between 1:282/1031 BBBS and 1:14/5 
Mystic.
And in the past did exist between 21:1/128 BBBS and you 21:1/100 Mystic. That 
is 
where I think the confusion came from. I did notice that the problem happens 
when 
BBBS polls Mystic but doesn't seem to happen if Mystic polls BBBS. I suspect
that the 
problem stems from either the way BBBS is detecting a completed connection or 
the way 
that Mystic is expressing a completed connection.

Jeff

--- BBBS/Li6 v4.10 Toy-4