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

[Swati Sinha Deb]

Hi Pavlin,

I tried to run the XORP router without click and the problem lies with the 
RIP. It's not constructing the routing table properly.

Regards,
Swati

--On 18 April 2005 13:00 -0700 Pavlin Radoslavov <pavlin@icir.org> wrote:

>> 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"
>
> Can you make sure that in your configuration the above filename is
> within quotes. Though, if the first quote is missing the rtrmgr
> should have caught this error.
>
>> 	}
>>     }
>> }
>>
>> 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
>> 		  }
>> 	    }
>> 	}
>>     }
>> }
>
> If the filename quoting is not the problem, then I'd recommend to
> run your XORP router without Click. This will tell you whether the
> problem is in RIP or in Click. Once you get RIP running with native
> forwarding, then you can enable Click. In your tests, please don't run
> more than one Click user-level instances, because the result may be
> unpredictable.
>
> Regards,
> Pavlin



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