Ooooo. They are all going out as Metric-type 2
> On May 13, 2018, at 17:37, Matt Hoppes <mattli...@rivervalleyinternet.net> > wrote: > > Correct. A is distributing default route. Directly to C (in theory but not > happening) and to B which is distributing to C currently. > > This is edgeOS. > > I’m actually not sure. I’ll have to check on E1 vs E2. > >> On May 13, 2018, at 17:26, George Skorup <george.sko...@cbcast.com> wrote: >> >> OK, so only A is distributing the default route. as-type-1 or as-type-2? E1 >> takes path costs into account. E2 does not. >> >> Bounce a neighbor and see if it fixes itself. I assume RouterOS. I've seen >> weird stuff like this happen before. >> >>> On 5/13/2018 4:15 PM, Matt Hoppes wrote: >>> Only one - the Long one. >>> >>> The things connected to A take the direct path but the default is not >>> coming through for some reason. >>> >>> On May 13, 2018, at 17:12, George Skorup <george.sko...@cbcast.com> wrote: >>> >>>> How many default routes show up in the LSA table? >>>> >>>>> On 5/13/2018 3:51 PM, Matt Hoppes wrote: >>>>> OSPF question: >>>>> >>>>> A—-B—-C >>>>> And >>>>> A——C >>>>> >>>>> A is the Internet peering router. >>>>> >>>>> C should end up with two default routes in it correct? >>>>> >>>>> One through B and one directly to C? >>>>> >>>>> What’s odd is everything on A populated on Cs route table as direct >>>>> routes - except for the default route. >>>> >>
