Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 12631] New: BGP L2VPN EVPN Update with route type 2 incorrectly displayed as m

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	12631
Summary	BGP L2VPN EVPN Update with route type 2 incorrectly displayed as malformed
Product	Wireshark
Version	2.0.4
Hardware	x86
OS	Windows 7
Status	UNCONFIRMED
Severity	Minor
Priority	Low
Component	Dissection engine (libwireshark)
Assignee	bugzilla-admin@wireshark.org
Reporter	noqued@gmail.com

Created attachment 14743 [details]
BGP packet with 4 L2VPN EVPN update messages, 2 of them reported as malformed

Build Information:
Version 2.0.4 (v2.0.4-0-gdd7746e from master-2.0)

Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-bit) with Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.38.0, with SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 32-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without
AirPcap.
Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz (with SSE4.2), with 3071MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 40629
--
When opening the attached packet capture with 4 BGP L2VPN EVPN update messages
in a single packet, two of these update messages are reported as malformed due
to "Invalid EVPN Route Type(0)!", but the route type for all 4 update messages
is the same, and is correct (type 2: MAC Advertisement Route).

Also, the route type field is incorrectly labeled as "AFI", where it should be
"EVPN Route Type" AFI in this case is Layer-2 VPN (25) and has nothing to do
with route type.

This problem is reproducible on an Ubuntu Linux as well with Wireshark Version
1.12.4 (v1.12.4-0-gb4861da from master-1.12)

---

      You are receiving this mail because:

• You are watching all bug changes.