Binding to a specific interface to stabilize QUIC connectivity

[arrogantrabbit]

This appears to be a regression in 1.86.1. See this comment for proof:

QUIC misconfiguration in v1.86.1

@Alexey, yep, I’m the doofus, when I downgraded the node, my auto-updater happened to kick in shortly after and updated it back to the current one, and I did not notice. Now I confirm it’s definitely a regression in 1.86.1. Her is what I did: removed the IP in config, and downgraded to 1.84.2: [Screenshot 2023-08-26 at 1.07.38 PM] Then I upgraded to 1.86.1 [Screenshot 2023-08-26 at 1.09.38 PM] Then back to 1.84.2 – OK, back to 1.86.1 – Misconfigured (did not save screenshot) Th…

and this comment for potential culprit:

QUIC misconfiguration in v1.86.1

I did not analyze all code changes, but just looking at the difference in modules linked between “good” and “bad” releases, this catches the eye (see go.mod): golang.org/x/net, which provides socket support among other networky thing, was updated from v0.9.0 to v0.10.0 github.com/quic-go/quic-go, which, well, does the obviously relevant to the present discussion thing, was updated from v0.32.0 to v0.37.4! Related, github.com/quic-go/qtls-go1-20 was updated from v0.1.0 to v0.3.1!! That’s quite…