I think there may be a bug in our Fortigate. It has the ability to disable the MTU check in IPv4 so I could get IPv4 up, but no joy on IPv6. Anyway, thank you, I have my answer. The way to solve this is to do the correct thing. d On Sun, Sep 24, 2017 at 10:01 AM, Ondrej Zajicek <santiago@crfreenet.org> wrote:

On Thu, Sep 21, 2017 at 11:08:47AM -0600, Derek Andrew wrote:

...

We are running BIRD and BIRD6 to manage our BFD and OSPF relationship on our DNS servers.

We moved the DNS servers onto a Fortigate firewall. I was able to get the BIRD daemon running, but BIRD6 is complaining about an MTU mismatch with the neighbour.

Is there any way to tell BIRD to ignore the MTU? The OSPF status is showing the neighbour is in the Exchange state.

No, checking MTU is required by OSPF standard. Why do you have inconsistent MTU? Also, it should be noticed by both IPv4 and IPv6 versions.

-- Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."

-- Copyright 2017 Derek Andrew (excluding quotations) +1 306 966 4808 Communication and Network Services Information and Communications Technology Infrastructure Services *University of Saskatchewan*Peterson 120; 54 Innovation Boulevard Saskatoon,Saskatchewan,Canada. S7N 2V3 Timezone GMT-6 Typed but not read.