[quagga-dev 4590] ospfd placing incorrect routes into the routing table

Mario Kinsman mario.kinsman at gmail.com
Mon Feb 26 18:42:33 GMT 2007


Hello,

Has anyone heard of an issue where ospfd places routes into the routing
table that
contain an incorrect next hop for the destination network?
I am having an issue where I have 3 gre over IPSec tunnels set up on 4
different machines
all running fedora 6. My setup is below. Note for instance in the Augusta
routing table,
route to 172.16.101.9 points to next hop of 172.16.101.18 when it should
point to 172.16.101.6
since that is the next hop to the Arlington box where 172.16.101.9 lives but
instead it is pointing
through the Ashburn box. this is happening on multiple boxes for multiple
routes. Is this a bug?
Or is it a config error on my part. This config is pretty straight forward,
I dont see where I have made any error.
I am using Quagga V0.98.6.

Thank you in advance for your time,
Mario Kinsman


Augusta
tunnel0:172.16.101.5
tunnel1:172.16.101.17
tunnel2:172.16.101.21
network 172.16.101.5/32 area 0.0.0.0
network 172.16.101.17/32 area 0.0.0.0
network 172.16.101.21/32 area 0.0.0.0

route table:

172.16.101.21   172.16.101.22   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.5    172.16.101.6    255.255.255.255 UGH   34     0        0
tunnel0
172.16.101.22   0.0.0.0         255.255.255.255 UH    0      0        0
tunnel2
172.16.101.6    0.0.0.0         255.255.255.255 UH    0      0        0
tunnel0
172.16.101.17   172.16.101.18   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.18   0.0.0.0         255.255.255.255 UH    0      0        0
tunnel1
172.16.101.13   172.16.101.22   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.14   172.16.101.6    255.255.255.255 UGH   34     0        0
tunnel0
172.16.101.9    172.16.101.18   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.25   172.16.101.22   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.26   172.16.101.18   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.10   172.16.101.6    255.255.255.255 UGH   34     0        0
tunnel0


Arlington
tunnel0:172.16.101.6
tunnel1:172.16.101.9
tunnel2:172.16.101.13
network 172.16.101.6/32 area 0.0.0.0
network 172.16.101.9/32 area 0.0.0.0
network 172.16.101.13/32 area 0.0.0.0

route table:

172.16.101.21   172.16.101.14   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.5    0.0.0.0         255.255.255.255 UH    0      0        0
tunnel0
172.16.101.22   172.16.101.5    255.255.255.255 UGH   34     0        0
tunnel0
172.16.101.6    172.16.101.5    255.255.255.255 UGH   34     0        0
tunnel0
172.16.101.17   172.16.101.10   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.18   172.16.101.5    255.255.255.255 UGH   34     0        0
tunnel0
172.16.101.13   172.16.101.14   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.14   0.0.0.0         255.255.255.255 UH    0      0        0
tunnel2
172.16.101.9    172.16.101.10   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.25   172.16.101.14   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.26   172.16.101.10   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.10   0.0.0.0         255.255.255.255 UH    0      0        0
tunnel1

Ashburn
tunnel0:172.16.101.10
tunnel1:172.16.101.18
tunnel2:172.16.101.25
network 10.200.0.0/16 area 0.0.0.0
network 172.16.101.10/32 area 0.0.0.0
network 172.16.101.18/32 area 0.0.0.0
network 172.16.101.25/32 area 0.0.0.0

route table:

172.16.101.21   172.16.101.26   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.5    172.16.101.9    255.255.255.255 UGH   34     0        0
tunnel0
172.16.101.22   172.16.101.17   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.6    172.16.101.17   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.17   0.0.0.0         255.255.255.255 UH    0      0        0
tunnel1
172.16.101.18   172.16.101.17   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.13   172.16.101.26   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.14   172.16.101.9    255.255.255.255 UGH   34     0        0
tunnel0
172.16.101.25   172.16.101.26   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.9    0.0.0.0         255.255.255.255 UH    0      0        0
tunnel0
172.16.101.10   172.16.101.9    255.255.255.255 UGH   34     0        0
tunnel0
172.16.101.26   0.0.0.0         255.255.255.255 UH    0      0        0
tunnel2

Manila
tunnel0:172.16.101.14
tunnel1:172.16.101.22
tunnel2:172.16.101.26
network 172.16.101.14/32 area 0.0.0.0
network 172.16.101.22/32 area 0.0.0.0
network 172.16.101.26/32 area 0.0.0.0

route table:

172.16.101.5    172.16.101.13   255.255.255.255 UGH   34     0        0
tunnel0
172.16.101.21   0.0.0.0         255.255.255.255 UH    0      0        0
tunnel1
172.16.101.22   172.16.101.21   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.6    172.16.101.21   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.17   172.16.101.25   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.18   172.16.101.21   255.255.255.255 UGH   34     0        0
tunnel1
172.16.101.13   0.0.0.0         255.255.255.255 UH    0      0        0
tunnel0
172.16.101.14   172.16.101.13   255.255.255.255 UGH   34     0        0
tunnel0
172.16.101.9    172.16.101.25   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.25   0.0.0.0         255.255.255.255 UH    0      0        0
tunnel2
172.16.101.26   172.16.101.25   255.255.255.255 UGH   34     0        0
tunnel2
172.16.101.10   172.16.101.13   255.255.255.255 UGH   34     0        0
tunnel0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-dev/attachments/20070226/5bf70366/attachment-0001.html>


More information about the Quagga-dev mailing list