[Xorp-users] Problem starting XORP+User Click

jmorillo@ac.upc.edu jmorillo@ac.upc.edu
Wed, 12 Jan 2005 15:03:33 +0100


Hello,

I'm trying to use XORP in combination with User Level Click forwarding.
When I run ./xorp_rtrmgr I get the following error message:

[ 2005/01/12 14:47:07  ERROR xorp_fea:2593 LIBCOMM +499 comm_sock.c
comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr =
127.0.0.1, remote_port = 13000): Connection refused
[ 2005/01/12 14:47:07 WARNING xorp_fea FEA ] Could not open user-level Click
socket: Connection refused. Trying again...

Click is installed on /usr/local/bin.

I didn't modify the xorp_fea_click_config_generator file (maybe it's necessary
to do it), and my XORP configuration file is as follows:

/* $XORP: xorp/rtrmgr/config.boot.sample,v 1.20 2004/12/17 06:03:18 pavlin Exp $
*/

interfaces {
    interface eth1 {
	description: "data interface"
	enabled: true

	vif eth1 {
	    enabled: true
	    address 147.83.34.82 {
		prefix-length: 24
		broadcast: 147.83.34.255
		enabled: true
	    }

	}
    }
}

fea {
    enable-unicast-forwarding4: true
    /* enable-unicast-forwarding6: true */

    click {
	enabled: true

	/*
	 * 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 {
	    enabled: false
	    install-on-startup:	false
	    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:
"/user/local/xorp/fea/xorp_fea_click_config_generator"
	}

	user-click {
	    enabled: true
	    command-file: "/usr/local/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:
"/root/XORP/xorp/fea/xorp_fea_click_config_generator"
	}
    }
}

protocols {
    static {
	route4 0.0.0.0/0 {
	    nexthop: 147.83.34.2
	    metric: 0
	}
    }
}

Maybe I'm missing anything? What means startup-config-file: "/dev/null"? Any
help or suggestion will be welcome.
Thanks in advance,

julian