Routing

found out it is caused by the older image. version 18.4 works.

Today my co-worker showed me the working configuration which has the same line (## reference 'NAT-PBR' not found). So seems it is not the cause for my issue. Just no clue why not use the ip specified via next-ip.

I am just going to paste the first few lines of the commands since pasting a full BGP table would be impossible here. > show route protocol bgp table inet.0 detail inet.0: 921942 destinations, 4155324 routes (921932 active, 0 holddown, 156 hidden) ...

I replicated your config in lab, and don't really see any such issue. Can you kindly share the outputs of the following? (in both cases, when the route remains and vanishes the r2 routing instance) "show route protocol bgp table inet.0 detail" ...

Thanks for the reply, As you said, i am using policy based routing to route packets, sourced from a specific IP address to that routing-instance. The real problem is that the routes from the BGP neighbours that i am injecting through a rib-group ...

Hi, The ping can't be sourced from a forwarding type routing instance, as the interfaces still belong to the default instance. What is it that you are trying to achieve with this configuration? Forwarding-type instances are most commonly used for ...

When I looked a little deeper via root@sys# show logical-systems sys interfaces ge-0/0/6 | display inheritance I noticed the following: family inet { ## ## 'filter' was inherited from group 'NAT-PBR' ## filter ...