hrt/derrandz

I can finally reproduce this bug using the following script: ```go package main import ( "context" "crypto/rand" "fmt" "log" "net" "time" "crypto/tls" "crypto/ed25519" "crypto/x509" "math/big" "slices" "github.com/libp2p/go-libp2p" dht "github.com/libp2p/go-libp2p-kad-dht" "github.com/libp2p/go-libp2p/core/crypto"...

1. Whether it's an error or not, it results in an unclear panic which seems to me like an unhandled case. Passing two identical addresses should maybe be flagged? or...

Not too sure about #3338 but what we are trying to do is what inspired the whole reuse feature, we are implementing the RFC 9484 with raw quic conns and...

Thank you for your response and clarification. I will close this issue with the friendlier error msg PR.

I noticed that supplying listen addresses as `127.0.0.1` results in the transport never starting or listening, until changed to `0.0.0.0`, can you explain why?

hmmmm, what should we do when passed two identical listen addresses? that muxer panic is very ambiguous. maybe we should handle this case? passing two addresses is a user bug...

@MarcoPolo I went with a solution to simply ignore and discard duplicate listen addresses. Wdyt? or shall we return an error on validate?