Hi All, When I using bird 2.0.2 version ,I have an issue route include "unreachable", but I think this application is reasonable , anyone can help me ? Error is reported in codes: rt_update_hostentry() { .... if (a->hostentry) { /* Recursive route should not depend on another recursive route */ -------do you know the reason ?? log(L_WARN "Next hop address %I resolvable through recursive route for %N", he->addr, n->n.addr); goto done; } ...... } bird> show route all Table master4: 192.170.13.0/24 unreachable [bgp1 04:31:13.630 from 192.170.23.15] * (55/-) [AS2000i] Type: IBGP univ BGP.origin: IGP BGP.as_path: 2000 BGP.next_hop: 192.170.40.13 BGP.local_pref: 100 192.170.15.0/24 unicast [bgp1 04:31:13.630] * (55/0) [?] via 192.170.23.15 on A3IF1 Type: IBGP univ BGP.origin: Incomplete BGP.as_path: BGP.next_hop: 192.170.23.15 BGP.local_pref: 100 192.170.23.0/24 unicast [direct1 04:31:07.741] * (255) dev A3IF1 Type: device univ unicast [bgp1 04:31:13.630] (55/0) [?] via 192.170.23.15 on A3IF1 Type: IBGP univ BGP.origin: Incomplete BGP.as_path: BGP.next_hop: 192.170.23.15 BGP.local_pref: 100 192.170.27.0/24 unreachable [bgp1 04:31:13.630 from 192.170.23.15] * (55/-) [?] Type: IBGP univ BGP.origin: Incomplete BGP.as_path: BGP.next_hop: 192.170.15.27 BGP.local_pref: 100 unicast [kernel2 04:31:06.395] (10) via 192.170.23.15 on A3IF1 onlink Type: inherit univ Kernel.source: 4 Kernel.metric: 5 192.169.23.0/24 unicast [direct1 04:31:08.093] * (255) dev N1IF1 Type: device univ 192.170.40.0/24 unicast [bgp1 04:31:13.630] * (55/0) [?] via 192.170.23.15 on A3IF1 Type: IBGP univ BGP.origin: Incomplete BGP.as_path: BGP.next_hop: 192.170.23.15 BGP.local_pref: 100 unicast [kernel2 04:31:06.395] (10) via 192.170.23.15 on A3IF1 onlink Type: inherit univ Kernel.source: 4 Kernel.metric: 5 Thanks Arvin
On Wed, Jun 27, 2018 at 07:25:49AM +0000, Arvin Gan wrote:
Hi All, When I using bird 2.0.2 version ,I have an issue route include "unreachable", but I think this application is reasonable , anyone can help me ?
/* Recursive route should not depend on another recursive route */ -------do you know the reason ??
Hi This is implementation limitation. We support only one level of indirection, as it significantly simplify the recursive route handling and covers realistic use cases. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Hi Ondrej, Is any consideration/plan to optimize this limitation ? Thanks Arvin -----Original Message----- From: Ondrej Zajicek <santiago@crfreenet.org> Sent: Wednesday, June 27, 2018 7:07 PM To: Arvin Gan <AGan@advaoptical.com> Cc: bird-users@network.cz Subject: Re: BGP hostentry update On Wed, Jun 27, 2018 at 07:25:49AM +0000, Arvin Gan wrote:
Hi All, When I using bird 2.0.2 version ,I have an issue route include "unreachable", but I think this application is reasonable , anyone can help me ?
/* Recursive route should not depend on another recursive route */ -------do you know the reason ??
Hi This is implementation limitation. We support only one level of indirection, as it significantly simplify the recursive route handling and covers realistic use cases. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
On Wed, Jun 27, 2018 at 11:15:02AM +0000, Arvin Gan wrote:
Hi Ondrej, Is any consideration/plan to optimize this limitation ?
No hard plan for this. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Hi Ondrej, Thanks. It seems the limitation for iBGP is more impact, since more than one levels of indirection NEXT_HOP for iBGP is regular application. Thanks Arvin -----Original Message----- From: Ondrej Zajicek <santiago@crfreenet.org> Sent: Wednesday, June 27, 2018 7:22 PM To: Arvin Gan <AGan@advaoptical.com> Cc: bird-users@network.cz Subject: Re: BGP hostentry update On Wed, Jun 27, 2018 at 11:15:02AM +0000, Arvin Gan wrote:
Hi Ondrej, Is any consideration/plan to optimize this limitation ?
No hard plan for this. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Any method to bypass this limitation ? thanks -----Original Message----- From: Arvin Gan Sent: Thursday, June 28, 2018 11:11 AM To: 'Ondrej Zajicek' <santiago@crfreenet.org> Cc: bird-users@network.cz Subject: RE: BGP hostentry update Hi Ondrej, Thanks. It seems the limitation for iBGP is more impact, since more than one levels of indirection NEXT_HOP for iBGP is regular application. Thanks Arvin -----Original Message----- From: Ondrej Zajicek <santiago@crfreenet.org> Sent: Wednesday, June 27, 2018 7:22 PM To: Arvin Gan <AGan@advaoptical.com> Cc: bird-users@network.cz Subject: Re: BGP hostentry update On Wed, Jun 27, 2018 at 11:15:02AM +0000, Arvin Gan wrote:
Hi Ondrej, Is any consideration/plan to optimize this limitation ?
No hard plan for this. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
participants (2)
-
Arvin Gan -
Ondrej Zajicek