EIGRP Does not form neighborship

[mTaleqani]

In the current master version, EIGRPd does not work. in fact it does not send eigrp hello at all and hence no neighborship establishment happens !

[diivious]

I am successfully using the latest code - i had to disable firewalls to get the peers to form. Can you shed more light on your issue?

[mTaleqani]

using centos 6 and iptables is stopped. this is the configuration i have done :

Current configuration:
!
frr version 3.1-dev
frr defaults traditional
hostname Router
no ipv6 forwarding
hostname ospfd
hostname eigrpd
!
password zebra
enable password test
!
log stdout
!
router eigrp 1
 network 192.168.0.0/16 
!
router ospf
 ospf router-id 4.4.4.4
 network 192.168.0.0/16 area 0
 network 192.168.213.0/24 area 0

i have no problems with previous master versions but by the new updates for master version, i just wanted to test if the previous issues have been solved or not and seeing eigrpd not working at all. i tested the current master with centos 6 and 7 but no success. i see no eigrpd hellos being send or received.

[lunn]

I've seen something similar. Sometimes it sends one hello on each interface, and then no more. Other times it works. Seems like a race condition or bad usage of the timer API.

Because of #943, the daemon often does not run more than 10 seconds, so i'm prioritizing that problem first...

[diivious]

I am on CentOS7 and and did: systemctl stop firewalld systemctl disable firewalld

And was able to get peers up. But once that was working, and i got past the external route crash, I saw something odd with neighbors - it would crash when doing a "show ip eigrp nei" due to the hold timer being NULL. I was re-writing the TLV code, but will pause and spend some time and see if i can sort out why the nbr structure is not being setup completely...

[mTaleqani]

no firewall nor iptables are running. but got no success. i ran tcpdump and saw no eigrp hellos received by frr although pretty sure cisco router sends eigrp hello (frr and cisco can ping each other). since no one else having the same problem so i guess not frr problem (i think sth filtering hello packets !!) but it is weird because when i install frr master version 1 august 2017, it works with no problem but got problem with today's frr master version !!

[lunn]

Donnie

See: https://github.com/FRRouting/frr/pull/952 There could be other instances where the timer is accessed without first checking exists.

[eqvinox]

multicast joins were getting lost due to zapi socket permission problem, fixed in #969