Dagmar d'Surreal wrote:
> Original text cut
My fault is that the instructions were for SlackwareLinux 3.3 andI *did not*
mention that!
Please, accept my appologies ...
But also you can read from the INSTALL of tcpdump,
that *if* you want you can leave it under the structure
of tcpdump source tree, especially if you have any
problems.
On my system it wouldn't want to compile *without*
first building libpcap. After building libpcap, the libpcap
software tries to install a file called bpf.h under
/usr/local/include/net, but this on my system failed as there
were not a directory named /usr/local/include/net.
So, I simply created /usr/local/include/net to and
the bpf.h file in there. I *do not know* if this would be
a problem in my feature compilations
Exactly the same problem I had on OpenBSD 2.3,
and the same solution applied.
Considering both of the problematic compiles on the
named Unix-es, in my opinion it is much better just to
do what is said in INSTALL - just untar the libpcap
under tcpdump, of course I am sure that probably
the solution to this problem as just offered
by Dagmar d'Surreal, will be better.
Have anyone else used othr package than tcpdump,
to monitor traffic of his/her net ?
fire
