Consider the following scenario: An AS with multiple (lots) internal routers exchanging information via EIGRP. Out of these routers, two are border, with EBGP feeds to upstream providers. One of these routers is used as a default entry/exit point, whilst the other is used to lab purposes. A third router, somewhere in the depth of the network, requires a BGP routing table.
Neighbors (ibgp) between this third router and the "lab" border router have been established, with a lovely set of Internet routes reciding on the third router. The next hop of the ibgp routes are pointing towards the loopback of the "lab" border router. Everything seems absolutley fine. All loopbacks are reachable via the IGP, and from any BGP router.
Now, When I trace from the third router (from an interface address which is been announced via the "lab" border router to upstream) it decides to follow the candidate default route located on next-igp-hop (a pure igp router), exiting via the wrong border router, not the one specified by the BGP NEXT HOP.
I've checked the administrative distances, and they seem to be fine (perhaps not).
I'm confused, why could this be happenening? Any feedback would be greatly appreciated.
Thanks in advance.