On Dec 28, 2018, at 2:36 PM, Yang Yu wrote:
> On Fri, Dec 28, 2018 at 1:07 PM Guy Harris wrote:
>> From looking at the code, the logic appears to be "is the traffic to or from
>> UDP port 6635?"
>>
>> So *is* the traffic to or from UDP port 6635?
>
> indeed udp.dstport is 6635 (IANA assigned
On Fri, Dec 28, 2018 at 1:07 PM Guy Harris wrote:
> From looking at the code, the logic appears to be "is the traffic to or from
> UDP port 6635?"
>
> So *is* the traffic to or from UDP port 6635?
indeed udp.dstport is 6635 (IANA assigned for mpls-udp), so it turned
out a host was using udp/6635
On Dec 27, 2018, at 3:01 PM, Yang Yu wrote:
> In a packet capture of sFlow export packets, I noticed some sFlow
> samples were decoded as MPLS over UDP. The sFlow sampled packet was
> actually just a UDP VoIP packet with no dissector support.
>
> What logic does Wireshark use to opportunisticall
relevant protocols for the tasks at hand.
Met vriendelijke groet / With kind regards,
Hugo van der Kooij
-Original Message-
From: Wireshark-users On Behalf Of
Yang Yu
Sent: vrijdag 28 december 2018 00:02
To: wireshark-users@wireshark.org
Subject: [Wireshark-users] MPLS over UDP decoding
Hi,
In a packet capture of sFlow export packets, I noticed some sFlow
samples were decoded as MPLS over UDP. The sFlow sampled packet was
actually just a UDP VoIP packet with no dissector support.
What logic does Wireshark use to opportunistically consider UDP
payload to be MPLS? Thanks.
Flow sa
