From carsten at c-otto.de Sun Mar 1 01:28:26 2009 From: carsten at c-otto.de (Carsten Otto) Date: Sun, 1 Mar 2009 10:28:26 +0100 Subject: [Xorp-users] FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed In-Reply-To: <20090220225718.GH5984@carsten-otto> References: <20090220225718.GH5984@carsten-otto> Message-ID: <20090301092825.GB20594@carsten-otto> Hi again, Sorry Pavlin, your answer got lost, as my mailserver had a problem. So i am replying here. It does not help to delete the information for eth0.2, as I already wrote in the first mail: On Fri, Feb 20, 2009 at 11:57:19PM +0100, Carsten Otto wrote: > I attached the config file. Removing the sections for eth2 and eth0.2 at the > top does not resolve the problem. Any idea? Thanks, -- Carsten Otto carsten at c-otto.de www.c-otto.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090301/dc6fdc25/attachment.bin From carsten at c-otto.de Sun Mar 1 01:33:01 2009 From: carsten at c-otto.de (Carsten Otto) Date: Sun, 1 Mar 2009 10:33:01 +0100 Subject: [Xorp-users] cand-rp without BSR In-Reply-To: <20090218181948.GE25985@carsten-otto> References: <20090218181948.GE25985@carsten-otto> Message-ID: <20090301093301.GC20594@carsten-otto> Thanks for the answers! I think we just forgot to configure the cisco router that sits in between... Thanks, -- Carsten Otto carsten at c-otto.de www.c-otto.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090301/3088eab4/attachment.bin From bhavin81 at iitb.ac.in Mon Mar 2 02:50:01 2009 From: bhavin81 at iitb.ac.in (bhavin81 at iitb.ac.in) Date: Mon, 2 Mar 2009 16:20:01 +0530 (IST) Subject: [Xorp-users] help: getting the error no finder? In-Reply-To: <1c56f7b10903011954h78c13bdah625972737b60b32a@mail.gmail.com> References: <026537793ff8e6e43e0ddac9a83686a1.squirrel@gpo.iitb.ac.in> <1c56f7b10902282223h32a037eav6ea87fc4db35334d@mail.gmail.com> <1349eb262d6d5c9d18ffd39d1a2946fb.squirrel@gpo.iitb.ac.in> <1c56f7b10903011954h78c13bdah625972737b60b32a@mail.gmail.com> Message-ID: Hello Ram & friends, Thanks for the reply. Now i have got another problem. When i am running the ./xorp_rtrmgr then i am getting following errors: (a)group xorp does not exits (b)xorp_rtrmgr is shutting down due to init error. failed to open config.boot As i have said that i have not created any config file. Does that mean the error(b) is due to that reason. If yes then someone can please send me some config file so that at least i can begin. Can you please tell me how to create xrop group. Thanks in advance. Regards, Bhavin > Hi Bhavin, yesterday i didn't give u clear one. try this one. > 1. open a terminal, go to the xorp folder. > 2. then cd rtrmgr. > 3. ./xorp_rtrmgr.( it will enable fea,rib....etc.) > 4. open other terminal and run ./xorpsh. it welcomes u to xorp CLI > > > > On Sun, Mar 1, 2009 at 8:11 AM, wrote: > >> Hello Ram, >> >> Thanks for the reply. >> I have got one problem. I am not finding the folder where i >> have to execute rtrmgr. Can you please tell me the absolute path >> of that one. >> >> > Hi Bhavin, >> > did u run rtrmgr ? i think u did not. >> > >> > Run "./rtrmgr"( in rtr manager) and open other terminal go to the >> rtrmgr >> > directory and run "./xorpsh" >> > >> > On Sun, Mar 1, 2009 at 12:02 AM, wrote: >> > >> >> Hell friends, >> >> >> >> I am new to xorp. I have compiled xorp-1.6 on freebsd 7.1. >> >> I wrote command ./xropsh (in rtrmanager directory) and got the >> >> following >> >> error messagees: >> >> (A) Error XORPSH:44998 RTRMGR +96 xorpsh_main.cc wait_for >> >> xrl_router_ready >> >> Xrlrouter failes. >> >> No Finder? >> >> (B) Error XORPSH:44998 RTRMGR +906 xorpsh_main.cc >> >> xorpsh exiting due to an init error: >> >> failed to connect to router manager. >> >> >> >> I have not done anyother configuration in config file up to now. >> >> Please help. >> >> >> >> Thanks in advance for providing help. >> >> >> >> regards, >> >> Bhavin. >> >> >> >> _______________________________________________ >> >> Xorp-users mailing list >> >> Xorp-users at xorp.org >> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> >> >> > >> > >> > >> > -- >> > Ramkumar Cherukuri >> > >> >> >> > > > -- > Ramkumar Cherukuri > From rahulk.patel at einfochips.com Mon Mar 2 03:16:32 2009 From: rahulk.patel at einfochips.com (Rahul K Patel) Date: Mon, 02 Mar 2009 16:46:32 +0530 Subject: [Xorp-users] help: getting the error no finder? In-Reply-To: References: <026537793ff8e6e43e0ddac9a83686a1.squirrel@gpo.iitb.ac.in> <1c56f7b10902282223h32a037eav6ea87fc4db35334d@mail.gmail.com> <1349eb262d6d5c9d18ffd39d1a2946fb.squirrel@gpo.iitb.ac.in> <1c56f7b10903011954h78c13bdah625972737b60b32a@mail.gmail.com> Message-ID: <49ABC010.9080702@einfochips.com> Hi Bhavin, a) To add xorp group on rhel machine use following command #groupadd xorp b) Attached herewith is sample config file to configure interface eth0 in default mode. use config file with -b option ./xorp_rtrmgr -b config.xorp.interface Note: you need to modify config file in order to configure different routing protocol. see xorp manual for more detail on xorp commands. Thanks, Rahul Patel, Embedded Engineer, eInfochips Ltd, Ahmedabad. bhavin81 at iitb.ac.in wrote: > Hello Ram & friends, > > Thanks for the reply. Now i have got another problem. > When i am running the ./xorp_rtrmgr then i am getting following > errors: > (a)group xorp does not exits > (b)xorp_rtrmgr is shutting down due to init error. > failed to open config.boot > > As i have said that i have not created any config file. > Does that mean the error(b) is due to that reason. If yes then > someone can please send me some config file so that at least i can > begin. Can you please tell me how to create xrop group. > > Thanks in advance. > Regards, > Bhavin > > >> Hi Bhavin, yesterday i didn't give u clear one. try this one. >> 1. open a terminal, go to the xorp folder. >> 2. then cd rtrmgr. >> 3. ./xorp_rtrmgr.( it will enable fea,rib....etc.) >> 4. open other terminal and run ./xorpsh. it welcomes u to xorp CLI >> >> >> >> On Sun, Mar 1, 2009 at 8:11 AM, wrote: >> >> >>> Hello Ram, >>> >>> Thanks for the reply. >>> I have got one problem. I am not finding the folder where i >>> have to execute rtrmgr. Can you please tell me the absolute path >>> of that one. >>> >>> >>>> Hi Bhavin, >>>> did u run rtrmgr ? i think u did not. >>>> >>>> Run "./rtrmgr"( in rtr manager) and open other terminal go to the >>>> >>> rtrmgr >>> >>>> directory and run "./xorpsh" >>>> >>>> On Sun, Mar 1, 2009 at 12:02 AM, wrote: >>>> >>>> >>>>> Hell friends, >>>>> >>>>> I am new to xorp. I have compiled xorp-1.6 on freebsd 7.1. >>>>> I wrote command ./xropsh (in rtrmanager directory) and got the >>>>> following >>>>> error messagees: >>>>> (A) Error XORPSH:44998 RTRMGR +96 xorpsh_main.cc wait_for >>>>> xrl_router_ready >>>>> Xrlrouter failes. >>>>> No Finder? >>>>> (B) Error XORPSH:44998 RTRMGR +906 xorpsh_main.cc >>>>> xorpsh exiting due to an init error: >>>>> failed to connect to router manager. >>>>> >>>>> I have not done anyother configuration in config file up to now. >>>>> Please help. >>>>> >>>>> Thanks in advance for providing help. >>>>> >>>>> regards, >>>>> Bhavin. >>>>> >>>>> _______________________________________________ >>>>> Xorp-users mailing list >>>>> Xorp-users at xorp.org >>>>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >>>>> >>>>> >>>> >>>> -- >>>> Ramkumar Cherukuri >>>> >>>> >>> >>> >> -- >> Ramkumar Cherukuri >> >> > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090302/4718942e/attachment.html -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: config.xorp.interface Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090302/4718942e/attachment.ksh From pavlin at ICSI.Berkeley.EDU Mon Mar 2 10:54:13 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Mon, 02 Mar 2009 10:54:13 -0800 Subject: [Xorp-users] FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed In-Reply-To: <20090301092825.GB20594@carsten-otto> References: <20090220225718.GH5984@carsten-otto> <20090301092825.GB20594@carsten-otto> Message-ID: <200903021854.n22IsDhx015048@fruitcake.ICSI.Berkeley.EDU> An embedded and charset-unspecified text was scrubbed... Name: mfea.patch Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090302/4e43507e/attachment.ksh From carsten at c-otto.de Mon Mar 2 11:20:30 2009 From: carsten at c-otto.de (Carsten Otto) Date: Mon, 2 Mar 2009 20:20:30 +0100 Subject: [Xorp-users] FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed In-Reply-To: <200903021854.n22IsDhx015048@fruitcake.ICSI.Berkeley.EDU> References: <20090220225718.GH5984@carsten-otto> <20090301092825.GB20594@carsten-otto> <200903021854.n22IsDhx015048@fruitcake.ICSI.Berkeley.EDU> Message-ID: <20090302192030.GE30942@carsten-otto> On Mon, Mar 02, 2009 at 10:54:13AM -0800, Pavlin Radoslavov wrote: > Do you get the fatal error if you remove the 10.10.0.1 address so > the eth0.2 entry disappears from the "ifconfig -a" output? I will not try if there is another way to solve the problem. That address is more important than multicast functionality. > In addition, please try of the following patch. Note that it is > against the code in the CVS repository so it might not apply cleanly > for the 1.6 code. Will do. > Also, please note that I haven't tested that patch so I have > low expectations whether it will actually fix the issue. Well, at least you know the code :) Thanks, -- Carsten Otto carsten at c-otto.de www.c-otto.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090302/65d60049/attachment.bin From pavlin at ICSI.Berkeley.EDU Mon Mar 2 11:35:49 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Mon, 02 Mar 2009 11:35:49 -0800 Subject: [Xorp-users] FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed In-Reply-To: <20090302192030.GE30942@carsten-otto> References: <20090220225718.GH5984@carsten-otto> <20090301092825.GB20594@carsten-otto> <200903021854.n22IsDhx015048@fruitcake.ICSI.Berkeley.EDU> <20090302192030.GE30942@carsten-otto> Message-ID: <200903021935.n22JZn8i019996@fruitcake.ICSI.Berkeley.EDU> Carsten Otto wrote: > On Mon, Mar 02, 2009 at 10:54:13AM -0800, Pavlin Radoslavov wrote: > > Do you get the fatal error if you remove the 10.10.0.1 address so > > the eth0.2 entry disappears from the "ifconfig -a" output? > > I will not try if there is another way to solve the problem. That > address is more important than multicast functionality. My question re. the removal of the 10.10.0.1 address was from the perspective of narrowing the issue. Regards, Pavlin > > In addition, please try of the following patch. Note that it is > > against the code in the CVS repository so it might not apply cleanly > > for the 1.6 code. > > Will do. > > > Also, please note that I haven't tested that patch so I have > > low expectations whether it will actually fix the issue. > > Well, at least you know the code :) > > Thanks, > -- > Carsten Otto > carsten at c-otto.de > www.c-otto.de > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From carsten at c-otto.de Tue Mar 3 05:24:24 2009 From: carsten at c-otto.de (Carsten Otto) Date: Tue, 3 Mar 2009 14:24:24 +0100 Subject: [Xorp-users] FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed In-Reply-To: <20090302192030.GE30942@carsten-otto> References: <20090220225718.GH5984@carsten-otto> <20090301092825.GB20594@carsten-otto> <200903021854.n22IsDhx015048@fruitcake.ICSI.Berkeley.EDU> <20090302192030.GE30942@carsten-otto> Message-ID: <20090303132424.GD10543@daedalus.informatik.rwth-aachen.de> On Mon, Mar 02, 2009 at 10:54:13AM -0800, Pavlin Radoslavov wrote: > In addition, please try of the following patch. Note that it is > against the code in the CVS repository so it might not apply cleanly > for the 1.6 code. > Also, please note that I haven't tested that patch so I have > low expectations whether it will actually fix the issue. Loading (m)fea works. Now I run into the following error: [ 2009/03/03 14:20:07 INFO xorp_rtrmgr:25742 RTRMGR +101 module_manager.cc execute ] Executing module: rib (rib/xorp_rib) /usr/local/xorp/rib/xorp_rib: error: `/usr/local/xorp/rib/.libs/xorp_rib' does not exist This script is just a wrapper for xorp_rib. See the libtool documentation for more information. [ 2009/03/03 14:20:08 ERROR xorp_rtrmgr:25742 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/rib/xorp_rib": exited with exit status 1. (log attached) Please also note the various error messages regarding eth0.2 (which do not seem to be critical). Thanks, -- Carsten Otto carsten at c-otto.de www.c-otto.de -------------- next part -------------- [ 2009/03/03 14:20:23 INFO xorp_rtrmgr:28543 RTRMGR +249 master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea, mfea4, rib, fib2mrib, igmp, pimsm4 [ 2009/03/03 14:20:23 INFO xorp_rtrmgr:28543 RTRMGR +101 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2009/03/03 14:20:24 INFO xorp_fea MFEA ] MFEA enabled [ 2009/03/03 14:20:24 INFO xorp_fea MFEA ] CLI enabled [ 2009/03/03 14:20:24 INFO xorp_fea MFEA ] CLI started [ 2009/03/03 14:20:24 INFO xorp_fea MFEA ] MFEA enabled [ 2009/03/03 14:20:24 INFO xorp_fea MFEA ] CLI enabled [ 2009/03/03 14:20:24 INFO xorp_fea MFEA ] CLI started [ 2009/03/03 14:20:25 INFO xorp_rtrmgr:28543 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) [ 2009/03/03 14:20:29 INFO xorp_rtrmgr:28543 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2009/03/03 14:20:35 INFO xorp_rtrmgr:28543 RTRMGR +101 module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea) [ 2009/03/03 14:20:35 ERROR xorp_fea:28562 MFEA +1196 ../libproto/proto_node.hh set_config_pif_index ] Cannot set pif_index for vif eth0.2: no such vif [ 2009/03/03 14:20:35 ERROR xorp_fea:28562 MFEA +1229 ../libproto/proto_node.hh set_config_vif_flags ] Cannot set flags for vif eth0.2: no such vif [ 2009/03/03 14:20:35 ERROR xorp_fea:28562 MFEA +1124 ../libproto/proto_node.hh add_config_vif_addr ] Cannot add address to vif eth0.2: no such vif [ 2009/03/03 14:20:35 ERROR xorp_fea:28562 MFEA +697 mfea_node.cc vifaddr4_update ] Cannot add address 10.10.0.1 to vif eth0.2 from the set of configured vifs: Cannot add address to vif eth0.2: no such vif [ 2009/03/03 14:20:35 INFO xorp_fea MFEA ] Interface added: Vif[eth0] pif_index: 1 vif_index: 0 addr: 137.226.111.20 subnet: 137.226.108.0/22 broadcast: 137.226.111.255 peer: 0.0.0.0 addr: 137.226.111.254 subnet: 137.226.108.0/22 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/03/03 14:20:35 INFO xorp_fea MFEA ] Interface added: Vif[eth1] pif_index: 2 vif_index: 1 addr: 137.226.119.114 subnet: 137.226.119.112/29 broadcast: 137.226.119.119 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/03/03 14:20:35 INFO xorp_fea MFEA ] Interface added: Vif[eth2] pif_index: 3 vif_index: 2 Flags: MULTICAST BROADCAST MTU: 1500 [ 2009/03/03 14:20:35 INFO xorp_fea MFEA ] MFEA started [ 2009/03/03 14:20:35 INFO xorp_fea MFEA ] Interface enabled Vif[eth0] pif_index: 1 vif_index: 0 addr: 137.226.111.20 subnet: 137.226.108.0/22 broadcast: 137.226.111.255 peer: 0.0.0.0 addr: 137.226.111.254 subnet: 137.226.108.0/22 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/03/03 14:20:35 INFO xorp_fea MFEA ] Interface started: Vif[eth0] pif_index: 1 vif_index: 0 addr: 137.226.111.20 subnet: 137.226.108.0/22 broadcast: 137.226.111.255 peer: 0.0.0.0 addr: 137.226.111.254 subnet: 137.226.108.0/22 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/03/03 14:20:35 INFO xorp_fea MFEA ] Interface added: Vif[register_vif] pif_index: 1 vif_index: 3 addr: 137.226.111.20 subnet: 137.226.111.20/32 broadcast: 137.226.111.20 peer: 0.0.0.0 addr: 137.226.111.254 subnet: 137.226.111.254/32 broadcast: 137.226.111.254 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 [ 2009/03/03 14:20:35 INFO xorp_fea MFEA ] Interface enabled Vif[eth1] pif_index: 2 vif_index: 1 addr: 137.226.119.114 subnet: 137.226.119.112/29 broadcast: 137.226.119.119 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/03/03 14:20:35 INFO xorp_fea MFEA ] Interface started: Vif[eth1] pif_index: 2 vif_index: 1 addr: 137.226.119.114 subnet: 137.226.119.112/29 broadcast: 137.226.119.119 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/03/03 14:20:35 INFO xorp_fea MFEA ] Interface enabled Vif[register_vif] pif_index: 1 vif_index: 3 addr: 137.226.111.20 subnet: 137.226.111.20/32 broadcast: 137.226.111.20 peer: 0.0.0.0 addr: 137.226.111.254 subnet: 137.226.111.254/32 broadcast: 137.226.111.254 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/03/03 14:20:35 INFO xorp_fea MFEA ] Interface started: Vif[register_vif] pif_index: 1 vif_index: 3 addr: 137.226.111.20 subnet: 137.226.111.20/32 broadcast: 137.226.111.20 peer: 0.0.0.0 addr: 137.226.111.254 subnet: 137.226.111.254/32 broadcast: 137.226.111.254 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/03/03 14:20:35 INFO xorp_rtrmgr:28543 RTRMGR +101 module_manager.cc execute ] Executing module: rib (rib/xorp_rib) /usr/local/xorp/rib/xorp_rib: error: `/usr/local/xorp/rib/.libs/xorp_rib' does not exist This script is just a wrapper for xorp_rib. See the libtool documentation for more information. [ 2009/03/03 14:20:35 ERROR xorp_rtrmgr:28543 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/rib/xorp_rib": exited with exit status 1. [ 2009/03/03 14:20:35 INFO xorp_rtrmgr:28543 RTRMGR +323 module_manager.cc module_exited ] Module abnormal exit: rib [ 2009/03/03 14:20:37 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:38 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:39 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:40 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:41 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:42 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:43 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:44 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:45 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:46 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:47 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:48 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:49 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:50 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:51 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:52 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:53 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:54 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:55 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:56 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:57 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:58 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:20:59 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:21:00 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:21:01 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:21:02 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:21:03 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:21:04 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:21:05 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:21:06 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:21:07 WARNING xorp_rtrmgr:28543 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2009/03/03 14:21:07 ERROR xorp_rtrmgr:28543 RTRMGR +2003 task.cc task_fail ] Shutting down fatally wounded process (rib) [ 2009/03/03 14:21:07 ERROR xorp_rtrmgr:28543 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: Can't validate config ready of process rib [ 2009/03/03 14:21:07 ERROR xorp_rtrmgr:28543 RTRMGR +261 master_conf_tree.cc config_done ] Configuration failed: Can't validate config ready of process rib [ 2009/03/03 14:21:07 INFO xorp_rtrmgr:28543 RTRMGR +2233 task.cc run_task ] No more tasks to run [ 2009/03/03 14:21:07 INFO xorp_rtrmgr:28543 RTRMGR +176 module_manager.cc terminate ] Terminating module: fea [ 2009/03/03 14:21:07 INFO xorp_rtrmgr:28543 RTRMGR +176 module_manager.cc terminate ] Terminating module: firewall [ 2009/03/03 14:21:07 INFO xorp_rtrmgr:28543 RTRMGR +176 module_manager.cc terminate ] Terminating module: interfaces [ 2009/03/03 14:21:07 INFO xorp_rtrmgr:28543 RTRMGR +176 module_manager.cc terminate ] Terminating module: mfea4 [ 2009/03/03 14:21:07 INFO xorp_rtrmgr:28543 RTRMGR +199 module_manager.cc terminate ] Killing module: mfea4 [ 2009/03/03 14:21:08 ERROR xorp_rtrmgr:28543 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/fea/xorp_fea": terminated with signal 15. [ 2009/03/03 14:21:08 INFO xorp_rtrmgr:28543 RTRMGR +287 module_manager.cc module_exited ] Module killed during shutdown: mfea4 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090303/741dbdbe/attachment.bin From isaacnskb at gmail.com Tue Mar 3 04:07:51 2009 From: isaacnskb at gmail.com (Isaac) Date: Tue, 3 Mar 2009 04:07:51 -0800 Subject: [Xorp-users] Dynamic Tunnels/Callbacks Message-ID: <9312bbe60903030407l7f04b063v343d34451c066ca4@mail.gmail.com> Hello everyone, I am currently in the process of evaluating XORP for our custom solution. We tried XORP back in 2005 (even before OSPF was implemented) for multicast routing and it worked great. Now, I need to evaluate it again and see if it will be a good fit for this project. Before I do that, I want to see if someone has ran into a similar network topology or has done something similar and see if I can get some pointers. The attached image shows my current setup. The following describes the elements: * static[1-3] - Dumb routers that have static routes (including multicast, they just forward packets and dont care about membership) and they cannot be dynamically changed. * xorp[1-3] - These are the only items that can be tweaked. * windows[1-3] - Regular computers that always have to be connected transparently * modem[1-2] - Modems used to connect to dialin server * dialing - Dialin server running ppp that can also run XORP An element group consists of a windows, xorp, and static elements and each group is on a separate subnet. Currently there are two requirements 1) static1 usually dies (part of the experiment). When that happens xorp2 and xorp1 need to dial a server and communicate and exchange routes Windows 2 can talk to Windows 1. 2) Element groups should be able to join dynamically Currently I am thinking of creating tunnels dynamically between all XORP machines (n * xorp machines on each box) with a custom multicast protocol and running something like OSPF on the tunnels. This will allow me treat each XORP router as a next hop neighbor. Once OSPF detects a link is down, I could setup a callback for dialing and exchange routers between xorp1 and xorp2 over the dialin server. My questions are: 1) Can routing be done in this setup without dynamic tunnels 2) Can callbacks be setup on XORP so that when a router is down a script can be ran. 3) Other potential solutions. Thanks in advanced for any help. -- Isaac -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090303/0ce09096/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: xorp.jpg Type: image/jpeg Size: 37912 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090303/0ce09096/attachment-0001.jpg From pavlin at ICSI.Berkeley.EDU Tue Mar 3 10:27:38 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Tue, 03 Mar 2009 10:27:38 -0800 Subject: [Xorp-users] FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed In-Reply-To: <20090303132222.GC10543@daedalus.informatik.rwth-aachen.de> References: <20090220225718.GH5984@carsten-otto> <20090301092825.GB20594@carsten-otto> <200903021854.n22IsDhx015048@fruitcake.ICSI.Berkeley.EDU> <20090303132222.GC10543@daedalus.informatik.rwth-aachen.de> Message-ID: <200903031827.n23IRcOD013439@fruitcake.ICSI.Berkeley.EDU> Carsten Otto wrote: > On Mon, Mar 02, 2009 at 10:54:13AM -0800, Pavlin Radoslavov wrote: > > In addition, please try of the following patch. Note that it is > > against the code in the CVS repository so it might not apply cleanly > > for the 1.6 code. > > Also, please note that I haven't tested that patch so I have > > low expectations whether it will actually fix the issue. > > Loading (m)fea works. Now I run into the following error: > > [ 2009/03/03 14:20:07 INFO xorp_rtrmgr:25742 RTRMGR +101 module_manager.cc execute ] Executing module: rib (rib/xorp_rib) > /usr/local/xorp/rib/xorp_rib: error: `/usr/local/xorp/rib/.libs/xorp_rib' does not exist > This script is just a wrapper for xorp_rib. > See the libtool documentation for more information. > [ 2009/03/03 14:20:08 ERROR xorp_rtrmgr:25742 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/rib/xorp_rib": exited with exit status 1. > > (log attached) > > Please also note the various error messages regarding eth0.2 (which do not > seem to be critical). Please try the patch with the XORP-1.6 code (the patch should apply cleanly), because the code in the CVS repository is in flux. Regards, Pavlin From tom.gibson at ipvidnet.com Tue Mar 3 11:09:35 2009 From: tom.gibson at ipvidnet.com (Tom Gibson) Date: Tue, 03 Mar 2009 11:09:35 -0800 Subject: [Xorp-users] Xorp + Kernel Click on Linux -- Does this work for anyone in recent code? In-Reply-To: <200902262352.n1QNqN2f011365@fruitcake.ICSI.Berkeley.EDU> References: <49A4FF16.5000807@ipvidnet.com> <200902262352.n1QNqN2f011365@fruitcake.ICSI.Berkeley.EDU> Message-ID: <49AD806F.6060901@ipvidnet.com> Hi Pavlin, That's unfortunate. I'll gather some more details and then look at submitting a Bugzilla entry. I may try debugging the code and seeing if I can get a patch possibly. I was looking before at possibly using an old Xorp and Click version. It's a pain having to go back to such an old Kernel version though (to support the Kernel Click patches). I'll post another reply when I have an update. Thanks, Tom Pavlin Radoslavov wrote: > Tom, > > Unfortunately, the Click testing and support has fallen behind the > rest of the system. It has been a while since we tested them > together, and most likely it was with an older version of Click > (1.4.x). > > We are planning to add-back the Click support in the future. > In the mean time you can try XORP-1.6 with some of the older > Click versions (maybe Click-1.4.3?), though I don't know whether > this will actually work. If this doesn't work, you might want to try > some of the older XORP releases that should work with Click. > I believe I have used XORP-1.4 with Click-1.4.1. > > If other folks have more recent experience please speak up. > > Thanks, > Pavlin > > P.S. Could you submit a Bugzilla entry with the issue, and include > your XORP config file, so we can use that entry to track the > problem. > > > Tom Gibson wrote: > > >> Should the latest Xorp work fine with Kernel Click on Linux? It seems >> to be broke from what I can tell. >> >> Right now using the latest Click all I can get working is the user mode >> version. Kernel mode just causes Xorp startup to go bad with all kinds >> of timeout messages. The MFEA and RIB modules seem to hang and not >> respond. With a minimal config that doesn't enable any protocols or the >> MFEA / RIB modules it gets a little further but right after saying "no >> more tasks to do" I start getting these type of errors: >> >> >>> [ 2009/02/24 23:50:35 WARNING xorp_fea LIBXORP ] 10 seconds between calls to EventLoop::run >>> [ 2009/02/24 23:50:35 ERROR xorp_fea:10743 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive timeout >>> >> I remember using another version of Click I managed to get it to load >> with a minimal config (no protocols enabled). Tomorrow I'll test this >> again and get some more info on which version this was with. >> >> I'm new to both Xorp and Click code bases as well as Linux programming >> and tools like cvs. Can anyone offer guidance on getting this working? >> >> Thanks, >> >> Tom >> >> _______________________________________________ >> Xorp-users mailing list >> Xorp-users at xorp.org >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> From carsten at c-otto.de Wed Mar 4 11:33:29 2009 From: carsten at c-otto.de (Carsten Otto) Date: Wed, 4 Mar 2009 20:33:29 +0100 Subject: [Xorp-users] FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed In-Reply-To: <200903031827.n23IRcOD013439@fruitcake.ICSI.Berkeley.EDU> References: <20090220225718.GH5984@carsten-otto> <20090301092825.GB20594@carsten-otto> <200903021854.n22IsDhx015048@fruitcake.ICSI.Berkeley.EDU> <20090303132222.GC10543@daedalus.informatik.rwth-aachen.de> <200903031827.n23IRcOD013439@fruitcake.ICSI.Berkeley.EDU> Message-ID: <20090304193329.GD26763@carsten-otto> On Tue, Mar 03, 2009 at 10:27:38AM -0800, Pavlin Radoslavov wrote: > Please try the patch with the XORP-1.6 code (the patch should apply > cleanly), because the code in the CVS repository is in flux. Okay, that worked. It triggered some bug in IGMP code, though. I now transferred the VLAN to a physical LAN and XORP starts and works fine. It would be nice to have VLAN support, though. Thanks for your help, -- Carsten Otto carsten at c-otto.de www.c-otto.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090304/d6403dbc/attachment.bin From pavlin at ICSI.Berkeley.EDU Wed Mar 4 13:33:49 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Wed, 04 Mar 2009 13:33:49 -0800 Subject: [Xorp-users] FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed In-Reply-To: <20090304193329.GD26763@carsten-otto> References: <20090220225718.GH5984@carsten-otto> <20090301092825.GB20594@carsten-otto> <200903021854.n22IsDhx015048@fruitcake.ICSI.Berkeley.EDU> <20090303132222.GC10543@daedalus.informatik.rwth-aachen.de> <200903031827.n23IRcOD013439@fruitcake.ICSI.Berkeley.EDU> <20090304193329.GD26763@carsten-otto> Message-ID: <200903042133.n24LXnKx025358@fruitcake.ICSI.Berkeley.EDU> Carsten Otto wrote: > On Tue, Mar 03, 2009 at 10:27:38AM -0800, Pavlin Radoslavov wrote: > > Please try the patch with the XORP-1.6 code (the patch should apply > > cleanly), because the code in the CVS repository is in flux. > > Okay, that worked. It triggered some bug in IGMP code, though. I now Please submit a Bugzilla entry about the issue. > transferred the VLAN to a physical LAN and XORP starts and works fine. > It would be nice to have VLAN support, though. Down the road it should. Thanks, Pavlin From carsten at c-otto.de Wed Mar 4 13:54:10 2009 From: carsten at c-otto.de (Carsten Otto) Date: Wed, 4 Mar 2009 22:54:10 +0100 Subject: [Xorp-users] FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed In-Reply-To: <200903042133.n24LXnKx025358@fruitcake.ICSI.Berkeley.EDU> References: <20090220225718.GH5984@carsten-otto> <20090301092825.GB20594@carsten-otto> <200903021854.n22IsDhx015048@fruitcake.ICSI.Berkeley.EDU> <20090303132222.GC10543@daedalus.informatik.rwth-aachen.de> <200903031827.n23IRcOD013439@fruitcake.ICSI.Berkeley.EDU> <20090304193329.GD26763@carsten-otto> <200903042133.n24LXnKx025358@fruitcake.ICSI.Berkeley.EDU> Message-ID: <20090304215410.GF26763@carsten-otto> On Wed, Mar 04, 2009 at 01:33:49PM -0800, Pavlin Radoslavov wrote: > Please submit a Bugzilla entry about the issue. Sorry, I don't have the output. It only happens with your inofficial path, though (without the patch it crashes in mfea code, as already explained). > Down the road it should. Good :) Thanks, -- Carsten Otto carsten at c-otto.de www.c-otto.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090304/bda089a1/attachment.bin From rays at maine.edu Thu Mar 5 10:12:45 2009 From: rays at maine.edu (Soucy, Ray) Date: Thu, 5 Mar 2009 13:12:45 -0500 Subject: [Xorp-users] RIPng on XORP 1.6 to Cisco 7600 Message-ID: <36243D984F88BA4ABD1E0EFC1E61B989652B53@fudd.ad.maine.edu> Trying to get RIPng working on a test box and talking to a Cisco 7600. Did a trace on RIPng and see the following: [