From bhavin81 at iitb.ac.in Tue Aug 4 02:09:54 2009 From: bhavin81 at iitb.ac.in (bhavin81 at iitb.ac.in) Date: Tue, 4 Aug 2009 14:39:54 +0530 Subject: [Xorp-users] querry related with ground level work of xorp Message-ID: <75449f02339ad716b53a07c9fe73f200.squirrel@gpo.iitb.ac.in> Hello Friends, Where is the socket programing part in xorp. It it only in fea/data-plane or is it at somewhere else also? My doubt is use getsockopt or setsockopt for sending or receiving any pkt. (using raw socket feature) Regards, Bhavin. From bms at incunabulum.net Tue Aug 4 22:41:37 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Wed, 05 Aug 2009 06:41:37 +0100 Subject: [Xorp-users] querry related with ground level work of xorp In-Reply-To: <75449f02339ad716b53a07c9fe73f200.squirrel@gpo.iitb.ac.in> References: <75449f02339ad716b53a07c9fe73f200.squirrel@gpo.iitb.ac.in> Message-ID: <4A791B91.7010504@incunabulum.net> bhavin81 at iitb.ac.in wrote: > Hello Friends, > > Where is the socket programing part in xorp. It it only in fea/data-plane > or is it at somewhere else also? Only BGP and the FEA directly talk to the host's socket layer. > My doubt is use getsockopt or setsockopt > for sending or receiving any pkt. (using raw socket feature) > Please use libcomm for getsockopt()/setsockopt() wrapper operations, please only do this from within the FEA, this is what the raw socket XRLs are for. thanks, BMS From naresh_raga at yahoo.co.in Thu Aug 6 10:26:50 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Thu, 6 Aug 2009 22:56:50 +0530 (IST) Subject: [Xorp-users] xorpsh exiting due to an init error Message-ID: <983580.15346.qm@web94814.mail.in2.yahoo.com> Hi friends, I have successfully cross-compiled xorp-1.4 using crosstool-linux-gcc-3.3.4-glibc-2.3.2-0.28rc39.tar.bz2? and following the steps in BUILD_NOTES.This is cross-compiler for TS-7300 arm-kit provided by the board manufacturers..The kit had 2.4.26 kernel running on it.My host machine is x86 running ubuntu 8.04. When I am running ./xorp_rtrmgr(on kit) I am getting an error :\ [ERROR xorp_rtrmgr:9803 RTRMGR +210 main_rtrmgr.cc run] Shutting down due to an init error:Error reading XRL directory /usr/local/xorp/xrl/targets:No such file or directory. There is no problem with the cross-compiler because I have checked it with a cross-compiled hello.c program.The executable succesfully runs on the kit.. I am unable to understand the error. Please help me out. Thanks, Naresh Yahoo! recommends that you upgrade to the new and safer Internet Explorer 8. http://downloads.yahoo.com/in/internetexplorer/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090806/097d5e7f/attachment.html From greearb at candelatech.com Thu Aug 6 10:43:10 2009 From: greearb at candelatech.com (Ben Greear) Date: Thu, 06 Aug 2009 10:43:10 -0700 Subject: [Xorp-users] xorpsh exiting due to an init error In-Reply-To: <983580.15346.qm@web94814.mail.in2.yahoo.com> References: <983580.15346.qm@web94814.mail.in2.yahoo.com> Message-ID: <4A7B162E.3050407@candelatech.com> On 08/06/2009 10:26 AM, naresh raga wrote: > Hi friends, > I have successfully cross-compiled xorp-1.4 using > crosstool-linux-gcc-3.3.4-glibc-2.3.2-0.28rc39.tar.bz2 and following the > steps in BUILD_NOTES.This is cross-compiler for TS-7300 arm-kit provided > by the board manufacturers.The kit had 2.4.26 kernel running on it.My > host machine is x86 running ubuntu 8.04. When I am running > ./xorp_rtrmgr(on kit) I am getting an error :\ > > [ERROR xorp_rtrmgr:9803 RTRMGR +210 main_rtrmgr.cc run] Shutting down > due to an init error:Error reading XRL directory > /usr/local/xorp/xrl/targets:No such file or directory. > > There is no problem with the cross-compiler because I have checked it > with a cross-compiled hello.c program.The executable succesfully runs on > the kit. > I am unable to understand the error. Well, does that directory exist? [root at lanforge-D0-20 ~]# ls /usr/local/xorp/xrl/targets/ bgp4_mib.xrls ospfv2.xrls static_routes.xrls bgp.xrls ospfv3.xrls test_fea_ifmgr_mirror.xrls cli.xrls pim.xrls test_fea_rawlink.xrls coord.xrls policy.xrls test_finder_events.xrls fea_ifmgr_mirror.xrls profiler.xrls test_peer.xrls fea.xrls ribclient.xrls test_socket4.xrls fib2mrib.xrls rib.xrls test_socket6.xrls finder_client.xrls ripng.xrls test.xrls finder.xrls rip.xrls test_xrls.xrls mfea.xrls rtrmgr.xrls vrrp.xrls mld6igmp.xrls show_distances.xrls xorp_if_mib.xrls olsr4.xrls show_routes.xrls xorpsh.xrls Ben > > Please help me out. > Thanks, > Naresh > > > ------------------------------------------------------------------------ > Love Cricket? Check out live scores, photos, video highlights and more. > Click here > . > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Ben Greear Candela Technologies Inc http://www.candelatech.com From naresh_raga at yahoo.co.in Thu Aug 6 14:27:15 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Fri, 7 Aug 2009 02:57:15 +0530 (IST) Subject: [Xorp-users] xorpsh exiting due to an init error Message-ID: <619064.9910.qm@web94803.mail.in2.yahoo.com> - > Hi friends, > I have successfully cross-compiled xorp-1.4 using > crosstool-linux-gcc-3.3.4-glibc-2.3.2-0.28rc39.tar.bz2 and following the > steps in BUILD_NOTES.This is cross-compiler for TS-7300 arm-kit provided > by the board manufacturers.The kit had 2.4.26 kernel running on it.My > host machine is x86 running ubuntu 8.04. When I am running > ./xorp_rtrmgr(on kit) I am getting an error :\ > > [ERROR xorp_rtrmgr:9803 RTRMGR +210 main_rtrmgr.cc run] Shutting down > due to an init error:Error reading XRL directory > /usr/local/xorp/xrl/targets:No such file or directory. > > There is no problem with the cross-compiler because I have checked it > with a cross-compiled hello.c program.The executable succesfully runs on > the kit. > I am unable to understand the error. Well, does that directory exist? [root at lanforge-D0-20 ~]# ls /usr/local/xorp/xrl/targets/ bgp4_mib.xrls? ? ? ? ? ospfv2.xrls? ? ? ? ? static_routes.xrls bgp.xrls? ? ? ? ? ? ???ospfv3.xrls? ? ? ? ? test_fea_ifmgr_mirror.xrls cli.xrls? ? ? ? ? ? ???pim.xrls? ? ? ? ? ???test_fea_rawlink.xrls coord.xrls? ? ? ? ? ???policy.xrls? ? ? ? ? test_finder_events.xrls fea_ifmgr_mirror.xrls? profiler.xrls? ? ? ? test_peer.xrls fea.xrls? ? ? ? ? ? ???ribclient.xrls? ? ???test_socket4.xrls fib2mrib.xrls? ? ? ? ? rib.xrls? ? ? ? ? ???test_socket6.xrls finder_client.xrls? ???ripng.xrls? ? ? ? ???test.xrls finder.xrls? ? ? ? ? ? rip.xrls? ? ? ? ? ???test_xrls.xrls mfea.xrls? ? ? ? ? ? ? rtrmgr.xrls? ? ? ? ? vrrp.xrls mld6igmp.xrls? ? ? ? ? show_distances.xrls? xorp_if_mib.xrls olsr4.xrls? ? ? ? ? ???show_routes.xrls? ???xorpsh.xrls Ben I have cross-compiled xorp.I am unable to find /usr/local/xorp/ neither on my host system nor on my target kit.What I have done is copied the xrl folder in xorp-1.4(cross-compiled) to /usr/local/xorp/xrl/ on my target kit..But now I am facing new error when I run ./xorp_rtrmgr [ERROR xorp_rtrmgr:4671 XRL +634 xrl_router.cc wait_until_xrl_router_is_ready] XrlRouter failed. No Finder? What is meant by this? Thanks, Naresh. Looking for local information? Find it on Yahoo! Local http://in.local.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090807/882dbc4d/attachment.html From naresh_raga at yahoo.co.in Thu Aug 6 14:32:01 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Fri, 7 Aug 2009 03:02:01 +0530 (IST) Subject: [Xorp-users] Xrl router failed. No Finder? Message-ID: <257793.52597.qm@web94811.mail.in2.yahoo.com> Hi friends, ?I have successfully cross-compiled xorp-1.4 using ?crosstool-linux-gcc-3.3.4-glibc-2.3.2-0.28rc39.tar.bz2 by following the ?steps in BUILD_NOTES.This is cross-compiler for TS-7300 arm-kit provided ?by the board manufacturers.The kit had 2.4.26 kernel running on it.My ?host machine is x86 running ubuntu 8.04. When I am running ?./xorp_rtrmgr(on kit) I am getting an error :\ ?[ERROR xorp_rtrmgr:9803 RTRMGR +210 main_rtrmgr.cc run] Shutting down ?due to an init error:Error reading XRL directory ?/usr/local/xorp/xrl/targets:No such file or directory. ?There is no problem with the cross-compiler because I have checked it ?with a cross-compiled hello.c program.The executable succesfully runs on ?the kit. I am unable to find /usr/local/xorp/ neither on my host system nor on my target kit.What I have done is copied the xrl folder in xorp-1.4(cross-compiled) to /usr/local/xorp/xrl/ on my target kit.But now I am facing new error when I run ./xorp_rtrmgr [ERROR xorp_rtrmgr:4671 XRL +634 xrl_router.cc wait_until_xrl_router_is_ready] XrlRouter failed. No Finder? What is meant by this?Can anyone suggest whether? I am going in the right direction? Thanks, Naresh. See the Web's breaking stories, chosen by people like you. Check out Yahoo! Buzz. http://in.buzz.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090807/255dc9e8/attachment.html From naresh_raga at yahoo.co.in Thu Aug 6 23:35:25 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Fri, 7 Aug 2009 12:05:25 +0530 (IST) Subject: [Xorp-users] Error:Xrl router failed. No Finder? while running ./xorp_rtrmgr Message-ID: <922629.40247.qm@web94815.mail.in2.yahoo.com> Hi friends, ?I have successfully cross-compiled xorp-1.4 using ?crosstool-linux-gcc-3.3.4-glibc-2.3.2-0.28rc39.tar.bz2 by following the ?steps in BUILD_NOTES.This is cross-compiler for TS-7300 arm-kit provided ?by the board manufacturers.The target kit had 2.4.26 kernel running on it.My ?host machine is x86 running ubuntu 8.04.I have copied the xorp-1.4 built into my kit file system. When I am running ?./xorp_rtrmgr(on kit) I am getting an error :\ ?[ERROR xorp_rtrmgr:9803 RTRMGR +210 main_rtrmgr.cc run] Shutting down ?due to an init error:Error reading XRL directory ?/usr/local/xorp/xrl/targets:No such file or directory. ?There is no problem with the cross-compiler because I have checked it ?with a cross-compiled hello.c program.The executable succesfully runs on ?the kit. I am unable to find /usr/local/xorp/ neither on my host system nor on my target kit.What I have done is copied the xrl folder in xorp-1.4(cross-compiled) to /usr/local/xorp/xrl/ on my target kit.But now I am facing new error when I run ./xorp_rtrmgr [ERROR xorp_rtrmgr:25193 XRL +634 xrl_router.cc wait_until_xrl_router_is_ready] XrlRouter failed. No Finder? What is meant by this?Can anyone suggest whether? I am going in the right direction? Thanks, Naresh. Yahoo! recommends that you upgrade to the new and safer Internet Explorer 8. http://downloads.yahoo.com/in/internetexplorer/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090807/43c5a259/attachment.html From bhavin81 at iitb.ac.in Fri Aug 7 05:21:59 2009 From: bhavin81 at iitb.ac.in (bhavin81 at iitb.ac.in) Date: Fri, 7 Aug 2009 17:51:59 +0530 Subject: [Xorp-users] xorp architecture Message-ID: Hello All, I need to modify pim-sm implementation in xorp. I have gone through the code of pim-sm moduel of xorp. I need to modify such that user can specify some choice L,M or S in its IGMP message send to router. (which means i also need to modify igmp at user side so that it gives above three chices). The config files provided by user in xorp and their interface seems to be problem for me. Can you tell me that xorp is implemented at application layer or it is using tcp/ip stack of kernel? I mean to say is it simulating at application layer the network layer functionality? The other querry is while going through pim-sm code it uses pim_join prune function for sending join/prune messages but in which moudle is it really sent to another machine? I know most probably it is fea then can you tell me the way it goes from xorp one router to another router? like pim-sm --> pim-vif --> pim-node --> ---likewise. The last querry is from where pim-sm gets routing information since even if we do not run ospf or any other unicast routing protocol it is still capable of achieving multicast. Thanks in advance for you valuable help. Regards, Bhavin, Networking Student. From timothyc at ucla.edu Fri Aug 7 05:55:12 2009 From: timothyc at ucla.edu (Timothy Chow) Date: Fri, 7 Aug 2009 05:55:12 -0700 Subject: [Xorp-users] Empty routing table In-Reply-To: <4A434F75.5060108@incunabulum.net> References: <20090625015821.84505gugcw8eg8g8@mail.ucla.edu> <4A434F75.5060108@incunabulum.net> Message-ID: <000601ca175e$4e1c1b70$ea545250$@edu> Bruce, Sorry for this very late reply. I was off to work on other projects and I also wanted to collect more information on my side ... Once again, I am trying to cross-compile for an ARM platform. I am using an embedded software build system called OpenEmbedded (OE). It automates all the build process with correct environment variables, paths and whatnot to build embedded system software from source. I wrote a script for OE and instruct it to download the source from CVS. I found few problems with my build ... - All the executable binaries are generated as libtool wrapper scripts. I have to make the generated libtool script and change "fast_install" from "no" to "needless" in order to get the binaries correctly. - I was testing with static_routes and did a trace in several functions. Looks like the empty routing table problem is caused by the communication problems between the routing module and RIB. For example, the callback function send_rib_route_change_cb() never got called. - The info messages in some modules didn't get logged properly. Only the messages from xorp_rtrmgr were being logging. Messages from other modules such as xorp_fea and xorp_static_routes did not show up in the log at all. Looks like there are some library linkage problems to me? It would be great if you can give me some pointers on fixing this and comments from people who have cross-compiled XORP would be greatly appreciated ... Thanks, Tim -----Original Message----- From: Bruce Simpson [mailto:bms at incunabulum.net] Sent: Thursday, June 25, 2009 3:21 AM To: Timothy Chow Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] Empty routing table Timothy Chow wrote: > Hello all, > > I am porting XORP to an embedded target which has a ARM processor. > Everything got cross-compiled OK. xorp_rtrmgr and xorpsh also runs OK > under the target platform. > > I tried static and OSPF routing protocols, and looks like both > protocols do not populate the routing table at all. The "show routing > table" commands in xorpsh for both protocols gave me empty routing > tables. > Did they give you empty routing tables or empty *output* ? If there were empty tables you would have seen headers. Can you double confirm? Do the protocols involved see their own routes? Are you working from CVS sources, or a release tarball? We are currently waiting for clearance to move these sources to SourceForge so there isn't actually any point in committing bug fixes until that happens, sorry, this is a major hold-up. > I just wonder if there is anything or anywhere I can check if XORP is > working correctly on my target platform. Maybe something I missed > during the whole cross-compilation process? Any thoughts? > ARM is a strong alignment architecture. Whilst warnings have been fixed there are places in the code where strong alignment may be broken. thanks BMS From yangqqh at gmail.com Sat Aug 8 10:52:28 2009 From: yangqqh at gmail.com (Qihua Yang) Date: Sat, 8 Aug 2009 13:52:28 -0400 Subject: [Xorp-users] XORP configuration Message-ID: Hi, I try to use a PC running xorp to connect two computers. But there is only one Ethernet interface in that PC. Could you tell me how to configure interface? Do I need a hub connect xorp router, then connect two computers to that hub? Thanks a lot. Have a good day. Yang -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090808/7bbb697b/attachment.html From naresh_raga at yahoo.co.in Sun Aug 9 09:27:03 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Sun, 9 Aug 2009 21:57:03 +0530 (IST) Subject: [Xorp-users] Error:XrlRouter Failed.No Finder?while running ./xorp_rtrmgr Message-ID: <492146.22032.qm@web94805.mail.in2.yahoo.com> Hi friends, ?I have successfully cross-compiled xorp-1.4 using ?crosstool-linux-gcc-3.3.4-glibc-2.3.2-0.28rc39.tar.bz2 by following the ?steps in BUILD_NOTES.This is cross-compiler for TS-7300 arm-kit provided ?by the board manufacturers.The kit had 2.4.26 kernel running on it.My ?host machine is x86 running ubuntu 8.04. When I am running ?./xorp_rtrmgr(on kit) I am getting an error :\ ?[ERROR xorp_rtrmgr:9803 RTRMGR +210 main_rtrmgr.cc run] Shutting down ?due to an init error:Error reading XRL directory ?/usr/local/xorp/xrl/targets:No such file or directory. ?There is no problem with the cross-compiler because I have checked it ?with a cross-compiled hello.c program.The executable succesfully runs on ?the kit. I am unable to find /usr/local/xorp/ neither on my host system nor on my target kit.What I have done is copied the xrl folder in xorp-1.4(cross-compiled) to /usr/local/xorp/xrl/ on my target kit.But now I am facing new error when I run ./xorp_rtrmgr [ERROR xorp_rtrmgr:4671 XRL +634 xrl_router.cc wait_until_xrl_router_is_ready] XrlRouter failed. No Finder? What is meant by this?Can anyone suggest whether? I am going in the right direction? Thanks, Naresh. Looking for local information? Find it on Yahoo! Local http://in.local.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090809/cd270d2c/attachment.html From bms at incunabulum.net Mon Aug 10 00:23:55 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 10 Aug 2009 08:23:55 +0100 Subject: [Xorp-users] [Xorp-feedback] Inquiry In-Reply-To: <710390.29356.qm@web32405.mail.mud.yahoo.com> References: <710390.29356.qm@web32405.mail.mud.yahoo.com> Message-ID: <4A7FCB0B.7050205@incunabulum.net> Reza Kamel wrote: > To Whom It May Concern > > I'm developing an IP test bed and I was searching for a open-source > router. I amazed by your very nice software and I really appreciate if > you answer these questions about it before I try it: > > Is it possible that with making changes in the XORP source code, > we change the TTL of forwarding packets to desired value? where in the > code (File/Line)? > > XORP is control plane software. To change in-flight forwarded datagrams you need to go to the forwarding plane. So no, XORP cannot do this for you. You could take a look at the firewall support, that may help, if whichever method you choose to do this needs to be integrated with XORP in your deployment for some reason. thanks BMS From appletrp at gmail.com Mon Aug 10 07:26:22 2009 From: appletrp at gmail.com (Robert Appleton) Date: Mon, 10 Aug 2009 10:26:22 -0400 Subject: [Xorp-users] Basic Xorp Test Setup Message-ID: I'm trying to get a basic test setup to work (I had it working before but now I am trying to move it into a vm that plays in VMWare Player). Currently I have the router in a Fedora 10 VM (Running with VMWare Player) running on Windows 2003. I have the computer running xorp on one computer and two others attached with a switch. When I try to ping the two other computers to each other I get the result: Reply from 192.168._._: Destination host unreachable. Computer Setup: Computer 1: IP 192.168.1.110 Gateway 192.168.1.1 Computer 2: IP 192.168.2.120 Gateway 192.168.2.1 Xorp Computer: Is configured for address 192.168.1.1 -and- 192.168.2.1 When I ping Laptop 1 OR 2 to 192.168.1.1 I get a Reply When I ping Laptop 1 OR 2 to 192.168.2.1 I get a Reply Below I pasted by config file. Any help is appreciated interfaces { interface "eth1" { disable: false vif "eth1"{ disable: false address 192.168.1.1 { prefix-length: 24 broadcast: 192.168.1.255 disable: false } address 192.168.2.1 { prefix-length: 24 broadcast: 192.168.1.255 disable: false } } } } fea { unicast-forwarding4 { disable: false } } protocols { static { disable: false route 192.168.2.1/24 { next-hop: 192.168.2.120 } route 192.168.1.1/24 { next-hop: 192.168.1.110 } } } Let me know if any clarification is needed. Thanks - Robert Appleton From andyyuen at research.telcordia.com Mon Aug 10 07:39:06 2009 From: andyyuen at research.telcordia.com (Andy Yuen) Date: Mon, 10 Aug 2009 10:39:06 -0400 Subject: [Xorp-users] XORP to implement Muti-Topology Routing Message-ID: <4A80310A.9090207@research.telcordia.com> Hi I was wondering if it is possible to use XORP to implement Multi-topology routing over OSPF. I am looking for a solution in the user space and not hacking into the source code. On Cisco routers, it is possible to use route map to map each topology identifier such as TOS field to a particular static route using a route map. The question then becomes, (1)is there a way to map individual packet or traffic flow to a topology identifer? (2)is there a way to use XORP policy statement to implement route map on Cisco routers? Thanks Andy From bhavin81 at iitb.ac.in Mon Aug 10 18:11:24 2009 From: bhavin81 at iitb.ac.in (bhavin81 at iitb.ac.in) Date: Tue, 11 Aug 2009 06:41:24 +0530 Subject: [Xorp-users] xorp architecture] Message-ID: <3f8d71eb3bd9482d75dae13633147d97.squirrel@gpo.iitb.ac.in> Hello All, I need to modify pim-sm implementation in xorp. I have gone through the code of pim-sm moduel of xorp. I need to modify such that user can specify some choice L,M or S in its IGMP message send to router. (which means i also need to modify igmp at user side so that it gives above three chices). The config files provided by user in xorp and their interface seems to be problem for me. Can you tell me that xorp is implemented at application layer or it is using tcp/ip stack of kernel? I mean to say is it simulating at application layer the network layer functionality? The other querry is while going through pim-sm code it uses pim_join prune function for sending join/prune messages but in which moudle is it really sent to another machine? I know most probably it is fea then can you tell me the way it goes from xorp one router to another router? like pim-sm --> pim-vif --> pim-node --> ---likewise. The last querry is from where pim-sm gets routing information since even if we do not run ospf or any other unicast routing protocol it is still capable of achieving multicast. Thanks in advance for you valuable help. Regards, Bhavin, Networking Student. From jscinoz at gmail.com Thu Aug 13 23:27:06 2009 From: jscinoz at gmail.com (Jack Coulter) Date: Fri, 14 Aug 2009 16:27:06 +1000 Subject: [Xorp-users] Error recieving routes from BGP peers Message-ID: <20090814062706.GA28701@jscinoz> Hi, I run a few routers on an anonymous overlay network called AnoNet. I used to use Quagga but I switched to XORP because it has better multicast support, which we intend on setting up soon. Anyways, My 3 routers cannot recieve routes from other XORP routers on the network, however if their peers are running Quagga instead, routes are recieved fine. They are getting accepted by the policy, however i get the following errors in the log: [ 2009/08/14 14:44:38 ERROR xorp_fea:11991 FEA +75 fibconfig_transaction.cc operation_result ] FIB transaction commit failed on AddEntry4: net = 1.13.37.128/26 nexthop = 1.33.8.1 ifname = ano-vps vifname = ano-vps metric = 0 admin_distance = 20 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false [ 2009/08/14 14:44:38 ERROR xorp_rib:12571 RIB +911 redist_xrl.cc dispatch_complete ] Failed to commit transaction: 102 Command failed AddEntry4: net = 1.13.37.128/26 nexthop = 1.33.8.1 ifname = ano-vps vifname = ano-vps metric = 0 admin_distance = 20 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false Which are repeated for every route advertised by peers. My config is below: interfaces { interface ano-vps { default-system-config } interface ano-ubuntudell { default-system-config } interface ano-absinthe { default-system-config } } policy { network4-list anonet4 { network 1.0.0.0/8 network 2.0.0.0/8 } network6-list anonet6 { network de00::/8 } policy-statement redist-static { term 1 { from { protocol: "static" } } } policy-statement anonet { term 1 { from { network4-list: "anonet4" network6-list: "anonet6" } then { accept } } } } protocols { static { route 1.13.37.64/26 { next-hop: 1.13.37.65 } route 2.13.37.64/26 { next-hop: 2.13.37.65 } route 1.33.6.0/24 { next-hop: 1.13.37.65 } route dead:3133:7:2::/64 { next-hop: dead:3133:7:2::1 } } bgp { bgp-id: 1.13.37.65 local-as: 1002 import: "anonet" export: "redist-static" peer 1.33.7.1 { local-ip: 1.33.7.2 as: 1001 next-hop: 1.33.7.2 ipv4-unicast: true ipv4-multicast: true ipv6-unicast: true ipv6-multicast: true } peer 1.33.8.1 { local-ip: 1.33.8.2 as: 1003 next-hop: 1.33.8.2 ipv4-unicast: true ipv4-multicast: true ipv6-unicast: true ipv6-multicast: true } peer 1.32.3.41 { local-ip: 1.32.3.42 as: 1971 next-hop: 1.32.3.42 ipv4-unicast: true ipv4-multicast: true ipv6-unicast: true ipv6-multicast: true } } } What am I doing wrong? Many thanks, Jack Coulter -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090814/2faf9436/attachment.bin From bms at incunabulum.net Sat Aug 15 07:43:09 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Sat, 15 Aug 2009 15:43:09 +0100 Subject: [Xorp-users] XORP to implement Muti-Topology Routing In-Reply-To: <4A80310A.9090207@research.telcordia.com> References: <4A80310A.9090207@research.telcordia.com> Message-ID: <4A86C97D.2050906@incunabulum.net> Andy Yuen wrote: > Hi > I was wondering if it is possible to use XORP to implement > Multi-topology routing over OSPF. > I am looking for a solution in the user space and not hacking into the > source code. > Sorry, this isn't possible without modifying the XORP OSPF implementation. Patches are very welcome. BMS (from beach, still on vacation, naughty for doing work) From bms at incunabulum.net Sat Aug 15 07:46:59 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Sat, 15 Aug 2009 15:46:59 +0100 Subject: [Xorp-users] Empty routing table In-Reply-To: <000601ca175e$4e1c1b70$ea545250$@edu> References: <20090625015821.84505gugcw8eg8g8@mail.ucla.edu> <4A434F75.5060108@incunabulum.net> <000601ca175e$4e1c1b70$ea545250$@edu> Message-ID: <4A86CA63.1020201@incunabulum.net> Timothy Chow wrote: > ... > - All the executable binaries are generated as libtool wrapper scripts. I > have to make the generated libtool script and change "fast_install" from > "no" to "needless" in order to get the binaries correctly. > Correct, this is normal if you build without installing XORP and is standard libtool behaviour. Perhaps being built from OE is a factor. To be honest, I found OE highly Linux specific and its overall source tree structure was non-intuitive. But if it works for you, great. I can't advise on OE further. > - I was testing with static_routes and did a trace in several functions. > Looks like the empty routing table problem is caused by the communication > problems between the routing module and RIB. For example, the callback > function send_rib_route_change_cb() never got called. > - The info messages in some modules didn't get logged properly. Only the > messages from xorp_rtrmgr were being logging. Messages from other modules > such as xorp_fea and xorp_static_routes did not show up in the log at all. > I assume you're using a different libc, e.g. uclibc. That is probably the key observation. I'm afraid I am unable to help you further, this is not a configuration which I use or which is in use by the commercial product. fingers crossed other users can help. thanks, BMS From r.harbird at cs.ucl.ac.uk Sat Aug 15 08:35:16 2009 From: r.harbird at cs.ucl.ac.uk (Rae Harbird) Date: Sat, 15 Aug 2009 16:35:16 +0100 Subject: [Xorp-users] Config file error In-Reply-To: <4A686E71.2060608@incunabulum.net> References: <4A686E71.2060608@incunabulum.net> Message-ID: Dear Bruce Thanks for your reply. Firstly, I am running XORP on Linux Ubuntu 9.04, kernel 2.6.28-13-generic #45-Ubuntu SMP Your debugging suggestions were very useful. In answer to your questions: > * Is runtime linkage for the rubi process OK? > * Verify this with ldd. It's entirely possible that if you have LD_RUN_PATH > or LD_LIBRARY_PATH set, or if you are running with shared libraries > (possibly missing or misdirected), or if there is some other runtime linker > problem (e.g. 32 bit vs 64 bit thunks) when the executable is invoked. Yes, I have checked with as you suggested. The process seems Ok. > > * Have you tried writing a shell script wrapper to profile the process > invocation? > * Typically I would use this technique for doing valgrind runs for leak > testing 'in place'. > * If you look at olsr4.tp in the shipping XORP 1.6 tarball, you'll see a > commented out reference to such a shell script wrapper. This was very useful. I tried this and the xorp_rubi process starts successfully. I can interact with xorp_rubi using the xrls successfully. Am I right in thinking that when you start the process independently in this way, the template file is not read? If that is correct then can you suggest a way of using a minimal / no template file as a way of continuing to debug this problem? Rae 2009/7/23 Bruce Simpson : > Hi, > > Sorry for the long delay in my response, I've been tied up with other tasks. > > Development questions, which involve walking the code like this can and do > fall by the wayside; I apologise. > > Rae Harbird wrote: >> >> Does anyone know what kind of configuration file error might cause this >> message or give me some hints about how to debug it? Please note: the rubi >> module depends on olsr which starts up successfully beforehand. > > * I'm not too familiar with the Router Manager internals, but I'll give this > my best shot. > * I'm going to assume that the XIF was parsed by clnt-gen.py and tgt-gen.py > OK. > * The configuration file, and template file, look sane on a first reading. > >> >> [ 2009/07/03 18:03:28 ?ERROR xorp_rtrmgr:30310 RTRMGR +691 >> master_conf_tree.cc commit_pass2_done ] Commit failed: Can't validate config >> ready of process rubi >> [ 2009/07/03 18:03:28 ?ERROR xorp_rtrmgr:30310 RTRMGR +261 >> master_conf_tree.cc config_done ] Configuration failed: Can't validate >> config ready of process rubi > > Looking at the code, it appears that the error message is triggered in > rtrmgr/task.cc, Task::step2_3_done(). > > This callback is invoked in response to _config_validation->validate() in > that class. I see a bunch of state machines in there, which seem to be there > to deal with asynchronous process startup, in a fairly generic, > non-UNIX-specific, way. > > The most likely explanation is that the xorp_rubi executable cannot be run. > To my mind, the error messages in task.cc are obtuse, and difficult to > understand. If the process can't be run, the Router Manager should be much > smarter about diagnosis. > > Questions: > * Is runtime linkage for the rubi process OK? > * Verify this with ldd. It's entirely possible that if you have LD_RUN_PATH > or LD_LIBRARY_PATH set, or if you are running with shared libraries > (possibly missing or misdirected), or if there is some other runtime linker > problem (e.g. 32 bit vs 64 bit thunks) when the executable is invoked. > > * Have you tried writing a shell script wrapper to profile the process > invocation? > * Typically I would use this technique for doing valgrind runs for leak > testing 'in place'. > * If you look at olsr4.tp in the shipping XORP 1.6 tarball, you'll see a > commented out reference to such a shell script wrapper. > > Please let us know what platform you're working with when reporting problems > like this, it greatly helps us to pin down possible causes. > > thanks, > BMS > From andyyuen at research.telcordia.com Tue Aug 18 15:38:11 2009 From: andyyuen at research.telcordia.com (Andy Yuen) Date: Tue, 18 Aug 2009 18:38:11 -0400 Subject: [Xorp-users] policy on static route Message-ID: <4A8B2D53.4020409@research.telcordia.com> Hi Suppose there is a node 10.2.2.2. I want to set up a policy such that the next-hop to destination 10.1.1.0/24 is 10.2.5.5 when some metric or tag value is 1 and the next-hop is 10.2.4.4 when the corresponding metric or value is 2. Is it possible to define policy statement for static routes? Normally, I want to use 10.2.5.5, but occasionally I want to use 10.2.4.4 based on the current value of metric as defined in the policy statement. The reason behind doing this is making it possible to modify the static route by modifying a metric value only, instead of uploading the whole router configuration with new static route. This try to emulate multi-topology routing, where the metric value corresponds to the DSCP value. I use the following but get an error when this is loaded to the configuration. Thanks Andy PS On the user manual, it says it is possible to define export policy for static routes. Wonder how that is done. static { * export: "myroutes"* route 10.1.1.0/24 { next-hop: 10.2.5.5 } disable: false interface-route 0.0.0.0/0 { next-hop-interface: "my_discard" next-hop-vif: "my_discard" next-hop-router: 0.0.0.0 metric: 1 } } policy{ policy-statement "myroutes" { term a{ from{ protocol: "static" } to { } then { metric: 2 } } term b{ from{ protocol: "static" metric : 1 network4: 10.1.1.0/24 } to { } then { nexthop4: 10.2.5.5 } } term c{ from{ protocol: "static" metric : 2 network4: 10.1.1.0/24 } to { } then { nexthop4: 10.2.4.4 } } } } -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090818/3abb5546/attachment.html From andyyuen at research.telcordia.com Wed Aug 19 08:50:59 2009 From: andyyuen at research.telcordia.com (Andy Yuen) Date: Wed, 19 Aug 2009 11:50:59 -0400 Subject: [Xorp-users] XORP to implement Muti-Topology Routing In-Reply-To: <4A8BD480.3000307@incunabulum.net> References: <4A80310A.9090207@research.telcordia.com> <4A86C97D.2050906@incunabulum.net> <4A88B8B2.5050201@research.telcordia.com> <4A8BD480.3000307@incunabulum.net> Message-ID: <4A8C1F63.5010801@research.telcordia.com> Bruce Thanks for your response. I am forwarding it to the mailing lists. Cheers Andy Bruce Simpson wrote: > Andy Yuen wrote: >> Thanks Bruce. >> Actually we are going to implement MTR for Cisco routers in our final >> implementation. What we want to do on XORP is for validation of a >> reactive protocols for traffic engineering. When congestion is >> detected at some link, the node will try to reroute some traffic by >> sending a message to the source node of a selected traffic flow. The >> source node then selects an alternate route and topology to reach >> destination. I was wondering for demo purposes, is it possible to use >> policy statement to set different routes for different router tags >> and use the set statement to set all packets arriving with a specific >> router tag? >> I am not familiar with policy statement yet and just curious to know >> if it is possible. > > I think you can match on the tag field in the AS-External-LSA > according to the manual -- I guess this is what you mean by router > tag. Router ID matching isn't supported. I did add this to OLSR as it > seemed reasonable to do that, particularly given OLSR is peer-to-peer > in the p2p sense; OSPF isn't. > > Having said that, TE / MT mods to the OSPF implementation would be > great and something worth considering as a feature, it's a case of who > gets paid to sit down and do it, if it isn't already in XORP, Inc's > product roadmap (I don't believe it is). > > PS It would be great if you could Cc: XORP related traffic to the > xorp-users or xorp-hackers list. thanks! From abee_peraye at hotmail.com Fri Aug 21 20:32:43 2009 From: abee_peraye at hotmail.com (abee peraye) Date: Sat, 22 Aug 2009 10:32:43 +0700 Subject: [Xorp-users] Multicast using Xorp Message-ID: Hi,It's my first time using Xorp. I want to build simple Multicast Network with 1server, 2routers, and 1client.I'm running Xorp on FreeBSD. Here's my network topology and Xorp configuration: Server-o----------o-Router1-o---------o-Router2-o---------o-Client192.168.1.1/24 1.2/24 2.1/24 2.2/24 3.1/24 3.2/24 Xorp configuration on Router1: interfaces { interface rl0 { default-system-config disable: false } interface fxp0 { default-system-config disable: false }}protocols { fib2mrib { disable: false } igmp { disable: false interface rl0 { vif rl0 { disable: false } } interface fxp0 { vif fxp0 { disable: false } } } pimsm4 { disable: false interface rl0 { vif rl0 { disable: false } } interface fxp0 { vif fxp0 { disable: false } } interface register_vif { vif register_vif { disable: false } } switch-to-spt-threshold { disable: false interval: 100 bytes: 4096000 } }}plumbing { mfea4 { disable: false interface rl0 { vif rl0 { disable: false } } interface fxp0 { vif fxp0 { disable: false } } interface register_vif { vif register_vif { disable: false } } }} Xorp Configuration on Router2: interfaces { interface rl0 { default-system-config disable: false } interface rl1 { default-system-config disable: false }}protocols { fib2mrib { disable: false } igmp { disable: false interface rl0 { vif rl0 { disable: false } } interface rl1 { vif rl1 { disable: false } } } Pimsm4 { disable: false interface rl0 { vif rl0 { disable: false } } interface rl1 { vif rl1 { disable: false } } interface register_vif { vif register_vif { disable: false } } switch-to-spt-threshold { disable: false interval: 100 bytes: 4096000 } }}plumbing { mfea4 { disable: false interface rl0 { vif rl0 { disable: false } } interface rl1 { vif rl1 { disable: false } } interface register_vif { vif register_vif { disable: false } } }} For static routing, I'm using OSPFD from Quagga. For Server and Client, I'm using VLC Player.The situation right now, I only can ping from Server to Client. But when I'm Streaming Multicast, Client can't receive it.Is there something wrong with my Xorp Configuration? Or maybe I missed some configuration line? Because with Configuration on Router1 like that, I already success Stream Multicast from Server to Client, but only passed 1router.Actually, I want to build Multicast Network with 3routers. But I stuck at 2routers. Thanks for helping.-Abee _________________________________________________________________ What can you do with the new Windows Live? Find out http://www.microsoft.com/windows/windowslive/default.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090822/2e8fb881/attachment.html From emixp at gmx.net Mon Aug 24 01:00:43 2009 From: emixp at gmx.net (Emi) Date: Mon, 24 Aug 2009 10:00:43 +0200 Subject: [Xorp-users] xorpsh crash. is there any solution? Message-ID: <20090824080043.56120@gmx.net> Hi there Once upon a time, in the xorp-hackers mailing list, there was a discussion about a bug causing xorpsh to crash with 100% cpu load when configuring xorp from a script, caused by a spinlock or so. Is there any solution or patch for this problem? with best regards -- GRATIS f?r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 From murad03_khan at yahoo.com Mon Aug 24 03:17:45 2009 From: murad03_khan at yahoo.com (Murad) Date: Mon, 24 Aug 2009 03:17:45 -0700 (PDT) Subject: [Xorp-users] XORP on USB Message-ID: <341863.55936.qm@web52403.mail.re2.yahoo.com> Hi, Has anybody used XORP on any linux distribution running from USB stick. Any help will be highly appreciated. I want to run XORP from Debian (lenny) on a USB stick. Regards, Murad -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090824/021366f6/attachment.html From greearb at candelatech.com Mon Aug 24 08:13:39 2009 From: greearb at candelatech.com (Ben Greear) Date: Mon, 24 Aug 2009 08:13:39 -0700 Subject: [Xorp-users] xorpsh crash. is there any solution? In-Reply-To: <20090824080043.56120@gmx.net> References: <20090824080043.56120@gmx.net> Message-ID: <4A92AE23.3010805@candelatech.com> Emi wrote: > Hi there > > Once upon a time, in the xorp-hackers mailing list, there was a discussion about a bug causing xorpsh to crash with 100% cpu load when configuring xorp from a script, caused by a spinlock or so. > > Is there any solution or patch for this problem? > That is fixed in the latest stable code, as far as I can tell... Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From emixp at gmx.net Mon Aug 24 08:33:42 2009 From: emixp at gmx.net (Emi) Date: Mon, 24 Aug 2009 17:33:42 +0200 Subject: [Xorp-users] xorpsh crash. is there any solution? References: <20090824080043.56120@gmx.net> <4A92AE23.3010805@candelatech.com> Message-ID: Hi there Thenk you very much for the information. I will check the version of my code. with best regards From bms at incunabulum.net Mon Aug 24 14:49:08 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 24 Aug 2009 22:49:08 +0100 Subject: [Xorp-users] Announcement: XORP code repository is now live again Message-ID: <4A930AD4.90006@incunabulum.net> Hello all, This is to announce that the XORP code repository is now publicly available again. The community version of XORP is now being hosted at SourceForge. Public read-only Subversion access has been enabled. Once again, we are very sorry for the delay involved. Since the transition to XORP, Inc. it was necessary to seek legal advice, to ensure that releasing the code did not affect the company's position with regards to copyright and intellectual property. We are confident these issues have now been resolved, so open development of the code base may now re-commence. We look forward to your feedback, comments and suggestions. Testing of the public code is strongly encouraged; the more feedback we receive, the more quickly we can prepare a 1.7 release candidate from this branch. This would, however, be a maintenance release only, with no new features planned at this time. The major changes to the code in SVN, from 1.6, are as follows: * The adoption of a new Python-based build system, SCons. * The docs/ have been moved out of the source code directory itself. SCons has also been deployed there. * GNU autotools have been completely eliminated from the tree. * Platform support has also narrowed considerably, as we no longer have access to all of the testing resources. We are focusing on Ubuntu, Fedora and FreeBSD at this time. * SNMP support has also been dropped, as the work was incomplete. The main development plan is to refactor the code base to use the Boost C++ Libraries, and to transition XRL to Facebook/Apache's Thrift RPC middleware. This work has already begun. Here are some brief instructions for checking out the XORP code from Sourceforge SVN: XORP SVN Quick Hints ==================== To check out xorp source from trunk read-only: $ svn co http://xorp.svn.sourceforge.net/svnroot/xorp/trunk/xorp The first time you check out XORP you may get a message like this: Error validating server certificate for 'https://xorp.svn.sourceforge.net:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: *.svn.sourceforge.net - Valid: from Tue, 11 Nov 2008 20:25:27 GMT until Mon, 11 Jan 2010 20:25:27 GMT - Issuer: Equifax Secure Certificate Authority, Equifax, US - Fingerprint: 04:b2:70:e9:ba:cf:70:fc:e8:8a:22:86:14:13:51:97:1b:6a:de:38 (R)eject, accept (t)emporarily or accept (p)ermanently? All that should need to be done is to hit the 'p' key. To switch an existing read-only checkout to read-write access: $ svn switch --relocate http://xorp.svn.sourceforge.net/svnroot/xorp https://xorp.svn.sourceforge.net/svnroot/xorp This assumes you have a SourceForge account, and have been granted commit privileges for the xorp project. Once again, thanks for all your encouragement and support over the years, and your patience as we prepare to move in a radically different direction. We look forward to improving XORP further with your help. thanks, BMS From bms at incunabulum.net Mon Aug 24 14:49:20 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 24 Aug 2009 22:49:20 +0100 Subject: [Xorp-users] XORP on USB In-Reply-To: <341863.55936.qm@web52403.mail.re2.yahoo.com> References: <341863.55936.qm@web52403.mail.re2.yahoo.com> Message-ID: <4A930AE0.6000903@incunabulum.net> Murad wrote: > Hi, > > Has anybody used XORP on any linux distribution running from USB > stick. Any help will be highly appreciated. I want to run XORP from > Debian (lenny) on a USB stick. > The XORP LiveUSB build is based on FreeBSD, however, this was not part of the 1.6 release. You can check out the files under 'other' in the XORP SVN repository to get the necessary NanoBSD configuration to build the LiveUSB image. We do not currently support Linux in the LiveUSB or LiveCD builds. User contributions for this are of course welcome. thanks BMS From bms at incunabulum.net Mon Aug 24 14:52:37 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 24 Aug 2009 22:52:37 +0100 Subject: [Xorp-users] Multicast using Xorp In-Reply-To: References: Message-ID: <4A930BA5.2010109@incunabulum.net> Please check the list archives, as similar questions have been asked here before about stub multicast network setup. If you plan to receive Internet multicast, you need to contact your upstream provider for more details. You probably just need to: 1. configure an RP 2. define a scope for the RP 3. tell your VLC and/or streaming server to use multicast addresses within the RP's scope. thanks BMS From naresh_raga at yahoo.co.in Tue Aug 25 00:01:28 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Tue, 25 Aug 2009 00:01:28 -0700 (PDT) Subject: [Xorp-users] Error:XrlRouter Failed.No Finder?while running ./xorp_rtrmgr Message-ID: <373791.75055.qm@web94814.mail.in2.yahoo.com> Hi friends, ?I have successfully cross-compiled xorp-1.4 using ?crosstool-linux-gcc-3.3.4-glibc-2.3.2-0.28rc39.tar.bz2 by following the ?steps in BUILD_NOTES.This is cross-compiler for TS-7300 arm-kit provided ?by the board manufacturers.The kit had 2.4.26 kernel running on it.My ?host machine is x86 running ubuntu 8.04. When I am running ?./xorp_rtrmgr(on kit) I am getting an error :\ ?[ERROR xorp_rtrmgr:9803 RTRMGR +210 main_rtrmgr.cc run] Shutting down ?due to an init error:Error reading XRL directory ?/usr/local/xorp/xrl/targets:No such file or directory. ?There is no problem with the cross-compiler because I have checked it ?with a cross-compiled hello.c program.The executable succesfully runs on ?the kit. I am unable to find /usr/local/xorp/ neither on my host system nor on my target kit.What I have done is copied the xrl folder in xorp-1.4(cross-compiled) to /usr/local/xorp/xrl/ on my target kit.But now I am facing new error when I run ./xorp_rtrmgr [ERROR xorp_rtrmgr:4671 XRL +634 xrl_router.cc wait_until_xrl_router_is_ready] XrlRouter failed. No Finder? What is meant by this?Can anyone suggest whether? I am going in the right direction? Thanks, Naresh. Looking for local information? Find it on Yahoo! Local See the Web's breaking stories, chosen by people like you. Check out Yahoo! Buzz. http://in.buzz.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090825/3a449664/attachment.html From emixp at gmx.net Tue Aug 25 08:41:35 2009 From: emixp at gmx.net (Emi) Date: Tue, 25 Aug 2009 17:41:35 +0200 Subject: [Xorp-users] xorpsh crash. is there any solution? References: <20090824080043.56120@gmx.net> <4A92AE23.3010805@candelatech.com> Message-ID: Hi It's me again. I checked the version of my code, and noticed, that it was 1.5. So i installed this package: http://packages.debian.org/sid/i386/xorp/download. (xorp_1.6-1~rc2_i386.deb). sadly, xorpsh keeps crashing on my machines when configuring from scripts. Have I simply still installed the wrong version? And if yes, where are .deb packages for the right version available? Or am I facing a new kind of bug? I am currently not able to compile the sources on my machines, because my routers are in an isolated development and research network and installing compilers and other tootls to compile xorp would be difficult. with best regards from Austria From greearb at candelatech.com Tue Aug 25 08:58:27 2009 From: greearb at candelatech.com (Ben Greear) Date: Tue, 25 Aug 2009 08:58:27 -0700 Subject: [Xorp-users] xorpsh crash. is there any solution? In-Reply-To: References: <20090824080043.56120@gmx.net> <4A92AE23.3010805@candelatech.com> Message-ID: <4A940A23.2070009@candelatech.com> Emi wrote: > Hi > > It's me again. > > I checked the version of my code, and noticed, that it was 1.5. So i > installed this package: > http://packages.debian.org/sid/i386/xorp/download. > (xorp_1.6-1~rc2_i386.deb). > > sadly, xorpsh keeps crashing on my machines when configuring from > scripts. Have I simply still installed the wrong version? And if yes, > where are .deb packages for the right version available? Or am I > facing a new kind of bug? > > I am currently not able to compile the sources on my machines, because > my routers are in an isolated development and research network and > installing compilers and other tootls to compile xorp would be difficult. Well, it's fixed in my code branch at least. I'm not sure what that .deb package is really based on. I don't have pre-compiled packages for debian, however. The official xorp tree opened up yesterday too, but I haven't had a chance to look at it. Thanks, Ben > > with best regards from Austria -- Ben Greear Candela Technologies Inc http://www.candelatech.com From rae.harbird at gmail.com Tue Aug 25 12:56:45 2009 From: rae.harbird at gmail.com (Rae Harbird) Date: Tue, 25 Aug 2009 20:56:45 +0100 Subject: [Xorp-users] [Xorp-hackers] Announcement: XORP code repository is now live again In-Reply-To: <4A930AD4.90006@incunabulum.net> References: <4A930AD4.90006@incunabulum.net> Message-ID: Hi I am running XORP on Linux Ubuntu 9.04, kernel 2.6.28-13-generic #45-Ubuntu I have checked out the code from the svn repository and started using SCons (which I like). Everything is going well and I can run up "xorp_rtrmgr" successfully. I am having trouble getting scons to install the binaries and libraries for olsr. I have been running scons from the top directory as follows: scons . sudo scons install I have made minor amendments to some of the scons config files which may (or may not) have helped the situation: 1. SConstruct - modified line: env['WITH_OLSR'] = ARGUMENTS.get('enable-olsr', False) to: env['WITH_OLSR'] = ARGUMENTS.get('enable-olsr', True) 2. Modified the subdirs variable in the top-level SConscript directory to include 'olsr' 3. Added or uncommented references to olsr4 in: xrl/interfaces/SConscript xrl/targets/SConscript etc/templates/SConscript I get a warning when I run "scons .": scons: warning: Ignoring missing SConscript 'obj/i686-linux-public17/olsr/SConscript' File "/data/XORP/XORP_SVN_1.6/xorp/SConscript", line 50, in The obj/i686-linux-public17/olsr directory is created although remains empty. There is no olsr directory under /usr/local/xorp/ either. What have I missed? Rae ===== 2009/8/24 Bruce Simpson : > Hello all, > > This is to announce that the XORP code repository is now publicly > available again. The community version of XORP is now being hosted at > SourceForge. Public read-only Subversion access has been enabled. > > ? ?Once again, we are very sorry for the delay involved. Since the > transition to XORP, Inc. it was necessary to seek legal advice, to > ensure that releasing the code did not affect the company's position > with regards to copyright and intellectual property. We are confident > these issues have now been resolved, so open development of the code > base may now re-commence. > > ? ?We look forward to your feedback, comments and suggestions. Testing > of the public code is strongly encouraged; the more feedback we receive, > the more quickly we can prepare a 1.7 release candidate from this > branch. This would, however, be a maintenance release only, with no new > features planned at this time. > > ? ?The major changes to the code in SVN, from 1.6, are as follows: > ?* The adoption of a new Python-based build system, SCons. > ?* The docs/ have been moved out of the source code directory itself. > SCons has also been deployed there. > ?* GNU autotools have been completely eliminated from the tree. > ?* Platform support has also narrowed considerably, as we no longer have > access to all of the testing resources. We are focusing on Ubuntu, > Fedora and FreeBSD at this time. > ?* SNMP support has also been dropped, as the work was incomplete. > > ? ?The main development plan is to refactor the code base to use the > Boost C++ Libraries, and to transition XRL to Facebook/Apache's Thrift > RPC middleware. This work has already begun. > > Here are some brief instructions for checking out the XORP code from > Sourceforge SVN: > > XORP SVN Quick Hints > ==================== > > To check out xorp source from trunk read-only: > > ?$ svn co http://xorp.svn.sourceforge.net/svnroot/xorp/trunk/xorp > > The first time you check out XORP you may get a message like this: > > Error validating server certificate for > 'https://xorp.svn.sourceforge.net:443': > ?- The certificate is not issued by a trusted authority. Use the > ? fingerprint to validate the certificate manually! > Certificate information: > ?- Hostname: *.svn.sourceforge.net > ?- Valid: from Tue, 11 Nov 2008 20:25:27 GMT until Mon, 11 Jan 2010 > 20:25:27 GMT > ?- Issuer: Equifax Secure Certificate Authority, Equifax, US > ?- Fingerprint: 04:b2:70:e9:ba:cf:70:fc:e8:8a:22:86:14:13:51:97:1b:6a:de:38 > (R)eject, accept (t)emporarily or accept (p)ermanently? > > All that should need to be done is to hit the 'p' key. > > To switch an existing read-only checkout to read-write access: > > ?$ svn switch --relocate http://xorp.svn.sourceforge.net/svnroot/xorp > https://xorp.svn.sourceforge.net/svnroot/xorp > > This assumes you have a SourceForge account, and have been granted commit > privileges for the xorp project. > > Once again, thanks for all your encouragement and support over the > years, and your patience as we prepare to move in a radically different > direction. We look forward to improving XORP further with your help. > > thanks, > BMS > > _______________________________________________ > Xorp-hackers mailing list > Xorp-hackers at icir.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers > From jtc at acorntoolworks.com Tue Aug 25 14:40:12 2009 From: jtc at acorntoolworks.com (J.T. Conklin) Date: Tue, 25 Aug 2009 14:40:12 -0700 Subject: [Xorp-users] [Xorp-hackers] Announcement: XORP code repository is now live again In-Reply-To: (Rae Harbird's message of "Tue, 25 Aug 2009 20:56:45 +0100") References: <4A930AD4.90006@incunabulum.net> Message-ID: <877hwr7etf.fsf@orac.acorntoolworks.com> Rae Harbird writes: > I am running XORP on Linux Ubuntu 9.04, kernel 2.6.28-13-generic #45-Ubuntu > > I have checked out the code from the svn repository and started using > SCons (which I like). Everything is going well and I can run up > "xorp_rtrmgr" successfully. > > I am having trouble getting scons to install the binaries and > libraries for olsr. > > I have been running scons from the top directory as follows: > > scons . > sudo scons install > > I have made minor amendments to some of the scons config files which > may (or may not) have helped the situation: > > 1. SConstruct - modified line: > > env['WITH_OLSR'] = ARGUMENTS.get('enable-olsr', False) > > to: > > env['WITH_OLSR'] = ARGUMENTS.get('enable-olsr', True) This changes the default for OLSR from False to True. It should have been possible to specify this option on the command line with "scons enable-olsr=true ...". The intent is that all build options are available through command line arguments. We recently found some issue with the handling of binary valued options. For example, both enable-olsr=True and enable-olsr=False would actually enable the option because the argument is a string and in Python non- zero length strings evaluate as True in boolean contexts. I've just checked in a fix for this for the 'shared' and 'strip' options, and will extend it to all boolean options over time. > 2. Modified the subdirs variable in the top-level SConscript directory > to include 'olsr' I believe this should have been 'contrib/olsr'. Actually, what's missing is a SConscript within contrib which enables (adds to subdirs) the various contrib modules based on build options. But until that's done, you'll want to add 'contrib/olsr' to the top SConstruct. One word of warning is that will defeat the build option, as the olsr SConscript has no conditionals of its own. > 3. Added or uncommented references to olsr4 in: > > xrl/interfaces/SConscript > xrl/targets/SConscript > etc/templates/SConscript Yes, these are needed. One thing that has been discussed is moving the XLR interface and target files, router manager template files, etc. out of a common directory and into each protocol (There are common bits, of course, that would still have to live in a common directory). The advantage of this is that all the protocol related code would be in one place, and if we go further conditionalizing the building of individual XORP protocols, all those conditionals will be in the protocol's SConscript rather than scattered around/across the source tree. It may not make sense to do this now, especially with the upcoming plans to update the IPC mechanism, but community feedback on this idea would be most welcome. > I get a warning when I run "scons .": > > scons: warning: Ignoring missing SConscript > 'obj/i686-linux-public17/olsr/SConscript' > File "/data/XORP/XORP_SVN_1.6/xorp/SConscript", line 50, in I think this will be fixed once you address 2). > What have I missed? I don't think you've missed much. I'm not sure what the status of OLSR is and how/why it's build was missed. Perhaps Bruce will have something to say on that point. That being said, I'm not suprised by the type of problems you ran into. I expect more of a similar nature as more people check out the new public code and try out the new build system. But they all should be easy to fix, and the faster the problems are reported the quicker they will be resolved. --jtc -- J.T. Conklin From abee_peraye at hotmail.com Tue Aug 25 21:15:23 2009 From: abee_peraye at hotmail.com (abee peraye) Date: Wed, 26 Aug 2009 11:15:23 +0700 Subject: [Xorp-users] Multicast using Xorp In-Reply-To: <4A930BA5.2010109@incunabulum.net> References: <4A930BA5.2010109@incunabulum.net> Message-ID: From: abee_peraye at hotmail.com To: bms at incunabulum.net Subject: RE: [Xorp-users] Multicast using Xorp Date: Tue, 25 Aug 2009 15:10:19 +0700 Hi Bruce, I just want to build multicast for private network. Do you mean I have to configure RP in bootstrap config?Yes, i've been trying that before, but just in Router1. Well, multicast still didn't work. Client can't receive multicast stream from Server. Here's my bootstrap configuration in Router1: protocols { pimsm4 { bootstrap { cand-rp { group-prefix 224.0.0.0/4 { cand-bsd-by-vif-name: "rl0" cand-bsd-by-vif-address: 192.168.2.1 } } }} Do I must config bootstrap in every router? or just in one router? I'm looking forward for your help.Thank you -Abee > Date: Mon, 24 Aug 2009 22:52:37 +0100 > From: bms at incunabulum.net > To: abee_peraye at hotmail.com > CC: xorp-users at xorp.org > Subject: Re: [Xorp-users] Multicast using Xorp > > Please check the list archives, as similar questions have been asked > here before about stub multicast network setup. > > If you plan to receive Internet multicast, you need to contact your > upstream provider for more details. > > You probably just need to: > 1. configure an RP > 2. define a scope for the RP > 3. tell your VLC and/or streaming server to use multicast addresses > within the RP's scope. > > thanks > BMS Be seen with Buddy! Tag your picture and win exciting prizes! Click here _________________________________________________________________ Share your memories online with anyone you want. http://www.microsoft.com/indonesia/windows/windowslive/products/photos-share.aspx?tab=1 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090826/c3590322/attachment.html From bms at incunabulum.net Wed Aug 26 04:46:15 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Wed, 26 Aug 2009 12:46:15 +0100 Subject: [Xorp-users] OLSR build glue In-Reply-To: References: <4A930AD4.90006@incunabulum.net> Message-ID: <4A952087.2050800@incunabulum.net> Hi Rae, Thanks for your ongoing interest in OLSR, which is an optional XORP component at the moment. If you can test a prospective release candidate on Ubuntu, that is excellent, we need all the help we can get to push out a 1.7-RC. Unfortunately, at the moment, OLSR isn't a priority, as we try to bring the XORP install up under the new build system. We may get around to fixing this later on, as we figure out some of the kinks with SCons. For now, we've focused on the core XORP components which people are using. What we really want to see is a means of building/installing optional XORP components without having everything in one central location in the source directory. This was achieved with FTJam, and should be possible with SCons. Based on what you've posted, it sounds like a path needs to be fixed somewhere, as olsr resides under 'contrib'. The obj/ hierarchy which SCons creates corresponds to the source directories. JT just cut over to using the Variables() object in SConstruct, so scons command line options for the build might need a rethink. thanks, BMS From Anthony.Brock at oregonstate.edu Wed Aug 26 11:29:43 2009 From: Anthony.Brock at oregonstate.edu (Brock, Anthony - NET) Date: Wed, 26 Aug 2009 11:29:43 -0700 Subject: [Xorp-users] Xorp and MPLS Message-ID: <7B4268E5ACB878429B58D4BE5B780E8301F43FBD@NWS-EXCH2.nws.oregonstate.edu> We've successfully started using xorp (version 1.5) for an internal routing project. In light of how well it has functioned so far, we would like to use it as a BGP route reflector for our MPLS infrastructure. Is this currently supported in xorp? I found the sections of the xorp manual that talk about configuring it as a route reflector, but I would like to confirm that it supports the extended community attributes needed for mpls before spending significant time on it. Thanks! Tony From bms at incunabulum.net Thu Aug 27 04:19:22 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 27 Aug 2009 12:19:22 +0100 Subject: [Xorp-users] Xorp and MPLS In-Reply-To: <7B4268E5ACB878429B58D4BE5B780E8301F43FBD@NWS-EXCH2.nws.oregonstate.edu> References: <7B4268E5ACB878429B58D4BE5B780E8301F43FBD@NWS-EXCH2.nws.oregonstate.edu> Message-ID: <4A966BBA.6060403@incunabulum.net> Brock, Anthony - NET wrote: > We've successfully started using xorp (version 1.5) for an internal > routing project. In light of how well it has functioned so far, we would > like to use it as a BGP route reflector for our MPLS infrastructure. > > Is this currently supported in xorp? I found the sections of the xorp > manual that talk about configuring it as a route reflector, but I would > like to confirm that it supports the extended community attributes > needed for mpls before spending significant time on it. > The bad news: It isn't implemented [yet]. We've kicked around the idea of supporting BGP for MPLS tag exchange (i.e. replace the use of raw LDP). This would require changes to the BGP code, of course. BGP is off the XORP, Inc. feature roadmap, the product focus is elsewhere -- for the moment. The ongoing news: There have been a few efforts to introduce MPLS to the BSD networking kernel, including NISTswitch (very old, not worth bothering with), perhaps the most mature open source effort was Ayame for NetBSD. Matthew Luckie was working on a port of Ayame to FreeBSD, however, I believe that effort stalled -- others may have pitched in since then. I handed my copy of 'MPLS and Label Switching Networks' over to donations at FreeBSD the other month. Can't speak for Linux -- code drops do exist. The good news: The SCons deployment, and refactoring of the XRL middleware, will make it possible to drop-in new features like this to the code much more easily, as working with XRL and GNU Autotools has been a cumbersome stumbling block for participation. The aim is to lower the bar, by making it possible to slot new stuff right in without hard dependencies on C++ itself. What to do next: You are not the only person to ask for BGP features -- so I'd suggest you either lobby XORP, Inc. directly, communicate with others in this forum who are looking to extend XORP's BGP, consult directly with developers (Hi! But busy doing the above), or even hoist the Jolly Roger and start a bounty for the feature. So it's a case of 'who dares wins'. later, BMS From bms at incunabulum.net Thu Aug 27 04:32:21 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 27 Aug 2009 12:32:21 +0100 Subject: [Xorp-users] Error:XrlRouter Failed.No Finder?while running ./xorp_rtrmgr In-Reply-To: <373791.75055.qm@web94814.mail.in2.yahoo.com> References: <373791.75055.qm@web94814.mail.in2.yahoo.com> Message-ID: <4A966EC5.8070607@incunabulum.net> Hi, We're not supporting cross-compilation of the code just at the moment. We'd appreciate any help in getting the SCons-ified code in SVN trunk to cross-compile, now that SVN has re-opened. For self-hosted builds where target and host are the same (and packaging for the major distros), this should not be an issue. The Endianness test needs to be told which endianness to expect on the target, and the LIBPATH, CPPPATH in the top level SConscript needs to be told not to look for resources it needs in hard-coded locations on the host system. The defaults set there are fine for Ubuntu, FreeBSD, NetBSD and OpenSolaris. The Router Manager needs the *.xrls files to know which XRLs to send directly to the processes which it manages. You should verify that xorp_rtrmgr is able to start its internal Finder, and is listening on port 19999 (the default TCP listen port for the XORP Finder IPC broker) when you start the process. thanks, BMS From bms at incunabulum.net Thu Aug 27 04:35:45 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 27 Aug 2009 12:35:45 +0100 Subject: [Xorp-users] Announce: XORP's Ohloh profile updated Message-ID: <4A966F91.50802@incunabulum.net> Hi all, I have updated the XORP profile page on Ohloh.net: https://www.ohloh.net/p/xorp We're waiting for the SvnSync import to complete, to update the code history. If you are actively using XORP, please feel free to create an Ohloh account, and indicate that you're a XORP user. thanks, BMS From bms at incunabulum.net Thu Aug 27 04:44:00 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 27 Aug 2009 12:44:00 +0100 Subject: [Xorp-users] Config file error In-Reply-To: References: <4A686E71.2060608@incunabulum.net> Message-ID: <4A967180.2050104@incunabulum.net> Rae Harbird wrote: > Am I right in thinking that when you start the process > independently in this way, the template file is not read? Correct, template files are processed by the Router Manager. If you run a process independently, this won't be read. > If that is > correct then can you suggest a way of using a minimal / no template > file as a way of continuing to debug this problem? > At the moment, the code in public SVN is still using XRL. You might want to look at one of the shell script stubs used to drive the protocols for testing: http://xorp.svn.sourceforge.net/viewvc/xorp/trunk/xorp/pim/xrl_pim_shell_funcs.sh?view=log We'll obliterate these as part of the move to Thrift, when that happens (1.8 or 2.0). One of the problems with XRL, is that the *return* of compound/structured data isn't handled well. For example, most of the tools/ exist as C++ programs, just because they need to read, parse and display this structured data. Thrift can streamline this process, by putting struct and collection support into the RPC middleware layer itself. It does however mean moving to an object-oriented scripting language (Python, Ruby). Given we already use Python a lot, this is tasty. thanks BMS From bms at incunabulum.net Thu Aug 27 05:03:55 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 27 Aug 2009 13:03:55 +0100 Subject: [Xorp-users] Empty routing table In-Reply-To: <000601ca175e$4e1c1b70$ea545250$@edu> References: <20090625015821.84505gugcw8eg8g8@mail.ucla.edu> <4A434F75.5060108@incunabulum.net> <000601ca175e$4e1c1b70$ea545250$@edu> Message-ID: <4A96762B.3020606@incunabulum.net> Timothy Chow wrote: > Looks like there are some library linkage problems to me? It would be great > if you can give me some pointers on fixing this and comments from people who > have cross-compiled XORP would be greatly appreciated ... > Try the public SVN code. We have eliminated the GNU autotools from the source tree. This is a very turbulent change, however, it means libtool is no longer part of the critical path. Cross-compilation is not currently functional, however, please see other posts today on this subject for information on what work needs to be done. At the moment we're focusing on delivering the 1.7-RC, and we welcome all help from the community to make that happen. thanks, BMS From bms at incunabulum.net Thu Aug 27 07:52:27 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 27 Aug 2009 15:52:27 +0100 Subject: [Xorp-users] Underlying VIF is not UP..please solve this problem In-Reply-To: <200904221604.46398.hhund@astaro.com> References: <503670.20521.qm@web94813.mail.in2.yahoo.com> <200904221604.46398.hhund@astaro.com> Message-ID: <4A969DAB.1090504@incunabulum.net> http://bugzilla.xorp.org/show_bug.cgi?id=560 Committed as SVN rev 11524, thanks! From naresh_raga at yahoo.co.in Thu Aug 27 10:08:32 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Thu, 27 Aug 2009 22:38:32 +0530 (IST) Subject: [Xorp-users] Error:XrlRouter Failed.No Finder?while running ./xorp_rtrmgr In-Reply-To: <4A966EC5.8070607@incunabulum.net> Message-ID: <995842.86886.qm@web94804.mail.in2.yahoo.com> Hi Bruce, When I googled on this error,I found http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2009-February/003004.html. It states that many debian users have faced with the same problem.I am also working on debian on TS7300 with 2.4.26 kernel. >The Router Manager needs the *.xrls files to know which XRLs to send >directly to the processes which it manages. >You should verify that xorp_rtrmgr is able to start its internal Finder, >and is listening on port 19999 (the default TCP listen port for the XORP >Finder IPC broker) when you start the process. In the above xorp thread also Moises said "That did the trick. The problem was the router firewall. I added some? rules for 127.0.0.1 connections and everything works well." I am unable to know how to verify xorp_rtrmgr is able to start its internal Finder or not?Also can you suggest what rules for 127.0.0.1 connections makes things working? Please help me out. Thanks, Naresh. Love Cricket? Check out live scores, photos, video highlights and more. Click here http://cricket.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090827/6f025674/attachment.html From bms at incunabulum.net Fri Aug 28 04:16:42 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Fri, 28 Aug 2009 12:16:42 +0100 Subject: [Xorp-users] Error:XrlRouter Failed.No Finder?while running ./xorp_rtrmgr In-Reply-To: <995842.86886.qm@web94804.mail.in2.yahoo.com> References: <995842.86886.qm@web94804.mail.in2.yahoo.com> Message-ID: <4A97BC9A.20302@incunabulum.net> Hi Naresh, Sorry to hear you are having problems running a cross build of XORP under Debian. naresh raga wrote: > > > > When I googled on this error,I found > http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2009-February/003004.html. > It states that many debian users have faced with the same > problem.I am also working on debian on TS7300 with 2.4.26 kernel. > My suggestion would be: to focus on verifying XORP 1.7-WIP from public SVN sources works OK, natively on the Debian derived systems, before attempting cross-compilation. Fixes/modifications WILL be needed to the new SCons build system, and we'd really appreciate your help in making this happen. I have verified the current SVN code builds on Ubuntu 9.04, which is also a Debian derived system. Due to a lack of resource, I don't plan to look at other Debian derived systems; I am focused on making sure the FreeBSD based XORP LiveUSB build works, and preliminary testing suggests everything is OK there. [This is largely a distraction for me at the moment, as I should really be getting on with the Thrift/Boost refactoring.] I can't speak for default firewall configs under this system you're using, although it is certainly one place to start looking. My understanding is that the firewall configurations for most distros will pass through traffic on loopback just fine, if this isn't the case, then please feel free to contribute in this forum. thanks, BMS From bms at incunabulum.net Sat Aug 29 04:20:47 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Sat, 29 Aug 2009 12:20:47 +0100 Subject: [Xorp-users] xorpsh crash. is there any solution? In-Reply-To: <4A940A23.2070009@candelatech.com> References: <20090824080043.56120@gmx.net> <4A92AE23.3010805@candelatech.com> <4A940A23.2070009@candelatech.com> Message-ID: <4A990F0F.5030401@incunabulum.net> Ben Greear wrote: > ... > I don't have pre-compiled packages for debian, however. The official > xorp tree opened up yesterday > too, but I haven't had a chance to look at it. > I've contacted you off-list about what would be needed to generate binary RPMs using SCons. There is support for ipkg generation in SCons, but not deb (last time I looked). It would be very useful to contribute .deb generation to SCons itself, and I am sure they would very much appreciate that contribution too. Given that ipkg support already exists, I imagine this wouldn't be a difficult task for someone already familiar with Python as a scripting language, and Debian derived systems as a platform. From naresh_raga at yahoo.co.in Sun Aug 30 12:13:21 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Mon, 31 Aug 2009 00:43:21 +0530 (IST) Subject: [Xorp-users] Error:XrlRouter Failed.No Finder?while running ./xorp_rtrmgr In-Reply-To: <4A97BC9A.20302@incunabulum.net> Message-ID: <604159.11858.qm@web94811.mail.in2.yahoo.com> Hi Bruce >You should verify that xorp_rtrmgr is able to start its internal >Finder, and is listening on port 19999 (the default TCP listen port >for the XORP Finder IPC broker) when you start the process. Can you suggest me how to verify that xorp_rtrmgr is able to start its internal Finder or not? I have found an interesting phenomenon .I have deleted xrl_router.cc in libxipc folder and after that I ran ./xorp_rtrmgr ,even then I ran into same error: [ERROR xorp_rtrmgr:4671 XRL +634 xrl_router.cc wait_until_xrl_router_is_ready] ?XrlRouter failed. No Finder? What could be the problem?I have also tried to comment the code of wait_until_router_ready and then ran xorp_rtrmgr.It also resulted in the same error. ? >My suggestion would be: to focus on verifying XORP 1.7-WIP from >public SVN sources works OK, natively on the Debian derived >systems, before attempting cross-compilation. >Fixes/modifications WILL be needed to the new SCons build >system, and we'd really appreciate your help in making this >happen. Sure Bruce,I will help you.Can you provide the link where I can get XORP-1.7 SVN source. Thanks, Naresh Love Cricket? Check out live scores, photos, video highlights and more. Click here http://cricket.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090831/a77b7d22/attachment.html From bms at incunabulum.net Mon Aug 31 04:36:30 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 31 Aug 2009 12:36:30 +0100 Subject: [Xorp-users] Error:XrlRouter Failed.No Finder?while running ./xorp_rtrmgr In-Reply-To: <604159.11858.qm@web94811.mail.in2.yahoo.com> References: <604159.11858.qm@web94811.mail.in2.yahoo.com> Message-ID: <4A9BB5BE.2090600@incunabulum.net> naresh raga wrote: > > > Sure Bruce,I will help you.Can you provide the link where I can > get XORP-1.7 SVN source. > http://www.xorp.org/cvs.html From bms at incunabulum.net Mon Aug 31 05:36:59 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 31 Aug 2009 13:36:59 +0100 Subject: [Xorp-users] Progress in Xorp development? In-Reply-To: References: Message-ID: <4A9BC3EB.7090309@incunabulum.net> Hi Christian, Public SVN reopened last week: http://www.xorp.org/cvs.html Christian Svensson wrote: > Hello. > > I was browsing the CVS code to look at what work is being done for 1.7 > / 2.0. I was very surprised to see that no real code has been > committed to CVS since 2008. We'd greatly appreciate feedback from users on the current SVN code, before a 1.7-RC can be cut. What we're really looking for is for users to be involved in this process more than was the case before. The most wide-ranging changes in public SVN are: the move to shared libraries, various size optimizations for the XRL code, and the move to the SCons build system, which mostly came from JT Conklin's efforts in the XORP, Inc. corporate branch. Since moving to SourceForge as the main rendezvous point for developers, we have access to their Trac and Wiki facilities. So we would really welcome contributions of HOWTOs, procedures, known issues and so on in these forums. Whilst XORP is technically high calibre code, we want this to be more accessible to users in the open source world. Unfortunately, we don't have time or resources to track/build/maintain this across this wide spectrum, so an element of 'self service' is needed, as is the case with any open source project. thanks again, BMS From bms at incunabulum.net Mon Aug 31 05:43:35 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 31 Aug 2009 13:43:35 +0100 Subject: [Xorp-users] problem xorp compiling on fc8 In-Reply-To: <249ccfe90902080922ga91e05di7b1e775c6da27c1@mail.gmail.com> References: <249ccfe90902080922ga91e05di7b1e775c6da27c1@mail.gmail.com> Message-ID: <4A9BC577.4030300@incunabulum.net> Aleksandar Cvjetic wrote: > Hello, > > I'm trying to compile XORP into FC8 following procedure on xorp.org > but have some problem. Here is the list of files > under top level xorp directory: Please try the most recent public SVN code which is known to build on Fedora 11:- http://www.xorp.org/cvs.html thanks, BMS From bms at incunabulum.net Mon Aug 31 05:44:56 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 31 Aug 2009 13:44:56 +0100 Subject: [Xorp-users] xorp architecture In-Reply-To: References: Message-ID: <4A9BC5C8.8070306@incunabulum.net> bhavin81 at iitb.ac.in wrote: > Hello All, > > I need to modify pim-sm implementation in xorp. I have gone > through the code of pim-sm moduel of xorp. I need to modify such > that user can specify some choice L,M or S in its IGMP message send > to router. (which means i also need to modify igmp at user side so > that it gives above three chices). The config files provided by user > in xorp and their interface seems to be problem for me. > Please refer to the xorp-hackers@ list, where issues of coupling between the MFC, MRT, IGMP and PIM-SM processes were discussed some months ago in May. You may need to search the archives to find this thread: vif indeces. Archives here: http://mailman.icsi.berkeley.edu/pipermail/xorp-hackers/ From rtruitt at hatterasnetworks.com Mon Aug 31 06:43:05 2009 From: rtruitt at hatterasnetworks.com (Roger Truitt) Date: Mon, 31 Aug 2009 09:43:05 -0400 Subject: [Xorp-users] Newbie struggling with Multicast routing Message-ID: <467C77F6373BDE4BB16A3E8A62C03955054C3BAA@Exchserv.hatteras.com> I'm a newbie with limited Linux skills struggling to get a simple multicast setup working. (I know you hear this too frequently). I have a simple single router network with a VLC server and VLC client: Eth2 Eth 1 VLC client ------------------------------- Xorp router ------------------------------------------VLC server 10.20.20.5 10.20.20.20 10.10.10.10 10.10.10.1 I have xorp compiled on CentOS 5: [root at st-linux1 /]# uname -r 2.6.18-128.4.1.el5xen I believe CentOS was compiled with multicast (do not know how to check other than the ifconfig command, see below). Using tcpdump I've verified that the video stream packets are getting to interface Eth1 but are not getting forwarded to Eth2. It is probably a very simple configuration problem but I have not been able to figure it out. I'm very thankful to any assistance to can provide. Here's my xorp config and output from various commands: [root at st-linux1 rtrmgr]# cat config.boot /* $XORP: xorp/rtrmgr/config/multicast4.boot,v 1.1 2007/08/29 06:49:43 pavlin Exp $ */ interfaces { interface eth1 { disable: false vif eth1 { address 10.10.10.10 { prefix-length: 24 broadcast: 10.10.10.255 disable: false } } } interface eth2 { disable: false vif eth2 { address 10.20.20.20 { prefix-length: 24 disable: false } } } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea4 { interface eth1 { vif eth1 { disable: false } } interface eth2 { vif eth2 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } traceoptions { flag all { disable: false } } } } protocols { igmp { interface eth1 { vif eth1 { disable: false } } interface eth2 { vif eth2 { disable: false } } traceoptions { flag all { disable: false } } } } /* protocols { static { mrib-route 10.30.0.0/16 { next-hop: 10.10.10.20 } } } */ protocols { pimsm4 { interface eth1 { vif eth1 { disable: false } } interface eth2 { vif eth2 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } /* Note: static-rps and bootstrap should not be mixed */ static-rps { rp 10.10.10.10 { group-prefix 224.0.0.0/4 { } } } /* bootstrap { disable: false cand-bsr { scope-zone 224.0.0.0/4 { cand-bsr-by-vif-name: "eth1" } } cand-rp { group-prefix 224.0.0.0/4 { cand-rp-by-vif-name: "eth1" } } } */ switch-to-spt-threshold { /* approx. 1K bytes/s (10Kbps) threshold */ disable: false interval: 100 bytes: 102400 } /* traceoptions { flag all { disable: false } } */ } } protocols { fib2mrib { disable: false } } [root at st-linux1 rtrmgr]# ********************************************** xorp at st-linux1.hatteras.com> show route table ipv4 multicast fib2mrib 10.10.10.0/24 [fib2mrib(254)/65535] > to 0.0.0.0 via eth1/eth1 10.20.20.0/24 [fib2mrib(254)/65535] > to 0.0.0.0 via eth2/eth2 xorp at st-linux1.hatteras.com> show pim join Group Source RP Flags 239.1.1.1 0.0.0.0 10.10.10.10 WC Upstream interface (RP): register_vif Upstream MRIB next hop (RP): UNKNOWN Upstream RPF'(*,G): UNKNOWN Upstream state: Joined Join timer: 49 Local receiver include WC: .O. Joins RP: ... Joins WC: ... Join state: ... Prune state: ... Prune pending state: ... I am assert winner state: ... I am assert loser state: ... Assert winner WC: ... Assert lost WC: ... Assert tracking WC: .OO Could assert WC: .O. I am DR: OOO Immediate olist RP: ... Immediate olist WC: .O. Inherited olist SG: .O. Inherited olist SG_RPT: .O. PIM include WC: .O. 239.1.1.1 10.10.10.1 10.10.10.10 SG SPT DirectlyConnectedS Upstream interface (S): eth1 Upstream interface (RP): register_vif Upstream MRIB next hop (RP): UNKNOWN Upstream MRIB next hop (S): UNKNOWN Upstream RPF'(S,G): UNKNOWN Upstream state: Joined Register state: RegisterNoinfo RegisterNotCouldRegister Join timer: 54 KAT(S,G) running: true Local receiver include WC: .O. Local receiver include SG: ... Local receiver exclude SG: ... Joins RP: ... Joins WC: ... Joins SG: ... Join state: ... Prune state: ... Prune pending state: ... I am assert winner state: ... I am assert loser state: ... Assert winner WC: ... Assert winner SG: ... Assert lost WC: ... Assert lost SG: ... Assert lost SG_RPT: ... Assert tracking SG: OO. Could assert WC: .O. Could assert SG: .O. I am DR: OOO Immediate olist RP: ... Immediate olist WC: .O. Immediate olist SG: ... Inherited olist SG: .O. Inherited olist SG_RPT: .O. PIM include WC: .O. PIM include SG: ... PIM exclude SG: ... --More-- (END) xorp at st-linux1.hatteras.com> show pim bootstrap Active zones: BSR Pri LocalAddress Pri State Timeout SZTimeout Expiring zones: BSR Pri LocalAddress Pri State Timeout SZTimeout Configured zones: BSR Pri LocalAddress Pri State Timeout SZTimeout xorp at st-linux1.hatteras.com> show pim interface Interface State Mode V PIMstate Priority DRaddr Neighbors eth1 UP Sparse 2 DR 1 10.10.10.10 0 eth2 UP Sparse 2 DR 1 10.20.20.20 0 register_vif UP Sparse 2 DR 1 10.10.10.10 0 xorp at st-linux1.hatteras.com> show pim mfc Group Source RP 239.1.1.1 10.10.10.1 10.10.10.10 Incoming interface : eth1 Outgoing interfaces: .O. xorp at st-linux1.hatteras.com> show pim mrib DestPrefix NextHopRouter VifName VifIndex MetricPref Metric 10.10.10.0/24 10.10.10.10 eth1 0 0 0 10.20.20.0/24 10.20.20.20 eth2 1 0 0 xorp at st-linux1.hatteras.com> xorp at st-linux1.hatteras.com> show igmp group Interface Group Source LastReported Timeout V State eth1 224.0.0.2 0.0.0.0 10.10.10.10 257 2 E eth1 224.0.0.13 0.0.0.0 10.10.10.10 136 2 E eth1 224.0.0.22 0.0.0.0 10.10.10.10 258 2 E eth1 224.0.0.251 0.0.0.0 10.10.10.1 259 2 E eth2 224.0.0.2 0.0.0.0 10.20.20.20 259 2 E eth2 224.0.0.13 0.0.0.0 10.20.20.20 139 2 E eth2 224.0.0.22 0.0.0.0 10.20.20.20 257 2 E eth2 224.0.0.251 0.0.0.0 10.20.20.20 134 2 E eth2 239.1.1.1 0.0.0.0 10.20.20.5 226 2 E xorp at st-linux1.hatteras.com> show mfea dataflow Group Source 239.1.1.1 10.10.10.1 Measured(Start|Packets|Bytes) Type Thresh(Interval|Packets|Bytes) Remain 227542.856781|10419|? <= 210.0|0|? 33.253729 xorp at st-linux1.hatteras.com> [root at st-linux1 config]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.20.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 10.10.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 192.168.16.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 224.0.0.0 0.0.0.0 240.0.0.0 U 0 0 0 eth2 0.0.0.0 192.168.23.254 0.0.0.0 UG 0 0 0 eth0 [root at st-linux1 config]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:08:74:92:E3:4D inet addr:192.168.16.111 Bcast:192.168.23.255 Mask:255.255.248.0 inet6 addr: fe80::208:74ff:fe92:e34d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:272641 errors:0 dropped:0 overruns:0 frame:0 TX packets:80039 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:18853793 (17.9 MiB) TX bytes:18254918 (17.4 MiB) eth1 Link encap:Ethernet HWaddr 00:0E:0C:83:12:C7 inet addr:10.10.10.10 Bcast:10.10.10.255 Mask:255.255.255.0 inet6 addr: fe80::20e:cff:fe83:12c7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:55473 errors:0 dropped:0 overruns:0 frame:0 TX packets:16321 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:71038916 (67.7 MiB) TX bytes:927499 (905.7 KiB) Base address:0xdcc0 Memory:ff6e0000-ff700000 eth2 Link encap:Ethernet HWaddr 00:04:2E:01:E1:9C inet addr:10.20.20.20 Bcast:10.20.20.255 Mask:255.255.255.0 inet6 addr: fe80::204:2eff:fe01:e19c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:301 errors:1 dropped:1 overruns:0 frame:0 TX packets:16861 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22428 (21.9 KiB) TX bytes:1149374 (1.0 MiB) Interrupt:18 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:21606334 errors:0 dropped:0 overruns:0 frame:0 TX packets:21606334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1610874289 (1.5 GiB) TX bytes:1610874289 (1.5 GiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:381938 errors:0 dropped:0 overruns:9 frame:0 TX packets:80176 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:25416172 (24.2 MiB) TX bytes:18315040 (17.4 MiB) Interrupt:20 Base address:0xec00 pimreg Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP RUNNING NOARP MTU:1472 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth4 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth5 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:80135 errors:0 dropped:0 overruns:0 frame:0 TX packets:272690 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:18269270 (17.4 MiB) TX bytes:18856825 (17.9 MiB) vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.4 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.5 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:51 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:10722 (10.4 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:220086 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11879215 (11.3 MiB) TX bytes:0 (0.0 b) [root at st-linux1 rtrmgr]# ./xorp_rtrmgr [ 2009/08/28 16:55:41 INFO xorp_rtrmgr:3764 RTRMGR +249 master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea, mfea4, rib, fib2mrib, igmp, pimsm4 [ 2009/08/28 16:55:41 INFO xorp_rtrmgr:3764 RTRMGR +101 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2009/08/28 16:55:43 INFO xorp_fea MFEA ] MFEA enabled [ 2009/08/28 16:55:43 INFO xorp_fea MFEA ] CLI enabled [ 2009/08/28 16:55:43 INFO xorp_fea MFEA ] CLI started [ 2009/08/28 16:55:43 INFO xorp_fea MFEA ] MFEA enabled [ 2009/08/28 16:55:43 INFO xorp_fea MFEA ] CLI enabled [ 2009/08/28 16:55:43 INFO xorp_fea MFEA ] CLI started [ 2009/08/28 16:55:43 INFO xorp_rtrmgr:3764 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) [ 2009/08/28 16:55:47 INFO xorp_rtrmgr:3764 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2009/08/28 16:55:53 INFO xorp_rtrmgr:3764 RTRMGR +101 module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea) [ 2009/08/28 16:55:53 INFO xorp_fea MFEA ] Interface added: Vif[eth1] pif_index: 3 vif_index: 0 addr: 10.10.10.10 subnet: 10.10.10.0/24 broadcast: 10.10.10.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/08/28 16:55:53 INFO xorp_fea MFEA ] Interface added: Vif[eth2] pif_index: 2 vif_index: 1 addr: 10.20.20.20 subnet: 10.20.20.0/24 broadcast: 10.20.20.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/08/28 16:55:53 INFO xorp_fea MFEA ] MFEA started [ 2009/08/28 16:55:53 INFO xorp_fea MFEA ] Interface enabled Vif[eth1] pif_index: 3 vif_index: 0 addr: 10.10.10.10 subnet: 10.10.10.0/24 broadcast: 10.10.10.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/08/28 16:55:53 INFO xorp_fea MFEA ] Interface started: Vif[eth1] pif_index: 3 vif_index: 0 addr: 10.10.10.10 subnet: 10.10.10.0/24 broadcast: 10.10.10.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/08/28 16:55:53 INFO xorp_fea MFEA ] Interface added: Vif[register_vif] pif_index: 3 vif_index: 2 addr: 10.10.10.10 subnet: 10.10.10.10/32 broadcast: 10.10.10.10 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 [ 2009/08/28 16:55:53 INFO xorp_fea MFEA ] Interface enabled Vif[eth2] pif_index: 2 vif_index: 1 addr: 10.20.20.20 subnet: 10.20.20.0/24 broadcast: 10.20.20.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/08/28 16:55:53 INFO xorp_fea MFEA ] Interface started: Vif[eth2] pif_index: 2 vif_index: 1 addr: 10.20.20.20 subnet: 10.20.20.0/24 broadcast: 10.20.20.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/08/28 16:55:53 INFO xorp_fea MFEA ] Interface enabled Vif[register_vif] pif_index: 3 vif_index: 2 addr: 10.10.10.10 subnet: 10.10.10.10/32 broadcast: 10.10.10.10 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/08/28 16:55:53 INFO xorp_fea MFEA ] Interface started: Vif[register_vif] pif_index: 3 vif_index: 2 addr: 10.10.10.10 subnet: 10.10.10.10/32 broadcast: 10.10.10.10 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/08/28 16:55:53 INFO xorp_rtrmgr:3764 RTRMGR +101 module_manager.cc execute ] Executing module: rib (rib/xorp_rib) [ 2009/08/28 16:55:55 INFO xorp_rtrmgr:3764 RTRMGR +101 module_manager.cc execute ] Executing module: fib2mrib (fib2mrib/xorp_fib2mrib) [ 2009/08/28 16:55:57 INFO xorp_rtrmgr:3764 RTRMGR +101 module_manager.cc execute ] Executing module: igmp (mld6igmp/xorp_igmp) [ 2009/08/28 16:55:57 WARNING xorp_rtrmgr:3764 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "IGMP" does not exist or is not enabled. [ 2009/08/28 16:55:57 INFO xorp_igmp MLD6IGMP ] Protocol enabled [ 2009/08/28 16:55:57 INFO xorp_igmp MLD6IGMP ] CLI enabled [ 2009/08/28 16:55:57 INFO xorp_igmp MLD6IGMP ] CLI started [ 2009/08/28 16:55:58 INFO xorp_igmp MLD6IGMP ] Protocol started [ 2009/08/28 16:55:58 INFO xorp_igmp MLD6IGMP ] Interface added: Vif[eth1] pif_index: 3 vif_index: 0 addr: 10.10.10.10 subnet: 10.10.10.0/24 broadcast: 10.10.10.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/08/28 16:55:58 INFO xorp_igmp MLD6IGMP ] Interface added: Vif[eth2] pif_index: 2 vif_index: 1 addr: 10.20.20.20 subnet: 10.20.20.0/24 broadcast: 10.20.20.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/08/28 16:55:59 INFO xorp_igmp MLD6IGMP ] Interface enabled: Vif[eth1] pif_index: 3 vif_index: 0 addr: 10.10.10.10 subnet: 10.10.10.0/24 broadcast: 10.10.10.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/08/28 16:55:59 INFO xorp_igmp MLD6IGMP ] Interface started: Vif[eth1] pif_index: 3 vif_index: 0 addr: 10.10.10.10 subnet: 10.10.10.0/24 broadcast: 10.10.10.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/08/28 16:55:59 INFO xorp_igmp MLD6IGMP ] Interface enabled: Vif[eth2] pif_index: 2 vif_index: 1 addr: 10.20.20.20 subnet: 10.20.20.0/24 broadcast: 10.20.20.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/08/28 16:55:59 INFO xorp_igmp MLD6IGMP ] Interface started: Vif[eth2] pif_index: 2 vif_index: 1 addr: 10.20.20.20 subnet: 10.20.20.0/24 broadcast: 10.20.20.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/08/28 16:55:59 INFO xorp_rtrmgr:3764 RTRMGR +101 module_manager.cc execute ] Executing module: pimsm4 (pim/xorp_pimsm4) [ 2009/08/28 16:55:59 WARNING xorp_rtrmgr:3764 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "PIMSM_4" does not exist or is not enabled. [ 2009/08/28 16:55:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.22 on vif eth1 [ 2009/08/28 16:55:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.10.10.10 to 224.0.0.1 on vif eth1 [ 2009/08/28 16:55:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.20.20.20 to 224.0.0.1 on vif eth2 [ 2009/08/28 16:56:00 INFO xorp_pimsm4 PIM ] Protocol enabled [ 2009/08/28 16:56:00 INFO xorp_pimsm4 PIM ] CLI enabled [ 2009/08/28 16:56:00 INFO xorp_pimsm4 PIM ] CLI started [ 2009/08/28 16:56:00 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.22 on vif eth1 [ 2009/08/28 16:56:00 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.22) on vif eth1 [ 2009/08/28 16:56:00 INFO xorp_pimsm4 PIM ] Protocol started [ 2009/08/28 16:56:00 INFO xorp_pimsm4 PIM ] Interface added: Vif[eth1] pif_index: 3 vif_index: 0 addr: 10.10.10.10 subnet: 10.10.10.0/24 broadcast: 10.10.10.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/08/28 16:56:00 INFO xorp_pimsm4 PIM ] Interface added: Vif[eth2] pif_index: 2 vif_index: 1 addr: 10.20.20.20 subnet: 10.20.20.0/24 broadcast: 10.20.20.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/08/28 16:56:00 INFO xorp_pimsm4 PIM ] Interface added: Vif[register_vif] pif_index: 0 vif_index: 2 addr: 10.10.10.10 subnet: 10.10.10.10/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 [ 2009/08/28 16:56:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.5 to 239.1.1.1 on vif eth2 [ 2009/08/28 16:56:01 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 239.1.1.1) on vif eth2 [ 2009/08/28 16:56:01 INFO xorp_pimsm4 PIM ] Interface enabled: Vif[eth1] pif_index: 3 vif_index: 0 addr: 10.10.10.10 subnet: 10.10.10.0/24 broadcast: 10.10.10.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/08/28 16:56:01 INFO xorp_pimsm4 PIM ] Interface started: Vif[eth1] pif_index: 3 vif_index: 0 addr: 10.10.10.10 subnet: 10.10.10.0/24 broadcast: 10.10.10.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/08/28 16:56:01 INFO xorp_pimsm4 PIM ] Interface enabled: Vif[eth2] pif_index: 2 vif_index: 1 addr: 10.20.20.20 subnet: 10.20.20.0/24 broadcast: 10.20.20.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/08/28 16:56:01 INFO xorp_pimsm4 PIM ] Interface started: Vif[eth2] pif_index: 2 vif_index: 1 addr: 10.20.20.20 subnet: 10.20.20.0/24 broadcast: 10.20.20.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/08/28 16:56:01 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 239.1.1.1: not found [ 2009/08/28 16:56:01 INFO xorp_pimsm4 PIM ] Interface enabled: Vif[register_vif] pif_index: 0 vif_index: 2 addr: 10.10.10.10 subnet: 10.10.10.10/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/08/28 16:56:01 INFO xorp_pimsm4 PIM ] Interface started: Vif[register_vif] pif_index: 0 vif_index: 2 addr: 10.10.10.10 subnet: 10.10.10.10/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/08/28 16:56:01 INFO xorp_rtrmgr:3764 RTRMGR +2233 task.cc run_task ] No more tasks to run [ 2009/08/28 16:56:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.13 on vif eth1 [ 2009/08/28 16:56:01 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.13) on vif eth1 [ 2009/08/28 16:56:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.13 on vif eth2 [ 2009/08/28 16:56:01 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.13) on vif eth2 [ 2009/08/28 16:56:02 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.2 on vif eth2 [ 2009/08/28 16:56:02 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.2) on vif eth2 [ 2009/08/28 16:56:02 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.13 on vif eth1 [ 2009/08/28 16:56:04 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.13 on vif eth1 [ 2009/08/28 16:56:04 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.22 on vif eth2 [ 2009/08/28 16:56:04 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.22) on vif eth2 [ 2009/08/28 16:56:05 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.251 on vif eth1 [ 2009/08/28 16:56:05 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.251) on vif eth1 [ 2009/08/28 16:56:05 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.251 on vif eth2 [ 2009/08/28 16:56:05 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.251) on vif eth2 [ 2009/08/28 16:56:07 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.13 on vif eth2 [ 2009/08/28 16:56:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.2 on vif eth1 [ 2009/08/28 16:56:09 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.2) on vif eth1 [ 2009/08/28 16:56:16 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.13 on vif eth2 [ 2009/08/28 16:56:30 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 10.10.10.10 to 224.0.0.1 [ 2009/08/28 16:56:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.10.10.10 to 224.0.0.1 on vif eth1 [ 2009/08/28 16:56:30 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 10.20.20.20 to 224.0.0.1 [ 2009/08/28 16:56:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.20.20.20 to 224.0.0.1 on vif eth2 [ 2009/08/28 16:56:31 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.2 on vif eth2 [ 2009/08/28 16:56:32 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.251 on vif eth1 [ 2009/08/28 16:56:33 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.2 on vif eth1 [ 2009/08/28 16:56:34 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.5 to 239.1.1.1 on vif eth2 [ 2009/08/28 16:56:34 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.13 on vif eth1 [ 2009/08/28 16:56:34 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.22 on vif eth1 [ 2009/08/28 16:56:35 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.22 on vif eth2 [ 2009/08/28 16:56:35 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.13 on vif eth2 [ 2009/08/28 16:56:36 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.251 on vif eth2 [ 2009/08/28 16:56:48 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 0 src = 10.10.10.1 dst = 239.1.1.1 [ 2009/08/28 16:56:48 TRACE xorp_fea MFEA ] Add MFC entry: (10.10.10.1, 239.1.1.1) iif = 0 olist = .O. [ 2009/08/28 16:57:13 TRACE xorp_fea MFEA ] RX dataflow message: src = 10.10.10.1 dst = 239.1.1.1 [ 2009/08/28 16:58:34 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 10.10.10.10 to 224.0.0.1 [ 2009/08/28 16:58:34 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.10.10.10 to 224.0.0.1 on vif eth1 [ 2009/08/28 16:58:34 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 10.20.20.20 to 224.0.0.1 [ 2009/08/28 16:58:34 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.20.20.20 to 224.0.0.1 on vif eth2 [ 2009/08/28 16:58:34 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.22 on vif eth1 [ 2009/08/28 16:58:35 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.251 on vif eth1 [ 2009/08/28 16:58:36 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.251 on vif eth2 [ 2009/08/28 16:58:37 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.13 on vif eth2 [ 2009/08/28 16:58:37 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.2 on vif eth1 [ 2009/08/28 16:58:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.22 on vif eth2 [ 2009/08/28 16:58:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.10.10 to 224.0.0.13 on vif eth1 [ 2009/08/28 16:58:42 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.5 to 239.1.1.1 on vif eth2 [ 2009/08/28 16:58:44 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.20.20.20 to 224.0.0.2 on vif eth2 [root at st-linux1 ~]# tcpdump -i eth1 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes 16:57:43.456643 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.468602 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.481594 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.494584 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.506579 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.519820 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.532563 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.545560 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.560550 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.575541 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.589535 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.609023 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.619766 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.634508 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.649500 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.664740 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.679482 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.694471 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.709717 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.724706 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.738702 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.754689 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.769680 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.784673 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.799669 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.814663 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.830649 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.845642 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.860882 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.875622 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.891616 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.906607 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.921595 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.936591 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.952578 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.969569 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:43.985564 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.002805 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.018539 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.035535 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.051525 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.068766 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.084501 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.103245 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.117482 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.134479 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.148474 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.161713 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.175452 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.188449 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.202194 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.214682 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.227424 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.241419 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.254407 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.267654 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.280647 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.293637 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.307630 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.320623 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.333612 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.346610 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.359599 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.372605 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.385586 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.399575 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.417067 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.425812 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.438552 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.451549 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 16:57:44.464540 IP 10.10.10.1.60981 > 239.1.1.1.search-agent: UDP, length 1316 [root at st-linux1 config]# tcpdump -i eth2 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes 09:04:07.918196 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:04:27.719643 IP 10.20.20.20 > ALL-SYSTEMS.MCAST.NET: igmp query v2 09:04:28.673543 IP 10.20.20.20 > IGMP.MCAST.NET: igmp v2 report IGMP.MCAST.NET 09:04:29.688037 IP 10.20.20.5 > 239.1.1.1: igmp v2 report 239.1.1.1 09:04:32.873587 IP 10.20.20.20 > ALL-ROUTERS.MCAST.NET: igmp v2 report ALL-ROUTERS.MCAST.NET 09:04:34.585607 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: igmp v2 report PIM-ROUTERS.MCAST.NET 09:04:35.317614 IP 10.20.20.20 > 224.0.0.251: igmp v2 report 224.0.0.251 09:04:37.918155 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:04:38.729978 IP 10.20.20.5.cnhrp > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 2416405484:2416405484(0) win 16384 09:04:41.706041 IP 10.20.20.5.cnhrp > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 2416405484:2416405484(0) win 16384 09:04:47.714997 IP 10.20.20.5.cnhrp > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 2416405484:2416405484(0) win 16384 09:05:07.918437 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:05:37.918791 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:05:38.820128 IP 10.20.20.5.tftp-mcast > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 70902040:70902040(0) win 16384 09:05:41.796187 IP 10.20.20.5.tftp-mcast > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 70902040:70902040(0) win 16384 09:05:47.805139 IP 10.20.20.5.tftp-mcast > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 70902040:70902040(0) win 16384 09:06:07.919128 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:06:32.720980 IP 10.20.20.20 > ALL-SYSTEMS.MCAST.NET: igmp query v2 09:06:36.311003 IP 10.20.20.20 > 224.0.0.251: igmp v2 report 224.0.0.251 09:06:37.919518 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:06:38.380967 IP 10.20.20.5 > 239.1.1.1: igmp v2 report 239.1.1.1 09:06:38.910266 IP 10.20.20.5.1759 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 4198292403:4198292403(0) win 16384 09:06:39.351029 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: igmp v2 report PIM-ROUTERS.MCAST.NET 09:06:41.095057 IP 10.20.20.20 > ALL-ROUTERS.MCAST.NET: igmp v2 report ALL-ROUTERS.MCAST.NET 09:06:41.279054 IP 10.20.20.20 > IGMP.MCAST.NET: igmp v2 report IGMP.MCAST.NET 09:06:41.886309 IP 10.20.20.5.1759 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 4198292403:4198292403(0) win 16384 09:06:47.895259 IP 10.20.20.5.1759 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 4198292403:4198292403(0) win 16384 09:07:07.919828 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:07:37.920189 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:07:39.000397 arp who-has 10.20.20.20 tell 10.20.20.5 09:07:39.000429 arp reply 10.20.20.20 is-at 00:04:2e:01:e1:9c (oui Unknown) 09:07:39.000545 IP 10.20.20.5.www-ldap-gw > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 1673441517:1673441517(0) win 16384 09:07:41.976406 IP 10.20.20.5.www-ldap-gw > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 1673441517:1673441517(0) win 16384 09:07:47.985358 IP 10.20.20.5.www-ldap-gw > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 1673441517:1673441517(0) win 16384 09:08:07.920550 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:08:35.597011 IP 10.20.20.5.netbios-dgm > 10.20.20.255.netbios-dgm: NBT UDP PACKET(138) 09:08:37.722648 IP 10.20.20.20 > ALL-SYSTEMS.MCAST.NET: igmp query v2 09:08:37.920841 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:08:39.090467 IP 10.20.20.5.cft-0 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 89842927:89842927(0) win 16384 09:08:40.124421 IP 10.20.20.20 > ALL-ROUTERS.MCAST.NET: igmp v2 report ALL-ROUTERS.MCAST.NET 09:08:41.072431 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: igmp v2 report PIM-ROUTERS.MCAST.NET 09:08:42.066550 IP 10.20.20.5.cft-0 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 89842927:89842927(0) win 16384 09:08:45.571705 IP 10.20.20.5 > 239.1.1.1: igmp v2 report 239.1.1.1 09:08:45.844480 IP 10.20.20.20 > 224.0.0.251: igmp v2 report 224.0.0.251 09:08:46.864498 IP 10.20.20.20 > IGMP.MCAST.NET: igmp v2 report IGMP.MCAST.NET 09:08:48.075502 IP 10.20.20.5.cft-0 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 89842927:89842927(0) win 16384 09:09:07.921183 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:09:37.921534 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:09:39.190625 IP 10.20.20.5.cft-1 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 2319511939:2319511939(0) win 16384 09:09:42.156670 IP 10.20.20.5.cft-1 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 2319511939:2319511939(0) win 16384 09:09:48.165625 IP 10.20.20.5.cft-1 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 2319511939:2319511939(0) win 16384 09:10:07.921879 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:10:37.922263 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34 09:10:39.270716 IP 10.20.20.5.cft-2 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 1468510659:1468510659(0) win 16384 09:10:42.246791 IP 10.20.20.5.cft-2 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 1468510659:1468510659(0) win 16384 09:10:42.724141 IP 10.20.20.20 > ALL-SYSTEMS.MCAST.NET: igmp query v2 09:10:42.853815 IP 10.20.20.20 > IGMP.MCAST.NET: igmp v2 report IGMP.MCAST.NET 09:10:45.709855 IP 10.20.20.20 > ALL-ROUTERS.MCAST.NET: igmp v2 report ALL-ROUTERS.MCAST.NET 09:10:46.252783 IP 10.20.20.5 > 239.1.1.1: igmp v2 report 239.1.1.1 09:10:48.255746 IP 10.20.20.5.cft-2 > rrcs-96-10-11-4.se.biz.rr.com.dtpt: S 1468510659:1468510659(0) win 16384 09:10:48.697891 IP 10.20.20.20 > PIM-ROUTERS.MCAST.NET: igmp v2 report PIM-ROUTERS.MCAST.NET 09:10:52.581929 IP 10.20.20.20 > 224.0.0.251: igmp v2 report 224.0.0.251 _____________________________________________________________________ This email message is for the sole use of the intended recipient(s) and may contain confidential and proprietary information of Hatteras Networks, Inc. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this email message, please contact the sender by reply email and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's Email System Administrator. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090831/61a6f9f6/attachment-0001.html From naresh_raga at yahoo.co.in Mon Aug 31 12:30:45 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Tue, 1 Sep 2009 01:00:45 +0530 (IST) Subject: [Xorp-users] Error:XrlRouter Failed.No Finder?while running ./xorp_rtrmgr In-Reply-To: <4A9BB5BE.2090600@incunabulum.net> Message-ID: <701838.69996.qm@web94803.mail.in2.yahoo.com> Hi Bruce, This is my complete error report generated when i executed xorp_rtrmgr.I have made sure my 127.0.0.1 is up and port 19999 is free.But even then it results in the same error. [WARNING xorp_rtrmgr:10336 LIBXORP +468 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 52.210000seconds. [WARNING xorp_rtrmgr:10336 LIBXORP +468 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 22.250000seconds. [ERROR xorp_rtrmgr:10336 XRL +634 xrl_router.cc wait_until_xrl_router_is_ready ] XrlRouter Failed.No Finder? I am unable to understand the last error message.Actually its indicating that error has been generated by xrl_router.cc file from XRL folder.But when I searched for xrl_router.cc in xrl folder,there is no such file.It actually lies in libxipc folder. I have put warning messages also so that it can give you complete idea on the problem. I think your friend pavlin has got resolved the problem in past.Both of you can help me out of this problem. Regards, Naresh. IIT DELHI. India See the Web's breaking stories, chosen by people like you. Check out Yahoo! Buzz. http://in.buzz.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090901/5b0460c4/attachment.html