2022-11-14 08:22:35 +0000 | commented answer | "ACKed segment that wasn't captured", but also "This is an ACK to the segment in frame: nnn". Many thanks, Guy. The problem appears to start after a break in a capture file. All packets after the break appear to |
2022-11-10 15:13:43 +0000 | edited question | "ACKed segment that wasn't captured", but also "This is an ACK to the segment in frame: nnn". "ACKed segment that wasn't captured", but also "This is an ACK to the segment in frame: nnn". On Wireshark Version 4.0.1 |
2022-11-10 15:03:53 +0000 | asked a question | "ACKed segment that wasn't captured", but also "This is an ACK to the segment in frame: nnn". "ACKed segment that wasn't captured", but also "This is an ACK to the segment in frame: nnn". On Wireshark Version 4.0.1 |
2022-10-07 13:49:49 +0000 | received badge | ● Editor (source) |
2022-10-07 13:49:49 +0000 | edited question | Filtering text before adding to tree Filtering text before adding to tree I'm trying to filter some ebcdic text before translating and adding to an item. At |
2022-10-07 13:12:37 +0000 | asked a question | Filtering text before adding to tree Filtering text before adding to tree I'm trying to filter some ebcdic text before translating and adding to an item. At |
2022-10-07 12:33:47 +0000 | marked best answer | LUA script add item to end of data gives stack overflow I'm writing my first dissector, so have a noob question, I'm afraid. How do I add an item from a fixed offset to the end of the data. According to the docs -1 is mean to do this, as in: but when I try that, or range(), I get: |
2022-10-07 12:33:47 +0000 | received badge | ● Scholar (source) |
2022-10-06 17:02:23 +0000 | commented question | LUA script add item to end of data gives stack overflow Well, that's odd. I'm sure I'd tried that too, but retesting proves me a liar. Many thanks! i |
2022-10-06 15:07:48 +0000 | asked a question | LUA script add item to end of data gives stack overflow LUA script add item to end of data gives stack overflow I'm writing my first dissector, so have a noob question, I'm afr |
2022-10-05 06:00:36 +0000 | commented answer | Command line packet dissection? Reassembly could well be involved: the message looks like it's been split into multiple datagrams. Both wireshark and t |
2022-10-04 11:40:59 +0000 | commented answer | Command line packet dissection? Regrettably, the same. |
2022-10-04 09:44:24 +0000 | commented answer | Command line packet dissection? Many thanks for that. There seem to be a few little quirks but I think I've got most of them sorted noe by adding in my |
2022-09-30 13:47:51 +0000 | asked a question | Command line packet dissection? Command line packet dissection? One of the tasks I use Wireshark for is to convert pcap capture files to csv format for |