Hi All;
I apologize in advance if this is a poor place to report a bug. The
manpage and REPORTING-BUGS file say to send bugs to bug-zebra@gnu.org,
which just doesn't seem like the right place to report a quagga bug.
I run a pair of route servers for the MaineExchangePoint, and have been
running Zebra on them for the last couple of years. Last week I attempted
to switch to Quagga 0.96.3. With the same configuration file, peers with
quagga get next-hops of the quagga route server instead of the appropriate
peer.
For example, AS65501 has interface 192.68.0.1 and peers with a quagga
route server 192.168.0.2 (AS65502). 65501 passes a route for
192.168.1.0/24 to AS65502. AS65503 at 192.168.0.3 peers with the route
server as well, and receives the route.
192.168.0.2, being a route server, has transparent-as turned on with both
peers. The idea is to get the routers to pass traffic to each other, that
the route server just exchanges routes with the peers.
With zebra, 192.168.0.3 sees the route to 192.168.1.0 through AS65501 with
a next hop of 192.168.0.1. This is how it should be.
With the same config file and quagga, 198.168.32.145 sees a route to
192.168.1.0 through AS65501 as it should, but the next-hop is the route
server (192.168.0.2) instead of the router.
This is definitely a problem.
Suggestions welcome. RTFM welcome if anyone points out TFM to R.
Thanks,
--- David
I apologize in advance if this is a poor place to report a bug. The
manpage and REPORTING-BUGS file say to send bugs to bug-zebra@gnu.org,
which just doesn't seem like the right place to report a quagga bug.
I run a pair of route servers for the MaineExchangePoint, and have been
running Zebra on them for the last couple of years. Last week I attempted
to switch to Quagga 0.96.3. With the same configuration file, peers with
quagga get next-hops of the quagga route server instead of the appropriate
peer.
For example, AS65501 has interface 192.68.0.1 and peers with a quagga
route server 192.168.0.2 (AS65502). 65501 passes a route for
192.168.1.0/24 to AS65502. AS65503 at 192.168.0.3 peers with the route
server as well, and receives the route.
192.168.0.2, being a route server, has transparent-as turned on with both
peers. The idea is to get the routers to pass traffic to each other, that
the route server just exchanges routes with the peers.
With zebra, 192.168.0.3 sees the route to 192.168.1.0 through AS65501 with
a next hop of 192.168.0.1. This is how it should be.
With the same config file and quagga, 198.168.32.145 sees a route to
192.168.1.0 through AS65501 as it should, but the next-hop is the route
server (192.168.0.2) instead of the router.
This is definitely a problem.
Suggestions welcome. RTFM welcome if anyone points out TFM to R.
Thanks,
--- David