9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
* [9fans] snoopy bug?
@ 2003-01-23 20:14 Sam
  2003-01-23 20:31 ` Russ Cox
  0 siblings, 1 reply; 3+ messages in thread
From: Sam @ 2003-01-23 20:14 UTC (permalink / raw)
  To: 9fans

term% snoopy -f 't=0x88a2'
after optimize: t = 0x88a2
snoopy: internal error: compilewalk: badly formed tree

Cheers,

Sam




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [9fans] snoopy bug?
  2003-01-23 20:14 [9fans] snoopy bug? Sam
@ 2003-01-23 20:31 ` Russ Cox
  2003-01-23 20:49   ` Sam
  0 siblings, 1 reply; 3+ messages in thread
From: Russ Cox @ 2003-01-23 20:31 UTC (permalink / raw)
  To: 9fans

i would argue that this is a syntax error misdiagnosed.
t=0x88a2 means nothing unless you say what kind of
packet the field is in.

snoopy -f 'ether(t=0x88a2)'

does what you want.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [9fans] snoopy bug?
  2003-01-23 20:31 ` Russ Cox
@ 2003-01-23 20:49   ` Sam
  0 siblings, 0 replies; 3+ messages in thread
From: Sam @ 2003-01-23 20:49 UTC (permalink / raw)
  To: 9fans

Ah, ok.  I got turned around by the following example
in the man page.  That makes more sense.

% snoopy -f 'arp || bootp'
after optimize: ether( arp || ip( udp( bootp ) ) )

Thanks,

Sam

On Thu, 23
Jan 2003, Russ Cox wrote:

> i would argue that this is a syntax error misdiagnosed.
> t=0x88a2 means nothing unless you say what kind of
> packet the field is in.
>
> snoopy -f 'ether(t=0x88a2)'
>
> does what you want.
>



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-01-23 20:49 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-23 20:14 [9fans] snoopy bug? Sam
2003-01-23 20:31 ` Russ Cox
2003-01-23 20:49   ` Sam

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).