![]() ![]() So I was about to open a bug report, annoyed that the new version would introduce a bug like that. I had used the trace for so many trainings that I was sure what Wireshark should have displayed, but it didn’t. They were slightly different from what I expected, and I knew they were just wrong. It happened to me during a Wireshark class a couple of years ago (using the then brand new version 0.99.6) that suddenly my delta time column showed strange values when I applied a filter. The reason for reading the release notes is simple: sometimes, things that you were used to behave in a certain way may have been changed by the developers. ![]() ![]() Okay, before I get to the TCP expert thing, let’s see why release notes are important. The second thing to do should be to read the release notes.Nobody seems to do it, but everybody should. Wireshark 1.12 has just arrived, and of course the first thing to do is to download and install the new version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |