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
web@pilot.org.ua changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|a new connected route |changing address on an
|doesn't activate existing |existing interface doesn't
|static routes, although |cause existing static routes
|ought to |to be revalidated
OS/Version|FreeBSD |All
Severity|normal |major
------- Additional Comments From web@pilot.org.ua 2007-11-09 08:55 -------
My recent research seems to prove, that the problem is OS-agnostic. There are
three cases, which I can reproduce on both FreeBSD and Linux. All of them are
constituted by a zebra daemon with some static routes configured.
A. Existing nexthop.
Starting zebra in a preconfigured environment, which has the nexthop of the
configured static routes reachable via a connected route results in those
statics being activated normally.
B. New interface being brought up.
Having zebra daemon running with configured static routes, we bring an interface
up, which makes the nexthop of the inactive statics reachable. All appropriate
statics get activated.
C. Changing address on an existing interface.
Having zebra daemon running, we change IP address of one of existing UP
interfaces so, that the new connected prefix covers nexthop(s) of some
configured, but inactive routes. A new connected route replaced the old one
and... nothing happens. At least before we make any further changes in the
connected routes set.
------- 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=418
web@pilot.org.ua changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|a new connected route |changing address on an
|doesn't activate existing |existing interface doesn't
|static routes, although |cause existing static routes
|ought to |to be revalidated
OS/Version|FreeBSD |All
Severity|normal |major
------- Additional Comments From web@pilot.org.ua 2007-11-09 08:55 -------
My recent research seems to prove, that the problem is OS-agnostic. There are
three cases, which I can reproduce on both FreeBSD and Linux. All of them are
constituted by a zebra daemon with some static routes configured.
A. Existing nexthop.
Starting zebra in a preconfigured environment, which has the nexthop of the
configured static routes reachable via a connected route results in those
statics being activated normally.
B. New interface being brought up.
Having zebra daemon running with configured static routes, we bring an interface
up, which makes the nexthop of the inactive statics reachable. All appropriate
statics get activated.
C. Changing address on an existing interface.
Having zebra daemon running, we change IP address of one of existing UP
interfaces so, that the new connected prefix covers nexthop(s) of some
configured, but inactive routes. A new connected route replaced the old one
and... nothing happens. At least before we make any further changes in the
connected routes set.
------- 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