<div dir="ltr">So the thing that sticks out to me is that you have both a copy of frr.conf and ospfd.conf. If you are not using an integrated config, just have the individual daemon files.. If you are using the integrated config just use the frr.conf. Having both causes the daemons to get confused and do the wrong thing as you are experiencing here.<div><br></div><div>donald</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 12, 2023 at 9:03 AM Brian J. Murrell <<a href="mailto:brian@interlinx.bc.ca">brian@interlinx.bc.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, 2023-07-11 at 17:51 -0300, Patrick Boutilier wrote:<br>
> On 2023-07-11 10:41, Brian J. Murrell wrote:<br>
> > no service integrated-vtysh-config<br>
> > <br>
> <br>
> <br>
> Have you tried putting the contents of /etc/frr/ospfd.conf in <br>
> /etc/frr/frr.conf ?<br>
<br>
I had not and indeed, that does resolve the issue. However:<br>
<br>
1. Doesn't `no service integrated-vtysh-config` mean that each<br>
daemon read's it's own config file (I.e. as I have configured it)<br>
and as such I should not need to put the ospfd.conf into<br>
frr.conf?<br>
2. If yes to the above and 8.5.2 is discontinuing `no service<br>
integrated-vtysh-config`, is that something that should happen in<br>
a bugfix release?<br>
3. If `no service integrated-vtysh-config` is being discontinued,<br>
wouldn't it be good if frr emitted an error to the effect that it<br>
is discontinued yet still specified in the configuration --<br>
alerting users that it will no longer work as they expect? <br>
<br>
Cheers,<br>
b.<br>
<br>
<br>
_______________________________________________<br>
frog mailing list<br>
<a href="mailto:frog@lists.frrouting.org" target="_blank">frog@lists.frrouting.org</a><br>
<a href="https://lists.frrouting.org/listinfo/frog" rel="noreferrer" target="_blank">https://lists.frrouting.org/listinfo/frog</a><br>
</blockquote></div>