Hi Damien,
Am 09.07.10 08:16, schrieb Damien Miller:
On Thu, 8 Jul 2010, Marian Hettwer wrote:
Hi all,
I'm experiencing a rather strang behaviour with tcpdump on OpenBSD 4.7 i386
running on a vmware esx vsphere 4.
My tcpdump gives no output at all on stdout, but if I use the very same
command with "-w foobar" it actually does dump packages.
I know that esx server are probably not supported, however, does anybody know
a work around this behavior? Or out of curiosity, where is this behaviour
coming from?
See below:
[r...@openlb38-1]<~> # tcpdump
tcpdump: listening on em0, link-type EN10MB
^C
198 packets received by filter
0 packets dropped by kernel
aah, 198 packets I couldn't see... hm hm...
Could be blocked on looking up hostnames. Try "tcpdump -n"
Yeah, it was a faulty entry in my resolv.conf. My box couldn't resolve
names. Using tcpdump -n or fixing resolv.conf fixed my issue.
Thanks,
Marian
