> 7 апр. 2016 г., в 7:10, Timo Teras <[email protected]> написал(а): > > 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?
Yes, I am using Ubuntu 14.04 (kernel 3.13.0-83) and netlink. > > 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. Apr 7 10:43:06 vm zebra[749]: vty[14]@::1(config)# ip route 1.2.3.0/24 192.168.0.1 Apr 7 10:43:06 vm zebra[749]: rib_link: 1.2.3.0/24 vrf 0: rn 0x936860, rib 0x9398e0 Apr 7 10:43:06 vm zebra[749]: rib_link: 1.2.3.0/24 vrf 0: adding dest to table Apr 7 10:43:06 vm zebra[749]: rib_queue_add: 1.2.3.0/24 vrf 0: work queue added Apr 7 10:43:06 vm zebra[749]: rib_meta_queue_add: 1.2.3.0/24 vrf 0: queued rn 0x936860 into sub-queue 1 Apr 7 10:43:06 vm zebra[749]: rib_queue_add: 1.2.3.0/24 vrf 0: rn 0x936860 queued Apr 7 10:43:06 vm zebra[749]: netlink_route_multipath() (single hop): RTM_NEWROUTE 1.2.3.0/24 vrf 0 type IPv4 nexthop Apr 7 10:43:06 vm zebra[749]: netlink_route_multipath() (single hop): nexthop via 192.168.0.1 if 3 Apr 7 10:43:06 vm zebra[749]: netlink_talk: netlink-cmd (vrf 0) type RTM_NEWROUTE(24), seq=6 Apr 7 10:43:06 vm zebra[749]: netlink_parse_info: netlink-cmd (vrf 0) ACK: type=RTM_NEWROUTE(24), seq=6, pid=0 Apr 7 10:43:06 vm zebra[749]: rib_process: 1.2.3.0/24 vrf 0: rn 0x936860 dequeued Apr 7 10:43:39 vm zebra[749]: vty[14]@::1(config)# ip route 1.2.3.0/24 192.168.1.1 Apr 7 10:43:39 vm zebra[749]: rib_queue_add: 1.2.3.0/24 vrf 0: work queue added Apr 7 10:43:39 vm zebra[749]: rib_meta_queue_add: 1.2.3.0/24 vrf 0: queued rn 0x936860 into sub-queue 1 Apr 7 10:43:39 vm zebra[749]: rib_queue_add: 1.2.3.0/24 vrf 0: rn 0x936860 queued Apr 7 10:43:39 vm zebra[749]: netlink_route_multipath() (single hop): RTM_NEWROUTE 1.2.3.0/24 vrf 0 type IPv4 nexthop Apr 7 10:43:39 vm zebra[749]: netlink_route_multipath() (single hop): nexthop via 192.168.0.1 if 3 Apr 7 10:43:39 vm zebra[749]: netlink_talk: netlink-cmd (vrf 0) type RTM_NEWROUTE(24), seq=7 Apr 7 10:43:39 vm zebra[749]: netlink_parse_info: netlink-cmd (vrf 0) ACK: type=RTM_NEWROUTE(24), seq=7, pid=0 Apr 7 10:43:39 vm zebra[749]: rib_process: 1.2.3.0/24 vrf 0: rn 0x936860 dequeued I see that both times zebra is trying to add nexthop 192.168.0.1. > > Thanks, > Timo _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
