> 7 апр. 2016 г., в 13:20, Timo Teras <[email protected]> написал(а):
> 
> On Thu, 7 Apr 2016 10:53:30 +0300
> Igor Ryzhov <[email protected]> wrote:
> 
>> I see that both times zebra is trying to add nexthop 192.168.0.1.
> 
> is this with the patch applied or not?

It's with patch applied. But I rechecked again and have different results, 
maybe I did something wrong last time.

Zebra shows the same - both routes are not in FIB:

S>  10.0.0.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 I can see both of them in kernel:

10.0.0.0/24  proto zebra  metric 20
        nexthop via 192.168.0.1  dev eth1 weight 1
        nexthop via 192.168.1.1  dev eth2 weight 1
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

> 
> I was able to reproduce the problem, but the patch fixed it for me.
> 
> Patch applied, I see is on vtysh:
> # show ip route 
> Codes: K - kernel route, C - connected, S - static, R - RIP,
>       O - OSPF, I - IS-IS, B - BGP, P - PIM, A - Babel,
>> - selected route, * - FIB route
> 
> K>* 0.0.0.0/0 via 10.252.5.129, eth0, src 10.252.5.192
> S>* 10.0.0.0/24 [1/0] via 10.252.5.130, eth0
>  *                   via 10.252.5.131, eth0
> C>* 10.252.5.128/25 is directly connected, eth0
> C>* 127.0.0.0/8 is directly connected, lo
> 
> And from command line "ip route":
> 
> 10.0.0.0/24  proto zebra  metric 20 
>       nexthop via 10.252.5.130  dev eth0 weight 1
>       nexthop via 10.252.5.131  dev eth0 weight 1
> 
> Could you also try that if after adding the static routes, writing
> config to disk, and restarting the zebra daemon it acts differently?

After saving the configuration and restarting zebra everything is ok:

S>* 10.0.0.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

> 
> Thanks,
> Timo


_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev

Reply via email to