If I try to add ipv6 address to target (or host) address, it needs to be in brackets in order to boundary controller to accept the address. For example: [abcd:1342:f5:1204::1d]
When I try to connect the target, the worker seems to get somehow confused about the brackets (somewhere they got duplicated?): “[[abcd:1342:f5:1204::1d]]:22”
Here’s the error from worker:
{"id":"0RsDHJav0B","source":"https://hashicorp.com/boundary/tstwrker/worker","specversion":"1.0","type":"error","data":{"error":"proxy.directDialer: unknown, unknown: error #0: dial tcp: address [[abcd:1342:f5:1204::1d]]:22: missing port in address","error_fields":{"Code":0,"Msg":"","Op":"proxy.directDialer","Wrapped":{"Op":"dial","Net":"tcp","Source":null,"Addr":null,"Err":{"Err":"missing port in address","Addr":"[[abcd:1342:f5:1204::1d]]:22"}}},"id":"e_9nkxTLSmAO","version":"v0.1","op":"worker.(Worker).handleProxy"},"datacontentype":"application/cloudevents","time":"2025-01-03T12:44:21.344391414+01:00"}
But if I use DNS hostname (AAAA-records) as target address (instead of putting ipv6 address directly as target address), then it just works.
Is there a another syntax to enter ipv6 addresses as “target address” or is that a bug?
This could be similar to Unable to specify listen port with any IPv6 address · Issue #701 · hashicorp/boundary · GitHub and Fix IPv6 binding by jefferai · Pull Request #703 · hashicorp/boundary · GitHub