diff options
| author | Jeff Morriss <jeff.morriss@ulticom.com> | 2010-04-12 21:35:19 +0000 |
|---|---|---|
| committer | Jeff Morriss <jeff.morriss@ulticom.com> | 2010-04-12 21:35:19 +0000 |
| commit | a1353706dc2f9daf155fea41386ae78bdc43165f (patch) | |
| tree | 5eb20e75eef57abfc9ced57dfc0c2cce282e500b /doc/rawshark.pod | |
| parent | d05485a32b55f781dd05bbdafcb574c625a648fb (diff) | |
Point out that hostname and MAC address resolution in capture filters will not
use any of the Wireshark "personal" files.
This helps to address the complaint in:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2904
svn path=/trunk/; revision=32452
Diffstat (limited to 'doc/rawshark.pod')
| -rw-r--r-- | doc/rawshark.pod | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/rawshark.pod b/doc/rawshark.pod index 187875951b..da86ec923e 100644 --- a/doc/rawshark.pod +++ b/doc/rawshark.pod @@ -285,6 +285,10 @@ file syntax; each line contains one IP address and name, separated by whitespace. The same directory as for the personal preferences file is used. +Capture filter name resolution is handled by libpcap on UNIX-compatible +systems and WinPCAP on Windows. As such the Wireshark personal F<hosts> file +will not be consulted for capture filter name resolution. + =item Name Resolution (ethers) The F<ethers> files are consulted to correlate 6-byte hardware addresses to @@ -308,6 +312,10 @@ example, F<C:\Program Files\Wireshark>) on Windows systems. The personal F<ethers> file is looked for in the same directory as the personal preferences file. +Capture filter name resolution is handled by libpcap on UNIX-compatible +systems and WinPCAP on Windows. As such the Wireshark personal F<ethers> file +will not be consulted for capture filter name resolution. + =item Name Resolution (manuf) The F<manuf> file is used to match the 3-byte vendor portion of a 6-byte |