Ethereal-users: Re: [Ethereal-users] hosts, ethers, & windows

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Serge Dergham" <serge@xxxxxxxxx>
Date: Fri, 22 Jun 2001 15:42:59 -0000
Getting this message when trying to set a "gateway" capture filter.

< Unable to parse filter string ('gateway' not supported in this
configuration) >

pleas explain, is this an ethereal, winpcap, or another component problem ?
what does "this configuration" mean, windows versions ?

thanks


----- Original Message -----
From: "Guy Harris" <gharris@xxxxxxxxx>
To: "Serge Dergham" <serge@xxxxxxxxx>
Cc: <ethereal-users@xxxxxxxxxxxx>
Sent: Friday, June 22, 2001 8:44 AM
Subject: Re: [Ethereal-users] hosts, ethers, & windows


> On Fri, Jun 22, 2001 at 01:25:42AM -0000, Serge Dergham wrote:
> > >From TCPDUMP man:
> >
> > <Host must be a name and must be
> >         found in both  /etc/hosts  and  /etc/ethers>
> >
> > When running ethereal windows & winPcap
> >
> > 1- I suppose /etc/hosts is the hosts file in windows directory, correct
?
>
> The tcpdump man page didn't state the requirement correctly; it should
> have been
>
> ...and must be found both by the OS's host name to IP address
> resolution mechanism and ...
>
> I.e., even on UNIX, it's not required that the host be in "/etc/hosts" -
> it can also be in the NIS, NIS+, or DNS hosts databases, if the OS is
> configured to search those databases.
>
> As such, on Windows, the host must be found by "gethostbyname()", which
> could include the hosts file, DNS, and perhaps even NBNS/WINS.
>
> > 2- What is /etc/ethers under windows ?
>
> You'd have to ask the WinPcap developers that (at least some of them may
> read this list; if you don't get a response, try asking
> winpcap@xxxxxxxxxxxxxxxxxxxxxxx); my machine isn't running Windows right
> now, so I can't use my MSDN stuff to see whether Windows has
> "ether_hostton()" and, if it does, what it searches (and Netscape 4.76
> doesn't seem to be able to handle the search result pages from MSDN).
>
>