WIP: Make the uPNP device search more reliable for LDN #641
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "upnp-fix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes where uPNP was failing due to it attempting to use the wrong network device.
It will now attempt to use each network device in turn until it succeeds.
This also adds more debug output to help figure out the cause of uPNP issues.
Needs testing from people who get the "Failed to open a port with UPnP for P2P connection." error.
Should probably add a uh, ahem
Fixes #639
Oh, nvm... You didn't add it @w@;
I don't know if it fixes it, that could be a separate issue as firewall rules weren't making a difference for me
Download the artifacts for this pull request:
Only for Developers
I mean, it took Mr. Food ( a person on discord) from failing to UPnP 6 times in a row, to just 2 fails, 1 working... Which was the same result for me. So I feel like this could be quite 50/50 lol-
Closing this for now as the fix hasn't worked for anyone other than me, @FluffyOMC found this issue in OpenNAT as the probable root cause
https://github.com/lontivero/Open.NAT/issues/100
for now you can disable IPv6 on your network interface (possibly also on your router?) as a workaround.
For now, we can either go to a different dependency for TCP, or just finish making everything UDP.
Pull request closed