SO_REUSEPORT not properly restored

[iangudger]

SO_REUSEPORT is implemented with a middleware endpoint in the transport demuxing path called multiPortEndpoint. It is currently regenerated on restore with a different randomly generated seed. In addition, the endpoints may not be re-registered with it in the same order. This will cause the behavior of SO_REUSEPORT to change across a S/R event in a user visible and incorrect way.

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 30 days.