Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Quagga: Bugs

[Bug 418] New: a new connected route doesn't activate existing static routes, although ought to

 

 

Quagga bugs RSS feed   Index | Next | Previous | View Threaded


bugzilla-daemon at allevil

Nov 1, 2007, 10:04 AM

Post #1 of 1 (1562 views)
Permalink
[Bug 418] New: a new connected route doesn't activate existing static routes, although ought to

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=418

Summary: a new connected route doesn't activate existing static
routes, although ought to
Product: Quagga
Version: 0.99.9
Platform: All
OS/Version: FreeBSD
Status: NEW
Severity: normal
Priority: Medium
Component: zebra
AssignedTo: web [at] pilot
ReportedBy: web [at] pilot
CC: paul [at] dishone,wawa [at] yandex-team


The configuration in question is as follows:
ip route 192.168.0.0/24 10.0.0.2
ip route 192.168.1.0/24 10.0.0.2
ip route 192.168.2.0/24 10.0.0.2
ip route 192.168.3.0/24 10.0.0.2
ip route 192.168.4.0/24 10.0.0.2
ip route 192.168.5.0/24 10.0.0.2
ip route 192.168.6.0/24 10.0.0.2
ip route 192.168.7.0/24 10.0.0.2
ip route 192.168.8.0/24 10.0.0.2
ip route 192.168.9.0/24 10.0.0.2

At the time zebra starts the nexthop 10.0.0.2 isn't reachable, hence the routes
are naturally inactive:
S 192.168.0.0/24 [1/0] via 10.0.0.2 inactive
S 192.168.1.0/24 [1/0] via 10.0.0.2 inactive
S 192.168.2.0/24 [1/0] via 10.0.0.2 inactive
S 192.168.3.0/24 [1/0] via 10.0.0.2 inactive
S 192.168.4.0/24 [1/0] via 10.0.0.2 inactive
S 192.168.5.0/24 [1/0] via 10.0.0.2 inactive
S 192.168.6.0/24 [1/0] via 10.0.0.2 inactive
S 192.168.7.0/24 [1/0] via 10.0.0.2 inactive
S 192.168.8.0/24 [1/0] via 10.0.0.2 inactive
S 192.168.9.0/24 [1/0] via 10.0.0.2 inactive

After that we configure an interface with 10.0.0.1/30 IP address. This new
connected route gets learned, but 10 static routes still remain inactive.

The sequence has been repeated on a Linux box and resulted in a proper behaviour:

ip route 192.168.0.0/24 10.0.0.5
ip route 192.168.1.0/24 10.0.0.5
ip route 192.168.2.0/24 10.0.0.5
ip route 192.168.3.0/24 10.0.0.5
ip route 192.168.4.0/24 10.0.0.5
ip route 192.168.5.0/24 10.0.0.5
ip route 192.168.6.0/24 10.0.0.5
ip route 192.168.7.0/24 10.0.0.5
ip route 192.168.8.0/24 10.0.0.5
ip route 192.168.9.0/24 10.0.0.5


S 192.168.0.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.1.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.2.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.3.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.4.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.5.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.6.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.7.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.8.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.9.0/24 [1/0] via 10.0.0.5 inactive

Now I configure 10.0.0.6/30 at a local interface, the new connected route gets
learned and static routes get updated:

C>* 10.0.0.4/30 is directly connected, test
S>* 192.168.0.0/24 [1/0] via 10.0.0.5, test
S>* 192.168.1.0/24 [1/0] via 10.0.0.5, test
S>* 192.168.2.0/24 [1/0] via 10.0.0.5, test
S>* 192.168.3.0/24 [1/0] via 10.0.0.5, test
S>* 192.168.4.0/24 [1/0] via 10.0.0.5, test
S>* 192.168.5.0/24 [1/0] via 10.0.0.5, test
S>* 192.168.6.0/24 [1/0] via 10.0.0.5, test
S>* 192.168.7.0/24 [1/0] via 10.0.0.5, test
S>* 192.168.8.0/24 [1/0] via 10.0.0.5, test
S>* 192.168.9.0/24 [1/0] via 10.0.0.5, test

After unconfiguring 10.0.0.6 from the interface things revert back:
S 192.168.0.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.1.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.2.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.3.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.4.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.5.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.6.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.7.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.8.0/24 [1/0] via 10.0.0.5 inactive
S 192.168.9.0/24 [1/0] via 10.0.0.5 inactive



------- 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 [at] lists
http://lists.quagga.net/mailman/listinfo/quagga-bugs

Quagga bugs RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.