osmocom
/
wireshark
11
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Explain why we dissect more than one address in the MP_REACH_NLRI 

attribute.

svn path=/trunk/; revision=3643
This commit is contained in:
Guy Harris 2001-07-03 02:38:27 +00:00
parent 19b3e8860c
commit 0523cad51b
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
packet-bgp.c
View File

@ -2,12 +2,13 @@
* Routines for BGP packet dissection.
* Copyright 1999, Jun-ichiro itojun Hagino <itojun@itojun.org>
*
* $Id: packet-bgp.c,v 1.41 2001/06/18 02:17:44 guy Exp $
* $Id: packet-bgp.c,v 1.42 2001/07/03 02:38:27 guy Exp $
*
* Supports:
* RFC1771 A Border Gateway Protocol 4 (BGP-4)
* RFC1965 Autonomous System Confederations for BGP
* RFC1997 BGP Communities Attribute
* RFC2545 BGP-4 Multiprotocol Extensions for IPv6 IDR
* RFC2796 BGP Route Reflection An alternative to full mesh IBGP
* RFC2842 Capabilities Advertisement with BGP-4
* RFC2858 Multiprotocol Extensions for BGP-4
@ -1285,6 +1286,11 @@ dissect_bgp_update(tvbuff_t *tvb, int offset, proto_tree *tree)
}
break;
case BGPTYPE_MP_REACH_NLRI:
/*
* RFC 2545 specifies that there may be more than one
* address in the MP_REACH_NLRI attribute in section
* 3, "Constructing the Next Hop field".
*/
af = tvb_get_ntohs(tvb, o + i + aoff);
proto_tree_add_text(subtree2, tvb, o + i + aoff, 2,
"Address family: %s (%u)",