Re: [Wireshark-dev] Capture filter syntax check - why no check before starting a session?

[Jaap Keuter]

Hi,

I've been toying with the idea of adding a precompile option button to  
the capture dialog. When pressing that a popup would show you the BPF  
code (like tcpdump -d) and a result of processing the capture filter.

Maybe you can file an enhancement bug?

Thanks,
Jaap


Send from my iPhone

On 3 feb 2010, at 12:00, Robert Kochem <rob...@mailueberfall.de> wrote:

> Hi Wireshark developers,
>
> I am currently fighting again with the capture filter syntax. I want  
> to
> build a relatively complex filter which isn't that simple.
>
> My major problem while developing the capture filter is that there  
> is the
> missing possibility to check the syntax of a filter. The only  
> possibility
> is to try starting a new capture session.
>
> I don't expect an real time checking while typing with highlighting  
> but a
> simple button for checking the syntax would be really great and would
> improve the option dialog significantly.
>
> Additionally the "Invalid capture filter" error dialog does not give  
> any
> clue what part of the filter string caused the error. A little bit  
> more
> verboseness would be helpful here, too.
>
> Is there any chance to get those two changes implemented?
>
> Robert
>
> ___________________________________________________________________________
 

> Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe