View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
---|---|---|---|---|---|---|---|---|---|
0001894 | OpenClonk | Engine - Network | public | 2017-02-25 19:47 | 2017-02-26 22:39 | ||||
Reporter | Luchs | ||||||||
Assigned To | Luchs | ||||||||
Priority | normal | Severity | major | Reproducibility | sometimes | ||||
Status | resolved | Resolution | fixed | ||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0001894: Initial connection may time out if the host has lots of link-local addresses | ||||||||
Description | Possible fixes: - Try initial connections faster (i.e. in parallel) - Don't send link-local IPv6 addresses to the masterserver if the interface doesn't have a global address as well. Multicast discovery should still allow finding games from networks without internet connectivity. - Sort addresses discovered by the masterserver/the netpuncher in front. May lead to sub-optimal address selection (like IPv4-over-DS-Lite instead of native IPv6). - Somehow prioritize address choices. Prefer connecting to IPv6 addresses if both partners have public IPv6 addresses listed. Sort IPv6 addresses by longest matching prefix. Use IPv4 as fallback. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files |
|
![]() |
|
Luchs (administrator) 2017-02-26 22:39 |
I added some prioritization now. However, the main issue was that the league didn't add its addresses properly (didn't update AddressCount), so those addresses were always ignored. |