Ask Your Question

sharkdam's profile - activity

2017-12-05 14:28:42 +0000 marked best answer does anyone have problems in dissecting LDP P2MP FEC elements?

Hi All, I would like to see multipoint LDP FEC elements like

ldp.msg.tlv.ldp_p2mp.addr_len   Address Length  Unsigned integer, 1 byte    1.12.0 to 2.4.2
ldp.msg.tlv.ldp_p2mp.ipv4_rtnodeaddr    Root Node Address   IPv4 address    1.12.0 to 2.4.2
ldp.msg.tlv.ldp_p2mp.oplength   Opaque Length   Unsigned integer, 2 bytes   1.12.0 to 2.4.2
ldp.msg.tlv.ldp_p2mp.opvalue    Opaque Value    Sequence of bytes   1.12.0 to 2.4.2
ldp.msg.tlv.ldp_p2mp.type   P2MP Type   Unsigned integer, 1 byte    1.12.0 to 2.4.2

I see that they are supported but when I open a capture with these packets wireshark cannot decode them

Frame 6130: 108 bytes on wire (864 bits), 108 bytes captured (864 bits) on interface 0
Ethernet II, Src: ca:01:1d:fd:00:08 (ca:01:1d:fd:00:08), Dst: ca:02:1e:0c:00:08 (ca:02:1e:0c:00:08)
Internet Protocol Version 4, Src: 10.0.0.101, Dst: 10.0.0.201
Transmission Control Protocol, Src Port: 646, Dst Port: 14535, Seq: 1981, Ack: 1981, Len: 54
Label Distribution Protocol
    Version: 1
    PDU Length: 50
    LSR ID: 10.0.0.101
    Label Space ID: 0
    Label Mapping Message
        0... .... = U bit: Unknown bit not set
        Message Type: Label Mapping Message (0x400)
        Message Length: 40
        Message ID: 0x00000132
        Forwarding Equivalence Classes TLV
            00.. .... = TLV Unknown bits: Known TLV, do not Forward (0x0)
            TLV Type: Forwarding Equivalence Classes TLV (0x100)
            TLV Length: 24
            **FEC Elements**
                **FEC Element 1**
                    **Unknown FEC TLV type**
                        **[Expert Info (Warning/Protocol): Unknown FEC TLV type]
                            [Unknown FEC TLV type]**
                            **[Severity level: Warning]**
                            **[Group: Protocol]**

I used 2.4.2 on Windows and 2.2.6 on linux, same results, any ideas?

Thanks.

2017-12-05 14:28:42 +0000 received badge  Scholar (source)
2017-12-05 08:34:51 +0000 commented answer does anyone have problems in dissecting LDP P2MP FEC elements?

Hello, I finally suceeded in rebuilding wireshark from source with the fix for bug 13171, I can confirm that now I see M

2017-12-05 08:25:41 +0000 commented answer does anyone have problems in dissecting LDP P2MP FEC elements?

Hello, I finally suceeded in rebuilding wireshark from source with the fix for bug 13171, I can confirm that now I see M

2017-12-04 12:52:49 +0000 commented answer does anyone have problems in dissecting LDP P2MP FEC elements?

I see that bug 13171 is now fixed, I tried to build new wireshark patching packet-ldp.c with the diff file attached to t

2017-11-29 10:26:10 +0000 commented answer does anyone have problems in dissecting LDP P2MP FEC elements?

Hello, file attached to the bug. Thanks.

2017-11-29 08:44:55 +0000 received badge  Rapid Responder
2017-11-29 08:44:55 +0000 answered a question does anyone have problems in dissecting LDP P2MP FEC elements?

Hello again, I checked on bugzilla and saw that there is already a bug opened for version 2.2.2 about the dissection of

2017-11-29 08:24:43 +0000 received badge  Rapid Responder
2017-11-29 08:24:43 +0000 answered a question does anyone have problems in dissecting LDP P2MP FEC elements?

Hello Jaap and All, I was trying to attach the pcap file, but blog says I need >60 point to attach a file, unfortuna

2017-11-28 13:42:55 +0000 asked a question does anyone have problems in dissecting LDP P2MP FEC elements?

does anyone have problems in dissecting LDP P2MP FEC elements? Hi All, I would like to see multipoint LDP FEC elements l