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.

---