| 2021-02-19 18:23:44 +0000 | received badge | ● Notable Question (source) |
| 2020-11-20 08:12:19 +0000 | received badge | ● Popular Question (source) |
| 2020-05-28 04:25:17 +0000 | commented answer | Wireshark does not read padding Yes I think it is a Scapy issue. Thanks! |
| 2020-05-27 23:03:24 +0000 | commented answer | Wireshark does not read padding Thank you for your answer. You meant the Total Length field in IP header should include the 14 bytes Ethernet header? Wh |
| 2020-05-27 22:56:12 +0000 | commented answer | Wireshark does not read padding Thanks for you answer. It is the way I create the packet. Although my packet looks the same as your packet "a", after wr |
| 2020-05-27 16:10:22 +0000 | received badge | ● Rapid Responder |
| 2020-05-27 16:10:22 +0000 | answered a question | Wireshark does not read padding https://drive.google.com/file/d/1Vut0he6booE9eiTUqM5jOECJpBG1H7uF/view?usp=sharing Please see the packet #6 in question |
| 2020-05-27 15:29:21 +0000 | received badge | ● Rapid Responder |
| 2020-05-27 15:29:21 +0000 | answered a question | Wireshark does not read padding Yes I did update ip.len which has the correct value 344. Everything looks good to me on Scapy. But Wireshark displays a |
| 2020-05-27 03:45:50 +0000 | asked a question | Wireshark does not read padding Wireshark does not read padding I use Scapy to read packet and apply encryption to payload and write the new packet to a |
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.