pa/eqemu-server
2
0
Fork 0
mirror of https://github.com/EQEmu/Server.git synced 2026-05-16 10:32:22 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated Packet and OpCode Analysis (markdown)

Logan 2019-02-28 14:13:27 -08:00
parent 44fc66eed0
commit a1b76f18dc
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Packet-and-OpCode-Analysis.md

@ -15,6 +15,9 @@ In your capture tool, select to log only UDP protocol traffic. You can further s
Sample filtering rule for Microsoft Network Analyzer to reduce noise:
`UDP and !TCP and !SSDP and !ICMPv6 and !DNS and !LLMNR and !WSDiscovery and !IPv6NoNxt and !IPv6 and *Destination != 10.0.0.255 and *Destination != yourmachineiphere and *Source != 192.168.2.225`
Another approach:
`UDP and (*Source in 69.174.0.0/16 or *Destination in 69.174.0.0/16)`
When I’m setting up for a capture, I initially log the entire login sequence from authentication, through character select, and into the server. That captures a large amount of data that is helpful for identifying the specific patch (the last time the client was patched), the server’s entire list of guilds, character select information, etc. This approach does log your account name and password. If you plan on sharing this capture file, make sure you delete those packets, and the packets that list your character names.
To configure Message Anaylzer to properly export for the extractor, first you need to right click the header column of the preview pane, and go to Add Column... Navigate to TCP->Segment->Payload. Right click and select Add as column. Now, right click a row in the Payload section column, select Display Binary Values As -> Hex. Now, To export the capture in Message Analyzer, go to Session -> Analysis Grid -> Export -> All, in the drop down choose Tab Delimited (*.txt)