On Thu, Jan 10, 2019 at 03:06:59PM +0700, Igor Podlesny wrote: > On Thu, 10 Jan 2019 at 01:21, Remi Locherer <remi.loche...@relo.ch> wrote: > [...] > > > > It is not intended. I'll look into it.
I can reproduce it. Interestingly it only sends out the wrong type when the "depend on" interfac (carp1 in your example) is down or in backup state and the configured type is 2. I don't have much time right now so please don't expect a fast fix. > > I see, thank you. BTW, if-when it's fixed would such a fix be brought > within standard syspatch update process or > what would it be otherwise? I don't think this is worth a syspatch. It is not a vulnerability or stability issue. And I also don't see how it affects existing setups. > > Can you also explain why Type 1 has been chosen as default one at all? For e. > g. > > https://www.juniper.net/documentation/en_US/junos/topics/concept/ospf-routing-external-metrics-overview.html > states "By default, OSPF uses the Type 2 external metric." > Bird OSPF also uses Type 2 for default route announcements. > > It's interesting hence why OpenOSPFD uses Type 1 instead. I have no clue. But now it is unlikely that the default changes since that would affect existing setups. > > -- > End of message. Next message? >
