[Wireshark-bugs] [Bug 15551] Ascend-Data-Filter (RADIUS attr 242) are not displayed in readable form
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15551 Guy Harris changed: What|Removed |Added OS|Windows 7 |All Hardware|x86 |All --- Comment #2 from Guy Harris --- Grump. Perhaps we need some way to have "conditional" inclusion of some RADIUS dictionary items, with RADIUS preferences that control whether to include them or not, rather than having somewhat not-well-known "uncomment this" tricks. That might require some extensions to the FreeRADIUS syntax to handle conditional definition, and small changes to some files. -- 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 15552] Bidirectional Capture Filters not working properly in MacOS 10.13
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15552 --- Comment #6 from Guy Harris --- First make sure that the requests don't have VLAN headers. If so, this is a well-known, long-standing issue with BPF filters and the filtering language; you'd have to do port 53 or (vlan and port 53) -- 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 15552] Bidirectional Capture Filters not working properly in MacOS 10.13
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15552 --- Comment #5 from Paul Fischer --- Created attachment 16951 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16951=edit Screenshot of TCPDUMP running in a terminal window showing the same behavior Proof tcpdump does the same thing. Thank you all for your time and help. -Paul -- 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 15518] Symbol not found: _clock_gettime in libgnutls.30.dylib
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15518 Guy Harris changed: What|Removed |Added Component|Qt UI |Build process Hardware|x86 |All -- 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 15552] Bidirectional Capture Filters not working properly in MacOS 10.13
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15552 Paul Fischer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #4 from Paul Fischer --- I tried with tcpdump and got the same results. I guess I need to file the bug report with Apple. # tcpdump -i en0 udp port 53 -- 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 15518] Symbol not found: _clock_gettime in libgnutls.30.dylib
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15518 Guy Harris changed: What|Removed |Added Status|INCOMPLETE |RESOLVED Resolution|--- |FIXED --- Comment #9 from Guy Harris --- (In reply to Guy Harris from comment #8) > If you have a pre-10.12 machine, and you try to install Wireshark 3.0.0 on > it, and it lets you do so, this becomes a "build process" bug on the > installer, otherwise we can close it. Nope, it doesn't let you install it. It does let you install it on 10.12, and it seems to run there. Closing as fixed, because the 3.0.0 installer won't let you install it on releases prior to 10.12. -- 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 15518] Symbol not found: _clock_gettime in libgnutls.30.dylib
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15518 Guy Harris changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |INCOMPLETE --- Comment #8 from Guy Harris --- To quote the 3.0.0 announcement: https://www.wireshark.org/news/ "The macOS package requires version 10.12 or later. If you’re running an older version of macOS, please use Wireshark 2.6." If you have a pre-10.12 machine, and you try to install Wireshark 3.0.0 on it, and it lets you do so, this becomes a "build process" bug on the installer, otherwise we can close it. -- 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 15518] Symbol not found: _clock_gettime in libgnutls.30.dylib
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15518 --- Comment #7 from Guy Harris --- (In reply to Guy Harris from comment #6) > Radar time! The radar was closed with the extraordinarily helpful note that the documented-nowhere-at-Apple "-Wunguarded-availability" flag should be used, rather than the also-documented-nowhere-at-Apple on-by-default "-Wunguarded-availability-new" flag; the latter flag only affects 10.13 and later development targets. The only documentation I could find is at https://clang.llvm.org/docs/LanguageExtensions.html which is a bit surprising, given how not-very-well-organized-and-maintained the Clang documentation at llvm.org has been, in my experience. And I have *no* clue why the they thought they needed *two* flags that differ by their behavior with deployment targets preceding what I presume is some arbitrary Darwin release. -- 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 15518] Symbol not found: _clock_gettime in libgnutls.30.dylib
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15518 Stig Bjørlykke changed: What|Removed |Added Severity|Blocker |Normal -- 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 15552] Bidirectional Capture Filters not working properly in MacOS 10.13
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15552 --- Comment #3 from Guy Harris --- Does it work with tcpdump? If not, that's a libpcap or macOS BPF bug. -- 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 15551] Ascend-Data-Filter (RADIUS attr 242) are not displayed in readable form
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15551 Uli Heilmeier changed: What|Removed |Added CC||u...@heilmeier.eu --- Comment #1 from Uli Heilmeier --- This seems to be related with bug 11630. Have you tried to uncomment attribute "X-Ascend-Data-Filter" in dictionary.ascend as João wrote? -- 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 15552] Bidirectional Capture Filters not working properly in MacOS 10.13
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15552 --- Comment #2 from Paul Fischer --- Created attachment 16950 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16950=edit The capture window showing several seconds of one sided capture -- 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 15552] Bidirectional Capture Filters not working properly in MacOS 10.13
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15552 --- Comment #1 from Paul Fischer --- Created attachment 16949 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16949=edit Display of the capture filter window -- 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 15552] New: Bidirectional Capture Filters not working properly in MacOS 10.13
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15552 Bug ID: 15552 Summary: Bidirectional Capture Filters not working properly in MacOS 10.13 Product: Wireshark Version: 3.0.0 Hardware: x86-64 OS: macOS 10.13 Status: UNCONFIRMED Severity: Normal Priority: Low Component: Dumpcap Assignee: bugzilla-ad...@wireshark.org Reporter: pfisc...@pfischer.com Target Milestone: --- Build Information: Downloaded binary for Wireshark 3.0 from the Wireshark.org website. -- Bidirectional capture filters do not work properly under MacOS 10.13. When I enter the capture filter, "port 53", and begin a capture I only see responses from the DNS server I am using 9.9.9.9. According to the Wireshark capture filter manual this should get me the requests from the machines on my network as well as the responses. I never see the requests go out. Only the responses. If I capture everything, and then apply a display filter I can see both the request and the response. So I know my system is wired up properly. If I use a capture filter specifying a specific vlan, that works properly. I can see all traffic going to and from all the machines on that network. SETUP: Mac Mini running MacOS 10.13 Wireshark 3.0 WiFi for administrative access Built-in Ethernet for packet capture The Ethernet port is connected to my core switch. The port on the switch is setup as a span port. It is mirroring the port that connects to my router/firewall. -- 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 15540] add EERO protocol
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15540 Alexis La Goutte changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||alexis.lagou...@gmail.com -- 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 12874] Unable to dissect SPDY streams after a protocol switch in plain text
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12874 Alexis La Goutte changed: What|Removed |Added Status|CONFIRMED |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 15540] add EERO protocol
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15540 --- Comment #1 from Gerrit Code Review --- Change 32191 merged by Alexis La Goutte: Add support for protocol broadcast by EERO Mesh AP's https://code.wireshark.org/review/32191 -- 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
