Hi! Is there something with these versions that is not compatibly with each other for the ospf to work in ipv6? Right now I have a bird 1.3.8 instance neither announce nor getting an routes in a area. It is stuck in the exchange state. The ip4 versions also get stuck in the loading state for a while and then continue. (during the loading state the routes are announced to the others - so it's working somewhat). -- //fredan
On Thu, Aug 30, 2012 at 09:12:30PM +0200, fredrik danerklint wrote:
Hi!
Is there something with these versions that is not compatibly with each other for the ospf to work in ipv6?
Right now I have a bird 1.3.8 instance neither announce nor getting an routes in a area. It is stuck in the exchange state.
OSPF on IPv6 between 1.3.6 and 1.3.8 works for me without any problems. Some more details? Is it stuck always even after BIRD restart? -- 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."
I've had the wrong mtu size of some of the instances. After changing that, everything works again. The strange part is though that bird has accepted this mismatch until version 1.3.8 without (?) any problem. 2012-08-31 14:48, Ondrej Zajicek skrev:
On Thu, Aug 30, 2012 at 09:12:30PM +0200, fredrik danerklint wrote:
Hi!
Is there something with these versions that is not compatibly with each other for the ospf to work in ipv6?
Right now I have a bird 1.3.8 instance neither announce nor getting an routes in a area. It is stuck in the exchange state.
OSPF on IPv6 between 1.3.6 and 1.3.8 works for me without any problems. Some more details? Is it stuck always even after BIRD restart?
-- //fredan
On Sat, Sep 08, 2012 at 04:59:57PM +0200, fredrik danerklint wrote:
I've had the wrong mtu size of some of the instances. After changing that, everything works again.
The strange part is though that bird has accepted this mismatch until version 1.3.8 without (?) any problem.
We added warning (OSPF: MTU mismatch with neighbour ...), but i don't see any change that would cause this problem with mismatched MTUs. -- 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."
participants (2)
-
fredrik danerklint -
Ondrej Zajicek