Strange networking issue possibly regarding Windows 10

[AdamN]

I've updated my test builds on my signature to handle "incorrect port" (now written as "unknown port") issue better by keeping track the new port for further communication.
However, keeping track of the port will only work if the player were able to receive a data on the "correct" port in order to get the sender port (which might be re-mapped), which mean the player who supposed to receive the data for the first time must not have their port being re-mapped.

Edit: You can also get the artifacts from this PR https://github.com/hrydgard/ppsspp/pull/14870

Please this those test builds to see whether they're better or not, because i'm having difficulty trying to reproduce the "incorrect port" issue on my end.
Please also test the "UseOriginalPort" thing with this, in case the issue why it didn't work before was because the port were different and being ignored by AdhocMatching.

I'm planning to do the same for GameMode (ie. keeping track the port) which potentially have similar issue to AdhocMatching, but i never tried to show a warning on screen, thus we never saw reports about it on GameMode.

PS: Players who had the warning shown on their screen are not the one who had their port being re-mapped, since they're able to receive data on the "correct" port.