raulk

Will be enabled by https://github.com/libp2p/go-libp2p/issues/526.

@whyrusleeping It's possible that in your second example there was 1 or more dials parked by the limiter due to FD limits being exceeded. Not sure where the tracing kicks...

We now have a dial pacer in the DHT: https://github.com/libp2p/go-libp2p-kad-dht/pull/237.

Risk of not doing this: an attacker could lead us to believe we are public when we aren't, therefore jeopardising inbound connectivity.

@vyzo care to elaborate?

My understanding is that this is easy to achieve. You register a Notifee that ignores all events unless you're undergoing AutoNAT determination. At that point, you track all incoming connections,...

Ah, understood the complexity now. I was sure I was missing something. I agree the IP address is an unreliable heuristic. I wonder if we can have the server open...

One simple way to solve what @vyzo pointed out is for the requesting peer to send a nonce in the request, and have the responding peer return a certificate of...

@Stebalien I'm not following the line of thinking that leads to stalling here. The mechanism proposed here is a strict improvement over the status quo. Just to be clear, the...

@Stebalien > Can't an attacker just tell us the wrong addresses? 1. AutoNAT does not allow us to learn own addresses. 2. AFAIK, that's identify. 3. With AutoNAT we can...