That functionality sounds exactly like what I would want it to be (by
default)...
I too open capture files captured from elsewhere and full of private IP
addresses.
I also see the problem with changing the functionality. I peaked at
ethereal and don't see a preference setting in the GUI for changing the
name resolution. I also believe that the current implementation doesn't
even allow somebody to have a preference file that will use DNS while
capturing, but not while opening. I think that such a functionality
would require a little bit of changes...
Greg Morris wrote:
> Yes, I know that you can turn this off... I was requesting that it be
> turned off by default and that if someone wants this capability they
> can turn it on. Perhaps what might be a better solution is that the
> name resolves be enabled by default on capture and disabled by default
> on an open... What do you think? :@)
>
> >>> Joerg Mayer <jmayer@xxxxxxxxx> 09/23/02 09:10AM >>>
> On Mon, Sep 23, 2002 at 09:00:01AM -0600, Greg Morris wrote:
> > Does anyone have an opinion on this?
>
> Yes :)
>
> > I would propose that we turn the name resolve off by default.
>
> I think it's OK the way it is. Your specific problem can be solved
> too:
> Just look at ~/.ethereal/preferences and change
> name_resolve: TRUE
> to FALSE
>
> Ciao
> Jörg
> --
> Joerg Mayer
> <jmayer@xxxxxxxxx>
> I found out that "pro" means "instead of" (as in proconsul). Now I
> know
> what proactive means.
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
