On Sun, Nov 05, 2017 at 06:19:12PM +0100, Jeremie Courreges-Anglas wrote:
> On Sun, Nov 05 2017, Jeremie Courreges-Anglas wrote:
> > ospf6d consistently fails when I ask it to reload its config, even
> > though I have a very basic test setup:
> >
> > area 0.0.0.0 {
> > interface em0 { pass
On Sun, Nov 05 2017, Jeremie Courreges-Anglas wrote:
> ospf6d consistently fails when I ask it to reload its config, even
> though I have a very basic test setup:
>
> area 0.0.0.0 {
> interface em0 { passive }
> interface vether0
> }
>
> Fixing ospf6d doesn't seem trivial. Having
yep, ok
Jeremie Courreges-Anglas(j...@wxcvbn.org) on 2017.11.05 15:50:42 +0100:
>
> ospf6d consistently fails when I ask it to reload its config, even
> though I have a very basic test setup:
>
> area 0.0.0.0 {
> interface em0 { passive }
> interface vether0
> }
>
> Fixing ospf
Ok (for what it's worth).
On Sun, Nov 05, 2017 at 03:50:42PM +0100, Jeremie Courreges-Anglas wrote:
>
> ospf6d consistently fails when I ask it to reload its config, even
> though I have a very basic test setup:
>
> area 0.0.0.0 {
> interface em0 { passive }
> interface vether0
>
OK
On 2017 Nov 05 (Sun) at 15:50:42 +0100 (+0100), Jeremie Courreges-Anglas wrote:
:
:ospf6d consistently fails when I ask it to reload its config, even
:though I have a very basic test setup:
:
:area 0.0.0.0 {
:interface em0 { passive }
:interface vether0
:}
:
:Fixing ospf6d does
ospf6d consistently fails when I ask it to reload its config, even
though I have a very basic test setup:
area 0.0.0.0 {
interface em0 { passive }
interface vether0
}
Fixing ospf6d doesn't seem trivial. Having it fail and exit doesn't
seem to be a sufficient incentive, so I prop