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

[Swati Sinha Deb]

Hi Pavlin,

Many thanks for the reply. I have exported the connected routes via RIP but 
still cannot figure it out why it is not creating the correct routing 
table. Please find my XORP configuration. Can you please advice.

interfaces {
    interface eth4 {
	description: "data interface"
	disable: false
	default-system-config
    }
    interface eth3 {
	description: "control interface"
	disable: false
	default-system-config
    }
}

fea {
    unicast-forwarding4 {
	disable: false
    }
    click {
	disable: false

	/*
	 * Set duplicate-routes-to-kernel to true if the XORP routes
	 * added to Click should be added to the system kernel as well.
	 */
	duplicate-routes-to-kernel: false

	/*
	 * Note: If both kernel-click and user-click are enabled, then
	 * typically kernel-click-config-generator-file and
	 * user-click-config-generator-file should point to different
	 * generator files. Otherwise, a single common generator
	 * wouldn't know whether to generate configuration for kernel-level
	 * Click or for user-level Click.
	 */
	kernel-click {
	    disable: true
	    install-on-startup:	true
	    kernel-click-modules: "/path/to/proclikefs.o:/path/to/click.o"
	    /* XXX: On FreeBSD we need only module click.ko */
	    /* kernel-click-modules: "/path/to/click.ko" */
	    mount-directory: "/click"
	    kernel-click-config-generator-file: 
"/usr/local/xorp/fea/xorp_fea_click_config_generator"
	}

	user-click {
	    disable: false
	    command-file: "/home/eessd/click/bin/click"
	    /*
	     * Note: don't add "-p <port>" as an extra argument, because it
	     * will conflict with the FEA's addition of the same argument.
	     */
	    command-extra-arguments: "-R"
	    command-execute-on-startup: true
	    control-address: 127.0.0.1
	    control-socket-port: 13000
	    startup-config-file: "/dev/null"
	    user-click-config-generator-file: 
/usr/local/xorp/fea/xorp_fea_click_config_generator"
	}
    }
}

protocols {
    rip {
/* Redistribute routes for connected interfaces */
	export connected {
	    metric: 0
	    tag: 0
	}
/* Run on specified network interface addresses */
	interface eth4 {
	    vif eth4 {
	      address 172.20.1.1 {
		    disable: false
		}
          }
	}
        interface eth3 {
	    vif eth3 {
		  address 172.20.2.1 {
		    disable: false
		  }
	    }
	}
    }
}


Regards,
Swati


--On 17 April 2005 17:19 -0700 Pavlin Radoslavov <pavlin@icir.org> wrote:

>> I have implemented a testbed (shown below) using XORP+click. Click is
>> running in user mode.
>>
>> CLIENTPC1 --- XORP1 ------ XORP2 ------ CLIENTPC2
>>
>> Both XORP1 & XORP2 have been configured for RIP on both the interfaces.
>> As  expected I can see the RIP packets on all the interfaces. But the
>> issue is  when I try to ping CLIENTPC2 from CLIENTPC1 it fails.
>>
>> To get around the above problem I added static routes to both XORP1 &
>> XORP2  so that they know routes to each others networks. When I try to
>> ping from  CLIENTPC1 to CLIENTPC2 it works!
>>
>> Can somebody please explain this behaviour? I would have expected that
>> RIP  would build the correct routing table and pass it on to click.
>
> What is the XORP configuration you are using?
> E.g., one possible reason that RIP doesn't work for you is because
> you are not exporting the connected routes via RIP
> (the "export connected" statement in the rip configuration
> section).
>
>> Second issue,
>>
>> I am capturing packets via click using the same testbed described above.
>> To  do this I have written a .click config file and start another
>> instance of  click. So at the moment there are 2 instances of click
>> running on my server  (the first started by XORP in user mode and the
>> second started manually by  myself). Is there a way to specify the
>> .click configuration in XORP  configuration file so that there is only
>> one instance of click running on  my server and that started by XORP in
>> user mode?
>
> The Click configuration used by XORP is generated by an external
> script. In the sample XORP Click configuration that script is set to
> fea/xorp_fea_click_config_generator.
> Hence, you would have to modify that script to add the extra Click
> configuration you need. Of course, you could use your own script,
> but then that script must follow few requirements. Those are listed
> in the beginning of fea/xorp_fea_click_config_generator.
>
> Regards,
> Pavlin
>
>
>>
>> Any advice on the above issues will be highly appreciated.
>>
>> Thanks.
>>
>> Regards
>> Swati
>>
>> ----------------------
>> 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
>> _______________________________________________
>> Xorp-users mailing list
>> Xorp-users@xorp.org
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>



----------------------
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