From benjamin at sonntag.fr Mon Jul 2 03:32:09 2007 From: benjamin at sonntag.fr (Benjamin Sonntag) Date: Mon, 02 Jul 2007 12:32:09 +0200 Subject: [Xorp-users] Problem using xorp on real internet ... Message-ID: <4688D429.1020904@sonntag.fr> Hi, I'm Benjamin Sonntag, from Gitoyen.net, a french network operator (I made an up-to-date package for xorp on debian) We are currently using quagga, but we have some problems with it (eg bgp flapping during transit disconnection) We are testing xorp and we hope we will be able to use it in production, but a (quite huge) problem appeared during our tests : We put our tests notes & results here (maybe in french, sorry) https://wiki.gitoyen.net/xorp/ our second test is when xorp receive all the Internet routes from a bgp transit operator (called bsd1 here). There is about 200K routes. The configuration used is here : https://wiki.gitoyen.net/xorp/config2.deb1.boot and the bgp peer is an openbgpd whose config is here https://wiki.gitoyen.net/xorp/config2.bsd1.boot The point is that XORP took about 35 minutes (on this mono-xeon box) to compute and add the routes to the fib ! During this time, xorp_bgpd and other processes took all the cpu cycles. Is this behavior normal ? Is Xorp bound to be used by network operator using bgp or does it need some (big) optimizations ? Is it something that can be done to make this far more lightweight ? or should we use openbgpd instead for this kind of usage ? Thanks in advance for you advices, Best regards, Benjamin Sonntag Gitoyen From zec at icir.org Mon Jul 2 05:18:21 2007 From: zec at icir.org (Marko Zec) Date: Mon, 2 Jul 2007 14:18:21 +0200 Subject: [Xorp-users] Problem using xorp on real internet ... In-Reply-To: <4688D429.1020904@sonntag.fr> References: <4688D429.1020904@sonntag.fr> Message-ID: <200707021418.21872.zec@icir.org> On Monday 02 July 2007 12:32, Benjamin Sonntag wrote: > Hi, > > I'm Benjamin Sonntag, from Gitoyen.net, a french network operator (I > made an up-to-date package for xorp on debian) > > We are currently using quagga, but we have some problems with it (eg > bgp flapping during transit disconnection) > > We are testing xorp and we hope we will be able to use it in > production, but a (quite huge) problem appeared during our tests : > > We put our tests notes & results here (maybe in french, sorry) > https://wiki.gitoyen.net/xorp/ > > our second test is when xorp receive all the Internet routes from a > bgp transit operator (called bsd1 here). There is about 200K routes. > > The configuration used is here : > https://wiki.gitoyen.net/xorp/config2.deb1.boot > and the bgp peer is an openbgpd whose config is here > https://wiki.gitoyen.net/xorp/config2.bsd1.boot > > The point is that XORP took about 35 minutes (on this mono-xeon box) > to compute and add the routes to the fib ! During this time, > xorp_bgpd and other processes took all the cpu cycles. > > Is this behavior normal ? Is Xorp bound to be used by network > operator using bgp or does it need some (big) optimizations ? > > Is it something that can be done to make this far more lightweight ? > or should we use openbgpd instead for this kind of usage ? Hi, you might try to configure and build XORP with a few optimization flags enabled, as described at the very bottom of the BUILD_NOTES file. The --enable-optimize and --disable-debug flags in particular should yield significant improvements, while the others are very much compiler specific but might be worth playing with. Nevertheless, even with compile-time optimizations enabled, XORP currently lags behind Quagga and OpenBGPD in terms of raw route-crunching throughput. Cheers, Marko From M.Handley at cs.ucl.ac.uk Mon Jul 2 07:05:44 2007 From: M.Handley at cs.ucl.ac.uk (Mark Handley) Date: Mon, 2 Jul 2007 15:05:44 +0100 Subject: [Xorp-users] Problem using xorp on real internet ... In-Reply-To: <200707021418.21872.zec@icir.org> References: <4688D429.1020904@sonntag.fr> <200707021418.21872.zec@icir.org> Message-ID: <84a612dd0707020705r579d08b0ia1caa089f9b5ccef@mail.gmail.com> On 7/2/07, Marko Zec wrote: > Hi, > > you might try to configure and build XORP with a few optimization flags > enabled, as described at the very bottom of the BUILD_NOTES file. The > --enable-optimize and --disable-debug flags in particular should yield > significant improvements, while the others are very much compiler > specific but might be worth playing with. Nevertheless, even with > compile-time optimizations enabled, XORP currently lags behind Quagga > and OpenBGPD in terms of raw route-crunching throughput. I agree. There are a lot of things we can do about this; some are on my list, after the jumbo patch I'm currently working on for 4-byte AS numbers. We use quite a bit more memory than we need to, in part because a lot of code for debugging is still in place. Removing this extra memory usage should help performance, as there's a good chance that just touching so much memory is one the the things that hurts us at the moment. - Mark From pavlin at icir.org Mon Jul 2 10:07:28 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 02 Jul 2007 10:07:28 -0700 Subject: [Xorp-users] Routing Capacity in XORP In-Reply-To: Message from Diego Salvador of "Fri, 29 Jun 2007 06:52:09 PDT." <522780.66113.qm@web57415.mail.re1.yahoo.com> Message-ID: <200707021707.l62H7S44035623@possum.icir.org> Diego Salvador wrote: > Hi! How to test routing capacity on XORP protocols in unicast (RIP, OSPF, BGP) and multicast (PIM-SM, MLD and IGMP)? Please define "routing capacity". If it is the max. forwarding bandwidth, it is determined by the underlying system, because XORP implements only the control plane. If it is, say, the maximum number of routes that can be stored, it is practically limited by the amount of RAM you have in your system. Regards, Pavlin > > Thanks. > > Diego > > > --------------------------------- > Tired of spam? Yahoo! Mail has the best spam protection around > http://ph.mail.yahoo.com_______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From atanu at ICSI.Berkeley.EDU Mon Jul 2 17:45:57 2007 From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh) Date: Mon, 02 Jul 2007 17:45:57 -0700 Subject: [Xorp-users] Problem using xorp on real internet ... In-Reply-To: Message from Benjamin Sonntag of "Mon, 02 Jul 2007 12:32:09 +0200." <4688D429.1020904@sonntag.fr> Message-ID: <75538.1183423557@tigger.icir.org> Benjamin> The point is that XORP took about 35 minutes (on this Benjamin> mono-xeon box) to compute and add the routes to the fib ! Benjamin> During this time, xorp_bgpd and other processes took all Benjamin> the cpu cycles. Hi, It shouldn't have taken so long for a single peering. Could you try your experiment again with the latest code from the CVS (a scheduling change was made after the release) and with Marko's suggested configuration flags. Atanu. From a.greenhalgh at cs.ucl.ac.uk Tue Jul 3 04:32:53 2007 From: a.greenhalgh at cs.ucl.ac.uk (Adam Greenhalgh) Date: Tue, 3 Jul 2007 12:32:53 +0100 Subject: [Xorp-users] XORP and Virtual Routers In-Reply-To: <699604.87840.qm@web57404.mail.re1.yahoo.com> References: <699604.87840.qm@web57404.mail.re1.yahoo.com> Message-ID: <4769af410707030432s751f57e2ya656805cff84f9f9@mail.gmail.com> Diego, Yes there is work under way at the moment at UCL to add virtual routing to xorp, the fea clean up you might have seen is part of this work. We are heading towards something link slide 21 in xorp-virt.pdf. What do you mean by a virtual router ? What do you want from a virtual router ? Adam On 6/26/07, Diego Salvador wrote: > Thanks to all of you replying my concern. I apologize because perhaps I was > wrong in building my statement here because what I want to know is the > virtual routing and forwarding in XORP based on what I have encountered from > the documents > http://www.ipinfusion.com/pdf/VirtualRouting_app-note_3rev0302.pdf > as well as this > http://www.cs.ucl.ac.uk/staff/M.Handley/slides/xorp-virt.pdf. > > Thanks. > > Diego > From eadigun at cs.up.ac.za Tue Jul 3 07:32:27 2007 From: eadigun at cs.up.ac.za (Emmanuel A. Adigun) Date: Tue, 3 Jul 2007 16:32:27 +0200 (SAST) Subject: [Xorp-users] Help with router manager Message-ID: <39591.137.215.41.60.1183473147.squirrel@staff.cs.up.ac.za> Hi, I just started using XORP and i've read all the accompanying documentation but i just can't seem to start the router manager. The log is attached below. I've modified the configuration file to work in my network environment as specified in the the manual and getting started docs but i get the same error message and it looks like the XORPSH won't start unless the router manager is running. Another thing is i don't know what the xrlrouter has to do with it? Is there a seperate config file for the xrl router that must be modified? Thanks in anticipation. Emmanuel The logs are as follows: *starting up routing manager by invoking-xorp_rtrmgr* [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +239 master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, rib, fib2mrib, igmp, pimsm4, policy, rip, static_routes, bgp, ospf4, ospf6 [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +96 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started [ 2007/07/03 16:18:36 ERROR xorp_fea:5895 FEA +665 ifconfig_set.cc push_vif_address ] Interface/Vif/Address error on eth0/eth0/169.254.8.11: Failed to configure address: AF_NETLINK NLMSG_ERROR message: Operation not permitted [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +747 module_manager.cc done_cb ] Command "/home/ayowole/Desktop/xorp-1.4/fea/xorp_fea": terminated with signal 11; aborted with a core dump. [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +291 module_manager.cc module_exited ] Module coredumped: interfaces [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1400 task.cc execute_done ] 210 Transport failed [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1998 task.cc task_fail ] Shutting down fatally wounded process (interfaces) [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +675 master_conf_tree.cc commit_pass2_done ] Commit failed: 210 Transport failed [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +251 master_conf_tree.cc config_done ] Configuration failed: 210 Transport failed [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +2228 task.cc run_task ] No more tasks to run *Starting up XORPSH* [ 2007/07/03 16:19:06 WARNING xorpsh RTRMGR ] [Operational Command File: /home/ayowole/Desktop/xorp-1.4/etc/templates/misc.cmds line 29]: Executable file not found: traceroute Waiting for xorp_rtrmgr... [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +90 xorpsh_main.cc wait_for_xrl_router_ready ] XrlRouter failed. No Finder? [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +897 xorpsh_main.cc main ] xorpsh exiting due to an init error: Failed to connect to the router manager From a.greenhalgh at cs.ucl.ac.uk Tue Jul 3 07:45:06 2007 From: a.greenhalgh at cs.ucl.ac.uk (Adam Greenhalgh) Date: Tue, 3 Jul 2007 15:45:06 +0100 Subject: [Xorp-users] Help with router manager In-Reply-To: <39591.137.215.41.60.1183473147.squirrel@staff.cs.up.ac.za> References: <39591.137.215.41.60.1183473147.squirrel@staff.cs.up.ac.za> Message-ID: <4769af410707030745vaafa048q9c12812a36e577b0@mail.gmail.com> Have you tried running as root ? It seems to fail when it tries to config the interfaces . Adam On 7/3/07, Emmanuel A. Adigun wrote: > Hi, > > I just started using XORP and i've read all the accompanying documentation > but i just can't seem to start the router manager. The log is attached > below. > > I've modified the configuration file to work in my network environment as > specified in the the manual and getting started docs but i get the same > error message and it looks like the XORPSH won't start unless the router > manager is running. > Another thing is i don't know what the xrlrouter has to do with it? Is > there a seperate config file for the xrl router that must be modified? > > Thanks in anticipation. > Emmanuel > > The logs are as follows: > > *starting up routing manager by invoking-xorp_rtrmgr* > > [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +239 > master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, > rib, fib2mrib, igmp, pimsm4, policy, rip, static_routes, bgp, ospf4, ospf6 > [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +96 module_manager.cc > execute ] Executing module: interfaces (fea/xorp_fea) > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started > [ 2007/07/03 16:18:36 ERROR xorp_fea:5895 FEA +665 ifconfig_set.cc > push_vif_address ] Interface/Vif/Address error on eth0/eth0/169.254.8.11: > Failed to configure address: AF_NETLINK NLMSG_ERROR message: Operation not > permitted > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +747 > module_manager.cc done_cb ] Command > "/home/ayowole/Desktop/xorp-1.4/fea/xorp_fea": terminated with signal 11; > aborted with a core dump. > [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +291 module_manager.cc > module_exited ] Module coredumped: interfaces > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1400 task.cc > execute_done ] 210 Transport failed > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1998 task.cc > task_fail ] Shutting down fatally wounded process (interfaces) > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +675 > master_conf_tree.cc commit_pass2_done ] Commit failed: 210 Transport > failed > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +251 > master_conf_tree.cc config_done ] Configuration failed: 210 Transport > failed > [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +2228 task.cc run_task > ] No more tasks to run > > *Starting up XORPSH* > > [ 2007/07/03 16:19:06 WARNING xorpsh RTRMGR ] [Operational Command File: > /home/ayowole/Desktop/xorp-1.4/etc/templates/misc.cmds line 29]: > Executable file not found: traceroute > Waiting for xorp_rtrmgr... > [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +90 xorpsh_main.cc > wait_for_xrl_router_ready ] XrlRouter failed. No Finder? > [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +897 xorpsh_main.cc main ] > xorpsh exiting due to an init error: Failed to connect to the router > manager > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > From eadigun at cs.up.ac.za Tue Jul 3 08:02:22 2007 From: eadigun at cs.up.ac.za (Emmanuel A. Adigun) Date: Tue, 3 Jul 2007 17:02:22 +0200 Subject: [Xorp-users] Help with router manager In-Reply-To: <4769af410707030745vaafa048q9c12812a36e577b0@mail.gmail.com> Message-ID: I have but seem to come up with the same error message and I'm also running under the XORP UNIX group. -----Original Message----- From: adam.greenhalgh at gmail.com [mailto:adam.greenhalgh at gmail.com] On Behalf Of Adam Greenhalgh Sent: 03 July 2007 04:45 PM To: Emmanuel A. Adigun Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] Help with router manager Have you tried running as root ? It seems to fail when it tries to config the interfaces . Adam On 7/3/07, Emmanuel A. Adigun wrote: > Hi, > > I just started using XORP and i've read all the accompanying documentation > but i just can't seem to start the router manager. The log is attached > below. > > I've modified the configuration file to work in my network environment as > specified in the the manual and getting started docs but i get the same > error message and it looks like the XORPSH won't start unless the router > manager is running. > Another thing is i don't know what the xrlrouter has to do with it? Is > there a seperate config file for the xrl router that must be modified? > > Thanks in anticipation. > Emmanuel > > The logs are as follows: > > *starting up routing manager by invoking-xorp_rtrmgr* > > [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +239 > master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, > rib, fib2mrib, igmp, pimsm4, policy, rip, static_routes, bgp, ospf4, ospf6 > [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +96 module_manager.cc > execute ] Executing module: interfaces (fea/xorp_fea) > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started > [ 2007/07/03 16:18:36 ERROR xorp_fea:5895 FEA +665 ifconfig_set.cc > push_vif_address ] Interface/Vif/Address error on eth0/eth0/169.254.8.11: > Failed to configure address: AF_NETLINK NLMSG_ERROR message: Operation not > permitted > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +747 > module_manager.cc done_cb ] Command > "/home/ayowole/Desktop/xorp-1.4/fea/xorp_fea": terminated with signal 11; > aborted with a core dump. > [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +291 module_manager.cc > module_exited ] Module coredumped: interfaces > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1400 task.cc > execute_done ] 210 Transport failed > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1998 task.cc > task_fail ] Shutting down fatally wounded process (interfaces) > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +675 > master_conf_tree.cc commit_pass2_done ] Commit failed: 210 Transport > failed > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +251 > master_conf_tree.cc config_done ] Configuration failed: 210 Transport > failed > [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +2228 task.cc run_task > ] No more tasks to run > > *Starting up XORPSH* > > [ 2007/07/03 16:19:06 WARNING xorpsh RTRMGR ] [Operational Command File: > /home/ayowole/Desktop/xorp-1.4/etc/templates/misc.cmds line 29]: > Executable file not found: traceroute > Waiting for xorp_rtrmgr... > [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +90 xorpsh_main.cc > wait_for_xrl_router_ready ] XrlRouter failed. No Finder? > [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +897 xorpsh_main.cc main ] > xorpsh exiting due to an init error: Failed to connect to the router > manager > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > From eadigun at cs.up.ac.za Tue Jul 3 09:02:13 2007 From: eadigun at cs.up.ac.za (Emmanuel A. Adigun) Date: Tue, 3 Jul 2007 18:02:13 +0200 (SAST) Subject: [Xorp-users] Help with router manager In-Reply-To: <4769af410707030804v900d92bw6bc3c4ffa91e0260@mail.gmail.com> References: <4769af410707030745vaafa048q9c12812a36e577b0@mail.gmail.com> <4769af410707030804v900d92bw6bc3c4ffa91e0260@mail.gmail.com> Message-ID: <45623.137.215.41.60.1183478533.squirrel@staff.cs.up.ac.za> Basic Config file used is attached below: interfaces { restore-original-config-on-shutdown: false interface eth0 { description: "data interface" disable: false /* default-system-config */ vif eth0 { disable: false address 169.254.8.11 { prefix-length: 24 broadcast: 169.254.255.255 disable: false } } } interface discard0 { description: "discard interface" disable: false discard: true vif discard0 { disable: false address 169.254.8.12 { prefix-length: 32 disable: false } } } } fea { unicast-forwarding4 { disable: false forwarding-entries { retain-on-startup: false retain-on-shutdown: false } } } protocols { static { route 169.254.0.0/16 { next-hop: 169.254.8.1 metric: 1 } mrib-route 169.254.0.0/16 { next-hop: 169.254.8.30 metric: 1 } } } Thanks > I think you need to attach your config file to a post to the list. > > adam > > On 7/3/07, Emmanuel A. Adigun wrote: >> I have but seem to come up with the same error message and I'm also >> running >> under the XORP UNIX group. >> >> -----Original Message----- >> From: adam.greenhalgh at gmail.com [mailto:adam.greenhalgh at gmail.com] On >> Behalf >> Of Adam Greenhalgh >> Sent: 03 July 2007 04:45 PM >> To: Emmanuel A. Adigun >> Cc: xorp-users at xorp.org >> Subject: Re: [Xorp-users] Help with router manager >> >> Have you tried running as root ? It seems to fail when it tries to >> config the interfaces . >> >> Adam >> >> On 7/3/07, Emmanuel A. Adigun wrote: >> > Hi, >> > >> > I just started using XORP and i've read all the accompanying >> documentation >> > but i just can't seem to start the router manager. The log is attached >> > below. >> > >> > I've modified the configuration file to work in my network environment >> as >> > specified in the the manual and getting started docs but i get the >> same >> > error message and it looks like the XORPSH won't start unless the >> router >> > manager is running. >> > Another thing is i don't know what the xrlrouter has to do with it? Is >> > there a seperate config file for the xrl router that must be modified? >> > >> > Thanks in anticipation. >> > Emmanuel >> > >> > The logs are as follows: >> > >> > *starting up routing manager by invoking-xorp_rtrmgr* >> > >> > [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +239 >> > master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, >> > rib, fib2mrib, igmp, pimsm4, policy, rip, static_routes, bgp, ospf4, >> ospf6 >> > [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +96 >> module_manager.cc >> > execute ] Executing module: interfaces (fea/xorp_fea) >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started >> > [ 2007/07/03 16:18:36 ERROR xorp_fea:5895 FEA +665 ifconfig_set.cc >> > push_vif_address ] Interface/Vif/Address error on >> eth0/eth0/169.254.8.11: >> > Failed to configure address: AF_NETLINK NLMSG_ERROR message: Operation >> not >> > permitted >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +747 >> > module_manager.cc done_cb ] Command >> > "/home/ayowole/Desktop/xorp-1.4/fea/xorp_fea": terminated with signal >> 11; >> > aborted with a core dump. >> > [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +291 >> module_manager.cc >> > module_exited ] Module coredumped: interfaces >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1400 task.cc >> > execute_done ] 210 Transport failed >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1998 task.cc >> > task_fail ] Shutting down fatally wounded process (interfaces) >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +675 >> > master_conf_tree.cc commit_pass2_done ] Commit failed: 210 Transport >> > failed >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +251 >> > master_conf_tree.cc config_done ] Configuration failed: 210 Transport >> > failed >> > [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +2228 task.cc >> run_task >> > ] No more tasks to run >> > >> > *Starting up XORPSH* >> > >> > [ 2007/07/03 16:19:06 WARNING xorpsh RTRMGR ] [Operational Command >> File: >> > /home/ayowole/Desktop/xorp-1.4/etc/templates/misc.cmds line 29]: >> > Executable file not found: traceroute >> > Waiting for xorp_rtrmgr... >> > [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +90 xorpsh_main.cc >> > wait_for_xrl_router_ready ] XrlRouter failed. No Finder? >> > [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +897 xorpsh_main.cc >> main ] >> > xorpsh exiting due to an init error: Failed to connect to the router >> > manager >> > >> > _______________________________________________ >> > Xorp-users mailing list >> > Xorp-users at xorp.org >> > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> > >> >> >> > From a.greenhalgh at cs.ucl.ac.uk Tue Jul 3 09:12:09 2007 From: a.greenhalgh at cs.ucl.ac.uk (Adam Greenhalgh) Date: Tue, 3 Jul 2007 17:12:09 +0100 Subject: [Xorp-users] Help with router manager In-Reply-To: <45623.137.215.41.60.1183478533.squirrel@staff.cs.up.ac.za> References: <4769af410707030745vaafa048q9c12812a36e577b0@mail.gmail.com> <4769af410707030804v900d92bw6bc3c4ffa91e0260@mail.gmail.com> <45623.137.215.41.60.1183478533.squirrel@staff.cs.up.ac.za> Message-ID: <4769af410707030912m33140f00mb60ed020de1d055f@mail.gmail.com> try commenting out the discard interface setting adam On 7/3/07, Emmanuel A. Adigun wrote: > Basic Config file used is attached below: > > interfaces { > restore-original-config-on-shutdown: false > interface eth0 { > description: "data interface" > disable: false > /* default-system-config */ > vif eth0 { > disable: false > address 169.254.8.11 { > prefix-length: 24 > broadcast: 169.254.255.255 > disable: false > } > } > } > > interface discard0 { > description: "discard interface" > disable: false > discard: true > vif discard0 { > disable: false > address 169.254.8.12 { > prefix-length: 32 > disable: false > } > } > } > } > > fea { > unicast-forwarding4 { > disable: false > forwarding-entries { > retain-on-startup: false > retain-on-shutdown: false > } > } > } > > protocols { > static { > route 169.254.0.0/16 { > next-hop: 169.254.8.1 > metric: 1 > > } > mrib-route 169.254.0.0/16 { > next-hop: 169.254.8.30 > metric: 1 > } > > } > } > > Thanks > > > > I think you need to attach your config file to a post to the list. > > > > adam > > > > On 7/3/07, Emmanuel A. Adigun wrote: > >> I have but seem to come up with the same error message and I'm also > >> running > >> under the XORP UNIX group. > >> > >> -----Original Message----- > >> From: adam.greenhalgh at gmail.com [mailto:adam.greenhalgh at gmail.com] On > >> Behalf > >> Of Adam Greenhalgh > >> Sent: 03 July 2007 04:45 PM > >> To: Emmanuel A. Adigun > >> Cc: xorp-users at xorp.org > >> Subject: Re: [Xorp-users] Help with router manager > >> > >> Have you tried running as root ? It seems to fail when it tries to > >> config the interfaces . > >> > >> Adam > >> > >> On 7/3/07, Emmanuel A. Adigun wrote: > >> > Hi, > >> > > >> > I just started using XORP and i've read all the accompanying > >> documentation > >> > but i just can't seem to start the router manager. The log is attached > >> > below. > >> > > >> > I've modified the configuration file to work in my network environment > >> as > >> > specified in the the manual and getting started docs but i get the > >> same > >> > error message and it looks like the XORPSH won't start unless the > >> router > >> > manager is running. > >> > Another thing is i don't know what the xrlrouter has to do with it? Is > >> > there a seperate config file for the xrl router that must be modified? > >> > > >> > Thanks in anticipation. > >> > Emmanuel > >> > > >> > The logs are as follows: > >> > > >> > *starting up routing manager by invoking-xorp_rtrmgr* > >> > > >> > [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +239 > >> > master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, > >> > rib, fib2mrib, igmp, pimsm4, policy, rip, static_routes, bgp, ospf4, > >> ospf6 > >> > [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +96 > >> module_manager.cc > >> > execute ] Executing module: interfaces (fea/xorp_fea) > >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled > >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled > >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started > >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled > >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled > >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started > >> > [ 2007/07/03 16:18:36 ERROR xorp_fea:5895 FEA +665 ifconfig_set.cc > >> > push_vif_address ] Interface/Vif/Address error on > >> eth0/eth0/169.254.8.11: > >> > Failed to configure address: AF_NETLINK NLMSG_ERROR message: Operation > >> not > >> > permitted > >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +747 > >> > module_manager.cc done_cb ] Command > >> > "/home/ayowole/Desktop/xorp-1.4/fea/xorp_fea": terminated with signal > >> 11; > >> > aborted with a core dump. > >> > [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +291 > >> module_manager.cc > >> > module_exited ] Module coredumped: interfaces > >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1400 task.cc > >> > execute_done ] 210 Transport failed > >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1998 task.cc > >> > task_fail ] Shutting down fatally wounded process (interfaces) > >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +675 > >> > master_conf_tree.cc commit_pass2_done ] Commit failed: 210 Transport > >> > failed > >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +251 > >> > master_conf_tree.cc config_done ] Configuration failed: 210 Transport > >> > failed > >> > [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +2228 task.cc > >> run_task > >> > ] No more tasks to run > >> > > >> > *Starting up XORPSH* > >> > > >> > [ 2007/07/03 16:19:06 WARNING xorpsh RTRMGR ] [Operational Command > >> File: > >> > /home/ayowole/Desktop/xorp-1.4/etc/templates/misc.cmds line 29]: > >> > Executable file not found: traceroute > >> > Waiting for xorp_rtrmgr... > >> > [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +90 xorpsh_main.cc > >> > wait_for_xrl_router_ready ] XrlRouter failed. No Finder? > >> > [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +897 xorpsh_main.cc > >> main ] > >> > xorpsh exiting due to an init error: Failed to connect to the router > >> > manager > >> > > >> > _______________________________________________ > >> > 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 > From eadigun at cs.up.ac.za Tue Jul 3 09:37:02 2007 From: eadigun at cs.up.ac.za (Emmanuel A. Adigun) Date: Tue, 3 Jul 2007 18:37:02 +0200 (SAST) Subject: [Xorp-users] Help with router manager In-Reply-To: <4769af410707030912m33140f00mb60ed020de1d055f@mail.gmail.com> References: <4769af410707030745vaafa048q9c12812a36e577b0@mail.gmail.com> <4769af410707030804v900d92bw6bc3c4ffa91e0260@mail.gmail.com> <45623.137.215.41.60.1183478533.squirrel@staff.cs.up.ac.za> <4769af410707030912m33140f00mb60ed020de1d055f@mail.gmail.com> Message-ID: <35555.137.215.41.60.1183480622.squirrel@staff.cs.up.ac.za> i get an even longer, uglier error message...: [ 2007/07/03 18:16:28 INFO xorp_rtrmgr:7686 RTRMGR +239 master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, rib, fib2mrib, igmp, pimsm4, policy, rip, static_routes, bgp, ospf4, ospf6 [ 2007/07/03 18:16:29 INFO xorp_rtrmgr:7686 RTRMGR +96 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2007/07/03 18:16:29 INFO xorp_fea MFEA ] MFEA enabled [ 2007/07/03 18:16:29 INFO xorp_fea MFEA ] CLI enabled [ 2007/07/03 18:16:29 INFO xorp_fea MFEA ] CLI started [ 2007/07/03 18:16:29 INFO xorp_fea MFEA ] MFEA enabled [ 2007/07/03 18:16:29 INFO xorp_fea MFEA ] CLI enabled [ 2007/07/03 18:16:29 INFO xorp_fea MFEA ] CLI started [ 2007/07/03 18:16:31 ERROR xorp_fea:7687 FEA +665 ifconfig_set.cc push_vif_address ] Interface/Vif/Address error on eth0/eth0/169.254.8.11: Failed to configure address: AF_NETLINK NLMSG_ERROR message: Operation not permitted [ 2007/07/03 18:16:31 ERROR xorp_fea:7687 FEA +578 ifconfig_set.cc push_vif_address ] Interface/Vif/Address error on eth0/eth0/169.254.8.11: Failed to delete address: AF_NETLINK NLMSG_ERROR message: Operation not permitted [ 2007/07/03 18:16:31 ERROR xorp_fea:7687 FEA +291 ifconfig_set.cc push_interface_end ] Interface error on eth0: Failed to configure interface: Permission denied [ 2007/07/03 18:16:31 WARNING xorp_fea XrlFeaTarget ] Handling method for ifmgr/0.1/commit_transaction failed: XrlCmdError 102 Command failed Interface/Vif/Address error on eth0/eth0/169.254.8.11: Failed to configure address: AF_NETLINK NLMSG_ERROR message: Operation not permitted [Also, failed to reverse-back to the previous config: Interface/Vif/Address error on eth0/eth0/169.254.8.11: Failed to delete address: AF_NETLINK NLMSG_ERROR message: Operation not permitted] [ 2007/07/03 18:16:31 ERROR xorp_rtrmgr:7686 RTRMGR +675 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Interface/Vif/Address error on eth0/eth0/169.254.8.11: Failed to configure address: AF_NETLINK NLMSG_ERROR message: Operation not permitted [Also, failed to reverse-back to the previous config: Interface/Vif/Address error on eth0/eth0/169.254.8.11: Failed to delete address: AF_NETLINK NLMSG_ERROR message: Operation not permitted] [ 2007/07/03 18:16:31 ERROR xorp_rtrmgr:7686 RTRMGR +251 master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Interface/Vif/Address error on eth0/eth0/169.254.8.11: Failed to configure address: AF_NETLINK NLMSG_ERROR message: Operation not permitted [Also, failed to reverse-back to the previous config: Interface/Vif/Address error on eth0/eth0/169.254.8.11: Failed to delete address: AF_NETLINK NLMSG_ERROR message: Operation not permitted] [ 2007/07/03 18:16:31 INFO xorp_rtrmgr:7686 RTRMGR +2228 task.cc run_task ] No more tasks to run [ 2007/07/03 18:16:31 INFO xorp_rtrmgr:7686 RTRMGR +171 module_manager.cc terminate ] Terminating module: interfaces [ 2007/07/03 18:16:31 INFO xorp_rtrmgr:7686 RTRMGR +194 module_manager.cc terminate ] Killing module: interfaces [ 2007/07/03 18:16:31 ERROR xorp_rtrmgr:7686 RTRMGR +747 module_manager.cc done_cb ] Command "/home/ayowole/Desktop/xorp-1.4/fea/xorp_fea": terminated with signal 15. [ 2007/07/03 18:16:31 INFO xorp_rtrmgr:7686 RTRMGR +282 module_manager.cc module_exited ] Module killed during shutdown: interfaces Is it possible to set permissions in the config file? Does it matter if the computer is a standalone computer, that is, if i manually type in an IP address-and the address is used in the config file? I'm connected to a LAN but i found out that if i use my DHCP assigned IP address when i run the router manager my computer acts as a router on our network! > try commenting out the discard interface setting > > adam > > On 7/3/07, Emmanuel A. Adigun wrote: >> Basic Config file used is attached below: >> >> interfaces { >> restore-original-config-on-shutdown: false >> interface eth0 { >> description: "data interface" >> disable: false >> /* default-system-config */ >> vif eth0 { >> disable: false >> address 169.254.8.11 { >> prefix-length: 24 >> broadcast: 169.254.255.255 >> disable: false >> } >> } >> } >> >> interface discard0 { >> description: "discard interface" >> disable: false >> discard: true >> vif discard0 { >> disable: false >> address 169.254.8.12 { >> prefix-length: 32 >> disable: false >> } >> } >> } >> } >> >> fea { >> unicast-forwarding4 { >> disable: false >> forwarding-entries { >> retain-on-startup: false >> retain-on-shutdown: false >> } >> } >> } >> >> protocols { >> static { >> route 169.254.0.0/16 { >> next-hop: 169.254.8.1 >> metric: 1 >> >> } >> mrib-route 169.254.0.0/16 { >> next-hop: 169.254.8.30 >> metric: 1 >> } >> >> } >> } >> >> Thanks >> >> >> > I think you need to attach your config file to a post to the list. >> > >> > adam >> > >> > On 7/3/07, Emmanuel A. Adigun wrote: >> >> I have but seem to come up with the same error message and I'm also >> >> running >> >> under the XORP UNIX group. >> >> >> >> -----Original Message----- >> >> From: adam.greenhalgh at gmail.com [mailto:adam.greenhalgh at gmail.com] On >> >> Behalf >> >> Of Adam Greenhalgh >> >> Sent: 03 July 2007 04:45 PM >> >> To: Emmanuel A. Adigun >> >> Cc: xorp-users at xorp.org >> >> Subject: Re: [Xorp-users] Help with router manager >> >> >> >> Have you tried running as root ? It seems to fail when it tries to >> >> config the interfaces . >> >> >> >> Adam >> >> >> >> On 7/3/07, Emmanuel A. Adigun wrote: >> >> > Hi, >> >> > >> >> > I just started using XORP and i've read all the accompanying >> >> documentation >> >> > but i just can't seem to start the router manager. The log is >> attached >> >> > below. >> >> > >> >> > I've modified the configuration file to work in my network >> environment >> >> as >> >> > specified in the the manual and getting started docs but i get the >> >> same >> >> > error message and it looks like the XORPSH won't start unless the >> >> router >> >> > manager is running. >> >> > Another thing is i don't know what the xrlrouter has to do with it? >> Is >> >> > there a seperate config file for the xrl router that must be >> modified? >> >> > >> >> > Thanks in anticipation. >> >> > Emmanuel >> >> > >> >> > The logs are as follows: >> >> > >> >> > *starting up routing manager by invoking-xorp_rtrmgr* >> >> > >> >> > [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +239 >> >> > master_conf_tree.cc execute ] Changed modules: interfaces, fea, >> mfea4, >> >> > rib, fib2mrib, igmp, pimsm4, policy, rip, static_routes, bgp, >> ospf4, >> >> ospf6 >> >> > [ 2007/07/03 16:18:34 INFO xorp_rtrmgr:5894 RTRMGR +96 >> >> module_manager.cc >> >> > execute ] Executing module: interfaces (fea/xorp_fea) >> >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled >> >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled >> >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started >> >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] MFEA enabled >> >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI enabled >> >> > [ 2007/07/03 16:18:35 INFO xorp_fea MFEA ] CLI started >> >> > [ 2007/07/03 16:18:36 ERROR xorp_fea:5895 FEA +665 ifconfig_set.cc >> >> > push_vif_address ] Interface/Vif/Address error on >> >> eth0/eth0/169.254.8.11: >> >> > Failed to configure address: AF_NETLINK NLMSG_ERROR message: >> Operation >> >> not >> >> > permitted >> >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +747 >> >> > module_manager.cc done_cb ] Command >> >> > "/home/ayowole/Desktop/xorp-1.4/fea/xorp_fea": terminated with >> signal >> >> 11; >> >> > aborted with a core dump. >> >> > [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +291 >> >> module_manager.cc >> >> > module_exited ] Module coredumped: interfaces >> >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1400 task.cc >> >> > execute_done ] 210 Transport failed >> >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +1998 task.cc >> >> > task_fail ] Shutting down fatally wounded process (interfaces) >> >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +675 >> >> > master_conf_tree.cc commit_pass2_done ] Commit failed: 210 >> Transport >> >> > failed >> >> > [ 2007/07/03 16:18:36 ERROR xorp_rtrmgr:5894 RTRMGR +251 >> >> > master_conf_tree.cc config_done ] Configuration failed: 210 >> Transport >> >> > failed >> >> > [ 2007/07/03 16:18:36 INFO xorp_rtrmgr:5894 RTRMGR +2228 task.cc >> >> run_task >> >> > ] No more tasks to run >> >> > >> >> > *Starting up XORPSH* >> >> > >> >> > [ 2007/07/03 16:19:06 WARNING xorpsh RTRMGR ] [Operational Command >> >> File: >> >> > /home/ayowole/Desktop/xorp-1.4/etc/templates/misc.cmds line 29]: >> >> > Executable file not found: traceroute >> >> > Waiting for xorp_rtrmgr... >> >> > [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +90 xorpsh_main.cc >> >> > wait_for_xrl_router_ready ] XrlRouter failed. No Finder? >> >> > [ 2007/07/03 16:19:35 ERROR xorpsh:5898 RTRMGR +897 xorpsh_main.cc >> >> main ] >> >> > xorpsh exiting due to an init error: Failed to connect to the >> router >> >> > manager >> >> > >> >> > _______________________________________________ >> >> > 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 >> > From salvador_d13 at yahoo.com.ph Wed Jul 4 07:10:45 2007 From: salvador_d13 at yahoo.com.ph (Diego Salvador) Date: Wed, 4 Jul 2007 07:10:45 -0700 (PDT) Subject: [Xorp-users] Routing Capacity in XORP In-Reply-To: <200707021707.l62H7S44035623@possum.icir.org> Message-ID: <913156.32635.qm@web57406.mail.re1.yahoo.com> Hi Pavlin, First of, thanks for your reply! The routing capacity I mean falls to your second statement about maximum number of routes that can be stored in memory or RAM. So in this case, it only depends on the amount of memory storage available in your system. What if I have 128MB of RAM and then I want to know if how much is the capacity of that given RAM, what tool should I used in generating routes? Is there any available tools for free to use? And on this given RAM capacity, I need to test each routing protocols either unicast [BGP, OSPF, RIP and static] and multicast [IGMP, MLD and PIM-SM]. I think this way, I can see how each routing protocols will be benchmark according to RAM load. Just tell me if I am doing the right benchmark. Thanks. Diego Pavlin Radoslavov wrote: Diego Salvador wrote: > Hi! How to test routing capacity on XORP protocols in unicast (RIP, OSPF, BGP) and multicast (PIM-SM, MLD and IGMP)? Please define "routing capacity". If it is the max. forwarding bandwidth, it is determined by the underlying system, because XORP implements only the control plane. If it is, say, the maximum number of routes that can be stored, it is practically limited by the amount of RAM you have in your system. Regards, Pavlin > > Thanks. > > Diego > > > --------------------------------- > Tired of spam? Yahoo! Mail has the best spam protection around > http://ph.mail.yahoo.com_______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users --------------------------------- Tired of spam? Yahoo! Mail has the best spam protection around http://ph.mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070704/9569b4c3/attachment.html From salvador_d13 at yahoo.com.ph Wed Jul 4 07:59:25 2007 From: salvador_d13 at yahoo.com.ph (Diego Salvador) Date: Wed, 4 Jul 2007 07:59:25 -0700 (PDT) Subject: [Xorp-users] XORP and Virtual Routers In-Reply-To: <4769af410707030432s751f57e2ya656805cff84f9f9@mail.gmail.com> Message-ID: <885309.11587.qm@web57408.mail.re1.yahoo.com> Hi Adam, Thanks to your reply! A virtual router is an emulation of a physical router at the software level that can create many instances of routers and protocols in a single unit. The instances of routers and protocols are independent to each other like for example, an instance of a virtual router [A] with virtual instances of protocols such as BGP, OSPF, ISIS, RIP, IGMP, PIM-SM and MLD and another instance of virtual router [B] with another virtual instances of protocols like what virtual router [A] has. So virtual router [A] is independent on virtual router [B] in a single physical unit. Virtual router is a solution commonly used for virtual networks serving many users with different routing protocol requirements and routing infrastructure. Thanks. Diego Adam Greenhalgh wrote: Diego, Yes there is work under way at the moment at UCL to add virtual routing to xorp, the fea clean up you might have seen is part of this work. We are heading towards something link slide 21 in xorp-virt.pdf. What do you mean by a virtual router ? What do you want from a virtual router ? Adam On 6/26/07, Diego Salvador wrote: > Thanks to all of you replying my concern. I apologize because perhaps I was > wrong in building my statement here because what I want to know is the > virtual routing and forwarding in XORP based on what I have encountered from > the documents > http://www.ipinfusion.com/pdf/VirtualRouting_app-note_3rev0302.pdf > as well as this > http://www.cs.ucl.ac.uk/staff/M.Handley/slides/xorp-virt.pdf. > > Thanks. > > Diego > --------------------------------- Tired of spam? Yahoo! Mail has the best spam protection around http://ph.mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070704/9820d3e5/attachment.html From pavlin at icir.org Wed Jul 4 13:19:56 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Wed, 04 Jul 2007 13:19:56 -0700 Subject: [Xorp-users] Routing Capacity in XORP In-Reply-To: Message from Diego Salvador of "Wed, 04 Jul 2007 07:10:45 PDT." <913156.32635.qm@web57406.mail.re1.yahoo.com> Message-ID: <200707042019.l64KJuBK011528@possum.icir.org> > First of, thanks for your reply! The routing capacity I mean falls > to your second statement about maximum number of routes that can > be stored in memory or RAM. So in this case, it only depends on > the amount of memory storage available in your system. What if I > have 128MB of RAM and then I want to know if how much is the > capacity of that given RAM, what tool should I used in generating > routes? Is there any available tools for free to use? And on this > given RAM capacity, I need to test each routing protocols either > unicast [BGP, OSPF, RIP and static] and multicast [IGMP, MLD and > PIM-SM]. I think this way, I can see how each routing protocols > will be benchmark according to RAM load. Just tell me if I am > doing the right benchmark. Are you looking for an answer for practical purpose or for academic purpose? If you are looking for a practical answer, BGP with full feed is going to be the largest memory user. I don't remember what is the typical usage, but the BGP folks on the list can give you some rough estimations. Theoretically, the state for the multicast routing protocols can be much worse than BGP. However, because the is a very small number of multicast sessions on global scale (e.g., tens or low hundreds) this is practically not an issue (yet). The IGMP/MLD memory usage should be dominated by the process startup size. The extra memory usage (per joined group per joined interface) should be relatively low: e.g., if you start testing with a large number of receivers, I wouldn't be surprised if the bottleneck is somewhere else (e.g., the CPU or communication overhead). Unfortunately I am not aware of any free tools that you can use to investigate the memory usage as a function of the routing load. For protocols like Static you could measure the used memory when no routes are installed. Then configure a large number of routes and measure the difference in memory usage. This should give you an idea how the memory usage grows. For other protocols you would need to do something similar, but then you need to find or write tools to generate the appropriate protocol control messages. E.g., Nemesis (http://nemesis.sourceforge.net/) is the tool that comes to mind. Regards, Pavlin > Thanks. > > Diego > > > Pavlin Radoslavov wrote: Diego Salvador wrote: > > > Hi! How to test routing capacity on XORP protocols in unicast (RIP, OSPF, BGP) and multicast (PIM-SM, MLD and IGMP)? > > Please define "routing capacity". > > If it is the max. forwarding bandwidth, it is determined by the > underlying system, because XORP implements only the control plane. > > If it is, say, the maximum number of routes that can be stored, it > is practically limited by the amount of RAM you have in your system. > > Regards, > Pavlin > > > > > Thanks. > > > > Diego > > > > > > --------------------------------- > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://ph.mail.yahoo.com_______________________________________________ > > Xorp-users mailing list > > Xorp-users at xorp.org > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > > --------------------------------- > Tired of spam? Yahoo! Mail has the best spam protection around > http://ph.mail.yahoo.com_______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From salvador_d13 at yahoo.com.ph Tue Jul 10 03:45:23 2007 From: salvador_d13 at yahoo.com.ph (Diego Salvador) Date: Tue, 10 Jul 2007 03:45:23 -0700 (PDT) Subject: [Xorp-users] XORP and Virtual Routers In-Reply-To: <4769af410707050457q528b60a3s95b40f628eb7732b@mail.gmail.com> Message-ID: <857782.88974.qm@web57401.mail.re1.yahoo.com> Hi Adam, On the first place, I only wanted to use the implementation if there's any available. Second, I want to know the status of your implementation design? Maybe I can help you in implementing this functionality. As of the moment, I'm still overloaded with my current work but let see what I can do. Thanks. Diego Adam Greenhalgh wrote: Diego, Good we are talking about the same thing. Are you looking to write code or use something once implemented ? Adam On 7/4/07, Diego Salvador wrote: > Hi Adam, > > Thanks to your reply! > > A virtual router is an emulation of a physical router at the software level > that can create many instances of routers and protocols in a single unit. > The instances of routers and protocols are independent to each other like > for example, an instance of a virtual router [A] with virtual instances of > protocols such as BGP, OSPF, ISIS, RIP, IGMP, PIM-SM and MLD and another > instance of virtual router [B] with another virtual instances of protocols > like what virtual router [A] has. So virtual router [A] is independent on > virtual router [B] in a single physical unit. > > Virtual router is a solution commonly used for virtual networks serving many > users with different routing protocol requirements and routing > infrastructure. > > Thanks. > > Diego > > > > Adam Greenhalgh wrote: > Diego, > > Yes there is work under way at the moment at UCL to add virtual > routing to xorp, the fea clean up you might have seen is part of this > work. We are heading towards something link slide 21 in xorp-virt.pdf. > > What do you mean by a virtual router ? > > What do you want from a virtual router ? > > Adam > > On 6/26/07, Diego Salvador wrote: > > Thanks to all of you replying my concern. I apologize because perhaps I > was > > wrong in building my statement here because what I want to know is the > > virtual routing and forwarding in XORP based on what I have encountered > from > > the documents > > > http://www.ipinfusion.com/pdf/VirtualRouting_app-note_3rev0302.pdf > > as well as this > > > http://www.cs.ucl.ac.uk/staff/M.Handley/slides/xorp-virt.pdf. > > > > Thanks. > > > > Diego > > > > > > ________________________________ > Tired of spam? Yahoo! Mail has the best spam protection around > http://ph.mail.yahoo.com > > --------------------------------- Tired of spam? Yahoo! Mail has the best spam protection around http://ph.mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070710/f7ebfb61/attachment.html From hantongs at gmail.com Wed Jul 18 00:57:31 2007 From: hantongs at gmail.com (Hansi) Date: Wed, 18 Jul 2007 15:57:31 +0800 Subject: [Xorp-users] Static Join Message Message-ID: <2f9e317b0707180057m5f274f64h483aca7f99dd51bd@mail.gmail.com> To whom it may concern: Hello, Does someone have an idea on what "static join message" is all about? Any help or pointers to specific resources/links would be much appreciated. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070718/147a6a6e/attachment.html From pavlin at icir.org Wed Jul 18 09:17:13 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Wed, 18 Jul 2007 09:17:13 -0700 Subject: [Xorp-users] Static Join Message In-Reply-To: Message from Hansi of "Wed, 18 Jul 2007 15:57:31 +0800." <2f9e317b0707180057m5f274f64h483aca7f99dd51bd@mail.gmail.com> Message-ID: <200707181617.l6IGHD4t094543@possum.icir.org> > Does someone have an idea on what "static join message" is all about? Any > help or pointers to specific resources/links would be much appreciated. Could you provide some context. E.g., is it about multicast, unicast or something else. If I have to take a guess, it is probably in the context of static join multicast messages. E.g., multicast group membership is dynamic in nature and the corresponding IGMP/MLD or, say, PIM-SM join messages are sent periodically. There are good reasons for this dynamic behavior and the existing multicast membership and routing protocols don't support "static join messages". Regards, Pavlin From daniel at clanbaker.com Wed Jul 18 14:57:08 2007 From: daniel at clanbaker.com (Daniel Baker) Date: Wed, 18 Jul 2007 16:57:08 -0500 Subject: [Xorp-users] Current Manual? Message-ID: <469E8CB4.2060502@clanbaker.com> Greetings. I am looking for a more current manual and / or configuration file examples than I have found on the Xorp.org website. There appear to be inconsistencies in between what I have discovered through past use of Xorp and what is described in the user manual at : http://www.xorp.org/releases/current/docs/user_manual/user_manual.pdf Is it safe to assume this is outdated or Am I just not reading it right? My issue is: The configuration file syntax described in the configuration file is not accepted by Xorp when running the Router manager (xorp_rtrmgr). The syntax found by exploring the configuration through the Xorp shell works for the configuration file once it has been cut and pasted into the file. This is where inconsistency is found. Anyone have any ideas, pointers or links? Dan. From pavlin at icir.org Wed Jul 18 14:10:14 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Wed, 18 Jul 2007 14:10:14 -0700 Subject: [Xorp-users] Current Manual? In-Reply-To: Message from Daniel Baker of "Wed, 18 Jul 2007 16:57:08 CDT." <469E8CB4.2060502@clanbaker.com> Message-ID: <200707182110.l6ILAEKC009639@possum.icir.org> > I am looking for a more current manual and / or configuration file > examples than I have found on the Xorp.org website. > > There appear to be inconsistencies in between what I have discovered > through past use of Xorp and what is described in the user manual at : > > http://www.xorp.org/releases/current/docs/user_manual/user_manual.pdf > > Is it safe to assume this is outdated or Am I just not reading it right? > > My issue is: > > The configuration file syntax described in the configuration file is not > accepted by Xorp when running the Router manager (xorp_rtrmgr). The > syntax found by exploring the configuration through the Xorp shell > works for the configuration file once it has been cut and pasted into > the file. This is where inconsistency is found. > > Anyone have any ideas, pointers or links? The User Manual on the XORP Web site should reflect the latest 1.4 release. If you are using the latest XORP code from CVS, then you also need the manual from CVS (under xorp/docs/user_manual, but you need LaTeX to compile the PS/PDF). If you have found any inconsistencies, please let us know so we can fix them. Thank you, Atanu & Pavlin From daniel at clanbaker.com Thu Jul 19 12:34:55 2007 From: daniel at clanbaker.com (Daniel Baker) Date: Thu, 19 Jul 2007 14:34:55 -0500 Subject: [Xorp-users] Unable to connect to CVS Servers for 2+ hours Message-ID: <469FBCDF.1000500@clanbaker.com> Greetings. I have been unable to download the Xorp code from the CVS server for more than 2 hours. Error messages: ### burner# svn co svn://:pserver:xorpcvs at anoncvs.xorp.org:/cvs svn: Can't connect to host 'anoncvs.xorp.org': Connection refused burner# svn co svn://:pserver:xorpcvs at anoncvs1.xorp.org:/cvs svn: Can't connect to host 'anoncvs1.xorp.org': Operation timed out #### I had wanted to try the CVS version instead of the ports tree on FreeBSD to get access to fresher documentation. Dan. From pavlin at icir.org Thu Jul 19 20:38:34 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Thu, 19 Jul 2007 20:38:34 -0700 Subject: [Xorp-users] Unable to connect to CVS Servers for 2+ hours In-Reply-To: Message from Daniel Baker of "Thu, 19 Jul 2007 14:34:55 CDT." <469FBCDF.1000500@clanbaker.com> Message-ID: <200707200338.l6K3cYj4023007@possum.icir.org> Daniel Baker wrote: > Greetings. > > I have been unable to download the Xorp code from the CVS server for > more than 2 hours. > > Error messages: > ### > > burner# svn co svn://:pserver:xorpcvs at anoncvs.xorp.org:/cvs > svn: Can't connect to host 'anoncvs.xorp.org': Connection refused > > burner# svn co svn://:pserver:xorpcvs at anoncvs1.xorp.org:/cvs > svn: Can't connect to host 'anoncvs1.xorp.org': Operation timed out > > #### > > I had wanted to try the CVS version instead of the ports tree on FreeBSD > to get access to fresher documentation. You need to use cvs instead of svn. See the following URL for details how to get the latest code from anon. CVS: http://www.xorp.org/cvs.html FYI, I just tried it and it works. Regards, Pavlin > Dan. > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From Frederic.Gilloteau at alcatel.fr Thu Jul 19 02:29:23 2007 From: Frederic.Gilloteau at alcatel.fr (Frederic Gilloteau) Date: Thu, 19 Jul 2007 11:29:23 +0200 Subject: [Xorp-users] XORP and RPM Compilation Message-ID: <001801c7c9e7$4b125730$da8911ac@ad2.ad.alcatel.com> Hello, I would like to compile xorp-1.4 to get the associated RPM. My problems are the following : 1) If I get the xorp src rpm from http://dag.wieers.com/rpm/packages/xorp/, The .spec file is not correct I think because templates/ and target/ directories are installed under /usr/share/xorp where xorp_rtrmgr expects them to be in /usr/etc/templates and /usr/xrl/targets. I can pass it as an option with -x and -t but then it fails again because xorp expects to find xorp_fea in /usr/fea/xorp_fea and this is situated in /usr/bin/xorp_fea .. ==> I tried 2) 2) I got a newer spec file from http://cvs.pld-linux.org/cgi-bin/cvsweb/SPECS/xorp.spec which seems to correct the paths problem, but this spec file failed to compile due to a libtool problem "libtool: unrecognized option `--tag=CC'". My libtool version is libtool-1.5.16.multilib2-3. (I read in the README that it should be 1.4) My question : Is there a working spec file I could use for xorp-1.4 which works with the libtool-1.5 ? Thanks in advance Regards, Fred -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070719/e0708515/attachment.html From pavlin at icir.org Fri Jul 20 11:28:26 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Fri, 20 Jul 2007 11:28:26 -0700 Subject: [Xorp-users] XORP and RPM Compilation In-Reply-To: Message from "Frederic Gilloteau" of "Thu, 19 Jul 2007 11:29:23 +0200." <001801c7c9e7$4b125730$da8911ac@ad2.ad.alcatel.com> Message-ID: <200707201828.l6KISQgd000824@possum.icir.org> Frederic Gilloteau wrote: > Hello, > > I would like to compile xorp-1.4 to get the associated RPM. > > My problems are the following : > > 1) If I get the xorp src rpm from http://dag.wieers.com/rpm/packages/xorp/, > The .spec file is not correct I think because templates/ and target/ > directories are installed under /usr/share/xorp where xorp_rtrmgr expects > them to be in /usr/etc/templates and /usr/xrl/targets. I can pass it as an > option with -x and -t but then it fails again because xorp expects to find > xorp_fea in /usr/fea/xorp_fea and this is situated in /usr/bin/xorp_fea .. Yes, the XORP rtrmgr assumes that it can find the xorp_fea binary under ${XORP_ROOT}/fea/xorp_fea. Similarly, it assumes to find the xorp_bgp binary under ${XORP_ROOT}/bgp/xorp_bgp, and so on. You could overwrite the XORP root prefix by setting the XORP_ROOT variable in shell environment, but you can't remove the "/fea/" part in the path without editing the rtrmgr templates. This however is too much hassle so I wouldn't recommend it. > ==> I tried 2) > > 2) I got a newer spec file from > http://cvs.pld-linux.org/cgi-bin/cvsweb/SPECS/xorp.spec which seems to > correct the paths problem, but this spec file failed to compile due to a > libtool problem "libtool: unrecognized option `--tag=CC'". My libtool > version is libtool-1.5.16.multilib2-3. (I read in the README that it should > be 1.4) > > > My question : Is there a working spec file I could use for xorp-1.4 which > works with the libtool-1.5 ? It appears the problem is that the above spec executes the autotools (libtoolize, aclocal, autoconf, automake) before running ./configure. This is not necessary just for compiling XORP, and only ./configure should be executed. The 1.4 code assumes certain (older) versions of the autotools, and if you use newer versions you will get the above "--tag=CC" libtool error. FYI, the latest XORP code in CVS has been updated to use the latest autotools, but those changes will be available in the next 1.5 release. I am not familiar with the RPM .spec build system, but you could try removing the following lines and see whether it fixes the problem: %{__libtoolize} %{__aclocal} %{__autoconf} %{__automake} Though, make sure that you first remove any older leftover builds and start with a fresh tree. Alternatively, you could just download the vanilla xorp-1.4.tar.gz tarball from the XORP web site, then compile and install it yourself: tar zxvf xorp-1.4.tar.gz cd xorp-1.4 ./configure gmake # Become root gmake install The last command will install everything in the /usr/local/xorp directory. Regards, Pavlin > Thanks in advance > > Regards, > > Fred > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From Frederic.Gilloteau at alcatel.fr Mon Jul 23 02:34:32 2007 From: Frederic.Gilloteau at alcatel.fr (Frederic Gilloteau) Date: Mon, 23 Jul 2007 11:34:32 +0200 Subject: [Xorp-users] XORP and RPM Compilation In-Reply-To: <200707201828.l6KISQgd000824@possum.icir.org> References: Message from "Frederic Gilloteau" of "Thu, 19 Jul 2007 11:29:23 +0200."<001801c7c9e7$4b125730$da8911ac@ad2.ad.alcatel.com> <200707201828.l6KISQgd000824@possum.icir.org> Message-ID: <001e01c7cd0c$ae494ed0$da8911ac@ad2.ad.alcatel.com> Hello Pavlin, Thanks for all informations. I could compile my RPM adding comments in front of the following sections : %{__libtoolize} %{__aclocal} %{__autoconf} %{__automake} Unfortunately, the resulting RPMS still produces all binary files directly under /usr/share/xorp ... By the way, the manual compilation works very well but I would like an RPM of it :-) Thanks Fred -----Original Message----- From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Pavlin Radoslavov Sent: vendredi 20 juillet 2007 20:28 To: Frederic Gilloteau Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] XORP and RPM Compilation Frederic Gilloteau wrote: > Hello, > > I would like to compile xorp-1.4 to get the associated RPM. > > My problems are the following : > > 1) If I get the xorp src rpm from > http://dag.wieers.com/rpm/packages/xorp/, > The .spec file is not correct I think because templates/ and target/ > directories are installed under /usr/share/xorp where xorp_rtrmgr > expects them to be in /usr/etc/templates and /usr/xrl/targets. I can > pass it as an option with -x and -t but then it fails again because > xorp expects to find xorp_fea in /usr/fea/xorp_fea and this is situated in /usr/bin/xorp_fea .. Yes, the XORP rtrmgr assumes that it can find the xorp_fea binary under ${XORP_ROOT}/fea/xorp_fea. Similarly, it assumes to find the xorp_bgp binary under ${XORP_ROOT}/bgp/xorp_bgp, and so on. You could overwrite the XORP root prefix by setting the XORP_ROOT variable in shell environment, but you can't remove the "/fea/" part in the path without editing the rtrmgr templates. This however is too much hassle so I wouldn't recommend it. > ==> I tried 2) > > 2) I got a newer spec file from > http://cvs.pld-linux.org/cgi-bin/cvsweb/SPECS/xorp.spec which seems to > correct the paths problem, but this spec file failed to compile due to > a libtool problem "libtool: unrecognized option `--tag=CC'". My > libtool version is libtool-1.5.16.multilib2-3. (I read in the README > that it should be 1.4) > > > My question : Is there a working spec file I could use for xorp-1.4 > which works with the libtool-1.5 ? It appears the problem is that the above spec executes the autotools (libtoolize, aclocal, autoconf, automake) before running ./configure. This is not necessary just for compiling XORP, and only ./configure should be executed. The 1.4 code assumes certain (older) versions of the autotools, and if you use newer versions you will get the above "--tag=CC" libtool error. FYI, the latest XORP code in CVS has been updated to use the latest autotools, but those changes will be available in the next 1.5 release. I am not familiar with the RPM .spec build system, but you could try removing the following lines and see whether it fixes the problem: %{__libtoolize} %{__aclocal} %{__autoconf} %{__automake} Though, make sure that you first remove any older leftover builds and start with a fresh tree. Alternatively, you could just download the vanilla xorp-1.4.tar.gz tarball from the XORP web site, then compile and install it yourself: tar zxvf xorp-1.4.tar.gz cd xorp-1.4 ./configure gmake # Become root gmake install The last command will install everything in the /usr/local/xorp directory. Regards, Pavlin > Thanks in advance > > Regards, > > Fred > _______________________________________________ > 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 From Frederic.Gilloteau at alcatel.fr Mon Jul 23 08:41:18 2007 From: Frederic.Gilloteau at alcatel.fr (Frederic Gilloteau) Date: Mon, 23 Jul 2007 17:41:18 +0200 Subject: [Xorp-users] RIP configuration Message-ID: <004d01c7cd3f$e95405a0$da8911ac@ad2.ad.alcatel.com> Hello, I try to configure RIP on two interfaces : Eth0 : 192.168.92.1 (with vif eth0) Eth1 : 172.20.0.90 (with vif eth1) I have configured these interfaces in the 'interfaces section' and in the 'RIP section'. My problem is that RIP is propagated on eth0 with success (seen with tcpdump -i eth0) but no route about the network associated to eth1 (172.20.0.0) is propagated through RIP. Using 'show rip status all' I can read : RIP on eth0 eth0 192.168.92.1 Status: enabled RIP on eth1 eth1 172.20.0.90 Status: enabled [gated by disabled FEA interface/vif/address] I have activated the fea section ... Moreover, in the logs of xorp_rtrmgr, I can sometimes read INFO : Detected iftree change on eth1 eth1 172.20.0.90 setting transport enable false . Do you have any idea ? Thanks in advance Regards Fred -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070723/8591e68b/attachment.html From pavlin at icir.org Mon Jul 23 11:09:32 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 23 Jul 2007 11:09:32 -0700 Subject: [Xorp-users] XORP and RPM Compilation In-Reply-To: Message from "Frederic Gilloteau" of "Mon, 23 Jul 2007 11:34:32 +0200." <001e01c7cd0c$ae494ed0$da8911ac@ad2.ad.alcatel.com> Message-ID: <200707231809.l6NI9Wge028238@possum.icir.org> Frederic Gilloteau wrote: > Hello Pavlin, > > Thanks for all informations. > > I could compile my RPM adding comments in front of the following sections : > > %{__libtoolize} > %{__aclocal} > %{__autoconf} > %{__automake} > > Unfortunately, the resulting RPMS still produces all binary files directly > under /usr/share/xorp ... As I mentioned earlier I am not familiar with RPM .spec configuration, but I guess you could try to fix this by editing the line after "%{__make} install \" In particular, remove the following: bindir=%{_bindir} sbindir=%{_sbindir} and see whether it will install the binaries under the default /usr/local/xorp location. In addition, you might have to comment-out all lines like the following that refer to _bindir and _sbindir: %attr(755,root,root) %{_bindir}/print_lsas Also, you might need to edit the path to xorpsh. If you get it to work this way, the result might not be exactly what you want but is a starter :) Regards, Pavlin > By the way, the manual compilation works very well but I would like an RPM > of it :-) > > Thanks > > Fred > > -----Original Message----- > From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On > Behalf Of Pavlin Radoslavov > Sent: vendredi 20 juillet 2007 20:28 > To: Frederic Gilloteau > Cc: xorp-users at xorp.org > Subject: Re: [Xorp-users] XORP and RPM Compilation > > Frederic Gilloteau wrote: > > > Hello, > > > > I would like to compile xorp-1.4 to get the associated RPM. > > > > My problems are the following : > > > > 1) If I get the xorp src rpm from > > http://dag.wieers.com/rpm/packages/xorp/, > > The .spec file is not correct I think because templates/ and target/ > > directories are installed under /usr/share/xorp where xorp_rtrmgr > > expects them to be in /usr/etc/templates and /usr/xrl/targets. I can > > pass it as an option with -x and -t but then it fails again because > > xorp expects to find xorp_fea in /usr/fea/xorp_fea and this is situated in > /usr/bin/xorp_fea .. > > Yes, the XORP rtrmgr assumes that it can find the xorp_fea binary under > ${XORP_ROOT}/fea/xorp_fea. Similarly, it assumes to find the xorp_bgp binary > under ${XORP_ROOT}/bgp/xorp_bgp, and so on. > You could overwrite the XORP root prefix by setting the XORP_ROOT variable > in shell environment, but you can't remove the "/fea/" part in the path > without editing the rtrmgr templates. > This however is too much hassle so I wouldn't recommend it. > > > ==> I tried 2) > > > > 2) I got a newer spec file from > > http://cvs.pld-linux.org/cgi-bin/cvsweb/SPECS/xorp.spec which seems to > > correct the paths problem, but this spec file failed to compile due to > > a libtool problem "libtool: unrecognized option `--tag=CC'". My > > libtool version is libtool-1.5.16.multilib2-3. (I read in the README > > that it should be 1.4) > > > > > > My question : Is there a working spec file I could use for xorp-1.4 > > which works with the libtool-1.5 ? > > It appears the problem is that the above spec executes the autotools > (libtoolize, aclocal, autoconf, automake) before running ./configure. This > is not necessary just for compiling XORP, and only ./configure should be > executed. The 1.4 code assumes certain > (older) versions of the autotools, and if you use newer versions you will > get the above "--tag=CC" libtool error. > FYI, the latest XORP code in CVS has been updated to use the latest > autotools, but those changes will be available in the next 1.5 release. > > I am not familiar with the RPM .spec build system, but you could try > removing the following lines and see whether it fixes the problem: > > %{__libtoolize} > %{__aclocal} > %{__autoconf} > %{__automake} > > Though, make sure that you first remove any older leftover builds and start > with a fresh tree. > > Alternatively, you could just download the vanilla xorp-1.4.tar.gz tarball > from the XORP web site, then compile and install it > yourself: > > tar zxvf xorp-1.4.tar.gz > cd xorp-1.4 > ./configure > gmake > # Become root > gmake install > > The last command will install everything in the /usr/local/xorp directory. > > Regards, > Pavlin > > > > Thanks in advance > > > > Regards, > > > > Fred > > _______________________________________________ > > 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 > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin at icir.org Mon Jul 23 11:18:10 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 23 Jul 2007 11:18:10 -0700 Subject: [Xorp-users] RIP configuration In-Reply-To: Message from "Frederic Gilloteau" of "Mon, 23 Jul 2007 17:41:18 +0200." <004d01c7cd3f$e95405a0$da8911ac@ad2.ad.alcatel.com> Message-ID: <200707231818.l6NIIAMK028378@possum.icir.org> > I try to configure RIP on two interfaces : > Eth0 : 192.168.92.1 (with vif eth0) > Eth1 : 172.20.0.90 (with vif eth1) > > I have configured these interfaces in the 'interfaces section' and in the > 'RIP section'. > > My problem is that RIP is propagated on eth0 with success (seen with tcpdump > -i eth0) but no route about the network associated to eth1 (172.20.0.0) is > propagated through RIP. > > Using 'show rip status all' I can read : > > RIP on eth0 eth0 192.168.92.1 > Status: enabled > > RIP on eth1 eth1 172.20.0.90 > Status: enabled [gated by disabled FEA interface/vif/address] > > I have activated the fea section ... > > Moreover, in the logs of xorp_rtrmgr, I can sometimes read INFO : Detected > iftree change on eth1 eth1 172.20.0.90 setting transport enable false . > > Do you have any idea ? I think you need to explicitly export the connected routes into RIP: policy { /* Describe connected routes for redistribution */ policy-statement connected { term export { from { protocol: "connected" } } } } protocols { rip { export: "connected" ... } } Regards, Pavlin > Thanks in advance > > Regards > > Fred > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From daniel at clanbaker.com Mon Jul 23 13:30:27 2007 From: daniel at clanbaker.com (Daniel Baker) Date: Mon, 23 Jul 2007 15:30:27 -0500 Subject: [Xorp-users] Is this a live Project? Message-ID: <46A50FE3.8080605@clanbaker.com> Greetings. Does this project live? Does it have any users? Dan. From pavlin at icir.org Mon Jul 23 14:29:20 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 23 Jul 2007 14:29:20 -0700 Subject: [Xorp-users] Is this a live Project? In-Reply-To: Message from Daniel Baker of "Mon, 23 Jul 2007 15:30:27 CDT." <46A50FE3.8080605@clanbaker.com> Message-ID: <200707232129.l6NLTK4D029759@possum.icir.org> Daniel Baker wrote: > Greetings. > > Does this project live? Yes. See the xorp-cvs mailing list archives for all the CVS commit messages: http://mailman.icsi.berkeley.edu/pipermail/xorp-cvs/ > Does it have any users? Yes, though we don't have a Web page that lists users/organizations that use XORP. Well, in last year's Sigcomm conference (http://www.sigcomm.org/sigcomm2006/) there were two papers that used XORP, so this is at least two documented users :) Regards, Pavlin > Dan. > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From ian.batterbee at aut.ac.nz Mon Jul 23 23:07:22 2007 From: ian.batterbee at aut.ac.nz (Ian Batterbee) Date: Tue, 24 Jul 2007 18:07:22 +1200 Subject: [Xorp-users] xorpsh hanging on 'show pim join'. Message-ID: <46A5971A.3020601@aut.ac.nz> Hi, I'm seeing some unexpected behaviour through xorpsh, in that the backend module appears to become unresponsive. If I issue "show pim join" repeatedly, the first few requests succeed, then subsequent commands never return - after about 15 (guess) seconds, the xorp_rtrmgr process says: "[ 2007/07/24 17:52:10 ERROR xorp_rtrmgr:20556 FINDER +85 finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed out" but xorpsh continues to wait until I hit ^C, at which point the rtrmgr says: [ 2007/07/24 17:52:56 ERROR xorp_pimsm4:20566 LIBXORP +213 buffered_asyncio.cc io_event ] read error 104 [ 2007/07/24 17:52:56 ERROR xorp_pimsm4:20566 XRL +159 xrl_pf_stcp.cc read_event ] Read failed (error = 104) [ 2007/07/24 17:52:56 ERROR xorp_pimsm4:20566 XRL +338 xrl_pf_stcp.cc die ] STCPRequestHandler died: read error ...presumably in response to me aborting the request. At that point, I can *occasionally* press [up] in xorpsh and the command works, but most of the time it hangs. if I shut xorp_rtrmgr down, and then restart it, things are okay again for a few minutes, and then the problem begins once more. xorp is speaking PIMv4 to a cisco router which connects to a education/research network, which has a lot of multicast traffic on it. Could the amount of sources could potentially be the problem ? If I simply start xorp_rtrmgr up, and then wait 5 minutes, the first time I issue 'show pim join', the output hangs. It *may* also have something to do with me piping the output through "| no-page " or "| find 233.0.76.26".. I'm not sure if that's related but I thought I better mention it in case it is. From noel_bongo at yahoo.com Tue Jul 24 03:10:12 2007 From: noel_bongo at yahoo.com (Noel Bongo) Date: Tue, 24 Jul 2007 03:10:12 -0700 (PDT) Subject: [Xorp-users] RIPv2 Backward Compatibility? Message-ID: <611244.99070.qm@web57608.mail.re1.yahoo.com> Hi, Does the implementation of RIP which is version 2, is backward compatible with RIP version 1? Because currently I have legacy routers that needs interoperability with XORP. Thanks -Noel --------------------------------- Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070724/c81e0d73/attachment.html From Frederic.Gilloteau at alcatel.fr Tue Jul 24 03:21:20 2007 From: Frederic.Gilloteau at alcatel.fr (Frederic Gilloteau) Date: Tue, 24 Jul 2007 12:21:20 +0200 Subject: [Xorp-users] RIP configuration In-Reply-To: <200707231818.l6NIIAMK028378@possum.icir.org> References: Message from "Frederic Gilloteau" of "Mon, 23 Jul 2007 17:41:18 +0200." <004d01c7cd3f$e95405a0$da8911ac@ad2.ad.alcatel.com> <200707231818.l6NIIAMK028378@possum.icir.org> Message-ID: <003501c7cddc$60b089b0$da8911ac@ad2.ad.alcatel.com> Hello Pavlin, I had explicitly add the connected policy statement with no success. My eth0 network is exported very well through RIP, only eth1 does not work. Any other idea ? :-) Thanks Fred ==> Here is my config.boot file : /*XORP Configuration File, v1.0*/ protocols { rip { interface eth0 { vif eth0 { address 192.168.92.1 { metric: 1 horizon: "split-horizon-poison-reverse" disable: false passive: false accept-non-rip-requests: true accept-default-route: true advertise-default-route: true route-timeout: 180 deletion-delay: 120 triggered-delay: 3 triggered-jitter: 66 update-interval: 30 update-jitter: 16 request-interval: 30 interpacket-delay: 50 } } } interface eth1 { vif eth1 { address 172.20.0.90 { metric: 1 horizon: "split-horizon-poison-reverse" disable: false passive: false accept-non-rip-requests: true accept-default-route: true advertise-default-route: true route-timeout: 180 deletion-delay: 120 triggered-delay: 3 triggered-jitter: 66 update-interval: 30 update-jitter: 16 request-interval: 30 interpacket-delay: 50 } } } export: "connected" } } policy { policy-statement connected { term export { from { protocol: "connected" } } } } fea { unicast-forwarding4 { disable: false } } interfaces { restore-original-config-on-shutdown: false interface eth0 { disable: false discard: false description: "ethernet" vif eth0 { disable: false address 192.168.92.1 { prefix-length: 24 broadcast: 192.168.92.255 disable: false } } } interface eth1 { disable: false discard: false description: "" vif eth1 { disable: false address 172.20.0.90 { prefix-length: 16 broadcast: 172.20.255.255 disable: false } } } } -----Original Message----- From: Pavlin Radoslavov [mailto:pavlin at icir.org] Sent: lundi 23 juillet 2007 20:18 To: Frederic Gilloteau Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] RIP configuration > I try to configure RIP on two interfaces : > Eth0 : 192.168.92.1 (with vif eth0) > Eth1 : 172.20.0.90 (with vif eth1) > > I have configured these interfaces in the 'interfaces section' and in > the 'RIP section'. > > My problem is that RIP is propagated on eth0 with success (seen with > tcpdump -i eth0) but no route about the network associated to eth1 > (172.20.0.0) is propagated through RIP. > > Using 'show rip status all' I can read : > > RIP on eth0 eth0 192.168.92.1 > Status: enabled > > RIP on eth1 eth1 172.20.0.90 > Status: enabled [gated by disabled FEA interface/vif/address] > > I have activated the fea section ... > > Moreover, in the logs of xorp_rtrmgr, I can sometimes read INFO : > Detected iftree change on eth1 eth1 172.20.0.90 setting transport enable false . > > Do you have any idea ? I think you need to explicitly export the connected routes into RIP: policy { /* Describe connected routes for redistribution */ policy-statement connected { term export { from { protocol: "connected" } } } } protocols { rip { export: "connected" ... } } Regards, Pavlin > Thanks in advance > > Regards > > Fred > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From Frederic.Gilloteau at alcatel.fr Tue Jul 24 08:19:39 2007 From: Frederic.Gilloteau at alcatel.fr (Frederic Gilloteau) Date: Tue, 24 Jul 2007 17:19:39 +0200 Subject: [Xorp-users] RIP configuration In-Reply-To: <200707231818.l6NIIAMK028378@possum.icir.org> References: Message from "Frederic Gilloteau" of "Mon, 23 Jul 2007 17:41:18 +0200." <004d01c7cd3f$e95405a0$da8911ac@ad2.ad.alcatel.com> <200707231818.l6NIIAMK028378@possum.icir.org> Message-ID: <000e01c7ce06$0da19f50$da8911ac@ad2.ad.alcatel.com> Ok, I did a mistake! No cable was plugged on my eth1 interface (In fact, a cable was but ethernet negotiation failed and the link was down) So the RIP route concerning this interface was not propagated (good functionnality) With a good ethernet connection on eth1, RIP is working well! Anyway, thanks for your help Fred -----Original Message----- From: Pavlin Radoslavov [mailto:pavlin at icir.org] Sent: lundi 23 juillet 2007 20:18 To: Frederic Gilloteau Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] RIP configuration > I try to configure RIP on two interfaces : > Eth0 : 192.168.92.1 (with vif eth0) > Eth1 : 172.20.0.90 (with vif eth1) > > I have configured these interfaces in the 'interfaces section' and in > the 'RIP section'. > > My problem is that RIP is propagated on eth0 with success (seen with > tcpdump -i eth0) but no route about the network associated to eth1 > (172.20.0.0) is propagated through RIP. > > Using 'show rip status all' I can read : > > RIP on eth0 eth0 192.168.92.1 > Status: enabled > > RIP on eth1 eth1 172.20.0.90 > Status: enabled [gated by disabled FEA interface/vif/address] > > I have activated the fea section ... > > Moreover, in the logs of xorp_rtrmgr, I can sometimes read INFO : > Detected iftree change on eth1 eth1 172.20.0.90 setting transport enable false . > > Do you have any idea ? I think you need to explicitly export the connected routes into RIP: policy { /* Describe connected routes for redistribution */ policy-statement connected { term export { from { protocol: "connected" } } } } protocols { rip { export: "connected" ... } } Regards, Pavlin > Thanks in advance > > Regards > > Fred > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From Frederic.Gilloteau at alcatel.fr Tue Jul 24 08:33:23 2007 From: Frederic.Gilloteau at alcatel.fr (Frederic Gilloteau) Date: Tue, 24 Jul 2007 17:33:23 +0200 Subject: [Xorp-users] Starting and Killing xorp_rtrmgr Message-ID: <000f01c7ce07$f8e3f390$da8911ac@ad2.ad.alcatel.com> Hello, One other question: Sometimes I 'quit' xorpsh and send a 'CTRL + d' signal to xorp_rtrmgr to kill the process . - Is there an other way of killing xorp_rtrmgr ? Moreover, when I want to start it again, I get the messages : Commit failed: 102 Command failed Module killed during shutdown: rip Module killed during shutdown: interfaces Module killed during shutdown: rib . And the process does not start .. Until I reboot! Is there something I can clean ? Please apologize for 'novice' questions :-) Thanks Fred -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070724/1ac1035d/attachment.html From pavlin at icir.org Tue Jul 24 10:28:00 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Tue, 24 Jul 2007 10:28:00 -0700 Subject: [Xorp-users] xorpsh hanging on 'show pim join'. In-Reply-To: Message from Ian Batterbee of "Tue, 24 Jul 2007 18:07:22 +1200." <46A5971A.3020601@aut.ac.nz> Message-ID: <200707241728.l6OHS0jx051862@possum.icir.org> Ian Batterbee wrote: > Hi, I'm seeing some unexpected behaviour through xorpsh, in that the > backend module appears to become unresponsive. > > If I issue "show pim join" repeatedly, the first few requests succeed, > then subsequent commands never return - after about 15 (guess) seconds, > the xorp_rtrmgr process says: > > "[ 2007/07/24 17:52:10 ERROR xorp_rtrmgr:20556 FINDER +85 > finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed out" > > but xorpsh continues to wait until I hit ^C, at which point the rtrmgr says: > > [ 2007/07/24 17:52:56 ERROR xorp_pimsm4:20566 LIBXORP +213 > buffered_asyncio.cc io_event ] read error 104 > [ 2007/07/24 17:52:56 ERROR xorp_pimsm4:20566 XRL +159 xrl_pf_stcp.cc > read_event ] Read failed (error = 104) > [ 2007/07/24 17:52:56 ERROR xorp_pimsm4:20566 XRL +338 xrl_pf_stcp.cc > die ] STCPRequestHandler died: read error > > ...presumably in response to me aborting the request. > > At that point, I can *occasionally* press [up] in xorpsh and the command > works, but most of the time it hangs. > > if I shut xorp_rtrmgr down, and then restart it, things are okay again > for a few minutes, and then the problem begins once more. > > xorp is speaking PIMv4 to a cisco router which connects to a > education/research network, which has a lot of multicast traffic on it. > Could the amount of sources could potentially be the problem ? > > If I simply start xorp_rtrmgr up, and then wait 5 minutes, the first > time I issue 'show pim join', the output hangs. > > It *may* also have something to do with me piping the output through "| > no-page " or "| find 233.0.76.26".. I'm not sure if that's related but I > thought I better mention it in case it is. Do you always use the "| no-page" or "| find 233.0.76.26" piping or it hangs even on "show pim join" only? Could you try "show pim join | count" to get some idea about the size of the output. If this fails, can you provide some estimation about the number of (S,G) and (*,G) PIM-SM entries inside the XORP router. Finally, could you confirm that running other commands like "show pim interface" don't create such problem. FYI, the current mechanism for obtaining the "show ..." output from the multicast-related processes is very hackish and needs to be replaced. Hopefully, after the replacement the problem you are seeing will go away, but it is good to know what is the source of the problem. My suspicion is the output size is relatively large, which the current mechanism probably doesn't handle well. Thanks, Pavlin > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin at icir.org Tue Jul 24 10:49:11 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Tue, 24 Jul 2007 10:49:11 -0700 Subject: [Xorp-users] Starting and Killing xorp_rtrmgr In-Reply-To: Message from "Frederic Gilloteau" of "Tue, 24 Jul 2007 17:33:23 +0200." <000f01c7ce07$f8e3f390$da8911ac@ad2.ad.alcatel.com> Message-ID: <200707241749.l6OHnBhP052120@possum.icir.org> > One other question: > > Sometimes I 'quit' xorpsh and send a 'CTRL + d' signal to xorp_rtrmgr to > kill the process . > > - Is there an other way of killing xorp_rtrmgr ? Hmmm, "CTRL + c" :) > Moreover, when I want to start it again, I get the messages : > > Commit failed: 102 Command failed > > Module killed during shutdown: rip > Module killed during shutdown: interfaces > Module killed during shutdown: rib > . > > And the process does not start .. Until I reboot! > > Is there something I can clean ? Are there any XORP leftover processes running after you kill xorp_rtrmgr? During shutdown the xorp_rtrmgr process should have killed all other XORP processes, but if any remained please kill them by hand before restarting XORP. E.g., "kill -9 " is your safest bet :) If there are no leftover processes, please check that the loopback interface is UP and configured. The XORP IPC mechanism uses the loopback interface so it should be always UP and running. If none of the above is the issue, then please send your configuration file, and your complete log messages: the first message when you run XORP for the first time when you kill the xorp_rtrmgr and the second message when XORP fails to start. If they contain any sensitive information that shouldn't go to the public (e.g., IP addresses, you could mask them because the particular values shouldn't be related to the problem. Alternatively, you could send me the info in a private email. FYI, to save the log messages it is best to run "script" before starting XORP in foreground, and then all the printed output will go to file "typescript". Regards, Pavlin From pavlin at icir.org Tue Jul 24 10:51:37 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Tue, 24 Jul 2007 10:51:37 -0700 Subject: [Xorp-users] RIPv2 Backward Compatibility? In-Reply-To: Message from Noel Bongo of "Tue, 24 Jul 2007 03:10:12 PDT." <611244.99070.qm@web57608.mail.re1.yahoo.com> Message-ID: <200707241751.l6OHpbaq052170@possum.icir.org> > Does the implementation of RIP which is version 2, is backward > compatible with RIP version 1? Because currently I have legacy > routers that needs interoperability with XORP. No, the XORP RIP implementation is RIPv2 only and doesn't implement RIPv1 compatibility. Regards, Pavlin > Thanks > > -Noel > > > --------------------------------- > Building a website is a piece of cake. > Yahoo! Small Business gives you all the tools to get online._______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From daniel at clanbaker.com Wed Jul 25 06:47:27 2007 From: daniel at clanbaker.com (Daniel Baker) Date: Wed, 25 Jul 2007 08:47:27 -0500 Subject: [Xorp-users] Xorp source code being spit by kernel at boot time Message-ID: <46A7546F.2010601@clanbaker.com> Good Morning I saw a curious thing in my log files which I have traced back to Xorp. The Kernel appears to be spitting out Xorp source code at boot time. Any thoughts? A portion of the log file is included: Dan. >>> burner# cat /var/log/messages :Log Purge: Jul 24 12:22:40 burner reboot: rebooted by keeper Jul 24 12:22:40 burner syslogd: exiting on signal 15 Jul 24 12:23:54 burner syslogd: kernel boot file is /boot/kernel/kernel Jul 24 12:23:54 burner kernel: /policy_backend/0.1/push_routes -> Jul 24 12:23:55 burner kernel: _sender_name:txt&protocol_name:txt&protocol_id:u32&message_type:u32&vif_name:txt&vif_index:u32&source_address:ipv6&dest_address:ipv6&protocol_message:binary Jul 24 12:23:55 burner kernel: 05 template_commands.cc XrlAction ] Jul 24 12:23:55 burner kernel: Jul 24 12:23:55 burner kernel: 18>Seg 11: >&area:ipv4=< Jul 24 12:23:56 burner kernel: Jul 24 12:23:56 burner kernel: c XrlAction ] Jul 24 12:23:56 burner kernel: < Jul 24 12:23:56 burner kernel: t&peer_port:u32 -> Jul 24 12:23:56 burner kernel: ol -> Jul 24 12:23:57 burner kernel: matches ] Jul 24 12:23:57 burner kernel: finder://pim/redist_transaction4/0.1/start_transaction -> tid:u32 Jul 24 12:23:57 burner kernel: nable_fib2mrib?enable:bool -> Jul 24 12:23:57 burner kernel: ldb.cc matches ] Jul 24 12:23:57 burner kernel: Jul 24 12:23:58 burner kernel: c matches ] Jul 24 12:23:58 burner kernel: ] Jul 24 12:23:58 burner kernel: Jul 24 12:23:58 burner kernel: matches ] Jul 24 12:23:58 burner kernel: receiver?xrl_target_name:txt&if_name:txt&vif_name:txt&ip_protocol:u32&enable_multicast_loopback:bool -> Jul 24 12:23:59 burner kernel: u32 -> Jul 24 12:23:59 burner kernel: ec:u32&interval_usec:u32 -> Jul 24 12:23:59 burner kernel: t_count:u32 -> Jul 24 12:23:59 burner kernel: 521 +53 xrldb.cc matches ] Jul 24 12:23:59 burner kernel: xthop:ipv6&metric:u32&admin_distance:u32&protocol_origin:txt -> Jul 24 12:24:00 burner kernel: atches ] Jul 24 12:24:00 burner kernel: :txt&target_instance:txt -> Jul 24 12:24:00 burner kernel: [ 521 +58 xrldb.cc matches ] Jul 24 12:24:00 burner kernel: db.cc matches ] Jul 24 12:24:00 burner kernel: ame:txt&enable:bool -> Jul 24 12:24:01 burner kernel: cc matches ] Jul 24 12:24:01 burner kernel: tches ] Jul 24 12:24:01 burner kernel: matches ] Jul 24 12:24:01 burner kernel: gr_mirror/fea_ifmgr_mirror/0.1/vif_set_broadcast_capable?ifname:txt&vifname:txt&capable:bool -> Jul 24 12:24:01 burner inetd[1046]: Accessing 10.10.4.200: No such file or directory, continuing anyway. Jul 24 12:24:01 burner inetd[1047]: 10.10.4.200: No such file or directory Jul 24 12:24:02 burner kernel: 118>[ 521 +58 xrldb.cc matches ] Jul 24 12:24:02 burner kernel: 118>------ Jul 24 12:24:02 burner kernel: matches ] Jul 24 12:24:02 burner kernel: tches ] Jul 24 13:31:02 burner su: keeper to root on /dev/ttyp0 Jul 24 14:53:07 burner login: ROOT LOGIN (root) ON ttyv0 Jul 24 14:53:10 burner reboot: rebooted by root Jul 24 14:53:10 burner syslogd: exiting on signal 15 Jul 24 14:58:34 burner syslogd: kernel boot file is /boot/kernel/kernel Jul 24 14:58:34 burner kernel: 7295 Jul 24 14:58:34 burner kernel: 67295 Jul 24 14:58:34 burner kernel: 21 +177 template_commands.cc XrlAction ] Jul 24 14:58:34 burner kernel: 1 +242 template_commands.cc XrlAction ] Jul 24 14:58:34 burner kernel: 9: >&statement:txt=< Jul 24 14:58:35 burner kernel: nds.cc XrlAction ] Jul 24 14:58:35 burner kernel: ommands.cc XrlAction ] Jul 24 14:58:35 burner kernel: ecv_kernel_signal_message6?xrl_sender_name:txt&protocol_name:txt&protocol_id:u32&message_type:u32&vif_name:txt&vif_index:u32&source_address:ipv6&dest_address:ipv6&protocol_message:binary -> Jul 24 14:58:36 burner kernel: fname:txt&no_carrier:bool -> Jul 24 14:58:36 burner kernel: us:u32&reason:txt Jul 24 14:58:36 burner kernel: 4&oaddr:ipv4 -> Jul 24 14:58:36 burner kernel: 2 xrldb.cc matches ] Jul 24 14:58:36 burner inetd[1046]: Accessing 10.10.4.200: No such file or directory, continuing anyway. Jul 24 14:58:36 burner inetd[1047]: 10.10.4.200: No such file or directory Jul 24 15:08:58 burner su: keeper to root on /dev/ttyp0 Jul 24 16:53:26 burner su: keeper to root on /dev/ttyp0 From pavlin at icir.org Wed Jul 25 11:08:43 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Wed, 25 Jul 2007 11:08:43 -0700 Subject: [Xorp-users] Xorp source code being spit by kernel at boot time In-Reply-To: Message from Daniel Baker of "Wed, 25 Jul 2007 08:47:27 CDT." <46A7546F.2010601@clanbaker.com> Message-ID: <200707251808.l6PI8hNk064792@possum.icir.org> Daniel Baker wrote: > Good Morning > > I saw a curious thing in my log files which I have traced back to Xorp. > > The Kernel appears to be spitting out Xorp source code at boot time. > Any thoughts? A portion of the log file is included: Interesting. What OS version and XORP version are you using and how did you compile XORP? E.g., did you enable any extra debugging, or just "./configure; gmake; gmake install" Another question is how do you run XORP? Starting it with init.d script (or equivalent) on system startup or by hand. If the former, could you send that startup script. If the latter, please specify the exact command you used. Also, did you see anything unusual (e.g., XORP-related process crashing). Finally, is this reproducible (e.g., every time you start XORP), or it happens from time to time. My initial guess is that XORP prints some extra log info which gets logged to /var/log/messages. For some reason however only a small set of the log messages are printed, and even those messages are split across multiple lines. Thanks, Pavlin > > Dan. > > > >>> > burner# cat /var/log/messages > :Log Purge: > Jul 24 12:22:40 burner reboot: rebooted by keeper > Jul 24 12:22:40 burner syslogd: exiting on signal 15 > Jul 24 12:23:54 burner syslogd: kernel boot file is /boot/kernel/kernel > Jul 24 12:23:54 burner kernel: /policy_backend/0.1/push_routes -> > Jul 24 12:23:55 burner kernel: > _sender_name:txt&protocol_name:txt&protocol_id:u32&message_type:u32&vif_name:txt&vif_index:u32&source_address:ipv6&dest_address:ipv6&protocol_message:binary > Jul 24 12:23:55 burner kernel: 05 template_commands.cc XrlAction ] > Jul 24 12:23:55 burner kernel: > Jul 24 12:23:55 burner kernel: 18>Seg 11: >&area:ipv4=< > Jul 24 12:23:56 burner kernel: > Jul 24 12:23:56 burner kernel: c XrlAction ] > Jul 24 12:23:56 burner kernel: < > Jul 24 12:23:56 burner kernel: t&peer_port:u32 -> > Jul 24 12:23:56 burner kernel: ol -> > Jul 24 12:23:57 burner kernel: matches ] > Jul 24 12:23:57 burner kernel: > finder://pim/redist_transaction4/0.1/start_transaction -> tid:u32 > Jul 24 12:23:57 burner kernel: nable_fib2mrib?enable:bool -> > Jul 24 12:23:57 burner kernel: ldb.cc matches ] > Jul 24 12:23:57 burner kernel: > Jul 24 12:23:58 burner kernel: c matches ] > Jul 24 12:23:58 burner kernel: ] > Jul 24 12:23:58 burner kernel: > Jul 24 12:23:58 burner kernel: matches ] > Jul 24 12:23:58 burner kernel: > receiver?xrl_target_name:txt&if_name:txt&vif_name:txt&ip_protocol:u32&enable_multicast_loopback:bool > -> > Jul 24 12:23:59 burner kernel: u32 -> > Jul 24 12:23:59 burner kernel: ec:u32&interval_usec:u32 -> > Jul 24 12:23:59 burner kernel: t_count:u32 -> > Jul 24 12:23:59 burner kernel: 521 +53 xrldb.cc matches ] > Jul 24 12:23:59 burner kernel: > xthop:ipv6&metric:u32&admin_distance:u32&protocol_origin:txt -> > Jul 24 12:24:00 burner kernel: atches ] > Jul 24 12:24:00 burner kernel: :txt&target_instance:txt -> > Jul 24 12:24:00 burner kernel: [ 521 +58 xrldb.cc matches ] > Jul 24 12:24:00 burner kernel: db.cc matches ] > Jul 24 12:24:00 burner kernel: ame:txt&enable:bool -> > Jul 24 12:24:01 burner kernel: cc matches ] > Jul 24 12:24:01 burner kernel: tches ] > Jul 24 12:24:01 burner kernel: matches ] > Jul 24 12:24:01 burner kernel: > gr_mirror/fea_ifmgr_mirror/0.1/vif_set_broadcast_capable?ifname:txt&vifname:txt&capable:bool > -> > Jul 24 12:24:01 burner inetd[1046]: Accessing 10.10.4.200: No such file > or directory, continuing anyway. > Jul 24 12:24:01 burner inetd[1047]: 10.10.4.200: No such file or directory > Jul 24 12:24:02 burner kernel: 118>[ 521 +58 xrldb.cc matches ] > Jul 24 12:24:02 burner kernel: 118>------ > Jul 24 12:24:02 burner kernel: matches ] > Jul 24 12:24:02 burner kernel: tches ] > Jul 24 13:31:02 burner su: keeper to root on /dev/ttyp0 > Jul 24 14:53:07 burner login: ROOT LOGIN (root) ON ttyv0 > Jul 24 14:53:10 burner reboot: rebooted by root > Jul 24 14:53:10 burner syslogd: exiting on signal 15 > Jul 24 14:58:34 burner syslogd: kernel boot file is /boot/kernel/kernel > Jul 24 14:58:34 burner kernel: 7295 > Jul 24 14:58:34 burner kernel: 67295 > Jul 24 14:58:34 burner kernel: 21 +177 template_commands.cc XrlAction ] > Jul 24 14:58:34 burner kernel: 1 +242 template_commands.cc XrlAction ] > Jul 24 14:58:34 burner kernel: 9: >&statement:txt=< > Jul 24 14:58:35 burner kernel: nds.cc XrlAction ] > Jul 24 14:58:35 burner kernel: ommands.cc XrlAction ] > Jul 24 14:58:35 burner kernel: > ecv_kernel_signal_message6?xrl_sender_name:txt&protocol_name:txt&protocol_id:u32&message_type:u32&vif_name:txt&vif_index:u32&source_address:ipv6&dest_address:ipv6&protocol_message:binary > -> > Jul 24 14:58:36 burner kernel: fname:txt&no_carrier:bool -> > Jul 24 14:58:36 burner kernel: us:u32&reason:txt > Jul 24 14:58:36 burner kernel: 4&oaddr:ipv4 -> > Jul 24 14:58:36 burner kernel: 2 xrldb.cc matches ] > Jul 24 14:58:36 burner inetd[1046]: Accessing 10.10.4.200: No such file > or directory, continuing anyway. > Jul 24 14:58:36 burner inetd[1047]: 10.10.4.200: No such file or directory > Jul 24 15:08:58 burner su: keeper to root on /dev/ttyp0 > Jul 24 16:53:26 burner su: keeper to root on /dev/ttyp0 > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From hantongs at gmail.com Wed Jul 25 20:38:39 2007 From: hantongs at gmail.com (Hansi) Date: Thu, 26 Jul 2007 11:38:39 +0800 Subject: [Xorp-users] Multicast Protocol Support Message-ID: <2f9e317b0707252038j33eb6168k6ca06610ffed1ca3@mail.gmail.com> To whom it may concern: Hello, XORP supports multicast protocols w/c includes pim-ssm, igmp and mld. Does it also include support for multicast BGP and multicast OSPF? If not, are there any plans to support it in future releases? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070726/d1a9c50a/attachment.html From pavlin at icir.org Thu Jul 26 11:23:43 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Thu, 26 Jul 2007 11:23:43 -0700 Subject: [Xorp-users] Multicast Protocol Support In-Reply-To: Message from Hansi of "Thu, 26 Jul 2007 11:38:39 +0800." <2f9e317b0707252038j33eb6168k6ca06610ffed1ca3@mail.gmail.com> Message-ID: <200707261823.l6QINhYQ006557@possum.icir.org> > XORP supports multicast protocols w/c includes pim-ssm, igmp and mld. Does > it also include support for multicast BGP and multicast OSPF? If not, are > there any plans to support it in future releases? By "multicast BGP" I presume you mean MBGP which actually stands for "Multiprotocol (Extensions for) BGP" as described in RFC 4760. Yes, XORP implements MBGP. As for MOSPF (Multicast OSPF) as described in RFC 1584, XORP does not implement it. There are very few commercial MOSPF implementations/deployments and in general almost everyone is using PIM-SM (or occasionally PIM-DM or DVMRP). Hence, MOSPF implementation is not on our TODO list. Regards, Pavlin > > Thanks! > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From a.greenhalgh at cs.ucl.ac.uk Thu Jul 26 11:36:08 2007 From: a.greenhalgh at cs.ucl.ac.uk (Adam Greenhalgh) Date: Thu, 26 Jul 2007 19:36:08 +0100 Subject: [Xorp-users] Multicast Protocol Support In-Reply-To: <200707261823.l6QINhYQ006557@possum.icir.org> References: <2f9e317b0707252038j33eb6168k6ca06610ffed1ca3@mail.gmail.com> <200707261823.l6QINhYQ006557@possum.icir.org> Message-ID: <4769af410707261136i26479b4o7b60dc9043976e38@mail.gmail.com> > As for MOSPF (Multicast OSPF) as described in RFC 1584, XORP does > not implement it. There are very few commercial MOSPF > implementations/deployments and in general almost everyone is using > PIM-SM (or occasionally PIM-DM or DVMRP). > Hence, MOSPF implementation is not on our TODO list. Hansi, You could have a go at writing it if you need it, it wouldn't be too hard. Adam From eadigun at cs.up.ac.za Mon Jul 30 04:28:10 2007 From: eadigun at cs.up.ac.za (Emmanuel A. Adigun) Date: Mon, 30 Jul 2007 13:28:10 +0200 Subject: [Xorp-users] Address not adding In-Reply-To: <200707241751.l6OHpbaq052170@possum.icir.org> Message-ID: Hi, I'm trying to implement RIP and I keep getting the attached error message. My config file is also attached below the error message. Any help will be appreciated. Thanks Emmanuel -------------- next part -------------- A non-text attachment was scrubbed... Name: xorplog.pdf Type: application/pdf Size: 26952 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070730/f8e4bd0a/attachment-0001.pdf From pavlin at icir.org Mon Jul 30 16:22:18 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 30 Jul 2007 16:22:18 -0700 Subject: [Xorp-users] Address not adding In-Reply-To: Message from "Emmanuel A. Adigun" of "Mon, 30 Jul 2007 13:28:10 +0200." Message-ID: <200707302322.l6UNMJFc060500@possum.icir.org> > I'm trying to implement RIP and I keep getting the attached error message. > My config file is also attached below the error message. > > Any help will be appreciated. Please try with enabling only one RIP address per interface/vif. I did some testings and it seems that currently you cannot enable more than address per interface/vif inside the RIP configuration. For the record, the root of the error is that on the systems I tested (Linux with kernel 2.6.20 and FreeBSD-4.10), you cannot join twice the same multicast group on the same socket with IP addresses that belong to the same interface. I.e., "Join(G, Ifaddr1)" and "Join(G, Ifaddr2)" on the same socket will fail if Ifaddr1 and Ifaddr2 belong to the same network interface, but will succeed if they belong to different network interfaces. Could you explain the reason you want to configure 2+ addresses (on the same interface) inside RIP. E.g., is it because you want to advertise the routes for each IP address or for some other reason? I believe that using a policy to export the "connected" routes will advertise the routes even if you enable only one of the IP addresses inside the RIP configuration, though I haven't explicitly tested that. Thanks, Pavlin > > Thanks > > Emmanuel > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From eadigun at cs.up.ac.za Mon Jul 30 23:53:29 2007 From: eadigun at cs.up.ac.za (Emmanuel A. Adigun) Date: Tue, 31 Jul 2007 08:53:29 +0200 Subject: [Xorp-users] Address not adding In-Reply-To: <200707302322.l6UNMJFc060500@possum.icir.org> Message-ID: Thanks Palvin. I want to configure two addresses in RIP solely to monitor routes advertisements, i.e. request and update packets sent and received. I'm also trying to create peer groups because at the moment when I say "show rip peer statistics all" there are no known peers. I'll try using a policy. At the moment it's working with two addresses and no more but there is no request and updates packets sent and received. Many thanks, Emmanuel -----Original Message----- From: Pavlin Radoslavov [mailto:pavlin at icir.org] Sent: 31 July 2007 01:22 AM To: Emmanuel A. Adigun Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] Address not adding > I'm trying to implement RIP and I keep getting the attached error message. > My config file is also attached below the error message. > > Any help will be appreciated. Please try with enabling only one RIP address per interface/vif. I did some testings and it seems that currently you cannot enable more than address per interface/vif inside the RIP configuration. For the record, the root of the error is that on the systems I tested (Linux with kernel 2.6.20 and FreeBSD-4.10), you cannot join twice the same multicast group on the same socket with IP addresses that belong to the same interface. I.e., "Join(G, Ifaddr1)" and "Join(G, Ifaddr2)" on the same socket will fail if Ifaddr1 and Ifaddr2 belong to the same network interface, but will succeed if they belong to different network interfaces. Could you explain the reason you want to configure 2+ addresses (on the same interface) inside RIP. E.g., is it because you want to advertise the routes for each IP address or for some other reason? I believe that using a policy to export the "connected" routes will advertise the routes even if you enable only one of the IP addresses inside the RIP configuration, though I haven't explicitly tested that. Thanks, Pavlin > > Thanks > > Emmanuel > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin at icir.org Tue Jul 31 10:40:57 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Tue, 31 Jul 2007 10:40:57 -0700 Subject: [Xorp-users] Address not adding In-Reply-To: Message from "Emmanuel A. Adigun" of "Tue, 31 Jul 2007 08:53:29 +0200." Message-ID: <200707311740.l6VHevES070778@possum.icir.org> Emmanuel A. Adigun wrote: > Thanks Palvin. > I want to configure two addresses in RIP solely to monitor routes > advertisements, i.e. request and update packets sent and received. Are you intending to configure RIP in such way so you can see the RIP packets originated by one of the IP addresses on the interface and received on the same interface (but the other IP address)? I don't think it will work this way. You should run RIP instances on two different (neighbor) machines, and even then you should enable RIP on one IP address per interface. > I'm also trying to create peer groups because at the moment when I say "show > rip peer statistics all" there are no known peers. Were you running RIP on two neighbor machines on a single machine with multiple addresses enabled? If the former, it should work so please send both configurations. If the latter, it won't work (see above). In any case, please let us know how it goes. We might need to rethink (and/or fix) the multiple IP address configuration in RIP, and your feedback will help us understand better your requirements for the multiple address configuration. Thanks, Pavlin > I'll try using a policy. > At the moment it's working with two addresses and no more but there is no > request and updates packets sent and received. > > Many thanks, > Emmanuel > > -----Original Message----- > From: Pavlin Radoslavov [mailto:pavlin at icir.org] > Sent: 31 July 2007 01:22 AM > To: Emmanuel A. Adigun > Cc: xorp-users at xorp.org > Subject: Re: [Xorp-users] Address not adding > > > I'm trying to implement RIP and I keep getting the attached error message. > > My config file is also attached below the error message. > > > > Any help will be appreciated. > > Please try with enabling only one RIP address per interface/vif. > > I did some testings and it seems that currently you cannot enable > more than address per interface/vif inside the RIP configuration. > > For the record, the root of the error is that on the systems I > tested (Linux with kernel 2.6.20 and FreeBSD-4.10), you cannot join > twice the same multicast group on the same socket with IP addresses > that belong to the same interface. I.e., > "Join(G, Ifaddr1)" and "Join(G, Ifaddr2)" on the same socket will > fail if Ifaddr1 and Ifaddr2 belong to the same network interface, > but will succeed if they belong to different network interfaces. > > > Could you explain the reason you want to configure 2+ addresses > (on the same interface) inside RIP. E.g., is it because you want to > advertise the routes for each IP address or for some other reason? > I believe that using a policy to export the "connected" routes will > advertise the routes even if you enable only one of the IP addresses > inside the RIP configuration, though I haven't explicitly tested > that. > > Thanks, > Pavlin > > > > > > > > Thanks > > > > Emmanuel > > _______________________________________________ > > 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