1. Forum
  2. fsxNet
  3. FSX MYS

  • Dupe IP issues

    From Avon@21:1/101 to g00r00 on Tue Jan 1 09:21:12 2019
    I've noticed today that an internal poll to 1/100 from another system (5/100) on the same internal IP has seemingly not cleared correctly from 1/100 at the end of the poll.

    5/100 poll looks like this

    Jan 01 08:54:09 S: NUL SYS fsxHUB Omicron [NET5]
    Jan 01 08:54:09 S: NUL ZYZ Avon
    Jan 01 08:54:09 S: NUL TIME Tue, 01 Jan 2019 08:54:09 1300
    Jan 01 08:54:09 S: NUL VER Mystic/1.12A42 binkp/1.0
    Jan 01 08:54:09 S: NUL BUILD 2018/12/30 23:40:08 Windows/32
    Jan 01 08:54:09 S: ADR 21:5/100@fsxnet
    Jan 01 08:54:09 R: NUL OPT TLS CRAM-MD5-24d08de7873d6150a71d2259a86326bf
    Jan 01 08:54:09 R: NUL SYS fsxHUB Risa [NET1]
    Jan 01 08:54:09 System fsxHUB Risa [NET1]
    Jan 01 08:54:09 R: NUL ZYZ Avon
    Jan 01 08:54:09 SysOp Avon
    Jan 01 08:54:09 R: NUL TIME Tue, 01 Jan 2019 08:54:09 1300
    Jan 01 08:54:09 Info TIME Tue, 01 Jan 2019 08:54:09 1300
    Jan 01 08:54:09 R: NUL VER Mystic/1.12A42 binkp/1.0
    Jan 01 08:54:09 Mailer Mystic/1.12A42 binkp/1.0
    Jan 01 08:54:09 R: NUL BUILD 2018/12/30 23:39:45 Windows/32
    Jan 01 08:54:09 Info BUILD 2018/12/30 23:39:45 Windows/32
    Jan 01 08:54:09 R: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
    Jan 01 08:54:10 S: NUL TLS
    Jan 01 08:54:10 R: NUL TLS
    Jan 01 08:54:10 Activating SSL session
    Jan 01 08:54:41 Error -25 (Timeout)
    Jan 01 08:54:41 Error activating session
    Jan 01 08:54:41 Failed to activate SSL
    Jan 01 08:54:41 Authorization failed

    and the 1/100 server shows the following (I added the xxx to redact the IP)

    ³ BINKP Unknown 192.168.1.xxx

    Logging at 1/100 shows

    + 2019.01.01 08:54:09 BINKP 1-HostName AGENCY
    + 2019.01.01 08:54:09 BINKP 1-S: NUL OPT TLS CRAM-MD5-24d08de7873d6150a71d2259a86326bf
    + 2019.01.01 08:54:09 BINKP 1-R: NUL SYS fsxHUB Omicron [NET5]
    + 2019.01.01 08:54:09 BINKP 1-System fsxHUB Omicron [NET5]
    + 2019.01.01 08:54:09 BINKP 1-S: NUL SYS fsxHUB Risa [NET1]
    + 2019.01.01 08:54:09 BINKP 1-S: NUL ZYZ Avon
    + 2019.01.01 08:54:09 BINKP 1-S: NUL TIME Tue, 01 Jan 2019 08:54:09 1300
    + 2019.01.01 08:54:09 BINKP 1-S: NUL VER Mystic/1.12A42 binkp/1.0
    + 2019.01.01 08:54:09 BINKP 1-S: NUL BUILD 2018/12/30 23:39:45 Windows/32
    + 2019.01.01 08:54:09 BINKP 1-S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
    + 2019.01.01 08:54:09 BINKP 1-R: NUL ZYZ Avon
    + 2019.01.01 08:54:09 BINKP 1-SysOp Avon
    + 2019.01.01 08:54:09 BINKP 1-R: NUL TIME Tue, 01 Jan 2019 08:54:09 1300
    + 2019.01.01 08:54:09 BINKP 1-Info TIME Tue, 01 Jan 2019 08:54:09 1300
    + 2019.01.01 08:54:09 BINKP 1-R: NUL VER Mystic/1.12A42 binkp/1.0
    + 2019.01.01 08:54:09 BINKP 1-Mailer Mystic/1.12A42 binkp/1.0
    + 2019.01.01 08:54:09 BINKP 1-R: NUL BUILD 2018/12/30 23:40:08 Windows/32
    + 2019.01.01 08:54:09 BINKP 1-Info BUILD 2018/12/30 23:40:08 Windows/32
    + 2019.01.01 08:54:09 BINKP 1-R: ADR 21:5/100@fsxnet
    + 2019.01.01 08:54:10 BINKP 1-R: NUL TLS
    + 2019.01.01 08:54:10 BINKP 1-S: NUL TLS
    + 2019.01.01 08:54:10 BINKP 1-Activating SSL session

    So now other polls to 1/100 internally over the LAN such as those from Agency BBS fail as the BinkP server has failed to clear the borked BinkP connection..so I'm getting dupe IP alerts.

    + 2019.01.01 08:59:27 BINKP > Connect on slot 3/25 (192.168.1.xxx)
    + 2019.01.01 08:59:27 BINKP 3-HostName AGENCY
    + 2019.01.01 08:59:27 BINKP 3-Refused (Duplicate IP)

    and

    + 2019.01.01 09:00:04 BINKP > Connect on slot 3/25 (192.168.1.xxx)
    + 2019.01.01 09:00:04 BINKP 3-HostName AGENCY
    + 2019.01.01 09:00:04 BINKP 3-Refused (Duplicate IP)
    + 2019.01.01 09:00:05 BINKP > Connect on slot 3/25 (66.56.183.126)
    + 2019.01.01 09:00:05 BINKP 3-HostName cpe-66-56-183-126.sc.res.rr.com
    + 2019.01.01 09:00:05 BINKP 3-Country United States of America (US)
    + 2019.01.01 09:00:05 BINKP > Connect on slot 4/25 (192.168.1.xxx)
    + 2019.01.01 09:00:05 BINKP 4-HostName AGENCY
    + 2019.01.01 09:00:05 BINKP 4-Refused (Duplicate IP)

    Only picked this up as messages I could tell we're not flowing so I went looking :)

    As I look at the 1/100 server I see three entries that *may* also be similar lockups?

    BINKP Unknown 192.168.1.xxx
    BINKP Unknown 2601:08C0:4280:1C81:020C:29F BINKP Unknown 108.36.95.87

    Best, Paul


    ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄ Eùavon@bbs.nz ÄÄÄÄÄÄ Wùbbs.nz ÄÄÄ ÄÄÄÄ Kùkeybase.io/avon ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

    --- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)