Page 1 of 1

humongous packet 0x4F

Posted: Sun Apr 15, 2018 9:25 am
by atreiu
last 2d client (7.0.63.2) on verifying account stage, before server list, send strange 0x4f packet. i don;t know mb some last clients do the same i just start make 2d working with my server.
Client#1: Humongous packet (length 63959) type 0x4F, 62 bytes (IP: 127.0.0.1, Ac
count: None)
0000 4f f9 d7 cb c5 c7 ab aa 2a ea 0a fa 02 fe 80 3f O....... *......?
0010 60 cf 18 f3 06 fc 01 ff 80 3f 60 4f 58 d3 16 95 `....... .?`OX...
0020 61 90 e8 d1 20 ef 88 bb a2 2e e8 0b fa 82 3e 60 a... ... ......>`
0030 cf 98 b3 a6 ac a9 ab aa 2a ea 0a fa 02 a3 ........ *.......
here cuple couple questions.
1. why 0x4f? this is Overall Light Level 2 bytes packet i've checked RUNUO there same
2. now POL don't working with <3 bytes packets. why but no matter

Code: Select all

if ( length < 3 )
  {
    report_weird_packet( client, "Too-short message" );
    return false;
  }
3. client stuck on verifying account and seems like POL don;t sent proper answer. what answer should be? =(

I sniff this client on server where all ok and there client send "4F00" like should be.

4. paket lenght 63959 bigger than client->buffer == 2560. This from POL comments - "This packet is most likely a client error, because the buffer should be big enough to handle anything sent by the known clients.". Maybe this is crush/error? But client not crached i can back and try to login again.

At this moment i';ve tried change UOFeatureEnable and hook this packets but no succes in login scene.

Anybody know, was is das?

Re: humongous packet 0x4F

Posted: Sun Apr 15, 2018 9:37 am
by Turley
Are you sure that you decrypted the client or used the correct cryptkey in your uoclient.cfg?

Re: humongous packet 0x4F

Posted: Sun Apr 15, 2018 9:52 am
by atreiu
thanks Tyrley! was crypted

Re: humongous packet 0x4F

Posted: Tue Apr 17, 2018 3:00 pm
by Nando
Just to clarify: the "length < 3" condition is only for variable-length packets. This makes sense because you need at least 3 bytes in those cases: packet id (1 byte) + size (2 bytes). ;)