Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.
http://bugzilla.quagga.net/show_bug.cgi?id=364
Summary: Old IP adresses sometimes prevent OSPF routes being
accepted
Product: Quagga
Version: 0.99.7
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: Medium
Component: ospfd
AssignedTo: maintainers@quagga.net
ReportedBy: mattilinnanvuori@yahoo.com
Previous IP addresses on an interface sometimes disturb OSPF routing.
In vtysh console (show ip route) this is seen as a kernel route that is directly
connected, when the computer in question does not accept the correct route of
the same network from another computer.
In the next example, 192.168.0.0/24 is an old network that does not exist in
Linux any more.
show ip route
...
K>* 192.168.0.0/24 is directly connected, eth2
O 192.168.1.0/24 [110/10] is directly connected, eth2, 00:27:38
C>* 192.168.1.0/24 is directly connected, eth2
K * 192.168.1.0/24 is directly connected, eth2
...
route -n
...
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
...
# ip addr show eth2
4: eth2: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:0d:88:c5:e0:c4 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global eth2
Even when the interface in question is configured again with other IP addresses
or all of its IP addresses are flushed, it does not help. Restarting ospfd and
zebra processes helps, but that is undesired because it breaks down routing for
a moment.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
Quagga-bugs mailing list
Quagga-bugs@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-bugs
comments should be made in the comments box of this bug
report.
http://bugzilla.quagga.net/show_bug.cgi?id=364
Summary: Old IP adresses sometimes prevent OSPF routes being
accepted
Product: Quagga
Version: 0.99.7
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: Medium
Component: ospfd
AssignedTo: maintainers@quagga.net
ReportedBy: mattilinnanvuori@yahoo.com
Previous IP addresses on an interface sometimes disturb OSPF routing.
In vtysh console (show ip route) this is seen as a kernel route that is directly
connected, when the computer in question does not accept the correct route of
the same network from another computer.
In the next example, 192.168.0.0/24 is an old network that does not exist in
Linux any more.
show ip route
...
K>* 192.168.0.0/24 is directly connected, eth2
O 192.168.1.0/24 [110/10] is directly connected, eth2, 00:27:38
C>* 192.168.1.0/24 is directly connected, eth2
K * 192.168.1.0/24 is directly connected, eth2
...
route -n
...
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
...
# ip addr show eth2
4: eth2: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:0d:88:c5:e0:c4 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global eth2
Even when the interface in question is configured again with other IP addresses
or all of its IP addresses are flushed, it does not help. Restarting ospfd and
zebra processes helps, but that is undesired because it breaks down routing for
a moment.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
Quagga-bugs mailing list
Quagga-bugs@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-bugs