iBGP and next hop - bird router

[skanda at tpg.com.au]

	Hi Bird users,

	  

	I need your kind assistance. We are running bird router in container
and peering with one of the edge routers using iBGP. This for a
looking glass.

	  

	All the routes are becoming unreachable due to next hops since the
bird router is not feed with all the next hops in the network. How can
get the issue resolved ? I want to the change the next hop on the bird
router(I don’t want the peering router to be next-hop-self.). Sofar,
I am unsuccessful.  By hashing out disable under the protocol, we see
the interfaces in the routing table.

	  

	I have done so far following things and unsuccessful.

	  

	protocol direct {

	#            
disabled;                             #
Disable by default

	              
ipv4;                                   
# Connect to default IPv4 table

	              
ipv6;                                   
# ... and to default IPv6 table

	}

	  

	filter looking_glass

	if ( net ~ [ 0.0.0.0/0{0,32} ] ) then

	            {

	                bgp_next_hop = 10.252.40.X; (tried
both VM or gateway address for VM. Not successful sofar)

	                accept;

	            }

	  

	  

	Please kindly advise for a working solution.

	  

	Regards,
 Skanda Arasalingam

	  PS: first time Bird user


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20240229/53432f76/attachment.htm>