Decode the word containing the opcode, flags, reply code, etc. in DNS
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Mon, 4 Jan 1999 09:13:46 +0000 (09:13 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Mon, 4 Jan 1999 09:13:46 +0000 (09:13 +0000)
commitd043e6689c07e27f30711d3ee064408cfdc8b074
treebee64f8f62638f04566a146fdd26a5016916507f
parentdf186f70a48f2c1f8b9c1ea4ad4f88a21920143b
Decode the word containing the opcode, flags, reply code, etc. in DNS
and NBNS requests.

Put the opcode in the COL_INFO field for DNS requests (it was already
there for NBNS requests).

Don't assume a DNS or NBNS request is neatly aligned on a 2-byte
boundary (it might not be if, for example, the packet is an FDDI
packet).

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@153 f5534014-38df-0310-8fa8-9805f1628bb7
packet-dns.c
packet-nbns.c
packet.h