View Full Version : RIP on StarV3 to RIP on Linux box.
DrLove73
01-23-2008, 09:10 AM
I need to connect RIP between StarV3 na Linux box (ClarkConnect = RHEL 4).
What needs to be set?
I turned on RIP on StarV3 units, and they are communicating with each other and with ADSL modem, but not with CC box.
Quagga on CC box is 0.98.3
Log is empty.
ripd.conf is:
Current configuration:
!
hostname kostana.alcom-group.net
password xxxxxxx
log file /var/log/ripd.log
log stdout
!
router rip
redistribute kernel
redistribute connected
redistribute static
network eth1
!
line vty
!
end
DrLove73
01-23-2008, 09:26 AM
When I monitor from terminal, I get this message:
RIP: update timer fire!
DrLove73
01-23-2008, 09:53 AM
Problem is not solved. take a look at the lower post.
Problem solved! It was a password issue.
When you install quagga, common sense dictates to change password in conf files: rip.conf,... You also need to cange password in zebra.conf, so she can connect to other daemons.
zebra.conf:
hostname kostana.alcom-group.net
password xxxxxxx
enable password xxxxxxx
log file /var/log/quagga/zebra.log
DrLove73
01-23-2008, 11:27 AM
I was celebrating to soon. RIP just shows me routes from his own system.
I have 2 Linux boxes, 4 StarV3 and 1 ADSL modem, all on the same subnet. Linux boxes do not talk neither between them selfs, nor with the rest. StarV3 and ADSL modem talk RIP just fine.
Does anybody have any experience with this?
Does passwords need to be the same on all RIP systems? I am out of time, so I will try this latter.
You may want to upgrade to Quagga 0.99.9 which resolves a lot of issues in 0.98.x
The password is only the password used to log into your local quagga configuration (remotely or otherwise), and can be different for each system.
DrLove73
01-23-2008, 03:47 PM
OK. I will have to find and download that new version.
Is different version solely responsible for this lack of communication and will resolve my problem (as far as you know)?
c.davis
01-23-2008, 05:41 PM
You can also try to 'push' RIP announcements between the boxes.
In the router-rip configuration area you can announce to specific targets:
neighbour 1.1.1.1
Replace 1.1.1.1 with the ip of the box you wish to announce to.
I cannot say for sure, but without you using the latest (known working) release, it's tough to troubleshoot. We have seen many issues with the 0.98.x 'stable' release in regards to rip, and other things that were fixed in the new 0.99.x releases.
OK. I will have to find and download that new version.
Is different version solely responsible for this lack of communication and will resolve my problem (as far as you know)?