[Xorp-users] Xorp-users Digest, Vol 25, Issue 9
Soon-Yong Sohn
ssohn at gmu.edu
Thu Apr 17 19:46:49 PDT 2008
Thank you for the reply.
I did all three as you mentioned, update xorp through cvs, install old version (1.4.3) of click, specify interfaces in detail. It makes some change in running xorp+click.
However, I got another error message at router as follows;
-----------------------------------------------------------------------------------
[ 2008/04/17 20:38:03 ERROR xorp_fea:19062 FEA +833 click_socket.cc user_click_command_stderr_cb ] User-level Click stderr output: LinearIPLookup: no gw for 302010a
LinearIPLookup: no gw for 302010a
LinearIPLookup: no gw for 302010a
LinearIPLookup: no gw for 302010a
[ 2008/04/17 20:38:04 ERROR xorp_fea:19062 FEA +833 click_socket.cc user_click_command_stderr_cb ] User-level Click stderr output: LinearIPLookup: no gw for 50000e0
-------------------------------------------------------------------------------
When I ping sink1 from source1, I got several duplicate acks as follows:
[ssohn at source1 ~]$ ping sink1
PING sink1-lan2 (10.1.2.3) 56(84) bytes of data.
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.765 ms
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.770 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.771 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.886 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.01 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.01 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.01 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.14 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.578 ms
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.581 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.583 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.584 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.586 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.703 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.706 ms (DUP!)
64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.707 ms (DUP!)
---------------------------------------------------------------------------
I am not sure these messages mean that xorp and click work fine.
I look forward to hearing you soon.
Thank you very much.
Eric
----- Original Message -----
From: xorp-users-request at xorp.org
Date: Wednesday, April 16, 2008 3:00 pm
Subject: Xorp-users Digest, Vol 25, Issue 9
> Send Xorp-users mailing list submissions to
> xorp-users at xorp.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> or, via email, send a message with subject or body 'help' to
> xorp-users-request at xorp.org
>
> You can reach the person managing the list at
> xorp-users-owner at xorp.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xorp-users digest..."
>
>
> Today's Topics:
>
> 1. Re: running xorp+click (Pavlin Radoslavov)
>
>
> -------------------------------------------------------------------
> ---
>
> Message: 1
> Date: Tue, 15 Apr 2008 13:55:35 -0700
> From: Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU>
> Subject: Re: [Xorp-users] running xorp+click
> To: Eric Sohn <ssohn at gmu.edu>
> Cc: xorp-users at xorp.org
> Message-ID: <200804152055.m3FKtZRb003271 at fruitcake.ICSI.Berkeley.EDU>
>
> Eric Sohn <ssohn at gmu.edu> wrote:
>
> > Hello,
> >
> >
> >
> > I am a newbie in xorp.
> >
> > I am trying to run xorp with click on emulab.net.
> >
> > I hope somebody can resolve the error.
> >
> > I attach the boot file and error message.
>
> What Click version are you using?
> Admitably, the support for newer Click releases is lagging behind.
> Could you try some of the following:
>
> * Use explicit interface configuration in the "interfaces" section
> instead of using the "default-system-config" statement; i.e.,
> explicitly add the vif and IP address information to the
> XORP configuration.
>
> * Use the latest XORP code from anon. CVS:
> http://www.xorp.org/cvs.html
>
> * Use an older Click version. If I remember correctly, originally we
> had XORP working with Click-1.4.3 (and/or Click-1.4.2?).
>
> Regards,
> Pavlin
>
> > NW topology is organized with 2 routers and 2 end systems. 2
> routers are
> > using xorp + click with RIP.
> >
> > Each router has two interfaces and each end system has one
> interface.>
> > Linking is source - r1 - r2 - sink
> >
> >
> >
> > Followings are the content of boot file;
> >
> > -----------------------------------------------------------------
> -----------
> > ---
> >
> > interfaces{
> >
> > restore-original-config-on-shutdown: false
> >
> > interface eth2 {
> >
> > disable: false
> >
> > default-system-config
> >
> > }
> >
> > interface eth5 {
> >
> > disable: false
> >
> > default-system-config
> >
> > }
> >
> > } /* </interfaces> */
> >
> >
> >
> > fea{
> >
> > unicast-forwarding4 {
> >
> > disable: false
> >
> > }
> >
> >
> >
> > unicast-forwarding6 {
> >
> > disable: true
> >
> > }
> >
> >
> >
> > click {
> >
> > disable: false
> >
> > duplicate-routes-to-kernel: true
> >
> >
> >
> > kernel-click{
> >
> > disable: true
> >
> > }
> >
> >
> >
> > user-click{
> >
> > disable: false
> >
> > command-file:
> "/users/ssohn/click/bin/click">
> > 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:
> > "/tmp/xorp-1.4/fea/xorp_fea_click_config_generator" <- no
> change in this
> > file
> >
> > }
> >
> > }
> >
> >
> >
> > } /* </fea> */
> >
> >
> >
> > protocols {
> >
> > static {
> >
> > route 10.1.1.0/24 {
> >
> > next-hop: 10.1.1.2
> >
> > metric: 1
> >
> > }
> >
> > route 10.1.3.0/24 {
> >
> > next-hop: 10.1.1.2
> >
> > metric: 1
> >
> > }
> >
> > mrib-route 10.1.1.0/24 {
> >
> > next-hop: 10.1.1.2
> >
> > metric: 1
> >
> > }
> >
> > mrib-route 10.1.3.0/24 {
> >
> > next-hop: 10.1.1.2
> >
> > metric: 1
> >
> > }
> >
> > }
> >
> > }
> >
> >
> >
> > protocols {
> >
> > rip {
> >
> > export connected {
> >
> > metric: 0
> >
> > tag: 0
> >
> > }
> >
> > export static {
> >
> > metric: 1
> >
> > tag: 0
> >
> > }
> >
> > interface eth2 {
> >
> > vif eth2 {
> >
> > address 10.1.2.2 {
> >
> > disable: false
> >
> > }
> >
> > }
> >
> > }
> >
> > interface eth5 {
> >
> > vif eth5 {
> >
> > address 10.1.1.3 {
> >
> > disable: false
> >
> > }
> >
> > }
> >
> > }
> >
> > }
> >
> > }
> >
> > -----------------------------------------------------------------
> -----------
> > -------------------------------------
> >
> >
> >
> >
> >
> > When I run this boot file, I got error message as follows;
> >
> >
> >
> > [ssohn at r2 ~/2routers]$ sudo /tmp/xorp-1.4/rtrmgr/xorp_rtrmgr -b
> > ~/2routers/R2.boot.rip
> >
> > [ 2008/04/15 14:14:50 INFO xorp_rtrmgr:4310 RTRMGR +239
> master_conf_tree.cc> execute ] Changed modules: interfaces, fea,
> rib, policy, rip, static_routes
> >
> > [ 2008/04/15 14:14:50 INFO xorp_rtrmgr:4310 RTRMGR +96
> module_manager.cc> execute ] Executing module: interfaces
> (fea/xorp_fea)>
> > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] MFEA enabled
> >
> > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI enabled
> >
> > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI started
> >
> > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] MFEA enabled
> >
> > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI enabled
> >
> > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI started
> >
> > [ 2008/04/15 14:14:52 INFO xorp_rtrmgr:4310 RTRMGR +96
> module_manager.cc> execute ] Executing module: fea (fea/xorp_fea)
> >
> > [ 2008/04/15 14:14:57 ERROR xorp_fea:4312 FEA +777
> ifconfig_set_click.cc> click_config_generator_done ] Failed to
> write the Click configuration:
> > User-level Click command error: 520-Write handler 'hotconfig' error:
> >
> > 520-<expr>:10: While configuring 'Print at 15 :: Print':
> >
> > 520- argument 1 takes string (label)
> >
> > 520-<expr>:17: While configuring 'Print at 27 :: Print':
> >
> > 520- argument 1 takes string (label)
> >
> > 520 Router could not be initialized!
> >
> > [ 2008/04/15 14:14:59 INFO xorp_rtrmgr:4310 RTRMGR +96
> module_manager.cc> execute ] Executing module: rib (rib/xorp_rib)
> >
> > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301
> > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing
> port number
> > for the Click forwarding table element to add entry net =
> 10.1.2.0/24> nexthop = 10.1.2.2 ifname = eth2 vifname = eth2
> metric = 0 admin_distance =
> > 0 xorp_route = true is_deleted = false is_unresolved = false
> > is_connected_route = true
> >
> > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +71
> fti_transaction.cc> operation_result ] FTI transaction commit
> failed on AddEntry4: net =
> > 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 vifname = eth2
> metric = 0
> > admin_distance = 0 xorp_route = true is_deleted = false
> is_unresolved =
> > false is_connected_route = true
> >
> > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301
> > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing
> port number
> > for the Click forwarding table element to add entry net =
> 10.1.1.0/24> nexthop = 10.1.1.3 ifname = eth5 vifname = eth5
> metric = 0 admin_distance =
> > 0 xorp_route = true is_deleted = false is_unresolved = false
> > is_connected_route = true
> >
> > [ 2008/04/15 14:14:59 WARNING xorp_fea XrlFeaTarget ] Handling
> method for
> > redist_transaction4/0.1/commit_transaction failed: XrlCmdError
> 102 Command
> > failed AddEntry4: net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname =
> eth2 vifname
> > = eth2 metric = 0 admin_distance = 0 xorp_route = true
> is_deleted = false
> > is_unresolved = false is_connected_route = true
> >
> > [ 2008/04/15 14:14:59 ERROR xorp_rib:4316 RIB +910 redist_xrl.cc
> > dispatch_complete ] Failed to commit transaction: 102 Command failed
> > AddEntry4: net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2
> vifname = eth2
> > metric = 0 admin_distance = 0 xorp_route = true is_deleted = false
> > is_unresolved = false is_connected_route = true
> >
> > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301
> > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing
> port number
> > for the Click forwarding table element to add entry net =
> fe80::/64 nexthop
> > = fe80::204:23ff:feb7:26dc ifname = eth2 vifname = eth2 metric = 0
> > admin_distance = 0 xorp_route = true is_deleted = false
> is_unresolved =
> > false is_connected_route = true
> >
> > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +71
> fti_transaction.cc> operation_result ] FTI transaction commit
> failed on AddEntry6: net =
> > fe80::/64 nexthop = fe80::204:23ff:feb7:26dc ifname = eth2
> vifname = eth2
> > metric = 0 admin_distance = 0 xorp_route = true is_deleted = false
> > is_unresolved = false is_connected_route = true
> >
> > [ 2008/04/15 14:14:59 WARNING xorp_fea XrlFeaTarget ] Handling
> method for
> > redist_transaction6/0.1/commit_transaction failed: XrlCmdError
> 102 Command
> > failed AddEntry6: net = fe80::/64 nexthop =
> fe80::204:23ff:feb7:26dc ifname
> > = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route =
> true> is_deleted = false is_unresolved = false is_connected_route
> = true
> >
> > [ 2008/04/15 14:14:59 ERROR xorp_rib:4316 RIB +910 redist_xrl.cc
> > dispatch_complete ] Failed to commit transaction: 102 Command failed
> > AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:feb7:26dc
> ifname = eth2
> > vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true
> is_deleted =
> > false is_unresolved = false is_connected_route = true
> >
> > [ 2008/04/15 14:15:01 INFO xorp_rtrmgr:4310 RTRMGR +96
> module_manager.cc> execute ] Executing module: policy
> (policy/xorp_policy)>
> > [ 2008/04/15 14:15:03 INFO xorp_rtrmgr:4310 RTRMGR +96
> module_manager.cc> execute ] Executing module: rip (rip/xorp_rip)
> >
> > [ 2008/04/15 14:15:05 WARNING xorp_policy:4317 XrlPolicyTarget +567
> > policy_base.cc handle_policy_0_1_export ] Handling method for
> > policy/0.1/export failed: XrlCmdError 102 Command failed Export
> of rip
> > failed: ConfError from line 179 of configuration.cc: exports:
> Protocol rip
> > unknown
> >
> > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +675
> > master_conf_tree.cc commit_pass2_done ] Commit failed: 102
> Command failed
> > Export of rip failed: ConfError from line 179 of
> configuration.cc: exports:
> > Protocol rip unknown
> >
> > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +251
> > master_conf_tree.cc config_done ] Configuration failed: 102
> Command failed
> > Export of rip failed: ConfError from line 179 of
> configuration.cc: exports:
> > Protocol rip unknown
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +2228
> task.cc run_task ]
> > No more tasks to run
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171
> module_manager.cc> terminate ] Terminating module: fea
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171
> module_manager.cc> terminate ] Terminating module: interfaces
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194
> module_manager.cc> terminate ] Killing module: interfaces
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171
> module_manager.cc> terminate ] Terminating module: policy
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194
> module_manager.cc> terminate ] Killing module: policy
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171
> module_manager.cc> terminate ] Terminating module: rib
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194
> module_manager.cc> terminate ] Killing module: rib
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171
> module_manager.cc> terminate ] Terminating module: rip
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194
> module_manager.cc> terminate ] Killing module: rip
> >
> > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747
> module_manager.cc> done_cb ] Command "/tmp/xorp-1.4/rib/xorp_rib":
> terminated with signal 15.
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282
> module_manager.cc> module_exited ] Module killed during shutdown: rib
> >
> > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747
> module_manager.cc> done_cb ] Command "/tmp/xorp-
> 1.4/policy/xorp_policy": terminated with signal
> > 15.
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282
> module_manager.cc> module_exited ] Module killed during shutdown:
> policy>
> > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747
> module_manager.cc> done_cb ] Command "/tmp/xorp-1.4/rip/xorp_rip":
> terminated with signal 15.
> >
> > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282
> module_manager.cc> module_exited ] Module killed during shutdown: rip
> >
> > [ 2008/04/15 14:15:07 INFO xorp_rtrmgr:4310 RTRMGR +233
> module_manager.cc> terminate_with_prejudice ] Killing module with
> prejudice: interfaces
> >
> >
> >
> >
> >
> >
> >
> > Plz plz help me out.
> >
> >
> >
> >
> >
> > Thank you in advance.
> >
> >
> >
> > Eric
> >
> > _______________________________________________
> > Xorp-users mailing list
> > Xorp-users at xorp.org
> > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>
>
> ------------------------------
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>
> End of Xorp-users Digest, Vol 25, Issue 9
> *****************************************
>
More information about the Xorp-users
mailing list