PDA

View Full Version : RIP Problems on V3 1.1.14 and Wrap

butchkemper
10-15-2007, 02:56 PM
I have a wrap board running V3 1.1.14 that is experiencing some kind of problem that causes a reboot. Sometimes, when the board reboots, the RIP routing does not come back up correctly. Here is what I have found:

RIP is running and has received the routes from all the neighbors. This is verified with a sho ip rip command.
The Kernel routing table only contains entries for the two connected interfaces. This is verified by looking at the Advanced -. System Reports -> View System Information and looking at the routing table.
An Activate Changes causes RIP to restart and then all the RIP routes show up in the Kernel routing table


The RIP configuration contains:

Router RIP
redistribute kernel
redistribute static
redistribute connected
version 2
network 205.247.118.0/24
neighbor 205.257.118.17
neighbor 205.247.118.21
neighbor 205.247.118.22
neighbor 205.247.118.42

My primary interest is why does the RIP process fail to insert the routes into the kernel? While I am searching for the solution, I am going to reinstall static routes in this machine.

Is the Quagga in V3 1.1.14 the same as V3 1.3.4?

Any suggestions would be appreciated.

Butch
lonnie
10-15-2007, 05:22 PM
The scripting is different so there are differences.

Can I ask why you use neighbour statements? We just run network 0.0.0.0/0 and it figures it all out. I do use discrete network statements when I do not want to announce a device.
butchkemper
10-15-2007, 05:30 PM
The neighbor statement forces unicast mode and I seemed to remember a problem with multicast and routing protocols over the wireless links.

Butch
lonnie
10-15-2007, 05:38 PM
The 1.3.4+ and onward have no multicast problems.

Your setup is not an error, I was just curious, since we do not use anything like that and it "just works".
gunther_01
10-15-2007, 09:33 PM
The 1.3.4+ and onward have no multicast problems.


Sorry to jump in here. But the neighbor statement with latest releases.

If it ain't broke don't fix it kind of thing? Since I too have those statments added for my network.
lonnie
10-16-2007, 12:44 AM
Sure, the statements will certainly not break anything. For the same reasoning, since my network is working fine, I would not add the statements.
butchkemper
10-16-2007, 05:55 AM
Is the Quagga in V3 1.1.14 the same as V3 1.3.4?
Butch

When I click on the CONFIGURE button and the RIP process prompts for a password, the software version is displayed. So to answer my own question:

V3 1.1.14 has Quagga 0.99.6
v3 1.3.5 has Quagga 0.99.7


Butch
lonnie
10-16-2007, 08:08 AM
1.1.xx series is complete and Tony was only adding the SNMP fix and a few other essentials.

Updates to programs are in the 1.3.xx series, and in fact 1.1.14 represents that last of a line. No further release is planned.

At this time we are using 1.3.0+ in our network and it is the only version we are working on for fixes and enhancements.