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-grammar.y | |
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-grammar.y')
-rw-r--r-- | dfilter-grammar.y | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/dfilter-grammar.y b/dfilter-grammar.y index d06fd61f5e..321fc27b6b 100644 --- a/dfilter-grammar.y +++ b/dfilter-grammar.y @@ -3,7 +3,7 @@ /* dfilter-grammar.y * Parser for display filters * - * $Id: dfilter-grammar.y,v 1.31 1999/10/14 08:05:51 guy Exp $ + * $Id: dfilter-grammar.y,v 1.32 1999/10/15 04:22:46 itojun Exp $ * * Ethereal - Network traffic analyzer * By Gerald Combs <gerald@zing.org> @@ -769,7 +769,7 @@ dfilter_mknode_ipv6_value(char *host) node->check_relation_func = check_relation_ipv6; /* XXX should use get_host_ipaddr6 */ - if (!ipv6_str_to_guint8_array(host, &node->value.ipv6[0])) { + if (!get_host_ipaddr6(host, &node->value.ipv6[0])) { /* Rather than free the mem_chunk allocation, let it * stay. It will be cleaned up when "dfilter_compile()" * calls "dfilter_destroy()". */ |