[Wireshark-bugs] [Bug 15086] Add feature to stop capture based on data content using - capture filters syntax
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15086 --- Comment #3 from Christopher Maynard --- (In reply to Peter Wu from comment #2) > The generic term for this feature is "trigger", and searching Bugzilla > showed these two results that cover other trigger actions (like start): > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2039 > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3967 > Other related bugs, questions, discussions: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4390 https://ask.wireshark.org/questions/1019/trigger-a-script https://ask.wireshark.org/questions/1709/automatically-start-capturing-packets-when-bandwidth-is-high https://ask.wireshark.org/questions/2049/trigger-a-capture https://ask.wireshark.org/questions/6585/triggers-for-wireshark https://ask.wireshark.org/questions/9682/trigger-an-executable-file-once-wireshark-finds-a-keyword-on-live-capture https://ask.wireshark.org/questions/26434/sound-alert https://ask.wireshark.org/questions/30118/email-function https://ask.wireshark.org/questions/39456/is-there-a-way-to-stop-capture-upon-http-error-404 https://ask.wireshark.org/questions/40888/custom-stop-recording-trigger https://ask.wireshark.org/questions/48212/trigger-the-capture https://ask.wireshark.org/questions/51887/tshark-auto-stop-conditions-extended-functionality https://ask.wireshark.org/questions/60412/how-do-i-trigger-an-alert-on-specific-frame-captured-during-live-scan https://www.wireshark.org/lists/wireshark-dev/200804/msg00078.html https://www.wireshark.org/lists/wireshark-users/201004/msg00016.html https://www.wireshark.org/lists/wireshark-users/201205/msg00018.html -- 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 15086] Add feature to stop capture based on data content using - capture filters syntax
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15086 Peter Wu changed: What|Removed |Added Ever confirmed|0 |1 Hardware|x86 |All CC||pe...@lekensteyn.nl OS|Windows 10 |All Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Peter Wu --- The generic term for this feature is "trigger", and searching Bugzilla showed these two results that cover other trigger actions (like start): https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2039 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3967 For dumpcap/tshark, extending the "-a " with a "cfilter:" argument seems natural. (The same code could potentially enable the "-b ".) When such a feature is added to dumpcap, it can actually very precisely control when to stop writing packets. In line with the other "-a" options, it should probably stop capturing *after* writing the matched 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 15086] Add feature to stop capture based on data content using - capture filters syntax
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15086 Dylan changed: What|Removed |Added Severity|Major |Enhancement -- 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 15086] Add feature to stop capture based on data content using - capture filters syntax
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15086 --- Comment #1 from Dylan --- See bigger description, use cases, etc in the other related bug: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15087 (stop based on display filter syntax) -- 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 15086] Add feature to stop capture based on data content using - capture filters syntax
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15086 Dylan changed: What|Removed |Added Summary|Add feature to stop capture |Add feature to stop capture |based on data content using |based on data content using |capture filters |- capture filters syntax -- 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
