["Oscar Fernandez Sierra" <espiralm@xxxxxxxxxxx>]

> > This happens even with filters the program makes automatically when I
double
> > click over a captured package, such
> > as
> >
> > (ip.addr eq 192.168.2.1 and .......)
>
> Double-click?  The filter in question looks like a "Follow TCP Stream"
> filter, but I didn't think you could get that simply by double-clicking.
>
> So are you saying that when you do a "Follow TCP Stream", you get a
>
> Unable to parse filter string (parse error)
>
> error?
>

Yes, you are OK

>
> You're not using that sort of filter as a capture filter - i.e., in the
> "Filter:" text field in the window popped up by the "Start" item in the
> "Capture" menu - are you?  If so, that won't work, unfortunately -
> capture filters have a different syntax from display filters.
>

You are OK again. I had read the FAQ, and I knew the filters were different.
But
the fact the only filters I saw where the ones automatically appeared when I
choosed
"Follow TCP Stream"  where the ones "(ip.addr eq 192.168.2.1 and .......)",
made my
mind go in the wrong address. I think it could be a good idea to separate
the
dialogs for capture and display. When you go to capture data, it has no
sense to let the
user choose a display filter.

Thanks for your help