owoTrack connections are not tracked properly by TrackersUDPServer

[ButterscotchV]

This is an issue between owoTrack reverting to an older protocol without a MAC address causing issues with connection tracking. This can be resolved in the server code.

There is also the issue of the "multi-server" code (new tracker popup) blocking owoTrack connecting, causing it to revert and then it never actually saves properly with the MAC. This can cause tracker duplication, failed connections, and odd tracker timeouts.

There is more to this issue but I no longer remember the details, so I will update this at a later date.