Prior to MapTool 1.15.0, starting a UPnP server would scan only a few possible interfaces while searching for UPnP-enabled gateways. Since 1.15.0, specifically on Windows, a dozen or more interfaces are checked. Since each one takes a few seconds, starting a server with UPnP can now take upwards of a minute.
To Reproduce
On Windows, open MapTool 1.15.0
Go to File > Start Server
Make sure the Use UPnP option is selected.
Click OK
Wait forever while dialogs show different interfaces being tried.
Expected Behaviour
Only "meaningful" interfaces are scanned for gateways, i.e., interfaces with an associated IP address and which can reasonable be expected to be associated with a UPnP-enabled gateway.
For this bug I'll focus on reducing the number of interfaces so UPnP performance is similar to 1.14. There are other possibilities for improving the UPnP experience, but we can open other issues for those.
Describe the Bug
Prior to MapTool 1.15.0, starting a UPnP server would scan only a few possible interfaces while searching for UPnP-enabled gateways. Since 1.15.0, specifically on Windows, a dozen or more interfaces are checked. Since each one takes a few seconds, starting a server with UPnP can now take upwards of a minute.
To Reproduce
Expected Behaviour
Only "meaningful" interfaces are scanned for gateways, i.e., interfaces with an associated IP address and which can reasonable be expected to be associated with a UPnP-enabled gateway.
Screenshots
No response
MapTool Info
1.15.0
Desktop
Windows 11
Additional Context
No response