[Xorp-users] XORP RIP enabled. Why are static routes required?

Swati Sinha Deb Swati.SinhaDeb@bristol.ac.uk
Wed, 27 Apr 2005 11:28:58 +0100


Hi Pavlin,

Thank you for all your help in fixing this issue. The issue was actually 
with the firewall settings as suggested by you. I have disabled the 
firewall settings and it started working.

Many thanks again.

Regards,
Swati



> Swati,
>
> Thanks for the detailed info. Everything looks fine, so
> unfortunately it is not getting any easier :)
>
> Before getting into the business of debugging the FEA, I'd like to
> eliminate one more suspect for the RIP packets delivery problem: the
> kernel. For example, if there are any, say, firewall rules or
> anything else that may be filtering the RIP packets.
>
> To do so, I'd like to ask you to use a very simple (and archaic)
> program just for the sake of sending and receiving multicast packets
> by using the RIPv2 multicast address and port number (224.0.0.9 and
> 520 respectively). Below are the
> instructions how to do this:
>
> 1. Go to http://netweb.usc.edu/pim/pimd/
>    and download mtest.tar.gz
>
> 2. Untar and compile mtest.tar.gz :
>
> tar zxvf mtest.tar.gz
> cd mtest
> gmake
>
>   Now you should have two binaries: msend (the sender), and mrcv
>   (the receiver).
>
>   Copy msend to Router1's file system, and mrcv to Router2's file
>   system.
>
> 3. Start as root the receiver on Router2's interface eth1. Note that
> you have to type the "j" and "r" commands after you start the
> binary:
>
> su root
> ./mrcv
> j 224.0.0.9 172.20.2.2
> r 224.0.0.9 520
>
>
> 4. Start the sender on Router1's interface eth3 (you don't have to
>    be a root). Again, you have to type the rest of the commands
>    after you start "msend":
>
> ./msend
> i 172.20.2.1
> t 1
> d 1 1000
> s 224.0.0.9 520
>
>
> After you start the sender, you should see the multicast packets
> being received by the receiver:
> Receive pkt # 0, for mgroup 224.0.0.9 port 520, length=1006,
> t_sec=134744073, t_usec=133744072 Receive pkt # 1, for mgroup 224.0.0.9
> port 520, length=1006, t_sec=134744073, t_usec=133744072 Receive pkt # 2,
> for mgroup 224.0.0.9 port 520, length=1006, t_sec=134744073,
> t_usec=133744072
>
> Just for reference purpose below I am including the logs from
> running those programs on my testbed.
>
> Thanks,
> Pavlin
>
> === RECEIVER ===
> root@xorp4[3] ./mrcv
> multicast receiving test program; enter ? for list of commands
> j 224.0.0.9 10.2.0.4
> group joined
> r 224.0.0.9 520
> Bind socket
> Receive pkt # 0, for mgroup 224.0.0.9 port 520, length=1006,
> t_sec=134744073, t_usec=133744072 Receive pkt # 1, for mgroup 224.0.0.9
> port 520, length=1006, t_sec=134744073, t_usec=133744072 Receive pkt # 2,
> for mgroup 224.0.0.9 port 520, length=1006, t_sec=134744073,
> t_usec=133744072 Receive pkt # 3, for mgroup 224.0.0.9 port 520,
> length=1006, t_sec=134744073, t_usec=133744072
>
>
> === SENDER ===
> pavlin@xorp2[12] ./msend
> multicast sending test program; enter ? for list of commands
> i 10.2.0.2
> interface set
> t 1
> ttl set to 1
> d 1 1000
> packet number set: 1000 packets
> s 224.0.0.9 520
> Sending... for 1000 packets
> Sent pkt # 0, for mgroup 224.0.0.9 port 520, length=1006, interval=982421
> microseconds Sent pkt # 1, for mgroup 224.0.0.9 port 520, length=1006,
> interval=982421 microseconds Sent pkt # 2, for mgroup 224.0.0.9 port 520,
> length=1006, interval=982421 microseconds Sent pkt # 3, for mgroup
> 224.0.0.9 port 520, length=1006, interval=982421 microseconds ^C
> ======



----------------------
Swati Sinha Deb, Research Fellow
Wireless and Networks Research Laboratory,
Electrical & Electronic Engineering, University of Bristol,
Merchant Venturers Building, Woodland Road,
Bristol BS8 1UB
E-mail: Swati.SinhaDeb@bristol.ac.uk
Tel.: +44 (0)117 331 5058