Support for IPv6 BGP (BGP-4 Multiprotocol Extensions)
Gaia Check Point security operating system that combines the strengths of both SecurePlatform and IPSO operating systems. implements BGP-4 with support for multiprotocol extensions and the exchange of IPv6 address prefixes, as described in RFCs 2545, 2858, and 3392.
You must use an IPv4 address for the router ID (BGP identifier). After the BGP session is up, prefixes can be advertised and withdrawn by sending normal "UPDATE
" messages that include either or both of the new multiprotocol attributes "MP_REACH_NLRI
" (used to advertise reachability of routes) and "MP_UNREACH_NLRI
" (used to withdraw routes).
The new attributes are backward compatible. If two routers have a BGP session and only one supports the multiprotocol attributes, they can still exchange unicast IPv4 routes even though they cannot exchange IPv6 routes.
|
Notes:
|
Configuring IPv6 BGP (BGP-4 Multiprotocol Extensions)
On each peer, configure the type of routes (Multiprotocol capability) to exchange between peers.
Select one of these:
-
IPv4 Unicast Only (this is the default)
-
IPv6 Unicast Only
-
Both IPv4 and IPv6
To establish BGP peering, the BGP routers must share a capability.
If your system is exchanging IPv4 routes over IPv6 (or IPv6 routes over IPv4), use the Gaia Clish The name of the default command line shell in Check Point Gaia operating system. This is a restricted shell (role-based administration controls the number of commands available in the shell). "
routemap
" commands to set nexthop to match the family of the routes being exchanged. If they do not match, the routes cannot be active.
|
Note - To configure routing policies for BGP-4 Multiprotocol Extensions, use the Gaia Clish " |