From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4.1) Gecko/20020314 Netscape6/6.2.2 Description of problem: Zebra does not update kernel routing table from learned rip v2 updates. show ip route and show ip rip report the expected routes but route -n does not reflect learned routes. Additionally, When a tunnel is added via hercules zebra deletes the default route. zebra and ripd are the only routeing protocl daemons running. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Start zebra on a network that is known to send multicast ripv2 routes 2.Start ripd on same 3. Actual Results: No routes are added Expected Results: route command should show same routes as show ip route issued from zebra vty. Additional info: Note The same level of zebra/ripd work fine on a slackware based box at the same kernel level 2.4.18 and zebra-0.92a
Your best bet for a quick solution is probably to ask upstream - the zebra mailing list etc.
Have you verified functionality at the given levels ?
nope.
Then what am I supposed to go to the zebra site with ? It works on slackware not on RedHat ? What suggestions do you suppose I'll get ?
The zebra site will put you in touch with people who know zebra from the ground up, and others who may be experiencing the same problem. I can do neither.
I have a similar problem on RH 8.0 beta. It appears that Zebra 0.92a has a problem. Versions 0.91a and 0.93a do not have this problem. It relates to the fact that it considers the RIP routes coming from a non-active link, *because* that link is a kernel route. We have remade the RH rpm with 0.93a and now it works!
I have seen this issue with many recent versions myself. Been perplexing trying to identify root cause, but restarting network and bgpd resolves it every time. Not a very good work around for a routing daemon.
Forgot to mention with bgp routes :-) And yes I do see them in the bgp table.
Red Hat Linux 7.3 is no longer supported. If you can reproduce this problem with a currently supported product, please open a new bug report.