Unable to connect via P2P even both public IPv6 are available

[jjqtony]

Describe the problem
I am pretty sure that both of my peers have public IPv6 address, however I fail to connect two peers via P2P.

Peer 1: ubunt Linux (with public IPv6)
Peer 2: Alpine linux (with public IPv6)

To Reproduce

Steps to reproduce the behavior:

Start Netbird service on two peers (both of them have public IPv6 address, their ping latency less than 40ms)
Run netbird status -d

Expected behavior

Status: Connected
-- detail --
Connection type: P2P
Direct: true

Are you using NetBird Cloud?

Yes

NetBird version

0.29.2

NetBird status -dA output:
netbird.cloud:
NetBird IP: 100.83.111.47
Status: Connected
-- detail --
Connection type: Relayed
ICE candidate (Local/Remote): relay/prflx
ICE candidate endpoints (Local/Remote): 198.51.100.0:46600/198.51.100.1:32751

[jclds139]

I'm running into the problem right now as well. I think (not absolutely certain), that it's related to client/internal/peer/worker_ice.go@153.
When I run the client manually, I get error in the form of
2024-12-12T16:59:14-05:00 WARN [peer: *****************=] client/internal/peer/worker_ice.go:269: got an error while resolving the udp address, err: address ****:****:****:****:****:****:****:****:51820: too many colons in address. which is triggering from line 267 which resolves the addresses. The go docs say If the host is a literal IPv6 address it must be enclosed in square brackets, as in "[2001:db8::1]:80" or "[fe80::1%zone]:80" (https://pkg.go.dev/net#Dial), so I'm guessing that up at line 153 there needs to be a check for IPv6 addresses so that the string is formatted correctly when loaded from the ice CandidatePair.

If so, that means this issue and #2327 are related.