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=431
------- Additional Comments From web@pilot.org.ua 2008-02-20 14:55 -------
There is a simple testcase to present the current queueing problem:
1. Enable zebra debug rib and figure out the order in which kernel routes get
imported into RIB (this depends on a patch committed after 0.99.9 release). Pick
2 connected routes N1 (imported former) and N2 (imported latter).
2. Put a static route into zebra.conf, which would address N1 via a gateway on N2.
3. Start zebra and see routing record like:
S 10.0.0.4/30 [1/0] via 192.168.3.1 inactive
C>* 10.0.0.4/30 is directly connected, em1
C>* 192.168.3.0/24 is directly connected, vlan3900
NEXTHOP_FLAG_ACTIVE isn't always computed properly for such nexthops. This issue
is just a cosmetic one, but the rest of odd effects is caused by the same RIB
queue processing procedures.
------- 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=431
------- Additional Comments From web@pilot.org.ua 2008-02-20 14:55 -------
There is a simple testcase to present the current queueing problem:
1. Enable zebra debug rib and figure out the order in which kernel routes get
imported into RIB (this depends on a patch committed after 0.99.9 release). Pick
2 connected routes N1 (imported former) and N2 (imported latter).
2. Put a static route into zebra.conf, which would address N1 via a gateway on N2.
3. Start zebra and see routing record like:
S 10.0.0.4/30 [1/0] via 192.168.3.1 inactive
C>* 10.0.0.4/30 is directly connected, em1
C>* 192.168.3.0/24 is directly connected, vlan3900
NEXTHOP_FLAG_ACTIVE isn't always computed properly for such nexthops. This issue
is just a cosmetic one, but the rest of odd effects is caused by the same RIB
queue processing procedures.
------- 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