MSGID: 2:280/464.47 61436c3a   
   REPLY: 2:5030/1997@fidonet 61435c5d   
   PID: JamNNTPd/Linux 1   
   CHRS: LATIN-1 2   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
   Alexey wrote (2021-09-16):   
      
    AF> Hello Oli!   
      
    AF> On Thu, 16 Sep 2021 at 12:49 +0100, you wrote to All:   
      
    O>>> I also use the literal IPv6 address. I just tried it on another   
    O>>> machine with 64-bit Linux and I cannot reproduce the problem   
    O>>> there. Interesting. Maybe specific to 32-bit (or armv7 /   
    O>>> Raspberry)?   
    Ol>> Correction: the IPv6 over Socks5 problem is the same on the 64-bit   
    Ol>> machine.   
      
    AF> Which probably mean the problem is on Socks5 server side.   
      
   The socks server only receives the first part of the IPv6 address and the port   
   number (fd12:24554).   
      
   This is exactly what binkd tries to do:   
      
    16 Sep 16:55:51 [2645] trying fd12 via socks 127.0.0.1:2080...   
      
   Looks very much like binkd cannot handle IPv6 addresses for socks5   
   connections. Socks server works fine with other software and IPv6.   
      
   ---   
    * Origin: https://www.vox.com/22654167/war-on-terror (2:280/464.47)   
   SEEN-BY: 1/123 14/0 90/1 103/705 105/81 114/709 120/340 123/131 124/5016   
   SEEN-BY: 129/305 153/757 154/10 203/0 221/0 226/30 227/114 229/200   
   SEEN-BY: 229/424 426 550 664 700 1017 240/2100 5138 5411 5824 5832   
   SEEN-BY: 240/5853 6309 249/109 206 307 317 280/464 5003 5555 282/1038   
   SEEN-BY: 292/854 8125 301/1 310/31 320/219 322/757 342/200 396/45   
   SEEN-BY: 423/120 460/58 633/280 712/848 770/1 2432/390 2452/250 2454/119   
   PATH: 280/464 240/5832 229/426