[Ulf Lamping <ulf.lamping@xxxxxx>]

Guy Harris wrote:

> Guy Harris wrote:
>
> > OK, so is there any reason to have the pathname of the file be a
> > settable parameter, or would it be sufficient to have, for example, a
> > file named "hosts" in the directory for personal configuration files
> > (i.e., the file would be ~/.ethereal/hosts on UN*X and, for example,
> > C:\Documents and Settings\{your login name}\Application Data\Ethereal
>
>
> I've checked in a change to have Ethereal (and Tethereal) load a 
> personal hosts file, in ~/.ethereal/hosts on UN*X and in "hosts" in 
> the Ethereal personal configuration directory on Windows.
I would think this should be mentioned in the user's guide somehow.

Do I understand it the right way:

Ethereal will read in the hosts file at program start if it is located 
at the places mentioned above and will add the entries to it's internal 
address resolution table(s).

The format is like the usual hosts file used on unix systems, an example 
might look like this:

# Comments must be prepended by the # sign!
192.168.0.1 homeserver

So Ethereal will resolve the IP address 192.168.0.1 to the string 
homeserver.

Will this only be valid for NSIP as mentioned in the subject line?

Regards, ULFL