Wireshark-bugs: [Wireshark-bugs] [Bug 13118] packet dissection for "OSPFv3 Router Information Op

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 10 Nov 2016 16:05:32 +0000

Comment # 4 on bug 13118 from 
Both of these pcap files have a TLV of SR protocol. It is expected that the
TLVs are not dissected.

I came across this bug while writing a dissector for this protocol. 

The Link local scope flooding shows that the output correctly. 

The area scope flooding shows that the LSA is unknown. But the tshark output
shows that this is recognized as the opaque lsa by the filter (output pruned)

bharath@bharath-Vostro-2520:$./tshark -r  
~/Downloads/wireshark_capture/ospfv3-SR-1.pcap -T json
[
  {
    "_index": "packets-2016-11-10",
    "_type": "pcap_file",
...
...
"LS Update Packet": {
            "ospf.ls.number_of_lsas": "1",
            "LSA-type 40972 (Unknown), len 28": {
              "ospf.lsa.age": "432",
              "ospf.v3.lsa.do_not_age": "0",
              "ospf.v3.lsa": "0x0000a00c",
              "ospf.v3.lsa.opaque": "1",
              "ospf.link_state_id": "0.0.0.0",
              "ospf.advrouter": "10.1.3.3",
              "ospf.lsa.seqnum": "0x80000001",
              "ospf.lsa.chksum": "0x0000dcfa",
              "ospf.lsa.length": "28",
              "_ws.expert": {
                "ospf.lsa.unknown_type": "",
                "_ws.expert.message": "Unknown LSA Type 0xa00c",
                "_ws.expert.severity": "6291456",
                "_ws.expert.group": "150994944"
              }
            }
          }
        }
      }
    }
  }

]


The line "ospf.v3.lsa.opaque": "1" says that this is recognized as the opaque
lsa. Although the dissection is not done for the opaque type.

You are receiving this mail because:
  • You are watching all bug changes.