Page 1 of 2 12 LastLast
Results 1 to 15 of 25

Thread: 10/21 patch

  1. #1
    Administrator
    Join Date
    Oct 2019
    Posts
    497

    10/21 patch

    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.

  2. #2
    Registered User
    Join Date
    Oct 2020
    Posts
    1

    Re: 10/21 patch

    Not working for me :/ anyone have the updated offsets ?

  3. #3
    Registered User
    Join Date
    Jul 2020
    Posts
    13

    Re: 10/21 patch

    Not working here either

  4. #4
    Administrator
    Join Date
    Oct 2019
    Posts
    497

    Re: 10/21 patch

    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.

  5. #5
    Developer
    Join Date
    Oct 2010
    Posts
    214

    Re: 10/21 patch

    Seems to work fine for me, no changes necessary. Maybe they're closing in?

  6. #6
    Registered User
    Join Date
    Jul 2020
    Posts
    13

    Re: 10/21 patch

    Newby, can you post what is working for you?

  7. #7
    Developer
    Join Date
    Oct 2010
    Posts
    214

    Re: 10/21 patch

    Not sure what you want me to post, my source tree matches whats in the repo.

  8. #8
    Did you SEQ today? BlueAdept's Avatar
    Join Date
    Dec 2001
    Posts
    2,005

    Re: 10/21 patch

    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
    Last edited by BlueAdept; 10-21-2020 at 04:19 PM.
    Filters for ShowEQ can now be found here. filters-5xx-06-20-05.tar.gz

    ShowEQ file section is here. https://sourceforge.net/project/show...roup_id=10131#

    Famous Quotes:

    Ratt: WTF you talkin' about BA? (Ok.. that sounds like a bad combo of Diffrent Strokes and A-Team)

    Razzle: I showeq my wife

  9. #9
    Administrator
    Join Date
    Oct 2019
    Posts
    497

    Re: 10/21 patch

    Nice catch! I can confirm that specifying the IP seems to work around the problem, at least for me.

  10. #10
    Developer
    Join Date
    Oct 2010
    Posts
    214

    Re: 10/21 patch

    Yeah, I have my IP specified in my showeq.xml file.

  11. #11
    Registered User
    Join Date
    Oct 2020
    Posts
    2

    Re: 10/21 patch

    Where am I supposed to be specifying the IP? Not locating a "showeq.xml" file in the directory. Sorry, new here.

  12. #12
    Administrator
    Join Date
    Oct 2019
    Posts
    497

    Re: 10/21 patch

    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.
    Last edited by cn187; 10-21-2020 at 05:15 PM.

  13. #13
    Registered User
    Join Date
    Oct 2020
    Posts
    2

    Re: 10/21 patch

    This makes sense. Tyvm...

  14. #14
    Did you SEQ today? BlueAdept's Avatar
    Join Date
    Dec 2001
    Posts
    2,005

    Re: 10/21 patch

    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
    Filters for ShowEQ can now be found here. filters-5xx-06-20-05.tar.gz

    ShowEQ file section is here. https://sourceforge.net/project/show...roup_id=10131#

    Famous Quotes:

    Ratt: WTF you talkin' about BA? (Ok.. that sounds like a bad combo of Diffrent Strokes and A-Team)

    Razzle: I showeq my wife

  15. #15
    Developer
    Join Date
    Oct 2010
    Posts
    214

    Re: 10/21 patch

    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.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

You may post new threads
You may post replies
You may post attachments
You may edit your posts
HTML code is Off
vB code is On
Smilies are On
[IMG] code is On