2022-01-01 22:47:35 +0000 | commented answer | invalid json request to tshark thanks for working on it. I seem to find other issues like a simple status is taken into account but then displays an er |
2021-12-31 22:02:39 +0000 | commented answer | invalid json request to tshark I used cat contrib/load-pcap.json | tr -d '\n' instead. I found another issue: the order of parameters in the json file |
2021-12-31 16:47:14 +0000 | marked best answer | invalid json request to tshark I've upgraded wireshark 3.4 -> 3.6 and the protocol for sharkd has changed.
I am doing I can't find how it is invalid. for the following info.json: I've got a similar issue with the following json NB: the doc at https://wiki.wireshark.org/Developmen... seems out of date |
2021-12-31 16:47:14 +0000 | received badge | ● Scholar (source) |
2021-12-31 16:29:39 +0000 | commented question | invalid json request to tshark thanks for trying. You should try my instructions with 3.6 though as the protocol changed, "req" is the old protocol. |
2021-12-31 16:28:48 +0000 | commented question | invalid json request to tshark the protocol changed in 3.6, "req" is the old protocol. |
2021-12-31 15:51:14 +0000 | commented question | invalid json request to tshark thanks for the link, looks like it is the same outdated documentation. I dont mind because I tend to look at the source |
2021-12-31 11:29:01 +0000 | asked a question | invalid json request to tshark invalid json request to tshark I've upgraded wireshark 3.4 -> 3.6 and the protocol for sharkd has changed. I am doin |