diff options
| author | Jun-ichiro itojun Hagino <itojun@itojun.org> | 1999-10-15 04:22:48 +0000 |
|---|---|---|
| committer | Jun-ichiro itojun Hagino <itojun@itojun.org> | 1999-10-15 04:22:48 +0000 |
| commit | 9558d968594f8ce0d9f3b32206660361a5fb7b1e (patch) | |
| tree | 667b266924534491f151dac6062f42cbaa2b6a42 /dfilter-scanner.l | |
| parent | 76d3e189fed83ec5a26373a1e7801a59e5faa111 (diff) | |
use proto_tree_add_item() for IPv6 header, to allow filtering like below
possible.
ipv6.nxt == 17
ipv6.dst == ff02::9
ipv6.src[0:2] == fe:80
modify dfilter lexical rule to allow standard IPv6 expression to be
passed up to parser.
XXX backward compat issue in lex rule, maybe
XXX IPv6 has chained headers. how will dfilter behave when we have
multiple protocol header of the same type?
XXX ipv6.nxt is not really useful due to IPv6 chained header. we need a
symbol to identify "final" protocol type on the chain (testing ipv6.final
but will SEGV).
svn path=/trunk/; revision=836
Diffstat (limited to 'dfilter-scanner.l')
| -rw-r--r-- | dfilter-scanner.l | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/dfilter-scanner.l b/dfilter-scanner.l index 252ab5fd69..dd883ae8a6 100644 --- a/dfilter-scanner.l +++ b/dfilter-scanner.l @@ -3,7 +3,7 @@ /* dfilter-scanner.l * Scanner for display filters * - * $Id: dfilter-scanner.l,v 1.20 1999/10/12 06:19:59 gram Exp $ + * $Id: dfilter-scanner.l,v 1.21 1999/10/15 04:22:47 itojun Exp $ * * Ethereal - Network traffic analyzer * By Gerald Combs <gerald@zing.org> @@ -159,7 +159,8 @@ le|\<\= { dfilter_lval.operand = TOK_LE; return TOK_LE; } } -[A-Za-z][A-Za-z0-9\.\_\-]+ { /* looks like a protocol, field name, or hostname */ +[A-Za-z0-9\:][A-Za-z0-9\.\_\-\:]+ { + /* looks like a protocol, field name, or hostname */ int retval = 0; enum ftenum ftype; |