Note that this document should apply to post-4.0 versions of

Digital^H^H^H^H^H^H^HTru64 UNIX, but make the note about DU 3.2 a bit
speculative (I don't have 3.2 documentation handy to check whether, for
example, you can use "doconfig" interactively).

Add a note about using "doconfig" interactively - the Tru64 UNIX FAQ
mentions that in its not on using tcpdump.

Expand on the discussion of "pfconfig" to explain that you're also
enabling "local copy" mode, and to mention the "-a" option to let you
enable local copy and promiscuous mode on all devices, and to explain
*why* you want to enable local copy and promiscuous mode.  Also, in the
example pfconfig command, put the network device name at the end - the
Tru64 UNIX FAQ, and the pfconfig man page, both put it there.


git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@2937 f5534014-38df-0310-8fa8-9805f1628bb7

1 files changed, 25 insertions, 12 deletions

diff --git a/README.tru64 b/README.tru64
index b21ffe545e..2f3524ac86 100644
--- a/README.tru64
+++ b/README.tru64
@@ -1,8 +1,9 @@
-$Id: README.tru64,v 1.2 2000/02/19 22:00:25 guy Exp $
+$Id: README.tru64,v 1.3 2001/01/24 06:50:16 guy Exp $
 
 The following instructions are applicable to Tru64 UNIX 
-(formerly Digital UNIX (formerly DEC OSF/1)) version 3.2 and 4.0.
-
+(formerly Digital UNIX (formerly DEC OSF/1)) version 4.0, and
+probably to later versions as well; at least some options apply to
+Digital UNIX 3.2 - perhaps all do.
 
 In order to use kernel packet filtering on this system, you have
 to configure it in such a way : 
@@ -11,11 +12,15 @@ Kernel configuration
 --------------------
 
 The packet filtering kernel option must be enabled at kernel
-installation. If it was not the case, you can rebuild the kernel
-after adding the following line in the kernel configuration file
-(/sys/conf/<HOSTNAME>):
+installation.  If it was not the case, you can rebuild the kernel with
+"doconfig -c" after adding the following line in the kernel
+configuration file (/sys/conf/<HOSTNAME>):
+
+	option PACKETFILTER
 
-option PACKETFILTER
+or use "doconfig" without any arguments to add the packet filter driver
+option via the kernel option menu (see the system administration
+documentation for information on how to do this).
 
 Device configuration
 --------------------
@@ -23,16 +28,24 @@ Device configuration
 Devices used for packet filtering must be created thanks to
 the following command (executed in the /dev directory):
 
-./MAKEDEV pfilt
+	./MAKEDEV pfilt
 
 Interface configuration
 -----------------------
 
-In order to capture all packets on a network, you may want to
-enable the promiscuous mode of the interface thanks to the
-pfconfig(1) command:
+In order to capture all packets on a network, you may want to allow
+applications to put the interface on that network into "local copy"
+mode, so that Ethereal can see packets sent by the host on which it's
+running as well as packets received by that host, and to put the
+interface into "promiscuous" mode, so that Ethereal can see packets on
+the network segment not sent to the host on which it's running, by using
+the pfconfig(1) command:
+
+	pfconfig +c +p <network_device>
 
-pfconfig <network_device> +c +p
+or allow application to put any interface into "local copy" or
+"promiscuous" mode by using the command:
 
+	pfconfig +c +p -a
 
 Note: all instructions given require root privileges.