- ServUO Version
- Publish Unknown
- Ultima Expansion
- None
If you run ServUO locally and use the ClassicUO client, you'll probably notice your latency is abnormal for a loopback address. Anything other than 0 is abnormal for a loopback address.
This happens because the 0xa8 packet puts the IP address in as 1.0.0.127. Regardless of whether or not the ClassicUO client should rewrite that IP as 127.0.0.1 or not, it is hitting it as 1.0.0.127, effectively creating a DDoS for any mirror IP addresses that are valid.
Because ServUO is its login server, pinging the server to see if it's up is meaningless since if you couldn't ping it, you couldn't get to the server list. I would suggest the AccountLoginAck packet be rewritten to put 127.127.127.127 as the pinged address. It will always be the loopback, even if the bytes are read in the incorrect order.
This happens because the 0xa8 packet puts the IP address in as 1.0.0.127. Regardless of whether or not the ClassicUO client should rewrite that IP as 127.0.0.1 or not, it is hitting it as 1.0.0.127, effectively creating a DDoS for any mirror IP addresses that are valid.
Because ServUO is its login server, pinging the server to see if it's up is meaningless since if you couldn't ping it, you couldn't get to the server list. I would suggest the AccountLoginAck packet be rewritten to put 127.127.127.127 as the pinged address. It will always be the loopback, even if the bytes are read in the incorrect order.
