[tcpdump-workers] pcap range no worky on ppc? (e.g. udp[2:2] = 137 udp[2:2] = 139)

Hello all, I attempted to use the following expression to filter netbios stuff: udp[2:2] = 137 udp[2:2] = 139 However this expression only captures port 137 packets on my two Power PC machines: - linux 2.4.18 ppc (debian) tcpdump version 3.8.3 / libpcap version 0.8.3 - OS X 10.3.4 PowerBook

Re: [tcpdump-workers] pcap range no worky on ppc? (e.g. udp[2:2] = 137 udp[2:2] = 139)

On Thu, Jun 17, 2004 at 03:19:40PM +1000, Ben Low wrote: I attempted to use the following expression to filter netbios stuff: udp[2:2] = 137 udp[2:2] = 139 However this expression only captures port 137 packets on my two Power PC machines: - linux 2.4.18 ppc (debian) tcpdump

[tcpdump-workers] Automatic report from sources (tcpdump libpcap htdocs) between 16.06.2004 - 17.06.2004 GMT

CVS log entries from 16.06.2004 (Wed) 09:06:57 - 17.06.2004 (Thu) 09:07:19 GMT = Summary by authors = Author: hannes File: tcpdump/print-lspping.c; Revisions: 1.10 Author: risso

Re: [tcpdump-workers] pcap range no worky on ppc? (e.g. udp[2:2]

Thanks Guy. As a workaround, rather than using the port statement, turning off the optimiser (-O) also does the job (as suggested in the 940212 bug report). Guy Harris wrote: ... It's a pcap 0.8 problem: ... -- Ben Low Senior Network Engineer 02 9385 1154 Enterprise IT Infrastructure Division of