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=377
------- Additional Comments From jrhett@netconsonance.com 2008-05-14 19:36 -------
"Routing next-hops of a protocol via that same protocol is not supported. It
seems suspect conceptually, even if one can find certain scenarios where it
might appear to work."
Uh... major providers require this as a setup. See the Cogent installation
instructions for example. You peer with your next hop, who gives you only a /32
route to the BGP speaker who will give you all of your routes.
------- 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=377
------- Additional Comments From jrhett@netconsonance.com 2008-05-14 19:36 -------
"Routing next-hops of a protocol via that same protocol is not supported. It
seems suspect conceptually, even if one can find certain scenarios where it
might appear to work."
Uh... major providers require this as a setup. See the Cogent installation
instructions for example. You peer with your next hop, who gives you only a /32
route to the BGP speaker who will give you all of your routes.
------- 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