[Wireshark-bugs] [Bug 14266] In a WiFi capture log, the 11ac “beamformed” and TXOP_PS_NOT_ALLOWED bits are shown as “true” in radiotap and “false” in "802.11 radio"
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14266 --- Comment #18 from Guy Harris--- (In reply to zpchi004 from comment #17) > I export 145 packets out, with the 145th packet being beamformed. > Then values of both TXOP_PS_NOT_ALLOWED and Beamformed are displayed > correctly. OK, so what happens if you export only the offending packet and all the packets *after* that, and read that? -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 14261] Kerberos dissector: kdc-options bits 14 and 16 are backwards
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14261 Michael Mannchanged: What|Removed |Added Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 14261] Kerberos dissector: kdc-options bits 14 and 16 are backwards
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14261 --- Comment #2 from Gerrit Code Review--- Change 24863 merged by Michael Mann: Kerberos: Update and fix KDCOptions and TicketFlags https://code.wireshark.org/review/24863 -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 14266] In a WiFi capture log, the 11ac “beamformed” and TXOP_PS_NOT_ALLOWED bits are shown as “true” in radiotap and “false” in "802.11 radio"
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14266 --- Comment #17 from zpchi...@yahoo.com --- I export 145 packets out, with the 145th packet being beamformed. Then values of both TXOP_PS_NOT_ALLOWED and Beamformed are displayed correctly. The 145th packet shows: a) Radiotap header v0 -> VHT info -> TXOP_PS_NOT_ALLOWED: True b) Radiotap header v0 -> VHT info -> Beamformed: True c) 802.11 radio info -> TXOP_PS_NOT_ALLOWED: True d) 802.11 radio info -> Beamformed: True -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing listArchives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 14261] Kerberos dissector: kdc-options bits 14 and 16 are backwards
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14261 Uli Heilmeierchanged: What|Removed |Added CC||u...@heilmeier.eu Ever confirmed|0 |1 Status|UNCONFIRMED |IN_PROGRESS -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 14261] Kerberos dissector: kdc-options bits 14 and 16 are backwards
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14261 --- Comment #1 from Gerrit Code Review--- Change 24863 had a related patch set uploaded by Uli Heilmeier: Kerberos: Update and fix KDCOptions and TicketFlags https://code.wireshark.org/review/24863 -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 11753] Additional grouping in Expert Information dialog
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11753 --- Comment #3 from Gerrit Code Review--- Change 24859 had a related patch set uploaded by Michael Mann: Add a model to use for Expert Info dialog. https://code.wireshark.org/review/24859 -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 13842] Expert info dialog should have "Collapse All"/"Expand All" options
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13842 --- Comment #2 from Gerrit Code Review--- Change 24859 had a related patch set uploaded by Michael Mann: Add a model to use for Expert Info dialog. https://code.wireshark.org/review/24859 -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 13831] Can't hide expert categories in Expert Information
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13831 --- Comment #2 from Gerrit Code Review--- Change 24859 had a related patch set uploaded by Michael Mann: Add a model to use for Expert Info dialog. https://code.wireshark.org/review/24859 -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 14274] Data field of BGP notification message is not dissected for Open message error/unsupported capability
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14274 Uli Heilmeierchanged: What|Removed |Added Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 10759] Tshark -z io, stat options export to csv format
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10759 Marcos Dionechanged: What|Removed |Added CC||mdi...@grulic.org.ar -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 14278] New: print stats when SIGUSR1 or other signal is received
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14278 Bug ID: 14278 Summary: print stats when SIGUSR1 or other signal is received Product: Wireshark Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: Enhancement Priority: Low Component: TShark Assignee: bugzilla-ad...@wireshark.org Reporter: mdi...@grulic.org.ar Target Milestone: --- Build Information: -- tshark in stats mode (-z) can print stats when the capture is finished. For UDP protocols like RTP, these stats are difficult to calculate in other fashion, so it would be really useful if we could make tshark spit the stats on a regular basis with a signal, dd style: Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying. tshark would need to reset is counters after the stats are calculated, so the next signal just print stats between signals. The equivalent I found so far is (as I remember it, I don't have the script with me right now): while true; do tshark -z rtp,streams -a duration:60 > rtp_stats.log done This bug and 10759 would be very useful for monitoring. -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing listArchives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 14266] In a WiFi capture log, the 11ac “beamformed” and TXOP_PS_NOT_ALLOWED bits are shown as “true” in radiotap and “false” in "802.11 radio"
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14266 Guy Harrischanged: What|Removed |Added Summary|In a WiFi capture log, the |In a WiFi capture log, the |11ac “beamformed” and |11ac “beamformed” and |TXOP_PS_NOT_ALLOWED bit are |TXOP_PS_NOT_ALLOWED bits |shown as “true” in radiotap |are shown as “true” in |and “false” in "802.11 |radiotap and “false” in |radio" |"802.11 radio" -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 14266] In a WiFi capture log, the 11ac “beamformed” and TXOP_PS_NOT_ALLOWED bit are shown as “true” in radiotap and “false” in "802.11 radio"
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14266 Guy Harrischanged: What|Removed |Added Summary|In a WiFi capture log, the |In a WiFi capture log, the |11ac “beamformed” bit is|11ac “beamformed” and |shown as both “true” and|TXOP_PS_NOT_ALLOWED bit are |“false” |shown as “true” in radiotap ||and “false” in "802.11 ||radio" -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 14266] In a WiFi capture log, the 11ac “beamformed” bit is shown as both “true” and “false”
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14266 --- Comment #16 from Guy Harris--- (In reply to zpchi004 from comment #15) > So wireshark displays a) and b) correctly. c) and d) are wrong. I.e., it gets it wrong in two cases where the radiotap flag bit is true. > So wireshark displays a), b) and d) correctly. c) is wrong. I.e., it gets it right in a case where the radiotap flag bit is false and gets it wrong where the radiotap flag is true. So there's *something* wrong that happens with a radiotap flag that's true - but it doesn't *always* happen; it requires that there be other packets, of some unknown sort, in the file. What happens if you write out a file that includes the offending packet and all the packets before it, but doesn't include any of the packets after it, and then read that file? (You should be able to do that by saving a range of packets starting with 1 and ending with the offending packet.) -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 14274] Data field of BGP notification message is not dissected for Open message error/unsupported capability
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14274 --- Comment #2 from Gerrit Code Review--- Change 24829 merged by Anders Broman: BGP: add Open message error/unsupported capability https://code.wireshark.org/review/24829 -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe