Thanks to everyone that replied.
It would seem that since (from my observations after this info) tcpdump does
not use lib_pcap on various systems; instead it defaults to the vendor
supplied packetfilters. In this case I needed to use pfconfig ( pfconfig +p
+c <device> ) to configure my ethernet device.
Thanks again for the timely responses,
-Will
-----Original Message-----
From: WScates_at_amc.jccbi.gov [mailto:WScates_at_amc.jccbi.gov]
Sent: Thursday, February 07, 2002 1:26 PM
To: tru64-unix-managers_at_ornl.gov
Subject: tcpdump
Hello managers,
While trying to investigate some oracle issues, I used tcpdump in an attempt
to monitor the network traffic.
In order to get a decent baseline on average times I also ran ping during
the test.
The problem I seem to have is that I am not able to view outbound packets
(as you would if running tcpdump from a linux box).
Example:
tcpdump -n ip host xxx.xx.xxx
tcpdump -n -vv ip host xxx.xx.xxx
tcpdump -n -vv -i tu0 host xxx.xx.xxx
tcpdump -vv ip host xxx.xx.xxx
13:19:25.124035 snap ip xxx.xx.xx.xxx > xxx.xx.xx.xxx: icmp: echo reply (ttl
124, id 13022)
13:19:26.147131 snap ip xxx.xx.xx.xxx > xxx.xx.xx.xxx: icmp: echo reply (ttl
124, id 13023)
13:19:27.172882 snap ip xxx.xx.xx.xxx > xxx.xx.xx.xxx: icmp: echo reply (ttl
124, id 13024)
This would be on a GS140 running Tru64 4.0g
Have I used the wrong switches (since I'm not seeing the 'whole'
conversation?), or is this how tcpdump works on Tru64.
-Will
Received on Thu Feb 07 2002 - 20:35:10 NZDT