From globalcouchsurfer at gmail.com Wed Dec 2 02:25:53 2009 From: globalcouchsurfer at gmail.com (CouchSurfer) Date: Wed, 2 Dec 2009 10:25:53 +0000 Subject: [Xorp-users] Policy Help Needed Message-ID: <2148c4de0912020225r720807fcr7e01228b67a66053@mail.gmail.com> Hi all, I am trying to configure an xorp router to filter out some routes via certain paths. Hopefully someone can help me out. I have one xorp router R0 with two interfaces. Each interface is connected to a BGP peer Ra and Rb. I received no med numbers from these peers. Each of these peer advertise the routes the same destinations D1/mask1 and D2/mask2. I want configure R0 so that it only accepts routes to D1/mask1 from Ra and routes to D2/mask2from Rb, and reject otherwise. At the moment I have a policy that looks like term 1 { from { network4: D2/mask2 } from { nexthop4: Ra } then { reject { } } } Thanks in advance -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091202/7f4d54c7/attachment.html From yindong1982 at gmail.com Wed Dec 2 08:24:23 2009 From: yindong1982 at gmail.com (dong yin) Date: Wed, 2 Dec 2009 08:24:23 -0800 Subject: [Xorp-users] Does xorp support remote Click running as forwarding node? Message-ID: Hi, Does Xorp(V1.6) support remote Click running as forwarding node? Initialize and update one forwarding node in a remote machine. Best, Dong -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091202/1dcceae2/attachment.html From bms at incunabulum.net Thu Dec 3 00:06:26 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 03 Dec 2009 08:06:26 +0000 Subject: [Xorp-users] Does xorp support remote Click running as forwarding node? In-Reply-To: References: Message-ID: <4B177182.30108@incunabulum.net> dong yin wrote: > Hi, > > Does Xorp(V1.6) support remote Click running as forwarding node? > Initialize and update one forwarding node in a remote machine. > To answer your question: In theory, yes, as long as the FEA process is running on the same machine as Click. A few words on the state of the Click code: Currently, the Click support does not have ongoing support in the public branch going forward, and really needs a committed maintainer. So far, there have been no volunteers. If Click support is strongly desired by XORP users 'out there', someone has to take responsibility for maintaining it. I'm not really in a position to maintain it (I don't use Click, it's not part of my remit really), I can only try to look at Click related patches on a best-effort basis, and I'm usually tied up elsewhere, as you can see. I appreciate people are looking for a stable release on which to build things. What's in SVN trunk has to be considered the active line of development; this makes it very difficult to support previous XORP releases, unless people are willing to come forward and volunteer to maintain previous releases in SVN, as branches. thanks, BMS From bms at incunabulum.net Thu Dec 3 13:40:08 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 03 Dec 2009 21:40:08 +0000 Subject: [Xorp-users] End-of-life on Windows support in XORP community branch In-Reply-To: <4A709497.90001@incunabulum.net> References: <4A537C10.2000204@incunabulum.net> <4A709497.90001@incunabulum.net> Message-ID: <4B183038.60404@incunabulum.net> Hi, No-one has come forward to support the Windows port, so I'm going to de-orbit burn it for 1.7. I've got patches lined up to do this. This should make life a bit easier for developers. Now that Windows 7 has finally been released, it should be a bit easier for someone to look at their new APIs. Windows IPv6 support, for example, is a bit more mature now. In any event, the Windows related changes will be in SVN change history, as well as the old release tarballs. A from-scratch approach might be good. The hardest part of porting XORP to Windows, was in tricking Winsock to give us packets without having to use service threads. cheers, BMS From mohd.arif at nechclst.in Sat Dec 5 20:32:06 2009 From: mohd.arif at nechclst.in (Mohd Arif) Date: Sun, 6 Dec 2009 10:02:06 +0530 Subject: [Xorp-users] Urgent Queries about XORP package Message-ID: <0A8CFEC45B7F4C419F7543867C47442301497D62@mailserver.nechclst.in> Dear All, I am a new user of XORP. I am still collecting information about XORP. I would be thankful to xorp mailing list for the clarifications: Query #1: Does XORP supports PPC architecture? If yes, what options are needed by "configure" to cross compile the source code? If no, then its a bad news :( Query #2: Is it possible to compile just PIM-SM in XORP software package? Query #3: Does PIM-SM have any dependency on other protocols supported by XORP? Query #3: Are XORP and QUAGGA compatible? I mean to say that is it possible to use OSPF implementation of QUAGGA and PIM-SM implementation of XORP together? Your initial inputs will help me to gain confidence. Thanks in advance. Best Regards, Mohd. Arif DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . ----------------------------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091206/9af11287/attachment.html From bms at incunabulum.net Mon Dec 7 10:48:21 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 07 Dec 2009 18:48:21 +0000 Subject: [Xorp-users] Urgent Queries about XORP package In-Reply-To: <0A8CFEC45B7F4C419F7543867C47442301497D62@mailserver.nechclst.in> References: <0A8CFEC45B7F4C419F7543867C47442301497D62@mailserver.nechclst.in> Message-ID: <4B1D4DF5.20602@incunabulum.net> Mohd Arif wrote: > > Dear All, > I am a new user of XORP. I am still collecting information about XORP. > I would be thankful to xorp mailing list for the clarifications: > > Query #1: Does XORP supports PPC architecture? If yes, what options > are needed by "configure" to cross compile the source code? If no, > then its a bad news :( > Cross-compilation currently hasn't been tested with the SCons build. You are welcome to contribute to the ongoing development effort of getting cross compilation to work with the new build system. > > Query #2: Is it possible to compile just PIM-SM in XORP software package? > Yes, if the SCons build is appropriately patched to build only what's needed. Patches to do this would be gratefully received. > > Query #3: Does PIM-SM have any dependency on other protocols supported > by XORP? > Yes, it requires the FEA, IGMP, MLD and libmrt components. > > > Query #3: Are XORP and QUAGGA compatible? I mean to say that is it > possible to use OSPF implementation of QUAGGA and PIM-SM > implementation of XORP together? > They are not designed to be interoperable in this way. However, you may be able to get this configuration working by using the kernel as an indirect RIB. This is of course not going to scale very well if you have a lot of routes, or if you need to use route policies. It is also a configuration that can't officially be supported; if you try this, you're on your own. I can't think of any singular advantage offered by using Quagga's OSPF implementation over what's already in the tree. > Your initial inputs will help me to gain confidence. > New contributors to the project are welcome. Do you plan to submit code? thanks, BMS From bms at incunabulum.net Mon Dec 7 10:59:44 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 07 Dec 2009 18:59:44 +0000 Subject: [Xorp-users] Urgent Queries about XORP package In-Reply-To: <4B1D4DF5.20602@incunabulum.net> References: <0A8CFEC45B7F4C419F7543867C47442301497D62@mailserver.nechclst.in> <4B1D4DF5.20602@incunabulum.net> Message-ID: <4B1D50A0.2060209@incunabulum.net> Bruce Simpson wrote: > Mohd Arif wrote: > >> Dear All, >> I am a new user of XORP. I am still collecting information about XORP. >> I would be thankful to xorp mailing list for the clarifications: >> >> Query #1: Does XORP supports PPC architecture? If yes, what options >> are needed by "configure" to cross compile the source code? If no, >> then its a bad news :( >> >> > > Cross-compilation currently hasn't been tested with the SCons build. > > You are welcome to contribute to the ongoing development effort of > getting cross compilation to work with the new build system. > P.S. The community code which is available, is largely agnostic of the platform you compile it for. XORP itself should build fine when targetted for the PowerPC architecture, providing you have the appropriate libraries. We just cut over to using Boost in SVN trunk, so you will need to make sure your cross build can supply that. If you do have a problem with a cross build, and the issue is code compliance or portability, within the XORP tree itself, then please raise a Trac ticket about it, preferably with a brief test case and your patch to fix the issue. Support in the community forum, for cross-compilation issues which arise outside of the XORP tree, can't be guaranteed. If you're lucky, post and ask here; another user may be using the same build configuration as you. If you are using a commercial toolchain, it's best to raise these sorts of questions directly through your vendor's support channel. If you are having difficulties building a staging area with appropriate libraries, it's difficult to give general advice about solving problems, as there is now such a wide variety of toolchains for embedded development out there (OpenWRT, OE etc). thanks, BMS From mohd.arif at nechclst.in Mon Dec 7 11:27:45 2009 From: mohd.arif at nechclst.in (Mohd Arif) Date: Tue, 8 Dec 2009 00:57:45 +0530 Subject: [Xorp-users] Urgent Queries about XORP package References: <0A8CFEC45B7F4C419F7543867C47442301497D62@mailserver.nechclst.in> <4B1D4DF5.20602@incunabulum.net> Message-ID: <0A8CFEC45B7F4C419F7543867C47442301497D64@mailserver.nechclst.in> Hi, Thanks for the kind words. I look forward to the contribution in XORP in whatever small way i can. Regarding interoperability of quagga and xorp: "As PIM is "protocol independent", so my understanding is that PIM make use of routing table managed by any unicast routing protocol, lets say ospf. It doesn't matter that the unicast routing protocol is an implementation of quagga or xorp because PIM-SM just refer to kernel routing table regardless of the fact that which unicast routing protocol are creating entries in routing table." With this understanding, i concluded that quagga implementation of ospf and xorp's PIM-SM can be used together. Is my understanding correct? Thanks in advance. ________________________________ From: Bruce Simpson [mailto:bms at incunabulum.net] Sent: Tue 12/8/2009 12:18 AM To: Mohd Arif Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] Urgent Queries about XORP package Mohd Arif wrote: > > Dear All, > I am a new user of XORP. I am still collecting information about XORP. > I would be thankful to xorp mailing list for the clarifications: > > Query #1: Does XORP supports PPC architecture? If yes, what options > are needed by "configure" to cross compile the source code? If no, > then its a bad news :( > Cross-compilation currently hasn't been tested with the SCons build. You are welcome to contribute to the ongoing development effort of getting cross compilation to work with the new build system. > > Query #2: Is it possible to compile just PIM-SM in XORP software package? > Yes, if the SCons build is appropriately patched to build only what's needed. Patches to do this would be gratefully received. > > Query #3: Does PIM-SM have any dependency on other protocols supported > by XORP? > Yes, it requires the FEA, IGMP, MLD and libmrt components. > > > Query #3: Are XORP and QUAGGA compatible? I mean to say that is it > possible to use OSPF implementation of QUAGGA and PIM-SM > implementation of XORP together? > They are not designed to be interoperable in this way. However, you may be able to get this configuration working by using the kernel as an indirect RIB. This is of course not going to scale very well if you have a lot of routes, or if you need to use route policies. It is also a configuration that can't officially be supported; if you try this, you're on your own. I can't think of any singular advantage offered by using Quagga's OSPF implementation over what's already in the tree. > Your initial inputs will help me to gain confidence. > New contributors to the project are welcome. Do you plan to submit code? thanks, BMS DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . ----------------------------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091208/f35394d0/attachment.html From esj at cs.fiu.edu Mon Dec 7 14:55:22 2009 From: esj at cs.fiu.edu (Eric S. Johnson) Date: Mon, 07 Dec 2009 17:55:22 -0500 Subject: [Xorp-users] cost of passive ospf interfaces is zero? Message-ID: <20091207225522.D54ABB883A7@cheetah.cs.fiu.edu> This may be me just misunderstanding something, but... With zebra and cisco routers if you have an interface set to "passive" but the network configured in the router ospf stanza, the network gets advertised (stub) with the cost as specified in the "ip ospf cost XXX" in the interface stanza. With xorp, if I set the network as passive the network is advertised with a cost of 0. IE: (forgive the ascii art :) another router (eth0=10.11.1.2) <- net 10.11.1.0/24 -> (10.11.1.1=eth0) problem router (eth1=10.11.0.1) <- net 10.11.0.0/24 -> If "problem router is a quagga (or IOS router, assume correct syntax difference) and is configured: interface eth0 ip address 10.11.1.1/24 ip ospf cost 5000 interface eth1 ip address 10.11.0.1/24 ip ospf cost 5000 router ospf network 10.11.1.0/24 area 1 network 10.11.0.0/24 area 1 passive-interface eth1 Then "another router" sees the cost to 10.11.0.0/24 as 5000 plus the cost out "another router"'s eth0. But if "problem router" is xorp with the ospf4 stanza looking like this: protocols { ospf4 { router-id: 10.11.0.1 area 0.0.0.1 { interface eth0 { vif "eth0" { address 10.11.1.1 { priority: 0 interface-cost: 5000 } } } interface eth1 { vif "eth1" { address 10.11.0.1 { priority: 0 interface-cost: 5000 passive { disable: false host: false } } } } } } Then "another router" sees the cost to 10.11.0.0/24 as ONLY the cost out "another router"'s eth0. The cost of the stub network is advertised by "problem router" as 0. I verified this with tcpdump. If the interface is set to passive the LSA sent sets the cost to 0. Now, granted, if network 10.11.0.0/24 is *REALLY* a stub network the cost to it shouldn't matter, but in my environment, it is not really a stub area, I just don't want OSPF to build adjacenies on it. And the behavior is different then other implementations.... Is this a bug? A feature? A sign for me to stop mis-using the concept of stub networks? Thoughts? E From jorn.rikkers at nl.thalesgroup.com Mon Dec 7 22:37:28 2009 From: jorn.rikkers at nl.thalesgroup.com (Rikkers Jorn) Date: Tue, 08 Dec 2009 07:37:28 +0100 Subject: [Xorp-users] Urgent Queries about XORP package In-Reply-To: <0A8CFEC45B7F4C419F7543867C47442301497D64@mailserver.nechclst.in> References: <0A8CFEC45B7F4C419F7543867C47442301497D62@mailserver.nechclst.in> <4B1D4DF5.20602@incunabulum.net> <0A8CFEC45B7F4C419F7543867C47442301497D64@mailserver.nechclst.in> Message-ID: <4B1DF428.50708@nl.thalesgroup.com> Hi Mohd Arif, You are correct. I've succesfully used the two together: Quagga's OSPF and XORP's PIM-SM and IGMP. Regards, Jorn On 07-12-2009 20:27, Mohd Arif wrote: > Hi, Thanks for the kind words. > I look forward to the contribution in XORP in whatever small way i can. > Regarding interoperability of quagga and xorp: > "As PIM is "protocol independent", so my understanding is that PIM > make use of routing table managed by any unicast routing protocol, > lets say ospf. > It doesn't matter that the unicast routing protocol is an > implementation of quagga or xorp because PIM-SM just refer to kernel > routing table regardless of the fact that which unicast routing > protocol are creating entries in routing table." > With this understanding, i concluded that quagga implementation of > ospf and xorp's PIM-SM can be used together. > Is my understanding correct? > > Thanks in advance. > > ------------------------------------------------------------------------ > *From:* Bruce Simpson [mailto:bms at incunabulum.net] > *Sent:* Tue 12/8/2009 12:18 AM > *To:* Mohd Arif > *Cc:* xorp-users at xorp.org > *Subject:* Re: [Xorp-users] Urgent Queries about XORP package > > Mohd Arif wrote: > > > > Dear All, > > I am a new user of XORP. I am still collecting information about XORP. > > I would be thankful to xorp mailing list for the clarifications: > > > > Query #1: Does XORP supports PPC architecture? If yes, what options > > are needed by "configure" to cross compile the source code? If no, > > then its a bad news :( > > > > Cross-compilation currently hasn't been tested with the SCons build. > > You are welcome to contribute to the ongoing development effort of > getting cross compilation to work with the new build system. > > > > > Query #2: Is it possible to compile just PIM-SM in XORP software > package? > > > > Yes, if the SCons build is appropriately patched to build only what's > needed. > > Patches to do this would be gratefully received. > > > > > Query #3: Does PIM-SM have any dependency on other protocols supported > > by XORP? > > > > Yes, it requires the FEA, IGMP, MLD and libmrt components. > > > > > > Query #3: Are XORP and QUAGGA compatible? I mean to say that is it > > possible to use OSPF implementation of QUAGGA and PIM-SM > > implementation of XORP together? > > > > They are not designed to be interoperable in this way. > > However, you may be able to get this configuration working by using the > kernel as an indirect RIB. This is of course not going to scale very > well if you have a lot of routes, or if you need to use route policies. > > It is also a configuration that can't officially be supported; if you > try this, you're on your own. > > I can't think of any singular advantage offered by using Quagga's OSPF > implementation over what's already in the tree. > > > Your initial inputs will help me to gain confidence. > > > > New contributors to the project are welcome. Do you plan to submit code? > > thanks, > BMS > > DISCLAIMER: > ----------------------------------------------------------------------------------------------------------------------- > The contents of this e-mail and any attachment(s) are confidential and > intended > for the named recipient(s) only. > It shall not attach any liability on the originator or NECHCL or its > affiliates. Any views or opinions presented in > this email are solely those of the author and may not necessarily reflect the > opinions of NECHCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, modification, > distribution and / or publication of > this message without the prior written consent of the author of this e-mail is > strictly prohibited. If you have > received this email in error please delete it and notify the sender > immediately. . > ----------------------------------------------------------------------------------------------------------------------- > ------------------------------------------------------------------------ > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > -- Met vriendelijke groet, Jorn Rikkers *This message contains Unclassified information* ------------------------------------------------------------------------------------------------------------ Disclaimer: If you are not the intended recipient of this email, please notify the sender and delete it. Any unauthorized copying, disclosure or distribution of this email or its attachment(s) is forbidden. Thales Nederland BV will not accept liability for any damage caused by this email or its attachment(s). Thales Nederland BV is seated in Hengelo and is registered at the Chamber of Commerce under number 06061578. ------------------------------------------------------------------------------------------------------------ From mohd.arif at nechclst.in Mon Dec 7 22:50:02 2009 From: mohd.arif at nechclst.in (Mohd Arif) Date: Tue, 8 Dec 2009 12:20:02 +0530 Subject: [Xorp-users] Urgent Queries about XORP package Message-ID: <0A8CFEC45B7F4C419F7543867C474423039D43B7@mailserver.nechclst.in> Hi Rikkers Jorn, Thank you very much for the confirmation. Looking forward for your continuous support. Best Regards, Mohd. Arif -----Original Message----- From: Rikkers Jorn [mailto:jorn.rikkers at nl.thalesgroup.com] Sent: Tuesday, December 08, 2009 12:07 PM To: Mohd Arif Cc: Bruce Simpson; xorp-users at xorp.org Subject: Re: [Xorp-users] Urgent Queries about XORP package Hi Mohd Arif, You are correct. I've succesfully used the two together: Quagga's OSPF and XORP's PIM-SM and IGMP. Regards, Jorn On 07-12-2009 20:27, Mohd Arif wrote: > Hi, Thanks for the kind words. > I look forward to the contribution in XORP in whatever small way i can. > Regarding interoperability of quagga and xorp: > "As PIM is "protocol independent", so my understanding is that PIM > make use of routing table managed by any unicast routing protocol, > lets say ospf. > It doesn't matter that the unicast routing protocol is an > implementation of quagga or xorp because PIM-SM just refer to kernel > routing table regardless of the fact that which unicast routing > protocol are creating entries in routing table." > With this understanding, i concluded that quagga implementation of > ospf and xorp's PIM-SM can be used together. > Is my understanding correct? > > Thanks in advance. > > ------------------------------------------------------------------------ > *From:* Bruce Simpson [mailto:bms at incunabulum.net] > *Sent:* Tue 12/8/2009 12:18 AM > *To:* Mohd Arif > *Cc:* xorp-users at xorp.org > *Subject:* Re: [Xorp-users] Urgent Queries about XORP package > > Mohd Arif wrote: > > > > Dear All, > > I am a new user of XORP. I am still collecting information about XORP. > > I would be thankful to xorp mailing list for the clarifications: > > > > Query #1: Does XORP supports PPC architecture? If yes, what options > > are needed by "configure" to cross compile the source code? If no, > > then its a bad news :( > > > > Cross-compilation currently hasn't been tested with the SCons build. > > You are welcome to contribute to the ongoing development effort of > getting cross compilation to work with the new build system. > > > > > Query #2: Is it possible to compile just PIM-SM in XORP software > package? > > > > Yes, if the SCons build is appropriately patched to build only what's > needed. > > Patches to do this would be gratefully received. > > > > > Query #3: Does PIM-SM have any dependency on other protocols supported > > by XORP? > > > > Yes, it requires the FEA, IGMP, MLD and libmrt components. > > > > > > Query #3: Are XORP and QUAGGA compatible? I mean to say that is it > > possible to use OSPF implementation of QUAGGA and PIM-SM > > implementation of XORP together? > > > > They are not designed to be interoperable in this way. > > However, you may be able to get this configuration working by using the > kernel as an indirect RIB. This is of course not going to scale very > well if you have a lot of routes, or if you need to use route policies. > > It is also a configuration that can't officially be supported; if you > try this, you're on your own. > > I can't think of any singular advantage offered by using Quagga's OSPF > implementation over what's already in the tree. > > > Your initial inputs will help me to gain confidence. > > > > New contributors to the project are welcome. Do you plan to submit code? > > thanks, > BMS > > DISCLAIMER: > ------------------------------------------------------------------------ ----------------------------------------------- > The contents of this e-mail and any attachment(s) are confidential and > intended > for the named recipient(s) only. > It shall not attach any liability on the originator or NECHCL or its > affiliates. Any views or opinions presented in > this email are solely those of the author and may not necessarily reflect the > opinions of NECHCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, modification, > distribution and / or publication of > this message without the prior written consent of the author of this e-mail is > strictly prohibited. If you have > received this email in error please delete it and notify the sender > immediately. . > ------------------------------------------------------------------------ ----------------------------------------------- > ------------------------------------------------------------------------ > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > -- Met vriendelijke groet, Jorn Rikkers *This message contains Unclassified information* ------------------------------------------------------------------------ ------------------------------------ Disclaimer: If you are not the intended recipient of this email, please notify the sender and delete it. Any unauthorized copying, disclosure or distribution of this email or its attachment(s) is forbidden. Thales Nederland BV will not accept liability for any damage caused by this email or its attachment(s). Thales Nederland BV is seated in Hengelo and is registered at the Chamber of Commerce under number 06061578. ------------------------------------------------------------------------ ------------------------------------ DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . ----------------------------------------------------------------------------------------------------------------------- From bms at incunabulum.net Mon Dec 7 23:36:34 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Tue, 08 Dec 2009 07:36:34 +0000 Subject: [Xorp-users] Urgent Queries about XORP package In-Reply-To: <0A8CFEC45B7F4C419F7543867C47442301497D64@mailserver.nechclst.in> References: <0A8CFEC45B7F4C419F7543867C47442301497D62@mailserver.nechclst.in> <4B1D4DF5.20602@incunabulum.net> <0A8CFEC45B7F4C419F7543867C47442301497D64@mailserver.nechclst.in> Message-ID: <4B1E0202.5040106@incunabulum.net> Mohd Arif wrote: > Hi, Thanks for the kind words. > I look forward to the contribution in XORP in whatever small way i can. > Regarding interoperability of quagga and xorp: > "As PIM is "protocol independent", so my understanding is that PIM > make use of routing table managed by any unicast routing protocol, > lets say ospf. > It doesn't matter that the unicast routing protocol is an > implementation of quagga or xorp because PIM-SM just refer to kernel > routing table regardless of the fact that which unicast routing > protocol are creating entries in routing table." > With this understanding, i concluded that quagga implementation of > ospf and xorp's PIM-SM can be used together. XORP's PIM needs to work with XORP's RIB process, which holds unicast routes for the purposes of the software multicast forwardng plane's RPF checks. If the state of your kernel's unicast routing table happens to be the same as what XORP thinks it is, then it might work. However mixing XORP and Quagga in this way is a completely unsupported configuration. From bms at incunabulum.net Tue Dec 8 02:56:14 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Tue, 08 Dec 2009 10:56:14 +0000 Subject: [Xorp-users] FreeBSD ports/net/xorp-devel added. Message-ID: <4B1E30CE.9000105@incunabulum.net> FYI all, In lieu of a 1.7 release, which is long overdue: I've checked in a FreeBSD port entry, for the current line of development in SVN, as of today: http://www.freshports.org/net/xorp-devel A few things are now turned on by default in the FreeBSD package, these are: * Optimization level -O1 in GNU C++ is now the default. XORP uses the C++ Standard Template Library. -O1 is necessary with gcc to generate reasonable code in this case. This offers a measurable binary size reduction, without compromising the ability to debug any code where needed. * Shared libraries. This offers a significant, measurable binary size reduction. FreeBSD/amd64 binaries for a full router are ~22MB. * Using UNIX domain sockets for IPC by default. These offer a measurable increase in RPC performance, when XORP components need only run on a single local router. * Using rtld ORIGIN; package relocation. On systems with a modern ELF runtime linker (FreeBSD 8.0, Linux), this allows the package to be relocated on disk. Other changes: * The Boost C++ libraries are now used by XORP, and you will need these to compile. * PCAP is now only linked by the FEA process. * SNMP support has been retired, as it was, in fact, mostly a no-op for all of the protocol modules except BGP. The implementation really needs to be revisited, to be scalable in BGP default-free-zone deployments. * The package now confirms to BSD hier(7), and should be compliant with the Linux Filesystem Hierarchy Standard (FHS), which should help folk packaging the community XORP tree for distribution in e.g. Ubuntu, Debian, Fedora. The only changes I'd plan further here, for now, would be to bring xorp_rtrmgr in line with the behaviour of other UNIX-like daemons; right now, the -d switch enables daemonization, rather than disabling it. thanks, BMS From esj at cs.fiu.edu Tue Dec 8 09:21:56 2009 From: esj at cs.fiu.edu (Eric S. Johnson) Date: Tue, 08 Dec 2009 12:21:56 -0500 Subject: [Xorp-users] cost of passive ospf interfaces is zero? In-Reply-To: <20091207225522.D54ABB883A7@cheetah.cs.fiu.edu> References: <20091207225522.D54ABB883A7@cheetah.cs.fiu.edu> Message-ID: <20091208172156.73265B88415@cheetah.cs.fiu.edu> A quick follow up to my own note from yesterday. As best I can tell from a quick read of rfc2328 the concept of what IOS/JunOS/quagga call "passive interfaces" is not really defined. 12.4.1 talks about loopback interfaces, but that seems to be the host: true case, right? There it says mask=0xffffffff and cost=0. But for the host: false case I can't seem to find anything that says what to do. Other than treat it as a normal stub network. Which would mean advertise the set cost, right? That is what the 3 other implementations I have access to do. The following patch seems to lets xorp behave like IOS/JunOS/quagga with regards to costs advertised on "passive" interfaces. I suppose it really should be done under the control of some sort of "act-like-everyone-else: true" setting, but that is a bit beyond my C-- grade C++ skills right now. E ---- [root at test-router xorp-1.6]# !diff diff -u ospf/peer.cc.orig ospf/peer.cc --- ospf/peer.cc.orig 2009-01-05 13:31:01.000000000 -0500 +++ ospf/peer.cc 2009-12-08 10:10:27.000000000 -0500 @@ -2612,16 +2612,17 @@ case Loopback: { // XXX - We should be checking to see if this is p2p unnumbered. uint16_t prefix_length; - if (_passive_host) + if (_passive_host) { prefix_length = IPv4::ADDR_BITLEN; - else { + router_link.set_metric(0); + } else { prefix_length = get_interface_prefix_length(); + router_link.set_metric(_peerout.get_interface_cost()); } IPNet net(get_interface_address(), prefix_length); router_link.set_type(RouterLink::stub); router_link.set_link_id(ntohl(net.masked_addr().addr())); router_link.set_link_data(ntohl(net.netmask().addr())); - router_link.set_metric(0); router_links.push_back(router_link); } return; From lhboi at yahoo.com Tue Dec 8 23:31:32 2009 From: lhboi at yahoo.com (LE Hong Boi) Date: Tue, 8 Dec 2009 23:31:32 -0800 (PST) Subject: [Xorp-users] problem when ppp interface down Message-ID: <291175.35054.qm@web53901.mail.re2.yahoo.com> Hi all, I am trying to set up a multicast router on a PPPoE server. I setup a Centos 5.2 machine with one NIC eth0, install VMware with host-only network vmnet1 (IP address: 192.168.24.1), install one guest Centos machine with host-only Ethernet. eth0 is used to serve PPPoE. The purpose is to stream video file through multicast from the guest machine to PPPoE client. Streaming software is VLC. The config.boot file is: /*XORP Configuration File, v1.0*/ interfaces { restore-original-config-on-shutdown: false interface vmnet1 { description: "server" disable: false discard: false unreachable: false management: false default-system-config { } } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea4 { disable: false interface vmnet1 { vif vmnet1 { disable: false } } interface register_vif { vif register_vif { disable: false } } traceoptions { flag all { disable: false } } } } protocols { igmp { disable: false interface vmnet1 { vif vmnet1 { disable: false } } traceoptions { flag all { disable: false } } } } protocols { pimsm4 { interface vmnet1 { vif vmnet1 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } /* Note: static-rps and bootstrap should not be mixed */ static-rps { rp 192.168.24.1 { group-prefix 224.0.0.0/4 { } } } switch-to-spt-threshold { /* approx. 1K bytes/s (10Kbps) threshold */ disable: false interval: 100 bytes: 102400 } traceoptions { flag all { disable: false } } } } protocols { fib2mrib { disable: false } } When a PPPoE client connect to this server, the script ip-up.local will call xorpsh to configure new ppp interface. For example: Welcome to XORP on testiptvbas xorp at testiptvbas> configure Entering configuration mode. There are no other users in configuration mode. [edit] xorp at testiptvbas# set interfaces interface ppp0 [edit] xorp at testiptvbas# set interfaces interface ppp0 default-system-config [edit] xorp at testiptvbas# commit OK [edit] xorp at testiptvbas# set plumbing mfea4 interface ppp0 [edit] xorp at testiptvbas# set plumbing mfea4 interface ppp0 vif ppp0 [edit] xorp at testiptvbas# commit OK [edit] xorp at testiptvbas# set protocols igmp interface ppp0 [edit] xorp at testiptvbas# set protocols igmp interface ppp0 vif ppp0 [edit] xorp at testiptvbas# commit OK [edit] xorp at testiptvbas# set protocols pimsm4 interface ppp0 [edit] xorp at testiptvbas# set protocols pimsm4 interface ppp0 vif ppp0 [edit] xorp at testiptvbas# commit OK [edit] xorp at testiptvbas# Now, the multicast works well. I can stream multicast video from the guest machine to the PPPoE client succesfully. The problem appears when PPPoE session disconnects. Here is the error output: [ 2009/12/08 13:17:24 INFO xorp_fea MFEA ] Interface stopped Vif[ppp0] pif_index: 12 vif_index: 2 addr: 192.168.30.1 subnet: 192.168.30.1/32 broadcast: 0.0.0.0 peer: 192.168.30.3 Flags: P2P MULTICAST MTU: 1492 DOWN IPv4 ENABLED [ 2009/12/08 13:17:24 INFO xorp_igmp MLD6IGMP ] Interface flags changed: Vif[ppp0] pif_index: 12 vif_index: 2 addr: 192.168.30.1 subnet: 192.168.30.1/32 broadcast: 0.0.0.0 peer: 192.168.30.3 Flags: P2P MULTICAST MTU: 1492 [ 2009/12/08 13:17:24 INFO xorp_pimsm4 PIM ] Interface flags changed: Vif[ppp0] pif_index: 12 vif_index: 2 addr: 192.168.30.1 subnet: 192.168.30.1/32 broadcast: 0.0.0.0 peer: 192.168.30.3 Flags: P2P MULTICAST MTU: 1492 [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (0.0.0.0, 224.0.0.2) on vif ppp0 [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (0.0.0.0, 224.0.0.13) on vif ppp0 [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (0.0.0.0, 224.0.0.22) on vif ppp0 [ 2009/12/08 13:17:24 INFO xorp_igmp MLD6IGMP ] Interface stopped: Vif[ppp0] pif_index: 12 vif_index: 2 addr: 192.168.30.1 subnet: 192.168.30.1/32 broadcast: 0.0.0.0 peer: 192.168.30.3 Flags: P2P MULTICAST MTU: 1492 DOWN IPv4 ENABLED [ 2009/12/08 13:17:24 INFO xorp_igmp MLD6IGMP ] Deleted address on interface ppp0: addr: 192.168.30.1 subnet: 192.168.30.1/32 broadcast: 0.0.0.0 peer: 192.168.30.3 [ 2009/12/08 13:17:24 ERROR xorp_igmp:5912 MLD6IGMP +1003 mld6igmp_node.cc delete_vif_addr ] Error updating primary address for vif ppp0: invalid primary address [ 2009/12/08 13:17:24 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.30.1 to 224.0.0.13 on vif ppp0 [ 2009/12/08 13:17:24 INFO xorp_pimsm4 PIM ] Deleted address on interface ppp0: addr: 192.168.30.1 subnet: 192.168.30.1/32 broadcast: 0.0.0.0 peer: 192.168.30.3 [ 2009/12/08 13:17:24 ERROR xorp_pimsm4:5913 PIM +1109 pim_node.cc delete_vif_addr ] Error updating primary and domain-wide addresses for vif ppp0: invalid primary address [ 2009/12/08 13:17:24 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 0.0.0.0 to 224.0.0.13 on vif ppp0 [ 2009/12/08 13:17:24 INFO xorp_pimsm4 PIM ] Interface stopped: Vif[ppp0] pif_index: 12 vif_index: 2 Flags: P2P MULTICAST MTU: 1492 DOWN IPv4 ENABLED [ 2009/12/08 13:17:24 WARNING xorp_igmp XrlMld6igmpTarget ] Handling method for mld6igmp/0.1/delete_protocol4 failed: XrlCmdError 102 Command failed Cannot delete protocol instance 'PIMSM_4' on vif ppp0 with vif_index 2 [ 2009/12/08 13:17:24 FATAL xorp_pimsm4:5913 PIM +2217 xrl_pim_node.cc mld6igmp_client_send_add_delete_protocol_mld6igmp_cb ] Cannot deregister with the MLD6IGMP: 102 Command failed Cannot delete protocol instance 'PIMSM_4' on vif ppp0 with vif_index 2 [ 2009/12/08 13:17:24 WARNING xorp_fea XrlFeaTarget ] Handling method for raw_packet4/0.1/send failed: XrlCmdError 102 Command failed Interface ppp0 is down [ 2009/12/08 13:17:24 ERROR xorp_rtrmgr:5888 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/pim/xorp_pimsm4": terminated with signal 6. [ 2009/12/08 13:17:24 INFO xorp_rtrmgr:5888 RTRMGR +299 module_manager.cc module_exited ] Module abnormally killed: pimsm4 [ 2009/12/08 13:17:24 ERROR xorp_fea:5889 LIBXORP +226 buffered_asyncio.cc io_event ] read error 104 [ 2009/12/08 13:17:24 ERROR xorp_fea:5889 XRL +169 xrl_pf_stcp.cc read_event ] Read failed (error = 104) [ 2009/12/08 13:17:24 ERROR xorp_fea:5889 XRL +378 xrl_pf_stcp.cc die ] STCPRequestHandler died: read error [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 192.168.24.1 to 224.0.0.2 on vif vmnet1 [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.24.1 to 224.0.0.13 [ 2009/12/08 13:17:25 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.24.1 to 224.0.0.13 [ 2009/12/08 13:17:26 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (0.0.0.0, 224.0.0.13) on vif vmnet1 [ 2009/12/08 13:17:26 WARNING xorp_rtrmgr:5888 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "PIMSM_4" does not exist or is not enabled. [ 2009/12/08 13:17:26 ERROR xorp_igmp:5912 MLD6IGMP +1106 xrl_mld6igmp_node.cc mld6igmp_client_send_add_delete_membership_cb ] XRL communication error: 201 Resolve failed [ 2009/12/08 13:17:27 INFO xorp_fea MFEA ] Interface deleted: ppp0 [ 2009/12/08 13:17:27 WARNING xorp_rtrmgr:5888 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "ifmgr_mirror-f81d1286737407c92dea75aaab3c6eed at 127.0.0.1" does not exist or is not enabled. [ 2009/12/08 13:17:27 INFO xorp_fea LIBFEACLIENT ] An error occurred sending an Xrl to "ifmgr_mirror-f81d1286737407c92dea75aaab3c6eed at 127.0.0.1". Target is being removed from list of interface update receivers. Then pim stops working. The problem is similar when I replace ppp0 with eth0 (instead of disconnect PPPoE, I ifdown eth0): pim stops working. How to fix this problem? Thanks in advance. LE Hong Boi Homepage: http://lhboi.homelinux.net From greearb at candelatech.com Tue Dec 8 23:54:32 2009 From: greearb at candelatech.com (Ben Greear) Date: Tue, 08 Dec 2009 23:54:32 -0800 Subject: [Xorp-users] problem when ppp interface down In-Reply-To: <291175.35054.qm@web53901.mail.re2.yahoo.com> References: <291175.35054.qm@web53901.mail.re2.yahoo.com> Message-ID: <4B1F57B8.5020708@candelatech.com> On 12/08/2009 11:31 PM, LE Hong Boi wrote: > [ 2009/12/08 13:17:24 INFO xorp_pimsm4 PIM ] Interface stopped: Vif[ppp0] pif_index: 12 vif_index: 2 Flags: P2P MULTICAST MTU: 1492 DOWN IPv4 ENABLED > [ 2009/12/08 13:17:24 WARNING xorp_igmp XrlMld6igmpTarget ] Handling method for mld6igmp/0.1/delete_protocol4 failed: XrlCmdError 102 Command failed Cannot delete protocol instance 'PIMSM_4' on vif ppp0 with vif_index 2 > [ 2009/12/08 13:17:24 FATAL xorp_pimsm4:5913 PIM +2217 xrl_pim_node.cc mld6igmp_client_send_add_delete_protocol_mld6igmp_cb ] Cannot deregister with the MLD6IGMP: 102 Command failed Cannot delete protocol instance 'PIMSM_4' on vif ppp0 with vif_index 2 > [ 2009/12/08 13:17:24 WARNING xorp_fea XrlFeaTarget ] Handling method for raw_packet4/0.1/send failed: XrlCmdError 102 Command failed Interface ppp0 is down > [ 2009/12/08 13:17:24 ERROR xorp_rtrmgr:5888 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/pim/xorp_pimsm4": terminated with signal 6. > [ 2009/12/08 13:17:24 INFO xorp_rtrmgr:5888 RTRMGR +299 module_manager.cc module_exited ] Module abnormally killed: pimsm4 > [ 2009/12/08 13:17:24 ERROR xorp_fea:5889 LIBXORP +226 buffered_asyncio.cc io_event ] read error 104 > [ 2009/12/08 13:17:24 ERROR xorp_fea:5889 XRL +169 xrl_pf_stcp.cc read_event ] Read failed (error = 104) > [ 2009/12/08 13:17:24 ERROR xorp_fea:5889 XRL +378 xrl_pf_stcp.cc die ] STCPRequestHandler died: read error > [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 192.168.24.1 to 224.0.0.2 on vif vmnet1 > [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.24.1 to 224.0.0.13 > [ 2009/12/08 13:17:25 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.24.1 to 224.0.0.13 > [ 2009/12/08 13:17:26 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (0.0.0.0, 224.0.0.13) on vif vmnet1 > [ 2009/12/08 13:17:26 WARNING xorp_rtrmgr:5888 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "PIMSM_4" does not exist or is not enabled. > [ 2009/12/08 13:17:26 ERROR xorp_igmp:5912 MLD6IGMP +1106 xrl_mld6igmp_node.cc mld6igmp_client_send_add_delete_membership_cb ] XRL communication error: 201 Resolve failed > [ 2009/12/08 13:17:27 INFO xorp_fea MFEA ] Interface deleted: ppp0 > [ 2009/12/08 13:17:27 WARNING xorp_rtrmgr:5888 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "ifmgr_mirror-f81d1286737407c92dea75aaab3c6eed at 127.0.0.1" does not exist or is not enabled. > [ 2009/12/08 13:17:27 INFO xorp_fea LIBFEACLIENT ] An error occurred sending an Xrl to "ifmgr_mirror-f81d1286737407c92dea75aaab3c6eed at 127.0.0.1". Target is being removed from list of interface update receivers. > > Then pim stops working. > > The problem is similar when I replace ppp0 with eth0 (instead of disconnect PPPoE, I ifdown eth0): pim stops working. > How to fix this problem? > Thanks in advance. I've fixed a bunch of similar issues in my xorp tree. If you can compile your own xorp, you might want to give it a try. If it still fails, please send me a trace from that and I'll see if I can fix it: http://www.candelatech.com/oss/xorp-ct.html Please note, this is based off of the upstream development tree, and I haven't done any solid testing since the last merge, so it may be a bit touchy. Let me know if you run into any troubles. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From alexis at via.ecp.fr Wed Dec 9 02:12:09 2009 From: alexis at via.ecp.fr (Alexis de Lattre) Date: Wed, 09 Dec 2009 11:12:09 +0100 Subject: [Xorp-users] kernel msg "mroute: pending queue full, dropping entries." Message-ID: <4B1F77F9.8020507@via.ecp.fr> Hello ! I have xorp running on the 2 firewall-routers of my network. I use xorp for PIM-SM and IGMP querier functionnality, in order to route multicast traffic accross my subnets. The firewall-routers are Debian 5.0 machines with Debian's 2.6.26-2-686 kernels. They are running xorp 1.6 (Debian package 1.6-1~rc2 taken from Debian Sid). The first firewall-router is an IGMP querier for a subnet which has 25 Mbit/s of multicast and doesn't print any particular kernel message. The other firewall-router (xorp configuration file enclosed) is an IGMP querier for a subnet which has a lot of multicast (about 500-600 Mbit/s). This router frequently prints these kernel messages : Dec 9 10:53:51 fireaj kernel: [326454.274784] mroute: pending queue full, dropping entries. Dec 9 10:53:58 fireaj kernel: [326461.330570] __ratelimit: 52 messages suppressed Dec 9 10:53:58 fireaj kernel: [326461.330579] mroute: pending queue full, dropping entries. The interface on which it receives the high multicast traffic is a Gigabit interface on PCIe bus. The machine is a Pentium D 2.8 Ghz (2 cores) with 2 Go of RAM. It is not swapping. There are 3 significant xorp process in term of CPU ressources : - xorp_fea process takes 40% of one core - xorp_pimsm4 takes 35% of one core - xorp_rtrmgr takes 20% of one core The result, when I run "dstat", is that one core is 0-5% idle and the other core is 95-100% idle. The load on the machine is about 1.7. At the moment, these is only very low inter-subnet multicast traffic (most of the time 0 Mbit/s, sometimes a few Mbit/s), so not many PIM requests. What does these "pending queue full, dropping entries" kernel messages mean ? What should I do to prevent these message from appearing ? Thanks in advance for your help ! -- Alexis de Lattre -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: config.boot Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091209/1a4c23ce/attachment.ksh From lhboi at yahoo.com Wed Dec 9 19:04:43 2009 From: lhboi at yahoo.com (LE Hong Boi) Date: Wed, 9 Dec 2009 19:04:43 -0800 (PST) Subject: [Xorp-users] problem when ppp interface down In-Reply-To: <4B1F57B8.5020708@candelatech.com> Message-ID: <825420.5257.qm@web53902.mail.re2.yahoo.com> --- On Wed, 12/9/09, Ben Greear wrote: > From: Ben Greear > Subject: Re: [Xorp-users] problem when ppp interface down > To: "LE Hong Boi" > Cc: xorp-users at xorp.org > Date: Wednesday, December 9, 2009, 2:54 PM > On 12/08/2009 11:31 PM, LE Hong Boi > wrote: > > > [ 2009/12/08 13:17:24 INFO xorp_pimsm4 PIM ] Interface > stopped: Vif[ppp0] pif_index: 12 vif_index: 2 Flags: P2P > MULTICAST MTU: 1492 DOWN IPv4 ENABLED > > [ 2009/12/08 13:17:24 WARNING xorp_igmp > XrlMld6igmpTarget ] Handling method for > mld6igmp/0.1/delete_protocol4 failed: XrlCmdError 102 > Command failed Cannot delete protocol instance 'PIMSM_4' on > vif ppp0 with vif_index 2 > > [ 2009/12/08 13:17:24? FATAL xorp_pimsm4:5913 PIM > +2217 xrl_pim_node.cc > mld6igmp_client_send_add_delete_protocol_mld6igmp_cb ] > Cannot deregister with the MLD6IGMP: 102 Command failed > Cannot delete protocol instance 'PIMSM_4' on vif ppp0 with > vif_index 2 > > [ 2009/12/08 13:17:24 WARNING xorp_fea XrlFeaTarget ] > Handling method for raw_packet4/0.1/send failed: XrlCmdError > 102 Command failed Interface ppp0 is down > > [ 2009/12/08 13:17:24? ERROR xorp_rtrmgr:5888 > RTRMGR +754 module_manager.cc done_cb ] Command > "/usr/local/xorp/pim/xorp_pimsm4": terminated with signal > 6. > > [ 2009/12/08 13:17:24? INFO xorp_rtrmgr:5888 > RTRMGR +299 module_manager.cc module_exited ] Module > abnormally killed: pimsm4 > > [ 2009/12/08 13:17:24? ERROR xorp_fea:5889 > LIBXORP +226 buffered_asyncio.cc io_event ] read error 104 > > [ 2009/12/08 13:17:24? ERROR xorp_fea:5889 XRL > +169 xrl_pf_stcp.cc read_event ] Read failed (error = 104) > > [ 2009/12/08 13:17:24? ERROR xorp_fea:5889 XRL > +378 xrl_pf_stcp.cc die ] STCPRequestHandler died: read > error > > [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_LEAVE_GROUP from 192.168.24.1 to 224.0.0.2 on vif > vmnet1 > > [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] TX > IGMP_MEMBERSHIP_QUERY from 192.168.24.1 to 224.0.0.13 > > [ 2009/12/08 13:17:25 TRACE xorp_igmp MLD6IGMP ] TX > IGMP_MEMBERSHIP_QUERY from 192.168.24.1 to 224.0.0.13 > > [ 2009/12/08 13:17:26 TRACE xorp_igmp MLD6IGMP ] > Notify routing delete membership for (0.0.0.0, 224.0.0.13) > on vif vmnet1 > > [ 2009/12/08 13:17:26? WARNING xorp_rtrmgr:5888 > XrlFinderTarget +407 ../xrl/targets/finder_base.cc > handle_finder_0_2_resolve_xrl ] Handling method for > finder/0.2/resolve_xrl failed: XrlCmdError 102 Command > failed Target "PIMSM_4" does not exist or is not enabled. > > [ 2009/12/08 13:17:26? ERROR xorp_igmp:5912 > MLD6IGMP +1106 xrl_mld6igmp_node.cc > mld6igmp_client_send_add_delete_membership_cb ] XRL > communication error: 201 Resolve failed > > [ 2009/12/08 13:17:27 INFO xorp_fea MFEA ] Interface > deleted: ppp0 > > [ 2009/12/08 13:17:27? WARNING xorp_rtrmgr:5888 > XrlFinderTarget +407 ../xrl/targets/finder_base.cc > handle_finder_0_2_resolve_xrl ] Handling method for > finder/0.2/resolve_xrl failed: XrlCmdError 102 Command > failed Target > "ifmgr_mirror-f81d1286737407c92dea75aaab3c6eed at 127.0.0.1" > does not exist or is not enabled. > > [ 2009/12/08 13:17:27 INFO xorp_fea LIBFEACLIENT ] An > error occurred sending an Xrl to > "ifmgr_mirror-f81d1286737407c92dea75aaab3c6eed at 127.0.0.1".? > Target is being removed from list of interface update > receivers. > > > > Then pim stops working. > > > > The problem is similar when I replace ppp0 with eth0 > (instead of disconnect PPPoE, I ifdown eth0): pim stops > working. > > How to fix this problem? > > Thanks in advance. > > I've fixed a bunch of similar issues in my xorp tree.? > If you can compile your own > xorp, you might want to give it a try.? If it still > fails, please send me a trace from > that and I'll see if I can fix it: > > http://www.candelatech.com/oss/xorp-ct.html > > Please note, this is based off of the upstream development > tree, and I haven't done any solid > testing since the last merge, so it may be a bit > touchy.? Let me know if you run into any troubles. > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc? http://www.candelatech.com > Thanks you, Ben! I got the source xorp.ct. Run scons and encounter the error message: TypeError: expected a character buffer object: File "/usr/src/xorp.ct/SConstruct", line 485: Split(env['CFLAGS'])) File "/usr/src/xorp.ct/SConstruct", line 484: lambda s: not s.startswith(tuple(strip_pg_flags)), Anything missing? Regards, Boi From greearb at candelatech.com Wed Dec 9 20:06:57 2009 From: greearb at candelatech.com (Ben Greear) Date: Wed, 09 Dec 2009 20:06:57 -0800 Subject: [Xorp-users] problem when ppp interface down In-Reply-To: <825420.5257.qm@web53902.mail.re2.yahoo.com> References: <825420.5257.qm@web53902.mail.re2.yahoo.com> Message-ID: <4B2073E1.7060601@candelatech.com> On 12/09/2009 07:04 PM, LE Hong Boi wrote: > > > --- On Wed, 12/9/09, Ben Greear wrote: > >> From: Ben Greear >> Subject: Re: [Xorp-users] problem when ppp interface down >> To: "LE Hong Boi" >> Cc: xorp-users at xorp.org >> Date: Wednesday, December 9, 2009, 2:54 PM >> On 12/08/2009 11:31 PM, LE Hong Boi >> wrote: >> >>> [ 2009/12/08 13:17:24 INFO xorp_pimsm4 PIM ] Interface >> stopped: Vif[ppp0] pif_index: 12 vif_index: 2 Flags: P2P >> MULTICAST MTU: 1492 DOWN IPv4 ENABLED >>> [ 2009/12/08 13:17:24 WARNING xorp_igmp >> XrlMld6igmpTarget ] Handling method for >> mld6igmp/0.1/delete_protocol4 failed: XrlCmdError 102 >> Command failed Cannot delete protocol instance 'PIMSM_4' on >> vif ppp0 with vif_index 2 >>> [ 2009/12/08 13:17:24 FATAL xorp_pimsm4:5913 PIM >> +2217 xrl_pim_node.cc >> mld6igmp_client_send_add_delete_protocol_mld6igmp_cb ] >> Cannot deregister with the MLD6IGMP: 102 Command failed >> Cannot delete protocol instance 'PIMSM_4' on vif ppp0 with >> vif_index 2 >>> [ 2009/12/08 13:17:24 WARNING xorp_fea XrlFeaTarget ] >> Handling method for raw_packet4/0.1/send failed: XrlCmdError >> 102 Command failed Interface ppp0 is down >>> [ 2009/12/08 13:17:24 ERROR xorp_rtrmgr:5888 >> RTRMGR +754 module_manager.cc done_cb ] Command >> "/usr/local/xorp/pim/xorp_pimsm4": terminated with signal >> 6. >>> [ 2009/12/08 13:17:24 INFO xorp_rtrmgr:5888 >> RTRMGR +299 module_manager.cc module_exited ] Module >> abnormally killed: pimsm4 >>> [ 2009/12/08 13:17:24 ERROR xorp_fea:5889 >> LIBXORP +226 buffered_asyncio.cc io_event ] read error 104 >>> [ 2009/12/08 13:17:24 ERROR xorp_fea:5889 XRL >> +169 xrl_pf_stcp.cc read_event ] Read failed (error = 104) >>> [ 2009/12/08 13:17:24 ERROR xorp_fea:5889 XRL >> +378 xrl_pf_stcp.cc die ] STCPRequestHandler died: read >> error >>> [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] RX >> IGMP_V2_LEAVE_GROUP from 192.168.24.1 to 224.0.0.2 on vif >> vmnet1 >>> [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] TX >> IGMP_MEMBERSHIP_QUERY from 192.168.24.1 to 224.0.0.13 >>> [ 2009/12/08 13:17:25 TRACE xorp_igmp MLD6IGMP ] TX >> IGMP_MEMBERSHIP_QUERY from 192.168.24.1 to 224.0.0.13 >>> [ 2009/12/08 13:17:26 TRACE xorp_igmp MLD6IGMP ] >> Notify routing delete membership for (0.0.0.0, 224.0.0.13) >> on vif vmnet1 >>> [ 2009/12/08 13:17:26 WARNING xorp_rtrmgr:5888 >> XrlFinderTarget +407 ../xrl/targets/finder_base.cc >> handle_finder_0_2_resolve_xrl ] Handling method for >> finder/0.2/resolve_xrl failed: XrlCmdError 102 Command >> failed Target "PIMSM_4" does not exist or is not enabled. >>> [ 2009/12/08 13:17:26 ERROR xorp_igmp:5912 >> MLD6IGMP +1106 xrl_mld6igmp_node.cc >> mld6igmp_client_send_add_delete_membership_cb ] XRL >> communication error: 201 Resolve failed >>> [ 2009/12/08 13:17:27 INFO xorp_fea MFEA ] Interface >> deleted: ppp0 >>> [ 2009/12/08 13:17:27 WARNING xorp_rtrmgr:5888 >> XrlFinderTarget +407 ../xrl/targets/finder_base.cc >> handle_finder_0_2_resolve_xrl ] Handling method for >> finder/0.2/resolve_xrl failed: XrlCmdError 102 Command >> failed Target >> "ifmgr_mirror-f81d1286737407c92dea75aaab3c6eed at 127.0.0.1" >> does not exist or is not enabled. >>> [ 2009/12/08 13:17:27 INFO xorp_fea LIBFEACLIENT ] An >> error occurred sending an Xrl to >> "ifmgr_mirror-f81d1286737407c92dea75aaab3c6eed at 127.0.0.1". >> Target is being removed from list of interface update >> receivers. >>> >>> Then pim stops working. >>> >>> The problem is similar when I replace ppp0 with eth0 >> (instead of disconnect PPPoE, I ifdown eth0): pim stops >> working. >>> How to fix this problem? >>> Thanks in advance. >> >> I've fixed a bunch of similar issues in my xorp tree. >> If you can compile your own >> xorp, you might want to give it a try. If it still >> fails, please send me a trace from >> that and I'll see if I can fix it: >> >> http://www.candelatech.com/oss/xorp-ct.html >> >> Please note, this is based off of the upstream development >> tree, and I haven't done any solid >> testing since the last merge, so it may be a bit >> touchy. Let me know if you run into any troubles. >> >> Thanks, >> Ben >> >> -- >> Ben Greear >> Candela Technologies Inc http://www.candelatech.com >> > > Thanks you, Ben! > I got the source xorp.ct. Run scons and encounter the error message: > TypeError: expected a character buffer object: > File "/usr/src/xorp.ct/SConstruct", line 485: > Split(env['CFLAGS'])) > File "/usr/src/xorp.ct/SConstruct", line 484: > lambda s: not s.startswith(tuple(strip_pg_flags)), What OS are you using? I'll sync down a fresh copy in a few minutes and make sure it works for me... Ben > > Anything missing? > Regards, > Boi > > > -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Wed Dec 9 20:16:37 2009 From: greearb at candelatech.com (Ben Greear) Date: Wed, 09 Dec 2009 20:16:37 -0800 Subject: [Xorp-users] problem when ppp interface down In-Reply-To: <825420.5257.qm@web53902.mail.re2.yahoo.com> References: <825420.5257.qm@web53902.mail.re2.yahoo.com> Message-ID: <4B207625.7050802@candelatech.com> On 12/09/2009 07:04 PM, LE Hong Boi wrote: > Thanks you, Ben! > I got the source xorp.ct. Run scons and encounter the error message: > TypeError: expected a character buffer object: > File "/usr/src/xorp.ct/SConstruct", line 485: > Split(env['CFLAGS'])) > File "/usr/src/xorp.ct/SConstruct", line 484: > lambda s: not s.startswith(tuple(strip_pg_flags)), Well, I don't see that error on Fedora 12, but I do see this one: Symlink("/home/greearb/git/xorp.ct/obj/i686-pc-linux-gnu/libcomm/libxorp_comm.so", as "/home/greearb/git/xorp.ct/obj/i686-pc-linux-gnu/lib/libxorp_comm.so") /home/greearb/git/xorp.ct/xrl/scripts/clnt-gen --output-dir obj/i686-pc-linux-gnu/xrl/interfaces xrl/interfaces/finder.xif In Xrl starting at line 16 in xrl/interfaces/finder.xif: Method name "&class_name:txt" has chars other than [A-Za-z][A-z0-9/_-]? scons: *** [obj/i686-pc-linux-gnu/xrl/interfaces/finder_xif.cc] Error 1 scons: building terminated because of errors. I'll see if I can figure this one out... Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From alexis at via.ecp.fr Fri Dec 11 00:42:33 2009 From: alexis at via.ecp.fr (Alexis de Lattre) Date: Fri, 11 Dec 2009 09:42:33 +0100 Subject: [Xorp-users] kernel msg "mroute: pending queue full, dropping entries." In-Reply-To: <4B1F77F9.8020507@via.ecp.fr> References: <4B1F77F9.8020507@via.ecp.fr> Message-ID: <4B2205F9.2000501@via.ecp.fr> Alexis de Lattre a ?crit : > Dec 9 10:53:51 fireaj kernel: [326454.274784] mroute: pending queue > full, dropping entries. > Dec 9 10:53:58 fireaj kernel: [326461.330570] __ratelimit: 52 messages > suppressed > Dec 9 10:53:58 fireaj kernel: [326461.330579] mroute: pending queue > full, dropping entries. I am the only one to get these "mroute: pending queue full, dropping entries" kernel messages ? I have never seen these messages on our router-firewalls before installing Xorp, so it's clearly linked. -- Alexis de Lattre From jnebrera at eneotecnologia.com Fri Dec 11 00:57:08 2009 From: jnebrera at eneotecnologia.com (Jaime Nebrera) Date: Fri, 11 Dec 2009 09:57:08 +0100 Subject: [Xorp-users] Route syncronization Message-ID: <1260521828.3439.20.camel@blas> Hi all, I'm wondering if exist any way to accomplish this task. We would like to have one router active and a second one passive for high availability. This second router would take the IP of the first one in case of failure (either using VRRP or IP Takeover). Now, when this second router wakes up it has to build all the routing stuff. I was wondering if there is any way to make the active router "send" the route information to the passive one while its alive. I have searched the web and found something called DIST, but only the paper, not the software itself (that BTW, they way works with XORP and Quagga). Any ideas? -- Jaime Nebrera - jnebrera at eneotecnologia.com Consultor TI - ENEO Tecnologia SL Pol. PISA - C/ Manufactura 6, P1, 3B Mairena del Aljarafe - 41927 - Sevilla Telf.- 955 60 11 60 / 619 04 55 18 From bms at incunabulum.net Fri Dec 11 02:14:06 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Fri, 11 Dec 2009 10:14:06 +0000 Subject: [Xorp-users] kernel msg "mroute: pending queue full, dropping entries." In-Reply-To: <4B2205F9.2000501@via.ecp.fr> References: <4B1F77F9.8020507@via.ecp.fr> <4B2205F9.2000501@via.ecp.fr> Message-ID: <4B221B6E.7060303@incunabulum.net> Alexis de Lattre wrote: > I am the only one to get these "mroute: pending queue full, dropping > entries" kernel messages ? > I have never seen these messages on our router-firewalls before > installing Xorp, so it's clearly linked. > It sounds like a message which may be specific to Linux's implementation of multicast forwarding; perhaps a Linux kernel developer experienced in this area would know more? thanks, BMS From bms at incunabulum.net Fri Dec 11 02:30:33 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Fri, 11 Dec 2009 10:30:33 +0000 Subject: [Xorp-users] Route syncronization In-Reply-To: <1260521828.3439.20.camel@blas> References: <1260521828.3439.20.camel@blas> Message-ID: <4B221F49.2060005@incunabulum.net> Jaime, It sounds to me like you've sort of already answered your own question (VRRP) ? Jaime Nebrera wrote: > ... > Now, when this second router wakes up it has to build all the routing > stuff. I was wondering if there is any way to make the active router > "send" the route information to the passive one while its alive. > Keeping router state in sync is usually a function of the routing protocol itself -- although it could be argued, in all sorts of academic contexts, that it isn't, or shouldn't be. Other than that, the question seems vague... If you're just bashing future routing ideas around, nanog-l@ might be a better forum. cheers, BMS From jnebrera at eneotecnologia.com Fri Dec 11 02:38:24 2009 From: jnebrera at eneotecnologia.com (Jaime Nebrera) Date: Fri, 11 Dec 2009 11:38:24 +0100 Subject: [Xorp-users] Route syncronization In-Reply-To: <4B221F49.2060005@incunabulum.net> References: <1260521828.3439.20.camel@blas> <4B221F49.2060005@incunabulum.net> Message-ID: <1260527904.3439.37.camel@blas> Hi Bruce, > It sounds to me like you've sort of already answered your own question > (VRRP) ? Maybe I didnt explain myself properly. Yes, VRRP warrants we will be able to move a "virtual" IP around in case of failure, but to my understanding, the secondary node has been "blind" with respect to route management all the time. When the primary goes down the backup takes its IP but has to "learn" and process all the routes. While doing that, traffic could be lost. My questioning was if there is any way to syncronize routing tables between the active and the passive node in such a way that when the passive goes live it already knows all if not all the routing information and work immediately. That was my question :) -- Jaime Nebrera - jnebrera at eneotecnologia.com Consultor TI - ENEO Tecnologia SL Pol. PISA - C/ Manufactura 6, P1, 3B Mairena del Aljarafe - 41927 - Sevilla Telf.- 955 60 11 60 / 619 04 55 18 From bms at incunabulum.net Fri Dec 11 02:59:23 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Fri, 11 Dec 2009 10:59:23 +0000 Subject: [Xorp-users] Route syncronization In-Reply-To: <1260527904.3439.37.camel@blas> References: <1260521828.3439.20.camel@blas> <4B221F49.2060005@incunabulum.net> <1260527904.3439.37.camel@blas> Message-ID: <4B22260B.6060303@incunabulum.net> Jaime Nebrera wrote: > My questioning was if there is any way to syncronize routing tables > between the active and the passive node in such a way that when the > passive goes live it already knows all if not all the routing > information and work immediately. > No, because this is usually a function of the routing protocol(s) involved. Here is a piece of research which may interest you: http://doc.tm.uka.de/2004/lichtwald-routing-convergence-icn2004.pdf cheers, BMS From alexis at via.ecp.fr Tue Dec 15 03:23:18 2009 From: alexis at via.ecp.fr (Alexis de Lattre) Date: Tue, 15 Dec 2009 12:23:18 +0100 Subject: [Xorp-users] kernel msg "mroute: pending queue full, dropping entries." In-Reply-To: <4B2205F9.2000501@via.ecp.fr> References: <4B1F77F9.8020507@via.ecp.fr> <4B2205F9.2000501@via.ecp.fr> Message-ID: <4B2771A6.4040405@via.ecp.fr> Alexis de Lattre a ?crit : > I am the only one to get these "mroute: pending queue full, dropping > entries" kernel messages ? > I have never seen these messages on our router-firewalls before > installing Xorp, so it's clearly linked. I upgraded the kernel to version 2.6.30 (package version 2.6.30-8~bpo50+1 from backports.org), and the kernel error message is still present... -- Alexis de Lattre From greearb at candelatech.com Tue Dec 15 07:27:07 2009 From: greearb at candelatech.com (Ben Greear) Date: Tue, 15 Dec 2009 07:27:07 -0800 Subject: [Xorp-users] kernel msg "mroute: pending queue full, dropping entries." In-Reply-To: <4B2771A6.4040405@via.ecp.fr> References: <4B1F77F9.8020507@via.ecp.fr> <4B2205F9.2000501@via.ecp.fr> <4B2771A6.4040405@via.ecp.fr> Message-ID: <4B27AACB.9080200@candelatech.com> On 12/15/2009 03:23 AM, Alexis de Lattre wrote: > Alexis de Lattre a ?crit : >> I am the only one to get these "mroute: pending queue full, dropping >> entries" kernel messages ? >> I have never seen these messages on our router-firewalls before >> installing Xorp, so it's clearly linked. > > I upgraded the kernel to version 2.6.30 (package version > 2.6.30-8~bpo50+1 from backports.org), and the kernel error message is > still present... This seems to be because xorp isn't reading it's socket quick enough. One might could increase the read-size for the buffer to allow more pkts to be queued, but that would require code changes most likely. See net/ipv4/ipmr.c in the Linux code. Thanks, Ben > -- Ben Greear Candela Technologies Inc http://www.candelatech.com From thomas.knowles at advatechpacific.com Wed Dec 16 12:25:40 2009 From: thomas.knowles at advatechpacific.com (Knowles, Thomas) Date: Wed, 16 Dec 2009 12:25:40 -0800 Subject: [Xorp-users] Q: Configuring static routes in OSPF Message-ID: I have not been able to get a static route to show up in LSAs Several variations of the configuration below have been tried. interfaces { interface eth1 { default-system-config } interface eth0 { default-system-config } interface tun1 { default-system-config } interface tun2 { default-system-config } } policy { policy-statement connected { term export { from { protocol: "connected" } } } } policy { policy-statement static { term export { from { protocol: "static" } } } } fea { unicast-forwarding4 { disable: false } } protocols { static { mrib-route 192.168.51.0/26 { next-hop: 192.168.51.4 } } fib2mrib { } ospf4 { export: "static" /* export: "connected" */ router-id: 192.168.37.2 traceoptions { flag { all { disable: true } } } area 0.0.0.0 { interface eth0 { vif eth0 { address 192.168.51.4 { priority: 0 } } } interface eth1 { vif eth1 { address 192.168.37.2 { } } } interface tun1 { vif tun1 { address 10.1.0.1 { } } } interface tun2 { vif tun2 { address 10.1.1.1 { } } } } } } Background: The topology can NOT be changed. IP forwarding is enabled and rp_filtering is disabled There will not be any routers connected to this router eth0 I know that the static route is defined as mirb, so fib2mirb is not required Xorpsh shows version 1.6 The tunnels and the eth1 ip addresses are seen with: Show route table ipv4 multicast final 10.1.0.0/26 [connected(0)/0] > via tun1/tun1 10.1.1.0/26 [connected(0)/0] > via tun2/tun2 10.1.2.0/26 [fib2mrib(254)/2] > to 10.1.0.2 via tun1/tun1 192.168.37.0/26 [connected(0)/0] > via eth1/eth1 192.168.37.64/26 [fib2mrib(254)/65535] > to 192.168.37.1 via eth1/eth1 192.168.37.128/26 [fib2mrib(254)/65535] > to 192.168.37.1 via eth1/eth1 192.168.37.2/32 [connected(0)/0] > via eth1/eth1 192.168.37.66/32 [connected(0)/0] > via tun1/tun1 192.168.37.130/32 [connected(0)/0] > via tun2/tun2 The physical connections are as follows: This router(A) has 2 phys: eth0 & eth1 Two other routers(B & C) are attached via two other linksys routers into a network switch A third linksys router is attached to this router eth1 and then to the switch So each of the Xorp routers are exchanging information via tunnels (tun1 & tun2) The static route is configured for this routers eth0 192.168.51.0/26 <->[192.168.51.4 (eth0 routerA eth1) 192.168.37.2/26 ] <----------------------> [.37.1 linksys routerA] <-> { switch } xxx.xxx.xx.x/26 <->[xxx.xxx.xx.x (eth0 routerB eth1) 192.168.37.64/26] <- tun1 10.1.0.0/26 --> [.xx.x linksys routerB] <-------^ xxx.xxx.xx.x/26 <->[xxx.xxx.xx.x (eth0 routerC eth1) 192.168.37.128/26] <- tun2 10.1.1.0/26 --> [.xx.x linksys routerC] <---------^ Thank you in advance for the help! mGby! Tom Knowles -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091216/d7d081dc/attachment-0001.html From srinivas.bandi at wipro.com Tue Dec 29 01:45:22 2009 From: srinivas.bandi at wipro.com (srinivas.bandi at wipro.com) Date: Tue, 29 Dec 2009 15:15:22 +0530 Subject: [Xorp-users] XORP documents Message-ID: <6324F38CCF371D40AD68BF1439B6488402716DC5@BLR-EC-MBX04.wipro.com> HI all, I'm not able to download Xorp user manual and design documents from http://www.xorp.org/ or even the mirrored sites. Can anyone send across the documents over mail to me. Thanks & regards Srinivas Bandi. (srinivas.bandi at wipro.com) Branch of Wipro Limited, Place of Commercial Register of the Branch: Kiel Commercial Registration Number of the branch : HRB 7178 KI VAT registration number - German Tax No:19/294/30609 Company name as Registered in Commercial Register : Wipro Limited (India) Zweigniederlassung Deutschland Legal form of the Company : Domestic Branch of the Foreign Limited liability Company. Company seat: Registered office at Doddakannelli, Sarjapur Road, Bangalore, India : 560 035. Tel : 91-80-28440011, Fax : 91-80-28440051, website: www.wipro.com Managing Director : Mr Azim H Premji Zweigniederlassung der Wipro Limited Registergericht: Kiel Handelsregisternummer: HRB 7178 KI Steuernummer: 19/294/30609 Firma laut Handelsregistereintrag: Wipro Limited (India) Zweigniederlassung Deutschland Rechtsform der Gesellschaft: inl?ndische Zweigniederlassung einer Aktiengesellschaft ausl?ndischen Rechts Sitz der Gesellschaft: Doddakannelli, Sarjapur Road, Bangalore, Indien 560 035 Tel. +91 80 28440011, Fax: +91 80 28440051, website: www.wipro.com Vorstandsvorsitzender: Azim H Premji The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091229/4af4e4b4/attachment.html From srinivas.bandi at wipro.com Tue Dec 29 04:48:33 2009 From: srinivas.bandi at wipro.com (srinivas.bandi at wipro.com) Date: Tue, 29 Dec 2009 18:18:33 +0530 Subject: [Xorp-users] Xorp questions : OSPF Message-ID: <6324F38CCF371D40AD68BF1439B6488402716FD9@BLR-EC-MBX04.wipro.com> Hi, I'm new to Xorp. Today I had an opportunity to browse through some of the documents and also the code. Mainly I was looking into OSPF protocol support and I have a question in this regard: I saw the ospfv2.xif file which provides an interface to configure OSPF related configurations. My understanding is, using these interfaces (XrlOspfv2V0p1Client) I can develop my own manager application to - Get and set the OSPF related configurations on OSPF daemon. - Get the LSAs - Get the areas lists - Neighbor list - Etc Question: I would like to know does this interfaces some kind of notification / observer mechanism to which my client application can register so that whenever a new neighbor is discovered and corresponding route is being added by OSPF daemon, my client application is notified? Thanks & regards Bandi. Branch of Wipro Limited, Place of Commercial Register of the Branch: Kiel Commercial Registration Number of the branch : HRB 7178 KI VAT registration number - German Tax No:19/294/30609 Company name as Registered in Commercial Register : Wipro Limited (India) Zweigniederlassung Deutschland Legal form of the Company : Domestic Branch of the Foreign Limited liability Company. Company seat: Registered office at Doddakannelli, Sarjapur Road, Bangalore, India : 560 035. Tel : 91-80-28440011, Fax : 91-80-28440051, website: www.wipro.com Managing Director : Mr Azim H Premji Zweigniederlassung der Wipro Limited Registergericht: Kiel Handelsregisternummer: HRB 7178 KI Steuernummer: 19/294/30609 Firma laut Handelsregistereintrag: Wipro Limited (India) Zweigniederlassung Deutschland Rechtsform der Gesellschaft: inl?ndische Zweigniederlassung einer Aktiengesellschaft ausl?ndischen Rechts Sitz der Gesellschaft: Doddakannelli, Sarjapur Road, Bangalore, Indien 560 035 Tel. +91 80 28440011, Fax: +91 80 28440051, website: www.wipro.com Vorstandsvorsitzender: Azim H Premji The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091229/5738e9d8/attachment.html From bms at incunabulum.net Tue Dec 29 13:38:17 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Tue, 29 Dec 2009 21:38:17 +0000 Subject: [Xorp-users] XORP documents In-Reply-To: <6324F38CCF371D40AD68BF1439B6488402716DC5@BLR-EC-MBX04.wipro.com> References: <6324F38CCF371D40AD68BF1439B6488402716DC5@BLR-EC-MBX04.wipro.com> Message-ID: <4B3A76C9.7080609@incunabulum.net> On 29/12/2009 09:45, srinivas.bandi at wipro.com wrote: > > HI all, > > I?m not able to download Xorp user manual and design documents from > http://www.xorp.org/ or even the mirrored sites. > I can't speak for the mirrors, but in any event: these documents are available from the community XORP source tree in source format, and you will need a full LaTeX toolchain to build them. thanks BMS -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091229/544ddd10/attachment.html