Issue in bgpd.
Venkateshwaran R <[email protected]> Tue, 20 Jan 2009 14:57:45 +0530 (IST)
| Newsgroups | gmane.network.zebra.bugs |
|---|---|
| Message-ID | <[email protected]> |
Dear All
Please find below issue that i found in bgpd.
Package details
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Zebra Version - zebra-0.95a
Linux version - 2.6.9-1.667(FC3)
zebra daemon - bgpd
RFC Reference
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RFC 4271, Page no 26 , Section5.1.2 bullet 1) describes.
1) if the first path segment of the AS_PATH is of type
AS_SEQUENCE, the local system prepends its own AS number as
the last element of the sequence (put it in the leftmost
position with respect to the position of octets in the
protocol message). If the act of prepending will cause an
overflow in the AS_PATH segment (i.e., more than 255 ASes),
it SHOULD prepend a new segment of type AS_SEQUENCE and
prepend its own AS number to this new segment.
To create this scenario i sent an UPDATE message with 255 ASes in AS_PATH a=
ttribute.
bgpd Behavior
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
"bgpd" adds its AS no as 256th position[ ie., doesn't introduce new segment=
due to overflow in the AS_PATH segment ]and
advertise the UPDATE message with the path segment length value =3D0[bgpd c=
onsiders path segment length value as
256, but the variable may declared with one byte ie., unsigned char].
Hope this clarifies you.=20
Please excuse me if any thing wrong in my side and explain me what i did an=
d how to get this.
Regards
Venkat
=0A=0A=0A Add more friends to your messenger and enjoy! Go to http://m=
essenger.yahoo.com/invite/