Disables "Follow TCP Stream" if compiled with wiretap.

svn path=/trunk/; revision=199

1 files changed, 9 insertions, 7 deletions

diff --git a/README b/README
index 27d02db196..a47d0ff6ba 100644
--- a/README
+++ b/README
@@ -51,15 +51,17 @@ development parallel to ethereal.  In the future it is hoped that
 wiretap will have more features than libpcap, but wiretap is still in
 its infancy.  You can compile ethereal with the wiretap library by using
 './configure --with-wiretap'.  Using wiretap will allow you to read
-pcap, Sniffer, Sun "snoop", LANalyzer, Microsoft Network Monitor, and
-AIX "iptrace" 2.0 trace files, but it disables display filters.  You can
-still capture packets from within ethereal using libpcap, and therefore
+libpcap, Sniffer, NetXray (and Sniffer Pro), Sun "snoop", LANalyzer,
+Microsoft Network Monitor, and AIX "iptrace" 2.0 trace files. Some minimal
+display filters now work. But because "Follow TCP Stream" relies on IP and TCP
+display filtering, and those aren't yet available in wiretap's display filter
+system, "Follow TCP Stream" is turned off when you compile --with-wiretap.
+
+You can still capture packets from within ethereal using libpcap, and therefore
 use libpcap-style capture filters, however.
 
-If you can live without display filters and would like to read non-pcap
-capture files, give wiretap a try. If you want to add support for other
-packet-capture file formats, please look at the wiretap source code in the
-wiretap directory.
+If you want to add support for other packet-capture file formats, please
+look at the wiretap source code in the wiretap directory.
 
 Please report any problems that are wiretap related to
 Gilbert Ramirez <gram@verdict.uthscsa.edu>. He uses token-ring at work, so he