Comment # 2
on bug 10426
from Kevin Bracey
Created attachment 13020 [details]
Example packet
Here's the offending packet. (With just the one packet you don't have the
compression context, but that doesn't affect the relevant part of the
dissector).
>From that I get:
Frame 1: 164 bytes on wire (1312 bits), 164 bytes captured (1312 bits) on
interface 0
Raw packet data
Internet Protocol Version 4, Src: 192.168.1.3 (192.168.1.3), Dst: 0.0.0.0
(0.0.0.0)
User Datagram Protocol, Src Port: zep (17754), Dst Port: zep (17754)
ZigBee Encapsulation Protocol, Channel: 11, Length: 104
IEEE 802.15.4 Data, Dst: Broadcast, Src: Stmicroe_03:00:00:9d:00
Frame Control Field: Data (0xc841)
Sequence Number: 162
Destination PAN: 0x8f46
Destination: 0xffff
Extended Source: Stmicroe_03:00:00:9d:00 (00:80:e1:03:00:00:9d:00)
Frame Check Sequence (TI CC24xx format): FCS OK
RSSI: 28 dBm
FCS Valid: True
LQI Correlation Value: 105
6LoWPAN
IPHC Header
011. .... = Pattern: IP header compression (0x03)
...1 1... .... .... = Traffic class and flow label: Version, traffic
class, and flow label compressed (0x0003)
.... .1.. .... .... = Next header: Compressed
.... ..00 .... .... = Hop limit: Inline (0x0000)
.... .... 0... .... = Context identifier extension: False
.... .... .1.. .... = Source address compression: Stateful
.... .... ..01 .... = Source address mode: 64-bits inline (0x0001)
.... .... .... 1... = Multicast address compression: True
.... .... .... .1.. = Destination address compression: Stateful
.... .... .... ..00 = Destination address mode: Reserved (0x0000)
[Expert Info (Error/Malformed): Illegal destination address mode]
[Message: Illegal destination address mode]
[Severity level: Error]
[Group: Malformed]
Hop limit: 255
Source: ::280:e103:0:9d00 (::280:e103:0:9d00)
Decoding comes out okay if I hack my IPHC compressor to write the destination
address mode as "01" instead.
You are receiving this mail because:
- You are watching all bug changes.