TID: Mystic BBS 1.12 A48   
   MSGID: 2:201/137 d646945c   
   REPLY: 2:203/2 61f6c9a6   
   TZUTC: 0100   
   Hello Conny!   
      
   On 30 Jan 2022, Conny Enström said the following...   
    CE> I use Binkd 1.1a-99 (Oct 18 2019 19:27:01/Linux), installed from Ubuntu   
    CE> repo. And it seems in your link this is the exact version with this   
    CE> problem, I will see if i can find a up tp date version.   
      
   Yep! Most likely that will solve the problem.   
      
   (I believe the colon and port number were interpreted as part of the hostname   
   in the earlier versions of binkd, leading to this error...)   
      
    CE> tcp        0      1 192.168.1.5:42058       219.89.83.33:* SYN_SENT      
    CE> 8760/binkd: call to   
    CE>    
    CE> Is this something created when the connection is made or something   
    CE> resistant somewhere?   
      
   That was just a check to see what binkd tried to connect to -- in that case,   
   port * = 0 of the remote hub (219.89.83.33), which was not the desired port. =)   
      
   The SYN_SENT status indicates that it has attempted to start the TCP   
   handshake, but has not gotten any further.   
      
   Best regards   
   Bj”rn   
      
   --- Mystic BBS v1.12 A48 2022/01/28 (Linux/64)   
    * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340   
   SEEN-BY: 123/120 131 124/5016 129/305 330 331 153/250 757 7715 154/10   
   SEEN-BY: 201/0 121 137 420 203/0 2 124 218/840 220/70 221/0 1 226/17   
   SEEN-BY: 226/30 227/114 229/110 200 206 307 317 424 426 550 664 700   
   SEEN-BY: 230/0 240/5832 250/5 8 266/512 267/800 280/464 5003 5555   
   SEEN-BY: 282/1038 292/854 8125 298/25 301/1 305/3 310/31 317/3 320/219   
   SEEN-BY: 322/757 341/234 342/200 396/45 423/120 460/58 633/280 712/848   
   SEEN-BY: 770/1 100 340 772/210 220 230 2452/250   
   PATH: 201/137 0 203/0 280/464 770/1 317/3 229/426