Wireshark-bugs: [Wireshark-bugs] [Bug 5458] New: BGP add-path (Additional Paths) support for IPv
Date: Wed, 1 Dec 2010 13:43:31 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5458

           Summary: BGP add-path (Additional Paths) support for IPv4
                    unicast
           Product: Wireshark
           Version: SVN
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: [email protected]
        ReportedBy: [email protected]


Created an attachment (id=5552)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5552)
Capture of a BGP session with add-path capability

Build Information:
TShark 1.5.0 (SVN Rev 35087 from /trunk)

Copyright 1998-2010 Gerald Combs <[email protected]> and contributors.
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 GLib 2.24.2, with libpcap 1.1.1, with libz 1.2.3.4,
without POSIX capabilities, without libpcre, with SMI 0.4.8, without c-ares,
with ADNS, without Lua, without Python, without GnuTLS, with Gcrypt 1.4.5,
without Kerberos, without GeoIP.

Running on Linux 2.6.32-3-686, with libpcap version 1.1.1, with libz 1.2.3.4.

Built using gcc 4.4.5.

--
BGP Additional Path is a new capability that enables BGP sessions from Route
Reflectors to announce more than one route per IP prefix, so as to help reduce
the convergence time of BGP on large networks (see the IDR for explanations)

This is a draft from 2006 that moved to pre-RFC status in 2010:
http://tools.ietf.org/html/draft-ietf-idr-add-paths

As of 2010 at least one implementation exist on a major router, and others are
expected in 2011.

The included capture is a BGP session with add-path capability between two
Cisco CRS3 running a beta version of IOS-XR 4.0.0T, only for IPv4 unicast
prefixes.

I did not manage to obtain a capture for any MP-BGP prefixes (IPv6, labeled IP,
VPNs) probably because it is not supported yet.

Note that the encoding of IPv4 NLRI and withdrawn routes is not compatible with
the standard BGP encoding, and the only indication of the decoding to use is in
the BGP OPEN messages (capability 69 = BGP add-path)

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.