On Thu, 7 Apr 2016 01:36:03 +0300 Igor Ryzhov <[email protected]> wrote:
> Thank you for the patch, but it doesn't fix the problem. > And things are more strange now. > > Zebra shows that it didn't add any of the two routes to the FIB: > > S> 1.2.3.0/24 [1/0] via 192.168.0.1, eth1 > via 192.168.1.1, eth2 > C>* 192.168.0.0/24 is directly connected, eth1 > C>* 192.168.1.0/24 is directly connected, eth2 > > But in the same time I see the first one in kernel routing table: > > 1.2.3.0/24 via 192.168.0.1 dev eth1 proto zebra metric 20 > 192.168.0.0/24 dev eth1 proto kernel scope link src > 192.168.0.101 192.168.1.0/24 dev eth2 proto kernel scope link src > 192.168.1.101 Is this on Linux? Is it using socket or netlink routing interface? Could you enable via vtysh: debug zebra events debug zebra kernel debug zebra rib debug zebra rib queue and "log syslog" or "log stdout" to capture logs. And report the full debug log here. Thanks, Timo _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
