To test your RIP code, and especially to create RIP transmissions that will excercise your RIPprovider, I have created three special programs.
captures real RIP output from a live system which uses RIP.
Since this must listen at the privileged RIP port 520,
it can only be used by root.
It saves the output in a special
which also encapsulates the source and timing of the data.
and sends it to a host and port of your choosing.
takes a text file in a special format,
and creates a
which can then be input to
The formats of the special files are as follows:
RIP session file
RIP session text file
T 18143 S 188.8.131.52 5555 R 184.108.40.206 255.255.254.0 0.0.0.0 7 R 220.127.116.11 255.255.255.0 0.0.0.0 1 R 18.104.22.168 255.255.254.0 0.0.0.0 5 T 18567 S 22.214.171.124 5555 R 126.96.36.199 255.255.254.0 188.8.131.52 3 R 184.108.40.206 255.255.254.0 0.0.0.0 7 T 0
RIPcreatorprogram to make a scatter file.
java RIPcreator scatter.txt scatter
RIPscatterprogram from your scatter file.
That is, if you run on studsys and send to netlab-a,
java RIPscatter srcHost srcPort dstHost dstPort scatter
while at the same time perhaps running on netlab-a:
java RIPscatter studsys 5555 netlab-a 6666 scatter
java RIPgather netlab-a 6666 scatter.new
The scatter.new file collected on netlab-a should be identical to the scatter file from which it was derived, except that possibly the sending host name and port has changed.
Of course what you really want is to run your own listener,
That was the point of creating these programs.
I suggest you create scatter.txt files that show systems becoming uncreachable, metrics increasing or decreasing, and so on.
You can leave your listener running, create a new file to test it,
RIPcreate/RIPscatter on that file.
Please realize that you can have
use the "limited-broadcast" address 255.255.255.255,
as long as you run them on different machines.
This would look like:
and when done you will expect someFile and someOtherFile to be the same.
on netlab-a: java RIPscatter localhost 4321 255.255.255.255 6666 someFile on netlab-b: java RIPgather 255.255.255.255 6666 someOtherFile
If you notice that broadcasting on netlab-a, say, does not reach studsys, you might stop and contemplate what the phrase "limited broadcast address" means.
There are some saved sesssion files already here: you can retrieve them into your own directory (they are binary, so you have to save them appropriately). Their lengths are shown preceding the name. The first one is the text file that created the second one: note that
The others were obtained from gather, and the name shoud give you an idea of how they were saved.
260 session.txt The remainder of these files are binary: download them by right-clicking and saving. 140 session 2280 session.255.255.255.255.520 7600 session.netlab-a.6666 41800 session.speckle.520 1600 session.studsys