From dscher at mitre.org Fri Feb 6 12:56:41 2009 From: dscher at mitre.org (Scher, Dave) Date: Fri, 6 Feb 2009 15:56:41 -0500 Subject: [Xorp-users] BGP Proxy for FEA Message-ID: <40B2D5567C6BFC489F07920CA4B9811901991E6442@IMCMBX1.MITRE.ORG> I was wondering the status of the XORP BGP proxy work for the FEA module. Has this been completed so that all routing protocols can be run in a distributed XORP setup? Thanks. Dave Scher -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090206/41f2da0f/attachment.html From aleksandar.cvjetic at gmail.com Sun Feb 8 09:22:47 2009 From: aleksandar.cvjetic at gmail.com (Aleksandar Cvjetic) Date: Sun, 8 Feb 2009 12:22:47 -0500 Subject: [Xorp-users] problem xorp compiling on fc8 Message-ID: <249ccfe90902080922ga91e05di7b1e775c6da27c1@mail.gmail.com> 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: [root at dhcppc2 xorp-1.6]# ls autom4te.cache contrib libfeaclient MakefileRootCheck.am rip bgp devnotes libproto MakefileRootCheck.in rtrmgr bootstrap docs libtool mibs static_routes BUGS ERRATA libxipc mld6igmp tests BUILD_NOTES etc libxorp mrt TODO cli examples LICENSE ospf utils config fea LICENSE.gpl pim VERSION config.h.in fib2mrib LICENSE.lgpl policy vrrp config.log Jamfile LICENSE.other README xrl configure Jamrules.in Makefile.am RELEASE_NOTES configure.in libcomm Makefile.in rib After typing ./configure I could see no error message but after typing gmake it seems that no makefile exist: [root at dhcppc2 xorp-1.6]# make make: *** No targets specified and no makefile found. Stop. Any advice for begginer? Thanks! p.s. I have downloaded gmake-3.81. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090208/d2e39d89/attachment.html From pavlin at ICSI.Berkeley.EDU Sun Feb 8 21:19:51 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Sun, 08 Feb 2009 21:19:51 -0800 Subject: [Xorp-users] problem xorp compiling on fc8 In-Reply-To: <249ccfe90902080922ga91e05di7b1e775c6da27c1@mail.gmail.com> References: <249ccfe90902080922ga91e05di7b1e775c6da27c1@mail.gmail.com> Message-ID: <200902090519.n195JpIS027190@fruitcake.ICSI.Berkeley.EDU> It appears something went wrong so ./configure didn't generate Makefile in the top-level directory. Please send the complete output of running ./configure even if there aren't any obvious errors. Pavlin 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: > > [root at dhcppc2 xorp-1.6]# ls > autom4te.cache contrib libfeaclient MakefileRootCheck.am rip > bgp devnotes libproto MakefileRootCheck.in rtrmgr > bootstrap docs libtool mibs > static_routes > BUGS ERRATA libxipc mld6igmp tests > BUILD_NOTES etc libxorp mrt TODO > cli examples LICENSE ospf utils > config fea LICENSE.gpl pim VERSION > config.h.in fib2mrib LICENSE.lgpl policy vrrp > config.log Jamfile LICENSE.other README xrl > configure Jamrules.in Makefile.am RELEASE_NOTES > configure.in libcomm Makefile.in rib > > After typing ./configure I could see no error message but after typing gmake > it seems that no makefile exist: > > [root at dhcppc2 xorp-1.6]# make > make: *** No targets specified and no makefile found. Stop. > > Any advice for begginer? Thanks! > p.s. I have downloaded gmake-3.81. > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From aleksandar.cvjetic at gmail.com Mon Feb 9 09:28:43 2009 From: aleksandar.cvjetic at gmail.com (Aleksandar Cvjetic) Date: Mon, 9 Feb 2009 12:28:43 -0500 Subject: [Xorp-users] problem xorp compiling on fc8 In-Reply-To: <200902090519.n195JpIS027190@fruitcake.ICSI.Berkeley.EDU> References: <249ccfe90902080922ga91e05di7b1e775c6da27c1@mail.gmail.com> <200902090519.n195JpIS027190@fruitcake.ICSI.Berkeley.EDU> Message-ID: <249ccfe90902090928g668a9379ycdab93ac1af2d903@mail.gmail.com> Hello, Below is complete output of ./configure command: [root at dhcppc2 xorp-1.6]# ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking how to recognize dependent libraries... pass_all checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for xlf90... no checking for f90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for xlf95... no checking for f95... no checking for fort... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for ftn... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... 98304 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... no checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking OpenSSL installation prefix... Could not find part of OpenSSL or one it's components in /usr /usr/local /usr/local/ssl /mingw /gnuwin32 /opt /usr/sfw Use --with-openssl=DIR to specify OpenSSL installation root. [root at dhcppc2 xorp-1.6]# Thanks a lot! On Mon, Feb 9, 2009 at 12:19 AM, Pavlin Radoslavov wrote: > It appears something went wrong so ./configure didn't generate > Makefile in the top-level directory. > Please send the complete output of running ./configure even if there > aren't any obvious errors. > > Pavlin > > 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: > > > > [root at dhcppc2 xorp-1.6]# ls > > autom4te.cache contrib libfeaclient MakefileRootCheck.am rip > > bgp devnotes libproto MakefileRootCheck.in rtrmgr > > bootstrap docs libtool mibs > > static_routes > > BUGS ERRATA libxipc mld6igmp tests > > BUILD_NOTES etc libxorp mrt TODO > > cli examples LICENSE ospf utils > > config fea LICENSE.gpl pim VERSION > > config.h.in fib2mrib LICENSE.lgpl policy vrrp > > config.log Jamfile LICENSE.other README xrl > > configure Jamrules.in Makefile.am RELEASE_NOTES > > configure.in libcomm Makefile.in rib > > > > After typing ./configure I could see no error message but after typing > gmake > > it seems that no makefile exist: > > > > [root at dhcppc2 xorp-1.6]# make > > make: *** No targets specified and no makefile found. Stop. > > > > Any advice for begginer? Thanks! > > p.s. I have downloaded gmake-3.81. > > _______________________________________________ > > Xorp-users mailing list > > Xorp-users at xorp.org > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090209/fa595fda/attachment.html From stegen at owns.com Mon Feb 9 17:38:28 2009 From: stegen at owns.com (Stegen Smith) Date: Mon, 09 Feb 2009 17:38:28 -0800 Subject: [Xorp-users] Question regarding xorp BGP Message-ID: <4990DA94.2050906@owns.com> Hello Group, It's been a while... had my head down with some other tasks for a few months there, but now get to return to the world of checking out xorp. Anyways... I've got a question, perhaps feature request, about xorp's bgp configuration/implementation. I've got a peer that I want to peer up with; however, they do some trickery which causes xorp_bgp to not want to form an adjacency. Here's the log snippet: [ 2009/02/09 17:08:56 INFO xorp_bgp BGP ] Sending: Notification Packet: UPDATE Message Error(3): Malformed AS_PATH(11) The configuration looks proper to me, and I'm able to get my openbsd systems able to connect using the 'enforce neighbor-as no' in openbgpd. So, I was wondering if this option is available to me, or if there's some trickery to make xorp_bgp to form an adjacency to a neighbor whose left most AS doesn't match its remote AS value? It doesn't seem that there is something like this in the manual, so I am asking the group. I hope I was clear enough, if not, please let me know and I'll try to provide more information. thanks! steen From hsegoy at gmail.com Tue Feb 10 03:21:41 2009 From: hsegoy at gmail.com (Yogesh Anyapanawar) Date: Tue, 10 Feb 2009 16:51:41 +0530 Subject: [Xorp-users] NAT Configurations on XORP Message-ID: <8360e6c80902100321t7f26e1efm19c4da17a944f24f@mail.gmail.com> Hi, I am looking for some sample configurations for setting up NAT rules. My requirement is fairly simple where I have different servers running different services in my management network and should be accessible from the public network. The router will also be configured as a firewall to accept only those requests that can be serviced in my management network. Comments/Samples will be greatly appreciated. Cheers, Yogesh -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090210/c25c8cfa/attachment.html From pavlin at ICSI.Berkeley.EDU Tue Feb 10 09:41:19 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Tue, 10 Feb 2009 09:41:19 -0800 Subject: [Xorp-users] problem xorp compiling on fc8 In-Reply-To: <249ccfe90902090928g668a9379ycdab93ac1af2d903@mail.gmail.com> References: <249ccfe90902080922ga91e05di7b1e775c6da27c1@mail.gmail.com> <200902090519.n195JpIS027190@fruitcake.ICSI.Berkeley.EDU> <249ccfe90902090928g668a9379ycdab93ac1af2d903@mail.gmail.com> Message-ID: <200902101741.n1AHfJvh002902@fruitcake.ICSI.Berkeley.EDU> The issue seems to be that you don't have OpenSSL installed (XORP requires both the library and the header files): > checking OpenSSL installation prefix... Could not find part of OpenSSL or > one it's components in /usr /usr/local /usr/local/ssl /mingw /gnuwin32 /opt > /usr/sfw > Use --with-openssl=DIR to specify OpenSSL installation root. To fix that you need to install the openssl-devel package (or the equivalent for your distro). If it is installed in a directory that is not in the above list, then use the --with-openssl=DIR option to ./configure. Regards, Pavlin Aleksandar Cvjetic wrote: > Hello, > > Below is complete output of ./configure command: > > [root at dhcppc2 xorp-1.6]# ./configure > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking target system type... i686-pc-linux-gnu > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking for style of include used by make... GNU > checking dependency style of gcc... gcc3 > checking how to run the C preprocessor... gcc -E > checking for g++... g++ > checking whether we are using the GNU C++ compiler... yes > checking whether g++ accepts -g... yes > checking dependency style of g++... gcc3 > checking how to run the C++ preprocessor... g++ -E > checking for a BSD-compatible install... /usr/bin/install -c > checking whether ln -s works... yes > checking for a sed that does not truncate output... /bin/sed > checking for grep that handles long lines and -e... /bin/grep > checking for egrep... /bin/grep -E > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for /usr/bin/ld option to reload object files... -r > checking for BSD-compatible nm... /usr/bin/nm -B > checking how to recognize dependent libraries... pass_all > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking dlfcn.h usability... yes > checking dlfcn.h presence... yes > checking for dlfcn.h... yes > checking how to run the C++ preprocessor... g++ -E > checking for g77... no > checking for xlf... no > checking for f77... no > checking for frt... no > checking for pgf77... no > checking for cf77... no > checking for fort77... no > checking for fl32... no > checking for af77... no > checking for xlf90... no > checking for f90... no > checking for pgf90... no > checking for pghpf... no > checking for epcf90... no > checking for gfortran... no > checking for g95... no > checking for xlf95... no > checking for f95... no > checking for fort... no > checking for ifort... no > checking for ifc... no > checking for efc... no > checking for pgf95... no > checking for lf95... no > checking for ftn... no > checking whether we are using the GNU Fortran 77 compiler... no > checking whether accepts -g... no > checking the maximum length of command line arguments... 98304 > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for objdir... .libs > checking for ar... ar > checking for ranlib... ranlib > checking for strip... strip > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC > checking if gcc PIC flag -fPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking whether the gcc linker (/usr/bin/ld) supports shared libraries... > yes > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... no > checking whether to build static libraries... yes > configure: creating libtool > appending configuration tag "CXX" to libtool > checking for ld used by g++... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking whether the g++ linker (/usr/bin/ld) supports shared libraries... > yes > checking for g++ option to produce PIC... -fPIC > checking if g++ PIC flag -fPIC works... yes > checking if g++ static flag -static works... yes > checking if g++ supports -c -o file.o... yes > checking whether the g++ linker (/usr/bin/ld) supports shared libraries... > yes > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > appending configuration tag "F77" to libtool > checking OpenSSL installation prefix... Could not find part of OpenSSL or > one it's components in /usr /usr/local /usr/local/ssl /mingw /gnuwin32 /opt > /usr/sfw > Use --with-openssl=DIR to specify OpenSSL installation root. > [root at dhcppc2 xorp-1.6]# > > Thanks a lot! > > On Mon, Feb 9, 2009 at 12:19 AM, Pavlin Radoslavov > wrote: > > > It appears something went wrong so ./configure didn't generate > > Makefile in the top-level directory. > > Please send the complete output of running ./configure even if there > > aren't any obvious errors. > > > > Pavlin > > > > 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: > > > > > > [root at dhcppc2 xorp-1.6]# ls > > > autom4te.cache contrib libfeaclient MakefileRootCheck.am rip > > > bgp devnotes libproto MakefileRootCheck.in rtrmgr > > > bootstrap docs libtool mibs > > > static_routes > > > BUGS ERRATA libxipc mld6igmp tests > > > BUILD_NOTES etc libxorp mrt TODO > > > cli examples LICENSE ospf utils > > > config fea LICENSE.gpl pim VERSION > > > config.h.in fib2mrib LICENSE.lgpl policy vrrp > > > config.log Jamfile LICENSE.other README xrl > > > configure Jamrules.in Makefile.am RELEASE_NOTES > > > configure.in libcomm Makefile.in rib > > > > > > After typing ./configure I could see no error message but after typing > > gmake > > > it seems that no makefile exist: > > > > > > [root at dhcppc2 xorp-1.6]# make > > > make: *** No targets specified and no makefile found. Stop. > > > > > > Any advice for begginer? Thanks! > > > p.s. I have downloaded gmake-3.81. > > > _______________________________________________ > > > Xorp-users mailing list > > > Xorp-users at xorp.org > > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin at ICSI.Berkeley.EDU Tue Feb 10 09:47:52 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Tue, 10 Feb 2009 09:47:52 -0800 Subject: [Xorp-users] NAT Configurations on XORP In-Reply-To: <8360e6c80902100321t7f26e1efm19c4da17a944f24f@mail.gmail.com> References: <8360e6c80902100321t7f26e1efm19c4da17a944f24f@mail.gmail.com> Message-ID: <200902101747.n1AHlqet003945@fruitcake.ICSI.Berkeley.EDU> Currently XORP doesn't have support for configuring NAT rules, so you would have to configure them by using the OS-specific mechanism provided by the OS itself. Regards, Pavlin Yogesh Anyapanawar wrote: > Hi, > > I am looking for some sample configurations for setting up NAT rules. > My requirement is fairly simple where I have different servers running > different services in my management network and should be accessible from > the public network. > The router will also be configured as a firewall to accept only those > requests that can be serviced in my management network. > Comments/Samples will be greatly appreciated. > > Cheers, > Yogesh > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From atanu at xorp.org Wed Feb 11 09:42:31 2009 From: atanu at xorp.org (Atanu Ghosh) Date: Wed, 11 Feb 2009 09:42:31 -0800 Subject: [Xorp-users] Question regarding xorp BGP In-Reply-To: <4990DA94.2050906@owns.com> References: <4990DA94.2050906@owns.com> Message-ID: <9a09c93f0902110942u4117b01cnaf259a65eddb070b@mail.gmail.com> Hi, If the AS numbers of the local and remote BGP are not equal then BGP considers the peering to be an external peering and the leading AS number in AS path must match the AS number of the peer. The error that you are seeing is what you would expect if there has been a mismatch. The XORP BGP does not have a flag to disable this check. The only way to disable the check is to form an internal peering by using the same AS number locally and remotely. What is your peer doing that you need to disable the check? Atanu. On Mon, Feb 9, 2009 at 5:38 PM, Stegen Smith wrote: > Hello Group, > > It's been a while... had my head down with some other tasks for a few months there, but now get to return to > the world of checking out xorp. Anyways... I've got a question, perhaps feature request, about xorp's bgp > configuration/implementation. > > I've got a peer that I want to peer up with; however, they do some trickery which causes xorp_bgp to not want to > form an adjacency. Here's the log snippet: > > [ 2009/02/09 17:08:56 INFO xorp_bgp BGP ] Sending: Notification Packet: UPDATE Message Error(3): Malformed AS_PATH(11) > > The configuration looks proper to me, and I'm able to get my openbsd systems able to connect using the 'enforce neighbor-as no' in openbgpd. > So, I was wondering if this option is available to me, or if there's some trickery to make xorp_bgp to form an adjacency to a neighbor > whose left most AS doesn't match its remote AS value? It doesn't seem that there is something like this in the manual, so I am asking the > group. > > I hope I was clear enough, if not, please let me know and I'll try to provide more information. > > thanks! > steen > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > From jet at gala.net Wed Feb 11 10:21:48 2009 From: jet at gala.net (Andriy Beregovenko) Date: Wed, 11 Feb 2009 20:21:48 +0200 Subject: [Xorp-users] importing BGP routes Message-ID: <44ba60c50902111021i538f9646ya6a70561e5c160e0@mail.gmail.com> I install xorp on my linux router, and i got some issue with exporting routes from bgp to kernel. I have cisco router as bgp peer, and annonce only one route (for test). On CISCO router: -------------------------------------------------------------------------- cisco-rtr>sh ip bgp nei 172.20.11.2 adv BGP table version is 681, local router ID is 10.114.250.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 10.114.250.0/24 0.0.0.0 0 32768 i Total number of prefixes 1 cisco-rtr> -------------------------------------------------------------------------- And on xorp i recive this route: -------------------------------------------------------------------------- jet at linux-rtr# run show bgp routes Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ------ ------- ---- ------- * 10.114.250.0/24 172.20.11.1 10.114.250.1 65101 i jet at linux-rtr# -------------------------------------------------------------------------- But as you can see, this route is no best, and it do not inject into RIB. While reading documentation, i understand that i must declare some policy for exporting route from BGP to RIB, so i write policy and apply it to peer: -------------------------------------------------------------------------- jet at linux-rtr# show policy policy-statement bgp_to_rib term 1 { from { protocol: "bgp" } then { accept { } } } jet at linux-rtr# show protocols bgp peer 172.20.11.1 local-ip: "172.20.11.2" as: "65101" next-hop: 172.20.11.2 > import: "bgp_to_rib" [edit] jet at linux-rtr# -------------------------------------------------------------------------- But then i trying to commit i recive error(in log): [ 2009/02/11 19:44:51 WARNING xorp_policy:8037 XrlPolicyTarget +543 policy_base.cc handle_policy_0_1_import ] Handling method for policy/0.1/import failed:XrlCmdError 102 Command failed Import of bgp failed: sem_error from line 278 of visitor_semantic.cc: May not define protocol for import policy at line 1 [ 2009/02/11 19:44:51 ERROR xorp_rtrmgr:8013 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Import of bgp failed: sem_error from line 278 of visitor_semantic.cc: May not define protocol for import policy at line 1 Please help with this issue, because i can not find more info about xorp configuration. From stegen at owns.com Wed Feb 11 14:13:53 2009 From: stegen at owns.com (Stegen Smith) Date: Wed, 11 Feb 2009 14:13:53 -0800 Subject: [Xorp-users] Question regarding xorp BGP In-Reply-To: <9a09c93f0902110942u4117b01cnaf259a65eddb070b@mail.gmail.com> References: <4990DA94.2050906@owns.com> <9a09c93f0902110942u4117b01cnaf259a65eddb070b@mail.gmail.com> Message-ID: <49934DA1.8020906@owns.com> Hi Atanu, When I receive updates from my peer, they strip out their AS from AS_PATH when they send me the updates. Obviously, as experienced, this can cause some issues without a way to get around it in xorp. I'm guessing my peer isn't the only one who behaves in this fashion as cisco has no bgp enforce-first-as, juniper has no bgp enforce-first-as, and openbgpd also the enforce neighbor-as no configuration options. It'd be cool to be able to have this functionality with xorp as well. If this is do-able, then that'd be awesome. I hope that helps, and let me know if you need anymore information. thanks! stegen Atanu Ghosh wrote: > Hi, > > If the AS numbers of the local and remote BGP are not equal then BGP > considers the peering to be an external peering > and the leading AS number in AS path must match the AS number of the > peer. The error that you are seeing is what you would expect if there > has been a mismatch. The XORP BGP does not have a flag to disable this > check. The only way to disable the check is to form an internal > peering by using the same AS number locally and remotely. > > What is your peer doing that you need to disable the check? > > Atanu. > > On Mon, Feb 9, 2009 at 5:38 PM, Stegen Smith wrote: >> Hello Group, >> >> It's been a while... had my head down with some other tasks for a few months there, but now get to return to >> the world of checking out xorp. Anyways... I've got a question, perhaps feature request, about xorp's bgp >> configuration/implementation. >> >> I've got a peer that I want to peer up with; however, they do some trickery which causes xorp_bgp to not want to >> form an adjacency. Here's the log snippet: >> >> [ 2009/02/09 17:08:56 INFO xorp_bgp BGP ] Sending: Notification Packet: UPDATE Message Error(3): Malformed AS_PATH(11) >> >> The configuration looks proper to me, and I'm able to get my openbsd systems able to connect using the 'enforce neighbor-as no' in openbgpd. >> So, I was wondering if this option is available to me, or if there's some trickery to make xorp_bgp to form an adjacency to a neighbor >> whose left most AS doesn't match its remote AS value? It doesn't seem that there is something like this in the manual, so I am asking the >> group. >> >> I hope I was clear enough, if not, please let me know and I'll try to provide more information. >> >> thanks! >> steen >> >> _______________________________________________ >> Xorp-users mailing list >> Xorp-users at xorp.org >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> > From moisesber at gmail.com Thu Feb 12 06:38:01 2009 From: moisesber at gmail.com (Moises Rodrigues) Date: Thu, 12 Feb 2009 11:38:01 -0300 Subject: [Xorp-users] ERROR on xorp_rtrmgr "XrlRouter failed. No Finder?" In-Reply-To: <7f7ee6060902120633k5faa96fcgca2b9c98ac41f29e@mail.gmail.com> References: <7f7ee6060902120633k5faa96fcgca2b9c98ac41f29e@mail.gmail.com> Message-ID: <7f7ee6060902120638l5203d625x5d89247a0acb5ca4@mail.gmail.com> Hi everyone, I have tried to run xorp on my router and I keep having the same problem. I've tried to compile versions 1.3, 1.5, 1.6 and cvs versions and keep getting the same error. Here is a log file from the 1.5 attemp: [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Boot file := ../config.boot [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Templates directory := /usr/local/xorp-1.3/etc/templates [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Xrl targets directory := /usr/local/xorp-1.3/xrl/targets [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Execute Xrls := true [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Restart failed processes := false [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Print verbose information := true [ 2009/02/12 01:16:04 ERROR xorp_rtrmgr:13425 XRL +640 xrl_router.cc wait_until_xrl_router_is_ready ] XrlRouter failed. No Finder? My system is Debian 4.0 stable gcc (GCC) 3.3.4 (Debian 1:3.3.4-3) g++ (GCC) 3.3.4 (Debian 1:3.3.4-3) My config.boot file is attached to this message. Commando line used: ./xorp_rtrmgr -b ../config.boot -v -l log I made some research over the net trying to find a solution for my problem, BTW I saw a lot of other Debian users with the same problem, but none of the tips worked. I tried to start the finder manualy, libxipc/xorp_finder and it seems to work OK but with the rtrmgr it just don't work. Please any help would welcome. I'm trying to make this work for over a week now. Thanks for your time anyway, Moises Rodrigues -------------- next part -------------- A non-text attachment was scrubbed... Name: config.boot Type: application/octet-stream Size: 2858 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090212/c67902ff/attachment.obj From pavlin at ICSI.Berkeley.EDU Thu Feb 12 11:06:31 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Thu, 12 Feb 2009 11:06:31 -0800 Subject: [Xorp-users] ERROR on xorp_rtrmgr "XrlRouter failed. No Finder?" In-Reply-To: <7f7ee6060902120638l5203d625x5d89247a0acb5ca4@mail.gmail.com> References: <7f7ee6060902120633k5faa96fcgca2b9c98ac41f29e@mail.gmail.com> <7f7ee6060902120638l5203d625x5d89247a0acb5ca4@mail.gmail.com> Message-ID: <200902121906.n1CJ6Vrg018539@fruitcake.ICSI.Berkeley.EDU> I presume you downloaded vanilla 1.6 source code from the xorp.org Web site and compiled it by hand. You shouldn't run xorp_finder by hand, because the xorp_rtrmgr process already includes it. For the sake of isolating the problem please try to run xorp_rtrmgr by using an empty config file: # Download and untar vanilla source code ./configure gmake cd rtrmgr touch empty.boot ./xorp_rtrmgr -b empty.boot I don't remember having issues on Debian-4.0 (see xorp/BUILD_NOTES), but it was with gcc-4.1 compiler. I have seen issues with gcc-3.4 on FreeBSD (see xorp/ERRATA), but I don't know whether the gcc-3.3 compiler you are using on Debian has similar issues. Regards, Pavlin Moises Rodrigues wrote: > Hi everyone, > > I have tried to run xorp on my router and I keep having the same > problem. I've tried to compile versions 1.3, 1.5, 1.6 and cvs versions > and keep getting the same error. > > Here is a log file from the 1.5 attemp: > > [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Boot file > := ../config.boot > [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Templates directory > := /usr/local/xorp-1.3/etc/templates > [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Xrl targets directory > := /usr/local/xorp-1.3/xrl/targets > [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Execute Xrls > := true > [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Restart failed > processes := false > [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Print verbose > information := true > [ 2009/02/12 01:16:04 ERROR xorp_rtrmgr:13425 XRL +640 xrl_router.cc > wait_until_xrl_router_is_ready ] XrlRouter failed. No Finder? > > My system is Debian 4.0 stable > gcc (GCC) 3.3.4 (Debian 1:3.3.4-3) > g++ (GCC) 3.3.4 (Debian 1:3.3.4-3) > My config.boot file is attached to this message. > > Commando line used: ./xorp_rtrmgr -b ../config.boot -v -l log > > I made some research over the net trying to find a solution for my > problem, BTW I saw a lot of other Debian users with the same problem, > but none of the tips worked. I tried to start the finder manualy, > libxipc/xorp_finder and it seems to work OK but with the rtrmgr it > just don't work. > Please any help would welcome. I'm trying to make this work for over a week now. > > Thanks for your time anyway, > > Moises Rodrigues > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From moisesber at gmail.com Thu Feb 12 11:38:55 2009 From: moisesber at gmail.com (Moises Rodrigues) Date: Thu, 12 Feb 2009 16:38:55 -0300 Subject: [Xorp-users] ERROR on xorp_rtrmgr "XrlRouter failed. No Finder?" In-Reply-To: <200902121906.n1CJ6Vrg018539@fruitcake.ICSI.Berkeley.EDU> References: <7f7ee6060902120633k5faa96fcgca2b9c98ac41f29e@mail.gmail.com> <7f7ee6060902120638l5203d625x5d89247a0acb5ca4@mail.gmail.com> <200902121906.n1CJ6Vrg018539@fruitcake.ICSI.Berkeley.EDU> Message-ID: <7f7ee6060902121138je33626fvcb3953ce995b7617@mail.gmail.com> Thanks for the reply man. Yes I did got the source and compiled it for all those versions that I said. I did what you told and got the same error: root at router:/local/xorp-debian/xorp-1.5/rtrmgr# ./xorp_rtrmgr -b empty.boot [ 2009/02/12 16:29:58 ERROR xorp_rtrmgr:14112 XRL +640 xrl_router.cc wait_until_xrl_router_is_ready ] XrlRouter failed. No Finder? I saw the BUILD_NOTES file and I didn't find anything that could help me. All the packages were instaled and the version were OK. On Thu, Feb 12, 2009 at 4:06 PM, Pavlin Radoslavov wrote: > I presume you downloaded vanilla 1.6 source code from the xorp.org > Web site and compiled it by hand. > You shouldn't run xorp_finder by hand, because the xorp_rtrmgr > process already includes it. > > For the sake of isolating the problem please try to run xorp_rtrmgr > by using an empty config file: > > # Download and untar vanilla source code > ./configure > gmake > cd rtrmgr > touch empty.boot > ./xorp_rtrmgr -b empty.boot > > I don't remember having issues on Debian-4.0 (see xorp/BUILD_NOTES), > but it was with gcc-4.1 compiler. I have seen issues with gcc-3.4 on > FreeBSD (see xorp/ERRATA), but I don't know whether the gcc-3.3 > compiler you are using on Debian has similar issues. > > Regards, > Pavlin > > Moises Rodrigues wrote: > >> Hi everyone, >> >> I have tried to run xorp on my router and I keep having the same >> problem. I've tried to compile versions 1.3, 1.5, 1.6 and cvs versions >> and keep getting the same error. >> >> Here is a log file from the 1.5 attemp: >> >> [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Boot file >> := ../config.boot >> [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Templates directory >> := /usr/local/xorp-1.3/etc/templates >> [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Xrl targets directory >> := /usr/local/xorp-1.3/xrl/targets >> [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Execute Xrls >> := true >> [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Restart failed >> processes := false >> [ 2009/02/12 01:15:34 TRACE xorp_rtrmgr RTRMGR ] Print verbose >> information := true >> [ 2009/02/12 01:16:04 ERROR xorp_rtrmgr:13425 XRL +640 xrl_router.cc >> wait_until_xrl_router_is_ready ] XrlRouter failed. No Finder? >> >> My system is Debian 4.0 stable >> gcc (GCC) 3.3.4 (Debian 1:3.3.4-3) >> g++ (GCC) 3.3.4 (Debian 1:3.3.4-3) >> My config.boot file is attached to this message. >> >> Commando line used: ./xorp_rtrmgr -b ../config.boot -v -l log >> >> I made some research over the net trying to find a solution for my >> problem, BTW I saw a lot of other Debian users with the same problem, >> but none of the tips worked. I tried to start the finder manualy, >> libxipc/xorp_finder and it seems to work OK but with the rtrmgr it >> just don't work. >> Please any help would welcome. I'm trying to make this work for over a week now. >> >> Thanks for your time anyway, >> >> Moises Rodrigues >> _______________________________________________ >> Xorp-users mailing list >> Xorp-users at xorp.org >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > From pavlin at ICSI.Berkeley.EDU Thu Feb 12 11:46:01 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Thu, 12 Feb 2009 11:46:01 -0800 Subject: [Xorp-users] ERROR on xorp_rtrmgr "XrlRouter failed. No Finder?" In-Reply-To: <7f7ee6060902121138je33626fvcb3953ce995b7617@mail.gmail.com> References: <7f7ee6060902120633k5faa96fcgca2b9c98ac41f29e@mail.gmail.com> <7f7ee6060902120638l5203d625x5d89247a0acb5ca4@mail.gmail.com> <200902121906.n1CJ6Vrg018539@fruitcake.ICSI.Berkeley.EDU> <7f7ee6060902121138je33626fvcb3953ce995b7617@mail.gmail.com> Message-ID: <200902121946.n1CJk14o023149@fruitcake.ICSI.Berkeley.EDU> Moises Rodrigues wrote: > Yes I did got the source and compiled it for all those versions that I said. > > I did what you told and got the same error: > root at router:/local/xorp-debian/xorp-1.5/rtrmgr# ./xorp_rtrmgr -b empty.boot > [ 2009/02/12 16:29:58 ERROR xorp_rtrmgr:14112 XRL +640 xrl_router.cc > wait_until_xrl_router_is_ready ] XrlRouter failed. No Finder? > > I saw the BUILD_NOTES file and I didn't find anything that could help > me. All the packages were instaled and the version were OK. Do you have any firewall rules installed that might be blocking some of the TCP ports? By default XORP is using the loopback interface (127.0.0.1) and TCP port 19999 for its internal communications, so please double-check that the loopback interface is up and operational and nothing is stopping that port. Pavlin From moisesber at gmail.com Thu Feb 12 13:02:43 2009 From: moisesber at gmail.com (Moises Rodrigues) Date: Thu, 12 Feb 2009 18:02:43 -0300 Subject: [Xorp-users] ERROR on xorp_rtrmgr "XrlRouter failed. No Finder?" In-Reply-To: <200902121946.n1CJk14o023149@fruitcake.ICSI.Berkeley.EDU> References: <7f7ee6060902120633k5faa96fcgca2b9c98ac41f29e@mail.gmail.com> <7f7ee6060902120638l5203d625x5d89247a0acb5ca4@mail.gmail.com> <200902121906.n1CJ6Vrg018539@fruitcake.ICSI.Berkeley.EDU> <7f7ee6060902121138je33626fvcb3953ce995b7617@mail.gmail.com> <200902121946.n1CJk14o023149@fruitcake.ICSI.Berkeley.EDU> Message-ID: <7f7ee6060902121302n6158f12k3b8c0224c6f869b3@mail.gmail.com> Thanks man! That did the trick. The problem was the router firewall. I added some rules for 127.0.0.1 connections and everything works well. BTW I read the info on the page and a little bit of the manual and I don't remember seeing anything about that. Please put some info about that if it don't have already. If it has, sorry for my mistake. Hope that this thread help somebody in the future. Mois?s Rodrigues On Thu, Feb 12, 2009 at 4:46 PM, Pavlin Radoslavov wrote: > Moises Rodrigues wrote: > >> Yes I did got the source and compiled it for all those versions that I said. >> >> I did what you told and got the same error: >> root at router:/local/xorp-debian/xorp-1.5/rtrmgr# ./xorp_rtrmgr -b empty.boot >> [ 2009/02/12 16:29:58 ERROR xorp_rtrmgr:14112 XRL +640 xrl_router.cc >> wait_until_xrl_router_is_ready ] XrlRouter failed. No Finder? >> >> I saw the BUILD_NOTES file and I didn't find anything that could help >> me. All the packages were instaled and the version were OK. > > Do you have any firewall rules installed that might be blocking some > of the TCP ports? By default XORP is using the loopback interface > (127.0.0.1) and TCP port 19999 for its internal communications, so > please double-check that the loopback interface is up and > operational and nothing is stopping that port. > > Pavlin > From pavlin at ICSI.Berkeley.EDU Thu Feb 12 15:52:58 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Thu, 12 Feb 2009 15:52:58 -0800 Subject: [Xorp-users] ERROR on xorp_rtrmgr "XrlRouter failed. No Finder?" In-Reply-To: <7f7ee6060902121302n6158f12k3b8c0224c6f869b3@mail.gmail.com> References: <7f7ee6060902120633k5faa96fcgca2b9c98ac41f29e@mail.gmail.com> <7f7ee6060902120638l5203d625x5d89247a0acb5ca4@mail.gmail.com> <200902121906.n1CJ6Vrg018539@fruitcake.ICSI.Berkeley.EDU> <7f7ee6060902121138je33626fvcb3953ce995b7617@mail.gmail.com> <200902121946.n1CJk14o023149@fruitcake.ICSI.Berkeley.EDU> <7f7ee6060902121302n6158f12k3b8c0224c6f869b3@mail.gmail.com> Message-ID: <200902122352.n1CNqwhR017191@fruitcake.ICSI.Berkeley.EDU> Moises Rodrigues wrote: > That did the trick. The problem was the router firewall. I added some > rules for 127.0.0.1 connections and everything works well. Great! > BTW I read the info on the page and a little bit of the manual and I > don't remember seeing anything about that. Please put some info about > that if it don't have already. If it has, sorry for my mistake. > Hope that this thread help somebody in the future. No, it is not in the documentation, but it should be (in the User Manual, FAQ, somewhere). Please add a Bugzilla entry about the missing info in the documentation. Thanks, Pavlin > Mois?s Rodrigues > > On Thu, Feb 12, 2009 at 4:46 PM, Pavlin Radoslavov > wrote: > > Moises Rodrigues wrote: > > > >> Yes I did got the source and compiled it for all those versions that I said. > >> > >> I did what you told and got the same error: > >> root at router:/local/xorp-debian/xorp-1.5/rtrmgr# ./xorp_rtrmgr -b empty.boot > >> [ 2009/02/12 16:29:58 ERROR xorp_rtrmgr:14112 XRL +640 xrl_router.cc > >> wait_until_xrl_router_is_ready ] XrlRouter failed. No Finder? > >> > >> I saw the BUILD_NOTES file and I didn't find anything that could help > >> me. All the packages were instaled and the version were OK. > > > > Do you have any firewall rules installed that might be blocking some > > of the TCP ports? By default XORP is using the loopback interface > > (127.0.0.1) and TCP port 19999 for its internal communications, so > > please double-check that the loopback interface is up and > > operational and nothing is stopping that port. > > > > Pavlin > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From erik at slagter.name Fri Feb 13 03:06:56 2009 From: erik at slagter.name (Erik Slagter) Date: Fri, 13 Feb 2009 12:06:56 +0100 Subject: [Xorp-users] Very simple multicast setup, yet can't find any text on how to do it! In-Reply-To: <497F71C4.2070804@slagter.name> References: <4971D73E.3030405@slagter.name> <497224C8.7070504@slagter.name> <200901171906.n0HJ6kHI007438@fruitcake.ICSI.Berkeley.EDU> <49723C16.5030409@slagter.name> <200901172230.n0HMUfbd021164@fruitcake.ICSI.Berkeley.EDU> <4973199E.60708@slagter.name> <49732F2C.3080801@slagter.name> <200901271235.n0RCZe8P008880@fruitcake.ICSI.Berkeley.EDU> <497F02B7.3040802@slagter.name> <200901271853.n0RIrX14022538@fruitcake.ICSI.Berkeley.EDU> <497F71C4.2070804@slagter.name> Message-ID: <49955450.8030008@slagter.name> To cut a long story short, I've managed to make a simple C++ app that does all what's necessary to use your box as multicast source for multiple interfaces, using mld. It also keeps track of clients, does mld inquiries, removes client when they either explicitly go away or do not answer mld queries and it even seems to work too ;-) For most of you this won't be interesting, but I target the lonely soul like me that also tries to achieve the same thing and now they don't need write something like this from scratch, just yell... BTW, strange I don't get any message from the usagi-users at ml.linux-ipv6.org list, even though I am subscribed and my message seem to get through... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3328 bytes Desc: S/MIME Cryptographic Signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090213/bb18a32d/attachment.bin From erik at slagter.name Fri Feb 13 09:08:39 2009 From: erik at slagter.name (Erik Slagter) Date: Fri, 13 Feb 2009 18:08:39 +0100 Subject: [Xorp-users] * SPAM * [3] Re: Very simple multicast setup, yet can't find any text on how to do it! In-Reply-To: References: <4971D73E.3030405@slagter.name> <49723C16.5030409@slagter.name> <200901172230.n0HMUfbd021164@fruitcake.ICSI.Berkeley.EDU> <4973199E.60708@slagter.name> <49732F2C.3080801@slagter.name> <200901271235.n0RCZe8P008880@fruitcake.ICSI.Berkeley.EDU> <497F02B7.3040802@slagter.name> <200901271853.n0RIrX14022538@fruitcake.ICSI.Berkeley.EDU> <497F71C4.2070804@slagter.name> <49955450.8030008@slagter.name> Message-ID: <4995A917.90902@slagter.name> Syed Khalid wrote: > Hello Erik > We would appreciate a copy of the program. > Thanks > Syed Did I mention it only works on ipv6? I guess there are already some apps that handle ipv4. I'll make a distributable version anyway. Please hang on. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3328 bytes Desc: S/MIME Cryptographic Signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090213/52d94cfe/attachment.bin From erik at slagter.name Fri Feb 13 09:42:11 2009 From: erik at slagter.name (Erik Slagter) Date: Fri, 13 Feb 2009 18:42:11 +0100 Subject: [Xorp-users] * SPAM * [3] Re: Very simple multicast setup, yet can't find any text on how to do it! In-Reply-To: <4995A917.90902@slagter.name> References: <4971D73E.3030405@slagter.name> <49723C16.5030409@slagter.name> <200901172230.n0HMUfbd021164@fruitcake.ICSI.Berkeley.EDU> <4973199E.60708@slagter.name> <49732F2C.3080801@slagter.name> <200901271235.n0RCZe8P008880@fruitcake.ICSI.Berkeley.EDU> <497F02B7.3040802@slagter.name> <200901271853.n0RIrX14022538@fruitcake.ICSI.Berkeley.EDU> <497F71C4.2070804@slagter.name> <49955450.8030008@slagter.name> <4995A917.90902@slagter.name> Message-ID: <4995B0F3.8090002@slagter.name> Erik Slagter wrote: > Syed Khalid wrote: >> Hello Erik >> We would appreciate a copy of the program. >> Thanks >> Syed > > Did I mention it only works on ipv6? I guess there are already some apps > that handle ipv4. > > I'll make a distributable version anyway. Please hang on. It's downloadable from here: http://erik.slagter.name/pub/m6f.tgz -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3328 bytes Desc: S/MIME Cryptographic Signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090213/b5c3115c/attachment-0001.bin From ramkumar.ch03 at gmail.com Sat Feb 14 12:33:56 2009 From: ramkumar.ch03 at gmail.com (Ramkumar Cherukuri) Date: Sat, 14 Feb 2009 14:33:56 -0600 Subject: [Xorp-users] Help required for how to install xorp in CentOS 5.2. Message-ID: <1c56f7b10902141233i7527ff3em2f81c38ad0a425de@mail.gmail.com> Hi all. i am new to xorp. i would like to know how to install xorp in Linux CentOS 5.2. i would like know how to make my desktop computer act as router. can any one give steps how to do that in CentOS 5.2.? your help would be appreciated. Thanks in advance. regards, Ramkumar -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090214/4face923/attachment.html From carsten at c-otto.de Wed Feb 18 10:19:48 2009 From: carsten at c-otto.de (Carsten Otto) Date: Wed, 18 Feb 2009 19:19:48 +0100 Subject: [Xorp-users] cand-rp without BSR Message-ID: <20090218181948.GE25985@carsten-otto> Dear list, due to a strange network policy I am not allowed (by non-technical rules) to announce my cand-rp to the BSR. As a workaround I configured every "client" to know my rp using a static configuration. On my router I did the same thing, as cand-rp always results in announcements to the BSR. Sadly, this does not work. As far as I know, my router is contacted with requests, but does not act as a RP. Is there a better solution than to block packets to the BSR (and hope the address does not change)? I am using a quite old version of XORP. Please just tell me if I can hope for improvements with a recent version. Best regards, -- Carsten Otto carsten at c-otto.de www.c-otto.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090218/fd98f20b/attachment.bin From pavlin at ICSI.Berkeley.EDU Wed Feb 18 11:09:17 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Wed, 18 Feb 2009 11:09:17 -0800 Subject: [Xorp-users] cand-rp without BSR In-Reply-To: <20090218181948.GE25985@carsten-otto> References: <20090218181948.GE25985@carsten-otto> Message-ID: <200902181909.n1IJ9HlB014837@fruitcake.ICSI.Berkeley.EDU> Carsten Otto wrote: > Dear list, > > due to a strange network policy I am not allowed (by non-technical > rules) to announce my cand-rp to the BSR. As a workaround I configured > every "client" to know my rp using a static configuration. On my router > I did the same thing, as cand-rp always results in announcements to the > BSR. Sadly, this does not work. As far as I know, my router is contacted > with requests, but does not act as a RP. Is there a better solution than > to block packets to the BSR (and hope the address does not change)? > > I am using a quite old version of XORP. Please just tell me if I can > hope for improvements with a recent version. Which XORP version are you using? If you just configure static-rps and all of them point to the same router (for the same group prefix) this is suppose to work. Please send your XORP config you are not sure. Also, please clarify what you mean by " does not act as a RP". Regards, Pavlin P.S. FYI, in the latest XORP-1.6 release, a PIM-SM router will accept Bootstrap messages only if the "bootstrap {}" block is in the config (empty block is fine). > Best regards, > -- > Carsten Otto > carsten at c-otto.de > www.c-otto.de > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From ramkumar.ch03 at gmail.com Thu Feb 19 19:28:42 2009 From: ramkumar.ch03 at gmail.com (Ramkumar Cherukuri) Date: Thu, 19 Feb 2009 21:28:42 -0600 Subject: [Xorp-users] error while entering in to shell (xropsh) Message-ID: <1c56f7b10902191928p18421776vbf2d4b5cfc70bf2d@mail.gmail.com> Hi Users, Today i downloaded xorp-1.6 and compiled and configured it in CentOS 5.2.. Every thing is completed fine.After gmake, i checked for gcheck, at end it gave some warnings. finally i tried to enter in to xorpsh, but i got the following errors so many times. i don't know the reason. what does causes to this error? can any one tell me what i need to do? [root at localhost xorp-1.6]# cd rtrmgr/ [root at localhost rtrmgr]# ./xorpsh [ 2009/02/19 20:37:20 ERROR xorpsh:5337 LIBXORP +714 asyncio.cc complete_transfer ] Write error 111 Thanks in advance. -- Ramkumar -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090219/c9e1cd99/attachment.html From pavlin at ICSI.Berkeley.EDU Fri Feb 20 09:45:29 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Fri, 20 Feb 2009 09:45:29 -0800 Subject: [Xorp-users] error while entering in to shell (xropsh) In-Reply-To: <1c56f7b10902191928p18421776vbf2d4b5cfc70bf2d@mail.gmail.com> References: <1c56f7b10902191928p18421776vbf2d4b5cfc70bf2d@mail.gmail.com> Message-ID: <200902201745.n1KHjTSE011058@fruitcake.ICSI.Berkeley.EDU> Ramkumar Cherukuri wrote: > Hi Users, > > Today i downloaded xorp-1.6 and compiled and configured it in CentOS 5.2.. > Every thing is completed fine.After gmake, i checked for gcheck, at end it > gave some warnings. > > finally i tried to enter in to xorpsh, but i got the following errors so > many times. i don't know the reason. > > what does causes to this error? can any one tell me what i need to do? > > > [root at localhost xorp-1.6]# cd rtrmgr/ > [root at localhost rtrmgr]# ./xorpsh > [ 2009/02/19 20:37:20 ERROR xorpsh:5337 LIBXORP +714 asyncio.cc > complete_transfer ] Write error 111 Did you run the xorp_rtrmgr first with your config, because it doesn't seem to be the case from the above commands. For testing purpose you can use an empty config file: cd rtrmgr touch config/emtpy.boot ./xorp_rtrmgr -b config/empty.boot Regards, Pavlin From carsten at c-otto.de Fri Feb 20 10:50:43 2009 From: carsten at c-otto.de (Carsten Otto) Date: Fri, 20 Feb 2009 19:50:43 +0100 Subject: [Xorp-users] cand-rp without BSR In-Reply-To: <200902181909.n1IJ9HlB014837@fruitcake.ICSI.Berkeley.EDU> References: <20090218181948.GE25985@carsten-otto> <200902181909.n1IJ9HlB014837@fruitcake.ICSI.Berkeley.EDU> Message-ID: <20090220185043.GB5984@carsten-otto> On Wed, Feb 18, 2009 at 11:09:17AM -0800, Pavlin Radoslavov wrote: > Which XORP version are you using? I cannot figure out how to get the version number, but the files are from June 2006. I am installing 1.6 right now. > If you just configure static-rps and all of them point to the same > router (for the same group prefix) this is suppose to work. I thought so, let's see if 1.6 helps. > Please send your XORP config you are not sure. Attached. > Also, please clarify what you mean by > " does not act as a RP". It does not forward/route/send the multicast data that is being requesting using PIM. It behaves like these packets are ignored (maybe because it does not feel responsible). Bye, -- Carsten Otto carsten at c-otto.de www.c-otto.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090220/f885d878/attachment.bin From carsten at c-otto.de Fri Feb 20 10:51:56 2009 From: carsten at c-otto.de (Carsten Otto) Date: Fri, 20 Feb 2009 19:51:56 +0100 Subject: [Xorp-users] cand-rp without BSR In-Reply-To: <20090220185043.GB5984@carsten-otto> References: <20090218181948.GE25985@carsten-otto> <200902181909.n1IJ9HlB014837@fruitcake.ICSI.Berkeley.EDU> <20090220185043.GB5984@carsten-otto> Message-ID: <20090220185156.GD5984@carsten-otto> On Fri, Feb 20, 2009 at 07:50:43PM +0100, Carsten Otto wrote: > Attached. Sorry, I forgot the file.. -- Carsten Otto carsten at c-otto.de www.c-otto.de -------------- next part -------------- /*XORP Configuration File, v1.0*/ interfaces { interface eth0 { disable: false discard: false description: "Intern" default-system-config { } } interface eth1 { disable: false discard: false description: "Extern" default-system-config { } } restore-original-config-on-shutdown: false } fea { unicast-forwarding4 { disable: false } } protocols { fib2mrib { disable: false } igmp { disable: false interface eth0 { vif eth0 { disable: false version: 2 enable-ip-router-alert-option-check: false query-interval: 125 query-last-member-interval: 1 query-response-interval: 10 robust-count: 2 } } interface eth1 { vif eth1 { disable: false version: 2 enable-ip-router-alert-option-check: false query-interval: 125 query-last-member-interval: 1 query-response-interval: 10 robust-count: 2 } } } pimsm4 { disable: false interface eth0 { vif eth0 { disable: false dr-priority: 1 enable-ip-router-alert-option-check: false hello-period: 30 hello-triggered-delay: 5 } } interface eth1 { vif eth1 { disable: false dr-priority: 1 enable-ip-router-alert-option-check: false hello-period: 30 hello-triggered-delay: 5 } } interface "register_vif" { vif "register_vif" { disable: false dr-priority: 1 enable-ip-router-alert-option-check: false hello-period: 30 hello-triggered-delay: 5 } } switch-to-spt-threshold { interval: 100 disable: false bytes: 102400 } static-rps { rp 134.130.56.193 { group-prefix 239.254.1.0/24 { rp-priority 255 } group-prefix 239.254.2.0/24 { rp-priority 255 } } rp 137.226.39.194 { group-prefix 239.254.18.0/24 { rp-priority 0 } } rp 137.226.119.114 { group-prefix 239.254.16.0/24 { rp-priority 0 } group-prefix 239.254.17.0/24 { rp-priority 0 } } } bootstrap { disable: false } } } plumbing { mfea4 { disable: false interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface "register_vif" { vif "register_vif" { disable: false } } } } -------------- 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/20090220/b342635e/attachment.bin From carsten at c-otto.de Fri Feb 20 10:54:47 2009 From: carsten at c-otto.de (Carsten Otto) Date: Fri, 20 Feb 2009 19:54:47 +0100 Subject: [Xorp-users] cand-rp without BSR In-Reply-To: <20090220185156.GD5984@carsten-otto> References: <20090218181948.GE25985@carsten-otto> <200902181909.n1IJ9HlB014837@fruitcake.ICSI.Berkeley.EDU> <20090220185043.GB5984@carsten-otto> <20090220185156.GD5984@carsten-otto> Message-ID: <20090220185446.GE5984@carsten-otto> On Fri, Feb 20, 2009 at 07:51:56PM +0100, Carsten Otto wrote: > static-rps { > rp 134.130.56.193 { > group-prefix 239.254.1.0/24 { > rp-priority 255 > } > group-prefix 239.254.2.0/24 { > rp-priority 255 > } > } > rp 137.226.39.194 { > group-prefix 239.254.18.0/24 { > rp-priority 0 > } > } > rp 137.226.119.114 { > group-prefix 239.254.16.0/24 { > rp-priority 0 > } > group-prefix 239.254.17.0/24 { > rp-priority 0 > } > } > } (Sorry for the spam, I need more coffee) To clarify: 137.226.119.114 is my XORP. The static-rp section of 137.226.56.193 looks the same, but streaming from my network to that network does not work. The XORP at 137.226.39.194 is still using a BSR-nonstatic-configuration and does serve data to 137.226.56.193 (and my network). Bye, -- Carsten Otto carsten at c-otto.de www.c-otto.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090220/549bade2/attachment.bin From carsten at c-otto.de Fri Feb 20 14:57:19 2009 From: carsten at c-otto.de (Carsten Otto) Date: Fri, 20 Feb 2009 23:57:19 +0100 Subject: [Xorp-users] FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed Message-ID: <20090220225718.GH5984@carsten-otto> Hi there, my fresh 1.6 installation with a config file based on the multicast example provided with the source crashes after a few seconds: [ 2009/02/20 23:52:58 INFO xorp_rtrmgr:27872 RTRMGR +249 master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea, mfea4, rib, fib2mrib, igmp, pimsm4 [ 2009/02/20 23:52:58 INFO xorp_rtrmgr:27872 RTRMGR +101 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] MFEA enabled [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] CLI enabled [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] CLI started [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] MFEA enabled [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] CLI enabled [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] CLI started [ 2009/02/20 23:53:00 INFO xorp_rtrmgr:27872 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) [ 2009/02/20 23:53:04 INFO xorp_rtrmgr:27872 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +101 module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea) [ 2009/02/20 23:53:10 FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed [ 2009/02/20 23:53:10 ERROR xorp_rtrmgr:27872 RTRMGR +2003 task.cc task_fail ] Shutting down fatally wounded process (mfea4) [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +176 module_manager.cc terminate ] Terminating module: mfea4 [ 2009/02/20 23:53:10 ERROR xorp_rtrmgr:27872 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: Can't startup process mfea4 [ 2009/02/20 23:53:10 ERROR xorp_rtrmgr:27872 RTRMGR +261 master_conf_tree.cc config_done ] Configuration failed: Can't startup process mfea4 [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +2233 task.cc run_task ] No more tasks to run [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +176 module_manager.cc terminate ] Terminating module: fea [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +176 module_manager.cc terminate ] Terminating module: firewall [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +176 module_manager.cc terminate ] Terminating module: interfaces [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +199 module_manager.cc terminate ] Killing module: interfaces [ 2009/02/20 23:53:10 ERROR xorp_rtrmgr:27872 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/fea/xorp_fea": terminated with signal 6. [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +287 module_manager.cc module_exited ] Module killed during shutdown: interfaces I attached the config file. Removing the sections for eth2 and eth0.2 at the top does not resolve the problem. $ ifconfig -a eth0 Link encap:Ethernet HWaddr 00:04:23:af:7a:20 inet addr:137.226.111.20 Bcast:137.226.111.255 Mask:255.255.252.0 inet6 addr: fe80::204:23ff:feaf:7a20/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:314709117 errors:294 dropped:6139195 overruns:0 frame:157 TX packets:320928163 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1686376969 (1.5 GiB) TX bytes:3859321010 (3.5 GiB) Base address:0xac00 Memory:fc3e0000-fc400000 eth1 Link encap:Ethernet HWaddr 00:04:23:ae:ab:78 inet addr:137.226.119.114 Bcast:137.226.119.119 Mask:255.255.255.248 inet6 addr: fe80::204:23ff:feae:ab78/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:48104013 errors:0 dropped:116496 overruns:0 frame:0 TX packets:3533100387 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1659314219 (1.5 GiB) TX bytes:1205554780 (1.1 GiB) Base address:0xbc00 Memory:fc5e0000-fc600000 eth2 Link encap:Ethernet HWaddr 00:04:23:af:7a:21 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:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth0.2 Link encap:Ethernet HWaddr 00:04:23:af:7a:20 inet addr:10.10.0.1 Bcast:10.10.255.255 Mask:255.255.0.0 inet6 addr: fe80::204:23ff:feaf:7a20/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:656786448 errors:0 dropped:0 overruns:0 frame:0 TX packets:664639075 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3040389292 (2.8 GiB) TX bytes:675407553 (644.1 MiB) ip6tnl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 NOARP MTU:1460 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) 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:3474546933 errors:0 dropped:0 overruns:0 frame:0 TX packets:3474546933 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1064854296 (1015.5 MiB) TX bytes:1064854296 (1015.5 MiB) 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) tunl0 Link encap:IPIP Tunnel HWaddr 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) Thanks, -- Carsten Otto carsten at c-otto.de www.c-otto.de -------------- next part -------------- /* $XORP: xorp/rtrmgr/config/multicast4.boot,v 1.1 2007/08/29 06:49:43 pavlin Exp $ */ interfaces { interface eth0 { default-system-config { } } interface eth0.2 { default-system-config { } } interface eth1 { default-system-config { } } interface eth2 { default-system-config { } } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea4 { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } } } protocols { igmp { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } } pimsm4 { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } static-rps { rp 137.226.56.193 { group-prefix 239.254.1.0/24 { } group-prefix 239.254.2.0/24 { } } rp 137.226.39.194 { group-prefix 239.254.18.0/24 { } } rp 137.226.119.114 { group-prefix 239.254.16.0/24 { } group-prefix 239.254.17.0/24 { } } } bootstrap { disable: false } switch-to-spt-threshold { disable: false interval: 100 bytes: 102400 } } } protocols { fib2mrib { disable: false } } -------------- 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/20090220/cbda5b95/attachment.bin From pavlin at ICSI.Berkeley.EDU Sun Feb 22 12:03:57 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Sun, 22 Feb 2009 12:03:57 -0800 Subject: [Xorp-users] FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed In-Reply-To: <20090220225718.GH5984@carsten-otto> References: <20090220225718.GH5984@carsten-otto> Message-ID: <200902222004.n1MK3vDc026290@fruitcake.ICSI.Berkeley.EDU> I believe the issue is that eth0.2 is not really a separate network interface, but an IP alias address. Hence in your XORP config you should just delete the "interface eth0.2" block, because the 10.10.0.1 address already belongs to interface/vif eth0. Regards, Pavlin P.S. In general, the Linux command "ip" (e.g., "ip addr" and "ip link") is better than "ifconfig". Carsten Otto wrote: > Hi there, > > my fresh 1.6 installation with a config file based on the multicast > example provided with the source crashes after a few seconds: > > [ 2009/02/20 23:52:58 INFO xorp_rtrmgr:27872 RTRMGR +249 master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea, mfea4, rib, fib2mrib, igmp, pimsm4 > [ 2009/02/20 23:52:58 INFO xorp_rtrmgr:27872 RTRMGR +101 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) > [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] MFEA enabled > [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] CLI enabled > [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] CLI started > [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] MFEA enabled > [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] CLI enabled > [ 2009/02/20 23:52:59 INFO xorp_fea MFEA ] CLI started > [ 2009/02/20 23:53:00 INFO xorp_rtrmgr:27872 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) > [ 2009/02/20 23:53:04 INFO xorp_rtrmgr:27872 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) > [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +101 module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea) > [ 2009/02/20 23:53:10 FATAL xorp_fea:27902 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed > [ 2009/02/20 23:53:10 ERROR xorp_rtrmgr:27872 RTRMGR +2003 task.cc task_fail ] Shutting down fatally wounded process (mfea4) > [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +176 module_manager.cc terminate ] Terminating module: mfea4 > [ 2009/02/20 23:53:10 ERROR xorp_rtrmgr:27872 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: Can't startup process mfea4 > [ 2009/02/20 23:53:10 ERROR xorp_rtrmgr:27872 RTRMGR +261 master_conf_tree.cc config_done ] Configuration failed: Can't startup process mfea4 > [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +2233 task.cc run_task ] No more tasks to run > [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +176 module_manager.cc terminate ] Terminating module: fea > [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +176 module_manager.cc terminate ] Terminating module: firewall > [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +176 module_manager.cc terminate ] Terminating module: interfaces > [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +199 module_manager.cc terminate ] Killing module: interfaces > [ 2009/02/20 23:53:10 ERROR xorp_rtrmgr:27872 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/fea/xorp_fea": terminated with signal 6. > [ 2009/02/20 23:53:10 INFO xorp_rtrmgr:27872 RTRMGR +287 module_manager.cc module_exited ] Module killed during shutdown: interfaces > > I attached the config file. Removing the sections for eth2 and eth0.2 at the > top does not resolve the problem. > > $ ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:04:23:af:7a:20 > inet addr:137.226.111.20 Bcast:137.226.111.255 Mask:255.255.252.0 > inet6 addr: fe80::204:23ff:feaf:7a20/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:314709117 errors:294 dropped:6139195 overruns:0 frame:157 > TX packets:320928163 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1686376969 (1.5 GiB) TX bytes:3859321010 (3.5 GiB) > Base address:0xac00 Memory:fc3e0000-fc400000 > > eth1 Link encap:Ethernet HWaddr 00:04:23:ae:ab:78 > inet addr:137.226.119.114 Bcast:137.226.119.119 Mask:255.255.255.248 > inet6 addr: fe80::204:23ff:feae:ab78/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:48104013 errors:0 dropped:116496 overruns:0 frame:0 > TX packets:3533100387 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1659314219 (1.5 GiB) TX bytes:1205554780 (1.1 GiB) > Base address:0xbc00 Memory:fc5e0000-fc600000 > > eth2 Link encap:Ethernet HWaddr 00:04:23:af:7a:21 > 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:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > eth0.2 Link encap:Ethernet HWaddr 00:04:23:af:7a:20 > inet addr:10.10.0.1 Bcast:10.10.255.255 Mask:255.255.0.0 > inet6 addr: fe80::204:23ff:feaf:7a20/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:656786448 errors:0 dropped:0 overruns:0 frame:0 > TX packets:664639075 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3040389292 (2.8 GiB) TX bytes:675407553 (644.1 MiB) > > ip6tnl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > NOARP MTU:1460 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) > > 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:3474546933 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3474546933 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1064854296 (1015.5 MiB) TX bytes:1064854296 (1015.5 MiB) > > 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) > > tunl0 Link encap:IPIP Tunnel HWaddr > 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) > > Thanks, > -- > Carsten Otto > carsten at c-otto.de > www.c-otto.de > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin at ICSI.Berkeley.EDU Sun Feb 22 12:07:03 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Sun, 22 Feb 2009 12:07:03 -0800 Subject: [Xorp-users] cand-rp without BSR In-Reply-To: <20090220185043.GB5984@carsten-otto> References: <20090218181948.GE25985@carsten-otto> <200902181909.n1IJ9HlB014837@fruitcake.ICSI.Berkeley.EDU> <20090220185043.GB5984@carsten-otto> Message-ID: <200902222007.n1MK73B0026615@fruitcake.ICSI.Berkeley.EDU> Carsten Otto wrote: > On Wed, Feb 18, 2009 at 11:09:17AM -0800, Pavlin Radoslavov wrote: > > Which XORP version are you using? See file xorp/VERSION. > I cannot figure out how to get the version number, but the files are > from June 2006. I am installing 1.6 right now. > > > If you just configure static-rps and all of them point to the same > > router (for the same group prefix) this is suppose to work. > > I thought so, let's see if 1.6 helps. > > > Please send your XORP config you are not sure. > > Attached. > > > Also, please clarify what you mean by > > " does not act as a RP". > > It does not forward/route/send the multicast data that is being > requesting using PIM. It behaves like these packets are ignored (maybe > because it does not feel responsible). There could be many reasons for that. E.g., the RP must have received PIM-SM Join messages from the downstream PIM routers and/or must have directly connected receivers. Typically, the "show pim join" xorpsh CLI command is a good starting point to investigate those issues. Pavlin From pavlin at ICSI.Berkeley.EDU Sun Feb 22 12:23:20 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Sun, 22 Feb 2009 12:23:20 -0800 Subject: [Xorp-users] cand-rp without BSR In-Reply-To: <20090220185446.GE5984@carsten-otto> References: <20090218181948.GE25985@carsten-otto> <200902181909.n1IJ9HlB014837@fruitcake.ICSI.Berkeley.EDU> <20090220185043.GB5984@carsten-otto> <20090220185156.GD5984@carsten-otto> <20090220185446.GE5984@carsten-otto> Message-ID: <200902222023.n1MKNKoU028489@fruitcake.ICSI.Berkeley.EDU> Carsten Otto wrote: > On Fri, Feb 20, 2009 at 07:51:56PM +0100, Carsten Otto wrote: > > static-rps { > > rp 134.130.56.193 { > > group-prefix 239.254.1.0/24 { > > rp-priority 255 > > } > > group-prefix 239.254.2.0/24 { > > rp-priority 255 > > } > > } > > rp 137.226.39.194 { > > group-prefix 239.254.18.0/24 { > > rp-priority 0 > > } > > } > > rp 137.226.119.114 { > > group-prefix 239.254.16.0/24 { > > rp-priority 0 > > } > > group-prefix 239.254.17.0/24 { > > rp-priority 0 > > } > > } > > } > > (Sorry for the spam, I need more coffee) > > To clarify: 137.226.119.114 is my XORP. The static-rp section of > 137.226.56.193 looks the same, but streaming from my network to that > network does not work. The XORP at 137.226.39.194 is still using a > BSR-nonstatic-configuration and does serve data to 137.226.56.193 (and > my network). In general, all PIM-SM routers (i.e., not only the RPs) in the domain must have same Cand-RP set so they can map to the exactly same RP for each group. In your setup, all your XORP PIM-SM routers must have exactly same cand-rps setup so they all will know that multicast to 239.254.1.0/24 and 239.254.2.0/24 must go to RP 134.130.56.193. The "show pim rps" CLI command should show same result for all routers. In your setup you are using different RPs for different multicast group prefixes, so you need to debug the issue(s) per group prefix. E.g., multicast to 239.254.1.0/24 or 239.254.2.0/24 will behave differently from multicast to 239.254.18.0/24 or to the (239.254.16.0/24, 239.254.17.0/24) prefixes. The "show pim join" command in the XORP routers directly connected to the sender(s) for those groups must show the (S,G) entry for the sender/group and the RP must be 134.130.56.193. If the entry is correct, then (depends on other factors), the source's data packets are either unicast (encapsulated in PIM Registers) to the RP, or are forwarded natively (on the (S,G) entries) directly toward the receivers. If in doubt, please send the output form "show pim join" from the PIM-SM Designated Router for the subnet with the sender (whose traffic is suppose to go to 137.226.56.193). Regards, Pavlin From tom.gibson at ipvidnet.com Wed Feb 25 00:19:34 2009 From: tom.gibson at ipvidnet.com (Tom Gibson) Date: Wed, 25 Feb 2009 00:19:34 -0800 Subject: [Xorp-users] Xorp + Kernel Click on Linux -- Does this work for anyone in recent code? Message-ID: <49A4FF16.5000807@ipvidnet.com> Should the latest Xorp work fine with Kernel Click on Linux? It seems to be broke from what I can tell. Right now using the latest Click all I can get working is the user mode version. Kernel mode just causes Xorp startup to go bad with all kinds of timeout messages. The MFEA and RIB modules seem to hang and not respond. With a minimal config that doesn't enable any protocols or the MFEA / RIB modules it gets a little further but right after saying "no more tasks to do" I start getting these type of errors: > [ 2009/02/24 23:50:35 WARNING xorp_fea LIBXORP ] 10 seconds between calls to EventLoop::run > [ 2009/02/24 23:50:35 ERROR xorp_fea:10743 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive timeout I remember using another version of Click I managed to get it to load with a minimal config (no protocols enabled). Tomorrow I'll test this again and get some more info on which version this was with. I'm new to both Xorp and Click code bases as well as Linux programming and tools like cvs. Can anyone offer guidance on getting this working? Thanks, Tom From ganeshamutha at gmail.com Wed Feb 25 06:30:32 2009 From: ganeshamutha at gmail.com (Ganesh kumar) Date: Wed, 25 Feb 2009 20:00:32 +0530 Subject: [Xorp-users] Booting error. Message-ID: Hi All, I am very new to XORP. I have downloaded latest 1.6 but i could able to compile successfully but i could not run. I created configure file by "-N" mode I took copy of the configuration and i restarted xorp_rtrmgr with -b "saved_boot_file" but i was getting following error and i not able to start the xorp_rtrmgr successfully. I was getting following error. Could any one of you please help me to resolve this issue.. Please. ./xorp_rtrmgr -b myboot.config [ 2009/02/25 19:31:35 INFO xorp_rtrmgr:6446 RTRMGR +249 master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea, mfea4, rib, fib2mrib, igmp, pimsm4 [ 2009/02/25 19:31:35 INFO xorp_rtrmgr:6446 RTRMGR +101 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] MFEA enabled [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI enabled [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI started [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] MFEA enabled [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI enabled [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI started [ 2009/02/25 19:31:37 ERROR xorp_fea:6447 FEA +207 ifconfig_set.cc push_config ] Interface error on dc0: interface not recognized [ 2009/02/25 19:31:37 WARNING xorp_fea XrlFeaTarget ] Handling method for ifmgr/0.1/commit_transaction failed: XrlCmdError 102 Command failed Interface error on dc0: interface not recognized [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Interface error on dc0: interface not recognized [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +261 master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Interface error on dc0: interface not recognized [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +2233 task.cc run_task ] No more tasks to run [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +176 module_manager.cc terminate ] Terminating module: interfaces [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +199 module_manager.cc terminate ] Killing module: interfaces [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +754 module_manager.cc done_cb ] Command "/opt/xorp-1.6/fea/xorp_fea": terminated with signal 15. [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +287 module_manager.cc module_exited ] Module killed during shutdown: interfaces Regards, Ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090225/d26bc36e/attachment.html From nithya.chandrakesan at xorp.net Wed Feb 25 10:42:07 2009 From: nithya.chandrakesan at xorp.net (Nithya Chandrakesan) Date: Wed, 25 Feb 2009 10:42:07 -0800 Subject: [Xorp-users] Booting error. In-Reply-To: References: Message-ID: <1dfe63a80902251042r4b484413of50233298b9e53f9@mail.gmail.com> Hi Ganesh, Could you please send us the config file that you were using to bring up xorp_rtrmgr? Sample config.boot files are available in xorp/rtrmgr/config directory. You need to modify the config files, as per the interface you are using. We will be able to narrow down the issue, by looking at the config file you are using. Also provide us the OS and kernel version. Thanks, Nithya. On Wed, Feb 25, 2009 at 6:30 AM, Ganesh kumar wrote: > Hi All, > > I am very new to XORP. I have downloaded latest 1.6 but i could able to > compile successfully but i could not run. > > I created configure file by "-N" mode I took copy of the configuration and > i restarted xorp_rtrmgr with -b "saved_boot_file" but i was getting > following error and i not able to start the xorp_rtrmgr successfully. I was > getting following error. > > Could any one of you please help me to resolve this issue.. Please. > > > > ./xorp_rtrmgr -b myboot.config > [ 2009/02/25 19:31:35 INFO xorp_rtrmgr:6446 RTRMGR +249 > master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea, > mfea4, rib, fib2mrib, igmp, pimsm4 > [ 2009/02/25 19:31:35 INFO xorp_rtrmgr:6446 RTRMGR +101 module_manager.cc > execute ] Executing module: interfaces (fea/xorp_fea) > [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] MFEA enabled > [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI enabled > [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI started > [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] MFEA enabled > [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI enabled > [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI started > [ 2009/02/25 19:31:37 ERROR xorp_fea:6447 FEA +207 ifconfig_set.cc > push_config ] Interface error on dc0: interface not recognized > [ 2009/02/25 19:31:37 WARNING xorp_fea XrlFeaTarget ] Handling method for > ifmgr/0.1/commit_transaction failed: XrlCmdError 102 Command failed > Interface error on dc0: interface not recognized > [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +691 > master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed > Interface error on dc0: interface not recognized > [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +261 > master_conf_tree.cc config_done ] Configuration failed: 102 Command failed > Interface error on dc0: interface not recognized > [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +2233 task.cc run_task > ] No more tasks to run > [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +176 module_manager.cc > terminate ] Terminating module: interfaces > [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +199 module_manager.cc > terminate ] Killing module: interfaces > [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +754 module_manager.cc > done_cb ] Command "/opt/xorp-1.6/fea/xorp_fea": terminated with signal 15. > [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +287 module_manager.cc > module_exited ] Module killed during shutdown: interfaces > > > > > Regards, > Ganesh > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090225/38095ad6/attachment.html From ganeshamutha at gmail.com Wed Feb 25 21:26:52 2009 From: ganeshamutha at gmail.com (Ganesh kumar) Date: Thu, 26 Feb 2009 10:56:52 +0530 Subject: [Xorp-users] Booting error. In-Reply-To: <1dfe63a80902251042r4b484413of50233298b9e53f9@mail.gmail.com> References: <1dfe63a80902251042r4b484413of50233298b9e53f9@mail.gmail.com> Message-ID: Hi Nithya and Tom, Thank you very much for your reply, I was created some configuration by running oxrp_rtrmgr -N and xorpsh in another terminal. i managed to create Multicast IGMPv3 in my network interface. (it was detected only one interface but i am having two NIC though i added one more interface manually). Using show -all i got information of configuration. i just simply copied those details and pasted in myboot.config i attached those detail with you. when i rebooted with (-b myboot.config) i got only the error message. My Linux Kernel : 2.6.21-1.3194.fc7 My needs are: *) Need to create IPv4 and IPv6 mutlicast (SSM, ASM) router. If you provide direct solution with XORP it would be much much much helpful. I am expecting your helpful reply. Thanks very much in advance. Regards, Ganesh 2009/2/26 Nithya Chandrakesan > Hi Ganesh, > > Could you please send us the config file that you were using to bring up > xorp_rtrmgr? > > Sample config.boot files are available in xorp/rtrmgr/config directory. You > need to modify the config files, as per the interface you are using. > We will be able to narrow down the issue, by looking at the config file you > are using. > Also provide us the OS and kernel version. > > Thanks, > Nithya. > > > > On Wed, Feb 25, 2009 at 6:30 AM, Ganesh kumar wrote: > >> Hi All, >> >> I am very new to XORP. I have downloaded latest 1.6 but i could able to >> compile successfully but i could not run. >> >> I created configure file by "-N" mode I took copy of the configuration and >> i restarted xorp_rtrmgr with -b "saved_boot_file" but i was getting >> following error and i not able to start the xorp_rtrmgr successfully. I was >> getting following error. >> >> Could any one of you please help me to resolve this issue.. Please. >> >> >> >> ./xorp_rtrmgr -b myboot.config >> [ 2009/02/25 19:31:35 INFO xorp_rtrmgr:6446 RTRMGR +249 >> master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea, >> mfea4, rib, fib2mrib, igmp, pimsm4 >> [ 2009/02/25 19:31:35 INFO xorp_rtrmgr:6446 RTRMGR +101 module_manager.cc >> execute ] Executing module: interfaces (fea/xorp_fea) >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] MFEA enabled >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI enabled >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI started >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] MFEA enabled >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI enabled >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI started >> [ 2009/02/25 19:31:37 ERROR xorp_fea:6447 FEA +207 ifconfig_set.cc >> push_config ] Interface error on dc0: interface not recognized >> [ 2009/02/25 19:31:37 WARNING xorp_fea XrlFeaTarget ] Handling method for >> ifmgr/0.1/commit_transaction failed: XrlCmdError 102 Command failed >> Interface error on dc0: interface not recognized >> [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +691 >> master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed >> Interface error on dc0: interface not recognized >> [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +261 >> master_conf_tree.cc config_done ] Configuration failed: 102 Command failed >> Interface error on dc0: interface not recognized >> [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +2233 task.cc run_task >> ] No more tasks to run >> [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +176 module_manager.cc >> terminate ] Terminating module: interfaces >> [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +199 module_manager.cc >> terminate ] Killing module: interfaces >> [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +754 >> module_manager.cc done_cb ] Command "/opt/xorp-1.6/fea/xorp_fea": terminated >> with signal 15. >> [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +287 module_manager.cc >> module_exited ] Module killed during shutdown: interfaces >> >> >> >> >> Regards, >> Ganesh >> >> _______________________________________________ >> Xorp-users mailing list >> Xorp-users at xorp.org >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090226/bd51db0b/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: myboot.config Type: application/octet-stream Size: 3509 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090226/bd51db0b/attachment.obj From lherve at interfaceconcept.com Thu Feb 26 02:55:23 2009 From: lherve at interfaceconcept.com (=?iso-8859-1?Q?Herv=E9_L=E9onard?=) Date: Thu, 26 Feb 2009 11:55:23 +0100 Subject: [Xorp-users] mfea failed when I configure VLAN Message-ID: <5D90A18A4A1F4F9E955492E60FF10F96@lehe6600v> Hello everybody, I'm trying to do multicast routing with differents VLANs on same physical interface eth0 on Linux. The unicast routing works very well but when i put "plumbing mfea4" in configuration I have a failer when I commit. I test the mfea4 without vlan and it works. It is only when I have configured vlan with vconfig that mfea4 failed when I commit in xorpsh configure mode. Thanks very much in advance for your help or any ideas. Here is some details: Linux kernel 2.6.24 xorp-1.5 and xorp-1.6 (I have tested both and I have the same issue). here is what I do: labo at labo-laptop> show interfaces eth0/eth0: Flags: mtu 1500 speed 10 Mbps inet6 fe80::21a:4bff:fe8d:5333 prefixlen 64 inet 192.168.1.7 subnet 192.168.1.0/24 physical index 2 ether 0:1a:4b:8d:53:33 eth0/eth0.2: Flags: mtu 1500 speed 10 Mbps inet6 fe80::21a:4bff:fe8d:5333 prefixlen 64 inet 192.168.2.7 subnet 192.168.2.0/24 physical index 3 ether 0:1a:4b:8d:53:33 vlan: 2 parent interface: eth0 labo at labo-laptop> configure Entering configuration mode. There are no other users in configuration mode. [edit] labo at labo-laptop# set plumbing mfe `mfe' is ambiguous. Possible completions: mfea4 Configure the IPv4 Multicast Forwarding Engine Abstraction mfea6 Configure the IPv6 Multicast Forwarding Engine Abstraction labo at labo-laptop# set plumbing mfea4 [edit] labo at labo-laptop# show interfaces { interface eth0 { default-system-config } } > plumbing { > mfea4 { > } > } [edit] labo at labo-laptop# commit Commit Failed Can't startup process mfea4[edit] labo at labo-laptop# here is the log of xorp: [ 2009/02/26 10:53:52 INFO xorp_rtrmgr:16736 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) [ 2009/02/26 10:53:56 INFO xorp_rtrmgr:16736 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2009/02/26 10:54:02 INFO xorp_rtrmgr:16736 RTRMGR +101 module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea) [ 2009/02/26 10:54:02 FATAL xorp_fea:16737 MFEA +539 mfea_node.cc vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed [ 2009/02/26 10:54:02 ERROR xorp_rtrmgr:16736 RTRMGR +2003 task.cc task_fail ] Shutting down fatally wounded process (mfea4) [ 2009/02/26 10:54:02 INFO xorp_rtrmgr:16736 RTRMGR +176 module_manager.cc terminate ] Terminating module: mfea4 [ 2009/02/26 10:54:02 ERROR xorp_rtrmgr:16736 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: Can't startup process mfea4 Best regards, Leonard From pavlin at ICSI.Berkeley.EDU Thu Feb 26 15:52:23 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Thu, 26 Feb 2009 15:52:23 -0800 Subject: [Xorp-users] Xorp + Kernel Click on Linux -- Does this work for anyone in recent code? In-Reply-To: <49A4FF16.5000807@ipvidnet.com> References: <49A4FF16.5000807@ipvidnet.com> Message-ID: <200902262352.n1QNqN2f011365@fruitcake.ICSI.Berkeley.EDU> Tom, Unfortunately, the Click testing and support has fallen behind the rest of the system. It has been a while since we tested them together, and most likely it was with an older version of Click (1.4.x). We are planning to add-back the Click support in the future. In the mean time you can try XORP-1.6 with some of the older Click versions (maybe Click-1.4.3?), though I don't know whether this will actually work. If this doesn't work, you might want to try some of the older XORP releases that should work with Click. I believe I have used XORP-1.4 with Click-1.4.1. If other folks have more recent experience please speak up. Thanks, Pavlin P.S. Could you submit a Bugzilla entry with the issue, and include your XORP config file, so we can use that entry to track the problem. Tom Gibson wrote: > Should the latest Xorp work fine with Kernel Click on Linux? It seems > to be broke from what I can tell. > > Right now using the latest Click all I can get working is the user mode > version. Kernel mode just causes Xorp startup to go bad with all kinds > of timeout messages. The MFEA and RIB modules seem to hang and not > respond. With a minimal config that doesn't enable any protocols or the > MFEA / RIB modules it gets a little further but right after saying "no > more tasks to do" I start getting these type of errors: > > > [ 2009/02/24 23:50:35 WARNING xorp_fea LIBXORP ] 10 seconds between calls to EventLoop::run > > [ 2009/02/24 23:50:35 ERROR xorp_fea:10743 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive timeout > > I remember using another version of Click I managed to get it to load > with a minimal config (no protocols enabled). Tomorrow I'll test this > again and get some more info on which version this was with. > > I'm new to both Xorp and Click code bases as well as Linux programming > and tools like cvs. Can anyone offer guidance on getting this working? > > Thanks, > > Tom > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin at ICSI.Berkeley.EDU Thu Feb 26 16:05:39 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Thu, 26 Feb 2009 16:05:39 -0800 Subject: [Xorp-users] Booting error. In-Reply-To: References: <1dfe63a80902251042r4b484413of50233298b9e53f9@mail.gmail.com> Message-ID: <200902270005.n1R05d9u012272@fruitcake.ICSI.Berkeley.EDU> Ganesh, Please have a look in the xorp/rtrmgr/config/multicast4.boot sample configuration file. It has the basic setup you need to enable multicast routing, but obviously you need to edit that file before starting XORP: the interface names, the IP addresses, and the static RPs info. If you are not sure about some of the configuration options please check with the XORP User Manual: Chapter 14 for IGMP and Chapter 15 for PIM-SM. Also, you must enable multicast routing in your kernel. Please see Section 15.3 for the Linux-specific kernel configuration options. Hope that helps, Pavlin Ganesh kumar wrote: > Hi Nithya and Tom, > > Thank you very much for your reply, > > I was created some configuration by running oxrp_rtrmgr -N and xorpsh in > another terminal. > > i managed to create Multicast IGMPv3 in my network interface. (it was > detected only one interface but i am having two NIC though i added one more > interface manually). > > Using show -all i got information of configuration. i just simply copied > those details and pasted in myboot.config i attached those detail with you. > > when i rebooted with (-b myboot.config) i got only the error message. > > My Linux Kernel : 2.6.21-1.3194.fc7 > > My needs are: > > *) Need to create IPv4 and IPv6 mutlicast (SSM, ASM) router. If you > provide direct solution with XORP it would be much much much helpful. > > I am expecting your helpful reply. > > Thanks very much in advance. > > Regards, > Ganesh > > > 2009/2/26 Nithya Chandrakesan > > > Hi Ganesh, > > > > Could you please send us the config file that you were using to bring up > > xorp_rtrmgr? > > > > Sample config.boot files are available in xorp/rtrmgr/config directory. You > > need to modify the config files, as per the interface you are using. > > We will be able to narrow down the issue, by looking at the config file you > > are using. > > Also provide us the OS and kernel version. > > > > Thanks, > > Nithya. > > > > > > > > On Wed, Feb 25, 2009 at 6:30 AM, Ganesh kumar wrote: > > > >> Hi All, > >> > >> I am very new to XORP. I have downloaded latest 1.6 but i could able to > >> compile successfully but i could not run. > >> > >> I created configure file by "-N" mode I took copy of the configuration and > >> i restarted xorp_rtrmgr with -b "saved_boot_file" but i was getting > >> following error and i not able to start the xorp_rtrmgr successfully. I was > >> getting following error. > >> > >> Could any one of you please help me to resolve this issue.. Please. > >> > >> > >> > >> ./xorp_rtrmgr -b myboot.config > >> [ 2009/02/25 19:31:35 INFO xorp_rtrmgr:6446 RTRMGR +249 > >> master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea, > >> mfea4, rib, fib2mrib, igmp, pimsm4 > >> [ 2009/02/25 19:31:35 INFO xorp_rtrmgr:6446 RTRMGR +101 module_manager.cc > >> execute ] Executing module: interfaces (fea/xorp_fea) > >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] MFEA enabled > >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI enabled > >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI started > >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] MFEA enabled > >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI enabled > >> [ 2009/02/25 19:31:36 INFO xorp_fea MFEA ] CLI started > >> [ 2009/02/25 19:31:37 ERROR xorp_fea:6447 FEA +207 ifconfig_set.cc > >> push_config ] Interface error on dc0: interface not recognized > >> [ 2009/02/25 19:31:37 WARNING xorp_fea XrlFeaTarget ] Handling method for > >> ifmgr/0.1/commit_transaction failed: XrlCmdError 102 Command failed > >> Interface error on dc0: interface not recognized > >> [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +691 > >> master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed > >> Interface error on dc0: interface not recognized > >> [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +261 > >> master_conf_tree.cc config_done ] Configuration failed: 102 Command failed > >> Interface error on dc0: interface not recognized > >> [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +2233 task.cc run_task > >> ] No more tasks to run > >> [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +176 module_manager.cc > >> terminate ] Terminating module: interfaces > >> [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +199 module_manager.cc > >> terminate ] Killing module: interfaces > >> [ 2009/02/25 19:31:37 ERROR xorp_rtrmgr:6446 RTRMGR +754 > >> module_manager.cc done_cb ] Command "/opt/xorp-1.6/fea/xorp_fea": terminated > >> with signal 15. > >> [ 2009/02/25 19:31:37 INFO xorp_rtrmgr:6446 RTRMGR +287 module_manager.cc > >> module_exited ] Module killed during shutdown: interfaces > >> > >> > >> > >> > >> Regards, > >> Ganesh > >> > >> _______________________________________________ > >> Xorp-users mailing list > >> Xorp-users at xorp.org > >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > >> > >> > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin at ICSI.Berkeley.EDU Thu Feb 26 16:12:08 2009 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Thu, 26 Feb 2009 16:12:08 -0800 Subject: [Xorp-users] mfea failed when I configure VLAN In-Reply-To: <5D90A18A4A1F4F9E955492E60FF10F96@lehe6600v> References: <5D90A18A4A1F4F9E955492E60FF10F96@lehe6600v> Message-ID: <200902270012.n1R0C87j012921@fruitcake.ICSI.Berkeley.EDU> It sounds like a bug in the FEA/MFEA. To get around it, could you try to include complete mfea configuration with the eth0 and the register_vif interfaces/vifs configured and enabled (e.g., see the xorp/rtrmgr/config/multicast4.boot sample config file). If this doesn't work, then please try to treat the VLAN as a complete separate interface (from XORP perspective), and provide the complete IP address config. E.g. interfaces { interface eth0 { vif eth0 { address 10.10.10.10 { prefix-length: 24 } } } interface vlan2 { vif vlan2 { address 10.20.20.20 { prefix-length: 24 } } } } and then use eth0/eth0 and vlan2/vlan2 in the rest of the XORP config. Hope that helps, Pavlin Herv? L?onard wrote: > > Hello everybody, > > I'm trying to do multicast routing with differents VLANs on same physical > interface eth0 on Linux. > The unicast routing works very well but when i put "plumbing mfea4" in > configuration I have a failer when I commit. > I test the mfea4 without vlan and it works. > > It is only when I have configured vlan with vconfig that mfea4 failed when I > commit in xorpsh configure mode. > > Thanks very much in advance for your help or any ideas. > > Here is some details: > Linux kernel 2.6.24 > xorp-1.5 and xorp-1.6 (I have tested both and I have the same issue). > > here is what I do: > labo at labo-laptop> show interfaces > eth0/eth0: Flags: mtu 1500 speed 10 Mbps > inet6 fe80::21a:4bff:fe8d:5333 prefixlen 64 > inet 192.168.1.7 subnet 192.168.1.0/24 > physical index 2 > ether 0:1a:4b:8d:53:33 > eth0/eth0.2: Flags: mtu 1500 speed 10 Mbps > inet6 fe80::21a:4bff:fe8d:5333 prefixlen 64 > inet 192.168.2.7 subnet 192.168.2.0/24 > physical index 3 > ether 0:1a:4b:8d:53:33 > vlan: 2 parent interface: eth0 > labo at labo-laptop> configure > Entering configuration mode. > There are no other users in configuration mode. > [edit] > labo at labo-laptop# set plumbing mfe > `mfe' is ambiguous. > Possible completions: > mfea4 Configure the IPv4 Multicast Forwarding Engine > Abstraction > mfea6 Configure the IPv6 Multicast Forwarding Engine > Abstraction > labo at labo-laptop# set plumbing mfea4 > [edit] > labo at labo-laptop# show > interfaces { > interface eth0 { > default-system-config > } > } > > plumbing { > > mfea4 { > > } > > } > > [edit] > labo at labo-laptop# commit > Commit Failed > Can't startup process mfea4[edit] > labo at labo-laptop# > > > here is the log of xorp: > [ 2009/02/26 10:53:52 INFO xorp_rtrmgr:16736 RTRMGR +101 module_manager.cc > execute ] Executing module: firewall (fea/xorp_fea) > [ 2009/02/26 10:53:56 INFO xorp_rtrmgr:16736 RTRMGR +101 module_manager.cc > execute ] Executing module: fea (fea/xorp_fea) > [ 2009/02/26 10:54:02 INFO xorp_rtrmgr:16736 RTRMGR +101 module_manager.cc > execute ] Executing module: mfea4 (fea/xorp_fea) > [ 2009/02/26 10:54:02 FATAL xorp_fea:16737 MFEA +539 mfea_node.cc > vif_update ] Assertion (vif_index != Vif::VIF_INDEX_INVALID) failed > [ 2009/02/26 10:54:02 ERROR xorp_rtrmgr:16736 RTRMGR +2003 task.cc > task_fail ] Shutting down fatally wounded process (mfea4) > [ 2009/02/26 10:54:02 INFO xorp_rtrmgr:16736 RTRMGR +176 module_manager.cc > terminate ] Terminating module: mfea4 > [ 2009/02/26 10:54:02 ERROR xorp_rtrmgr:16736 RTRMGR +691 > master_conf_tree.cc commit_pass2_done ] Commit failed: Can't startup process > mfea4 > > > Best regards, > Leonard > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From bhavin81 at iitb.ac.in Sat Feb 28 22:02:07 2009 From: bhavin81 at iitb.ac.in (bhavin81 at iitb.ac.in) Date: Sun, 1 Mar 2009 11:32:07 +0530 (IST) Subject: [Xorp-users] help: getting the error no finder? In-Reply-To: References: Message-ID: <026537793ff8e6e43e0ddac9a83686a1.squirrel@gpo.iitb.ac.in> Hell friends, I am new to xorp. I have compiled xorp-1.6 on freebsd 7.1. I wrote command ./xropsh (in rtrmanager directory) and got the following error messagees: (A) Error XORPSH:44998 RTRMGR +96 xorpsh_main.cc wait_for xrl_router_ready Xrlrouter failes. No Finder? (B) Error XORPSH:44998 RTRMGR +906 xorpsh_main.cc xorpsh exiting due to an init error: failed to connect to router manager. I have not done anyother configuration in config file up to now. Please help. Thanks in advance for providing help. regards, Bhavin.