It doesn't look like opcodes/structs changed, so things should still be working. Please post if you run into issues, as there could be changes to things I don't usually check.
Printable View
It doesn't look like opcodes/structs changed, so things should still be working. Please post if you run into issues, as there could be changes to things I don't usually check.
Not working for me :/ anyone have the updated offsets ?
Not working here either
OK, I've confirmed the issue. The opcodes and (usual) structs didn't change, but there was another change in the stream that's affecting decoding. I'll start looking into it.
Seems to work fine for me, no changes necessary. Maybe they're closing in?
Newby, can you post what is working for you?
Not sure what you want me to post, my source tree matches whats in the repo.
I think I found what it is. It doesnt detect the Next Client seen and by what ETH. I had to manually put in the IP address for it to see the packets. It does seem to work but I think some opcode has changed.
I saw a lot of this until I specified my IP
Warning: EQPacket: Unhandled net opcode 4d00, stream client-zone, size 261
Warning: EQPacket: Unhandled net opcode 0000, stream zone-client, size 237
Warning: EQPacket: Unhandled net opcode 4d00, stream client-zone, size 261
Warning: EQPacket: Unhandled net opcode 0000, stream zone-client, size 237
Warning: EQPacket: Unhandled net opcode 4d00, stream client-zone, size 261
Warning: EQPacket: Unhandled net opcode 4d00, stream client-zone, size 261
Warning: EQPacket: Unhandled net opcode 4d00, stream client-zone, size 261
Warning: EQPacket: Unhandled net opcode 4d00, stream client-zone, size 261
Warning: EQPacket: Unhandled net opcode 4d00, stream client-zone, size 261
Warning: EQPacket: Unhandled net opcode 4d00, stream client-zone, size 261
Warning: EQPacket: Unhandled net opcode 4d00, stream client-zone, size 261
Warning: EQPacket: Unhandled net opcode 4d00, stream client-zone, size 261
Nice catch! I can confirm that specifying the IP seems to work around the problem, at least for me.
Yeah, I have my IP specified in my showeq.xml file.
Where am I supposed to be specifying the IP? Not locating a "showeq.xml" file in the directory. Sorry, new here. :)
On further reflection, some of the people reporting issues may have been MySEQ users (one mentioned offsets, and the post history of the other indicates MySEQ)... Someone posted the new offsets here, so I moved that to the other forum.
For what it's worth, I've been needing to manually select "Monitor Next EQ Client Seen" for quite a while, so I figure this is just an extension of whatever has been causing that.
I've been meaning to dig into the SEQ networking code to learn more about it and the EQ protocol, so maybe this will give me a good excuse to actually do it... Fortunately, since specifying the IP seems to work around it, everyone's not dead in the water for however long it takes me to figure it out.
This makes sense. Tyvm...
I have done further testing. It will not work without setting the IP. I turned on logging but don't know how to figure out what it is looking for.
From the Global log:
Oct 21 2020 19:08:53:085 [10.10.70.XXX:54915->10.10.70.255:54915] [Size: 263]
[OPCode: 0x4d00]
000 | 00 4d 53 49 00 00 00 00 70 dc c4 a6 89 02 00 00 | .MSI....p.......
016 | a0 b6 7f 93 fb 00 00 00 00 00 00 00 00 00 00 00 | ................
032 | 33 27 00 00 00 00 00 00 60 dc c4 a6 89 02 00 00 | 3'......`.......
048 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
064 | 00 00 00 00 00 00 00 00 7c 6a b9 6a 00 00 00 00 | ........|j.j....
080 | c8 a3 16 6b 00 00 00 00 d9 ba 7f 93 fb 00 00 00 | ...k............
096 | 00 00 00 00 00 00 00 00 10 5f 5d a6 89 02 00 00 | ........._].....
112 | 24 b7 7f 93 fb 00 00 00 40 b7 7f 93 fb 00 00 00 | $.......@.......
128 | 28 f1 2c 7b FF FF FF FF 39 61 39 38 2d 32 37 66 | (.,{12345678-27f
144 | 36 2d 34 65 32 62 2d 39 66 63 35 2d 33 38 35 66 | 6-4e2b-9fc5-1234
160 | FF FF FF FF FF FF FF FF 7d 00 00 00 00 00 00 00 | 12345678}.......
176 | 01 00 00 00 fb 00 00 00 20 b7 7f 93 fb 00 00 00 | ........ .......
192 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
208 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
224 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
240 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
256 | 00 00 00 8e a8 a3 30 | ......0
Oct 21 2020 19:08:53:274 [10.10.70.xxx:32978->XXX.255.255.XXX:1900] [Size: 101]
[BAD CRC (f28c != d0a)! Sessions crossed or unitialized or non-EQ packet! ]
[SessionKey: 0]
It seems to be getting the right IP but I think the paket is bigger than it is supposed to be. The struct may need to be corrected.
That is the same packet it is complaining about in the main window when you dont specify an IP.
Warning: EQPacket: Unhandled net opcode 4d00, stream client-zone, size 261
That's actually a different protocol. Most of EQ's stuff is in the zone log. Global is an entirely different protocol that's used to set up the zone protocols, as near as I can figure.