This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
ABOUT CHECKMATES & FAQ
Create a Post
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Help

Are you a member of CheckMates?

×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have one, create one now for free!
Harald_Hansen
Advisor
‎2018-12-04 10:06 AM

BGP Multihop ignoring next hop

In the advanced router admin guide (Gaia Advanced Routing R80.10 Administration Guide) on BGP Multhop:

When traffic comes from a router that is not directly connected and multihop is enabled, BGP uses that router as the next hop, irrespective of the advertised routes that it gets.

There are certain situation where this behaviour is undesirable. 

In routers one can set next hop via route maps in one location. Routed not honouring the next hop settings are creating a mess in the routing tables.

The above should be a configurable setting, not a Check Point design choice. Now I have to create 10 times the configuration on each VS, on all routers etc. 

I suggest this ether to be part of the route maps, for instance a match on next hop or a setting on bgp external peer.

2 Replies
This widget could not be displayed.