a8649c0e74
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. svn path=/trunk/; revision=2937
52 lines
1.7 KiB
Text
52 lines
1.7 KiB
Text
$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 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 :
|
|
|
|
Kernel configuration
|
|
--------------------
|
|
|
|
The packet filtering kernel option must be enabled at kernel
|
|
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
|
|
|
|
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
|
|
--------------------
|
|
|
|
Devices used for packet filtering must be created thanks to
|
|
the following command (executed in the /dev directory):
|
|
|
|
./MAKEDEV pfilt
|
|
|
|
Interface configuration
|
|
-----------------------
|
|
|
|
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>
|
|
|
|
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.
|