michael1414 wrote:1) Could be added option to search specific opcode or packet names from all of the files ? For example if I have 137 plog files with packets and some specific packets are only in files: 1.plog, 20.plog, 45.plog. That could be grid with file names only and nothing more for now.
Since obviously all the packet logs you have were made by NP 0.8, I will not cover additional steps required when dealing with packet logs created by old versions of the tool.
For each protocol you have packet logs of (currently, they all should be 606, if you were testing on NA)
1. Open the packet display configuration:
2. Select packet(s) you want to search for:
3. Open the file selection dialog and tick 'Contains displayable packets':
If you have already navigated to a specific subdirectory where packet log files reside, you might need to wait for a second or so; otherwise files will be filtered out as you enter a directory. While filtering, only the packet log header is being read, so it will not take long nor will it cause heavy I/O (even if you have several GB of logs in a directory).
A few points worth noting:
1. By default, packet display configurations have all their packets selected. So if you have logs recorded with different protocols in the same directory, and have only set a packet display configuration for a single protocol, selecting 'Contains displayable packets' will still show all files that use a different protocol. You can use the date in the filename to distinguish which packet logs you should ignore in this case.
2. You can force NetPro to load a specific packet display config on startup automatically by naming it [protocol number].pdc and exporting to the default directory.
3. Selecting '???/Unknown' packet will cause you to see any packet logs that have packets with opcodes that are missing in a specific protocol's opcode_mapping.xml file. You cannot filter by concrete unknown opcodes.
michael1414 wrote:2) Could be option to actual packets synchronization ? For example if will be new chronicle and someone will be know bytes what means could be send to server and any of using this sniffer could be have option to sync packet files in new files are on server side.
I guess it would be easiest to just make a git repository for that. The question is, who will maintain it?
The guessing game is easiest when you are familiar (that is, spent some time) with newly added features. And new features sometimes require not only a super rich lvl 100 char (possible via NC-endorsed RWT, such as converting EUR to 2b worth brooches), but two clans of lvl 100 chars, where one owns a castle and a physical CH, while the other owns a fort and a residential CH, etc.
In any case, I could easily add a configuration option that would allow to load definitions from a specific directory (essentially, from that global public repository). But we'd need someone [a team, basically] who is interested in finding out each and every single field of each new/updated packet. As you can see, newest packets are far from perfect, having unk/0/1 as field descriptions. This is really bad, because structure can be easily deduced with little time investment; the meaning of each field is the only thing that matters.
In short: syncing files should be delegated to software that specializes in that, as it provides merging and easy conflict resolution capabilities. In fact, if a global definition repository existed, you could just symlink ./config/packets to your local copy.
If anyone is interested in maintaining such a repository, contact me or write in this thread – it can be created.