| 2023-08-15 15:39:44 +0000 | commented answer | Forcing decode of 'invalid' RTCP and RTP version That's my point, the protocol isn't actually different - it just has a different version number, and it changes the mean |
| 2023-08-14 23:21:09 +0000 | commented question | Forcing decode of 'invalid' RTCP and RTP version Aha! Thank you for that! I'm an embedded systems developer and we're always like 10-15 years behind on development tools |
| 2023-08-14 21:18:24 +0000 | asked a question | Forcing decode of 'invalid' RTCP and RTP version Forcing decode of 'invalid' RTCP and RTP version Hi, I'm working on debugging a new implementation of a semi-proprietar |
| 2019-12-15 00:17:09 +0000 | received badge | ● Famous Question (source) |
| 2019-12-15 00:17:09 +0000 | received badge | ● Notable Question (source) |
| 2019-12-15 00:17:09 +0000 | received badge | ● Popular Question (source) |
| 2018-12-02 20:30:49 +0000 | commented question | Segfault when enabling monitor mode with TL-WN722N v2 I've got a core dump. How do I get a stack trace? gdb says 'no stack'. I ran Wireshark with valgrind -v and it didn't |
| 2018-12-02 19:23:20 +0000 | received badge | ● Rapid Responder (source) |
| 2018-12-02 19:23:20 +0000 | answered a question | Segfault when enabling monitor mode with TL-WN722N v2 Dang it... it was the Atheros chipset I was going for. I think the vendor started shipping V2 without updating the list |
| 2018-12-02 01:48:19 +0000 | asked a question | Segfault when enabling monitor mode with TL-WN722N v2 Segfault when enabling monitor mode with TL-WN722N v2 I bought a TL-WN722N for monitor mode sniffing under Ubuntu since |
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.