Ok, after bonking my head on this for a day I figured it out. I had "output.default-originate=if-installed" defined at the bgp template level. When the BGP default route from R1 went active, the R2 Mikrotik would advertise 0.0.0.0/0 right back to R1 creating a loop. I fixed this by removing output.default-originate from the template and defining it at the connection instead.
However this presents another question. In a topology such as this, where each router is a private AS, where R1 is originating the 'real' default route, 0.0.0.0/0:
Normally R2, R3 and R4 would have output.default-originate disabled to the sessions facing each other and perhaps R2->R5 set to output.originate-default=always.
However, if any session from R2, R3, or R4 to R1 goes down they should advertise 0.0.0.0/0 via the closest peer.
How is this accomplished in conjunction with the output.default-originate parameter?
However this presents another question. In a topology such as this, where each router is a private AS, where R1 is originating the 'real' default route, 0.0.0.0/0:
Code:
|----- R3 | | R1 --- R2 --- R5 | | |----- R4However, if any session from R2, R3, or R4 to R1 goes down they should advertise 0.0.0.0/0 via the closest peer.
How is this accomplished in conjunction with the output.default-originate parameter?
Statistics: Posted by bdowne01 — Mon Jan 29, 2024 8:10 pm