Subject: tcpdump problem :)
To: None <port-vax@netbsd.org>
From: Bamdad Ehterami <bamdad@mehr.sharif.ac.ir>
List: port-vax
Date: 04/14/2001 16:20:28
Hi all, Bamdad again!:)
you know what's the problem? see for yourselves:
(It's a copy-paste of the screen)
NetBSD:~# tcpdump -ni le0 host 62.41.32.5
Segmentation fault (core dumped)
NetBSD:~# tcpdump -nOi le0 host 62.41.32.5
tcpdump: listening on le0
16:19:54.010000 arp who-has 62.41.32.5 tell 62.41.32.21
16:19:54.010001 arp reply 62.41.32.5 is-at 8:0:2b:2c:98:89
16:19:54.010002 62.41.32.21 > 62.41.32.5: icmp: echo request
16:19:54.010003 62.41.32.5 > 62.41.32.21: icmp: echo reply
16:19:55.010000 62.41.32.21 > 62.41.32.5: icmp: echo request
16:19:55.010001 62.41.32.5 > 62.41.32.21: icmp: echo reply
16:19:56.030002 62.41.32.21 > 62.41.32.5: icmp: echo request
16:19:56.030003 62.41.32.5 > 62.41.32.21: icmp: echo reply
^C
2100 packets received by filter
0 packets dropped by kernel
NetBSD:~#
As you see, the first tcpdump, crashes immediately upon start
but the second time when the optimizer code is turned off, everything
goes well, I've found this bug only in the 'host' expression (protocol
specification ('icmp','tcp',...) will work fine)
plus, I still can't get 'pine 4.33' to work...
thanks,
Bamdad:)