vyzo

It's not that simple. The AutoNATService peer uses a background host to dial back, so the peer ID is unknown. The best we can do is correlate the IP address,...

I think we should stick to a single transport for this, pipes look nice and simple.

What else can we do? We cant let the other side ping ad infinum and squat the resources. What do you recommend doing about logging?

want to take it over and mold it to suit your taste?

yeah, lets do it; base -vs- basic is confusing. Lets also have a blank profile to replace the blankhost.

or is that not useful?

I believ we want identify in the base host, the autonat dialer wont work without it.

actually maybe you are right, it doesnt really care.

cc myself

Can you try running with https://github.com/libp2p/go-libp2p-connmgr/pull/43 ? It has fixed our connection manager woes in the test relay, except the duplicate connections issue which is being worked on.