Ethereal-dev: Re: [Ethereal-dev] FW: [Ethereal-users] RE: Problem with ethereal 0.10.1 and 0.1
The default capture filter is determined from util.c:get_conn_cfilter().
It looks like CLIENTNAME on local connections gets set to "localhost"
instead of "console" on some systems. We should be able to fix this by
adding another check to CLIENTNAME (and perhaps REMOTEHOST and the other
environment variables). I'll see if I can find time to work on it in
the next few days, unless someone gets to it first.
Biot Olivier wrote:
FYI
(JPG screenshot of capture dialog removed)
Maybe we should remove the default capture filter.
Regards,
Olivier
-----Original Message-----
From: Yuval Pemper
I'm not including the response I got to my previous post, as I didn't
receive the email (I'm not a list member).
I've found the cause for the problem. It doesn't have anything to do with
name resolution of any kind. Whenever I start a capture, I have a default
capture filter "not ip host localhost" (see attached image). If I turn the
"Update list of packets in real time" option with this capture filter
enabled, the phenomenon I described in my previous email occurs. If I remove
this capture filter, everything works fine.
I have no idea where this filter capture comes from. I wasn't able to get
rid of it. Uninstalling and installing Ethereal and WinPcap 3.0 haven't
helped.
When I install Ethereal 0.10.2 on another Win2K machine, the abovementioned
default capture filter doesn't ever appear, and there is no problem. If I
turn the "Update list of packets in real time" option on this machine with
the problematic capture filter, I see the same problem.
Any help in getting rid of this default capture filter will be highly
appreciated...
Thanks,
Yuval
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
