I’m not too sure if this is a bug because the vast majority of software nowadays supports IPv6 so… If I setup a OSC In or Pipe In CHOP and leave the “local address”/“server address” field empty, the socket is only opened for IPv4 as I can see in netstat -an.
If I explicitly specify a local IPv6 address to bind to, it turns out that TD just opens a IPv4 socket without binding it to any address. There’s no warning or anything visible in the CHOP. It took me a long time to debug to figure that the IPv6 is ignored.
In case that IPv6 is not supported at all, there should be at least an error that the binding address is not supported.
What I wanted to accomplish: If you connect an iPad via USB to a Mac, there’s a p2p network established. This can be used to send OSC and other data between the devices. This is extremely useful because it saves a lot of effort for creating a dedicated network in the field. However, this network works only with IPv6.