From jonirucoeith at gmail.com Sat Sep 1 14:00:19 2007 From: jonirucoeith at gmail.com (Jon) Date: Sat, 1 Sep 2007 23:00:19 +0200 Subject: [Xorp-hackers] Using OSPF over GRE tunnels Message-ID: <471f67780709011400s1c5e643bld36bb53c55d29026@mail.gmail.com> Hello, We are trying out ospf, and need to make it work over gre tunnels. So far we have not been able to get the databases to synchronize. We do see that the hello packets are sent through the tunnel though. I have read on the mailing lists about others struggeling with gre tunnels, but that seems to be mostly related to pim. Has anyone tried an OSPF scenario with success? thanks in advance, Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20070901/b6844b7f/attachment.html From kristian at spritelink.net Thu Sep 13 07:10:16 2007 From: kristian at spritelink.net (Kristian Larsson) Date: Thu, 13 Sep 2007 16:10:16 +0200 Subject: [Xorp-hackers] VLAN support Message-ID: <46E944C8.8030909@spritelink.net> Hello everyone :) I've seen a few CVS commits recently relating to VLAN configuration. I would like to know what the current status is of the interface naming scheme. The current standard has been questioned on several occasions and I would like to see that the project reaches some form of consensus on this before just implementing things. I read through an old thread with the subject 'Some thoughts' which Hasso started. What is your view on those ideas? Do you currently have in mind a naming scheme for VLAN and other "sub-interfaces"? Kristian. From atanu at ICSI.Berkeley.EDU Thu Sep 13 15:18:28 2007 From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh) Date: Thu, 13 Sep 2007 15:18:28 -0700 Subject: [Xorp-hackers] OSPFv2 P2P Links In-Reply-To: Message from "Erlend Knutsen" of "Wed, 29 Aug 2007 10:43:50 +0200." Message-ID: <49891.1189721908@tigger.icir.org> Hi, A slightly modified fix is now in cvs. Revision Changes Path 1.282 +7 -3; commitid: 39d46e9b4737ea6; xorp/ospf/peer.cc Atanu. >>>>> "Erlend" == Erlend Knutsen writes: Erlend> Hi all, Added: "_peer.update_router_links()" to the end of Erlend> the method "Neighbour::tear_down_state()" Erlend> This seem to do the work for p2p!! The p2p link is now Erlend> correclty deleted from the LSA update, while the stub is Erlend> kept. When the neighbour comes up again the p2p links Erlend> appear again in the LSA update. Erlend> However we have only tested this once, with 3 routers and 1 Erlend> router at the edge going down/up. Erlend> Thanks Atanu! Erlend> Erlend Erlend> -----Original Message----- From: atanu at icir.org on behalf of Erlend> Atanu Ghosh Sent: on 29-aug-07 04:29 To: Erlend Knutsen Cc: Erlend> Bharadwaj Kalahasti; xorp-hackers at icir.org Subject: Re: Erlend> [Xorp-hackers] OSPFv2 P2P Links Erlend> Hi, Erlend> Adding a call to "update_router_links()" at the end of the Erlend> method "Neighbour ::tear_down_state()", should solve your Erlend> problem, let me know. Erlend> Atanu. >>>>> "Erlend" == Erlend Knutsen writes: Erlend> Kalahasti, I probably will be able to test the code. I run Erlend> 3 instances of OSPF over 3 vmware machines (debian Etch over Erlend> windows VMWare player). I may also be able to extend the Erlend> configuration with more machines and different topologies. Erlend> However, I have never testet NBMA and P2MP before, but I Erlend> guess I only need to make some small adjustments in the Erlend> config.boot file. Erlend> Regards, Erlend Erlend> _________________________________________________________________ Erlend> Fra: Bharadwaj Kalahasti [mailto:b_kalahasti at yahoo.com] Erlend> Sendt: ti 28-aug-07 19:50 Til: Bharadwaj Kalahasti; Erlend> xorp-hackers at icir.org; Erlend Knutsen Emne: Re: OSPFv2 P2P Erlend> Links Erlend> Erlend, You are right. The stub link should remain in the Erlend> Router-LSA while the Type 1 link should be removed due to Erlend> non-adjacency with the neighbor. I know of how the changes Erlend> need to be done. May be you can review them. If I make the Erlend> same changes for NBMA and P2MP, would you be able to test Erlend> them for me? I have a single Ubuntu linux loaded DELL PC Erlend> that does not help much but for a single router instance. Erlend> Thanks, Kalahasti >>>>>>>>>>>>>> Erlend> Thank you! This pretty much helped clearing up how OSPF p2p Erlend> is supposed to work. To answer your question: XORP only Erlend> seem to support p2p when configurig the neighbours Erlend> statically, so YES! XORP supports static Neighbours. When Erlend> running OSPF p2p over Ethernet the Router LSA (catched from Erlend> tcpdump) reports a p2p link and a stub link to the Ethernet Erlend> subnet between the routers. I can managed to multicast an Erlend> LSA update as a result of the Hello inactivity timer for the Erlend> p2p link. However the p2p link that went down is still Erlend> reported. I am looking further into the code now to try to Erlend> ensure that the "downed" p2p link is removed before a new Erlend> LSA is sent. Regards, Erlend --- Bharadwaj Kalahasti Erlend> wrote: >>> Erlend, Generally speaking, one set of implementations for >>> non-broadcast Erlend> neighbors such >>> as those of P2MP, P2P and NBMA seems to be to configure the >>> neighbors Erlend> as 'STATIC' >>> neighbors. For P2P Neighbors, the Hellos are multicast. The >>> Intf state for Erlend> the OSPF >>> interface should be P2P after the IP interface comes up. And the >>> Nbr state Erlend> should finally >>> be Full on the local end assuming that the Router ID of the >>> neighbor is Erlend> seen by the >>> local router. >>> >>> These are the steps that should happen: -- So assuming that your >>> neighbor has gone Down at the remote end Erlend> for the reasons >>> - Admin down, Link transmission failure but Link is still Up >>> etc, then Erlend> this should >>> cause Inactivity Timer to be fired on the local end. -- Expiry >>> of this timer should cause a new Router LSA to be Erlend> generated and >>> area-flooded but without the Neighbor's Router ID in its >>> Neighbor Erlend> list (since it >>> failed to have bi-directional communication). -- Since the new >>> Router-LSA would be different in its LS Header from Erlend> the previous >>> one for the same local router's Router ID, that should cause its Erlend> installation on >>> all of the area's routers and kick off a new SPF run once the Erlend> installation of the >>> Router-LSA in the LSDB is done. -- The SPF run should take care >>> of deleting the P2P host route in Erlend> the Routing >>> Table. >>> >>> >>> I think the implementation of a P2P Nbr is upto interpretation. Erlend> The catch here >>> is that a static configuration of the Nbr would mean that the >>> Hello Erlend> packet can always >>> have the Neighbor router listed in it indicating bi-directional Erlend> communication and >>> full adjacency though the link may actually be down (if knowing >>> the Erlend> existence of a >>> Neighbor implies including it in the sent Hello). The other way >>> to Erlend> interpret the >>> RFC is that configuration is good enough to know its existence >>> but its Erlend> inclusion in >>> the Hello is subject to event occurence on the link. >>> >>> I do not know the OSPFv2 code in XORP but if Static neighbors >>> are Erlend> not supported >>> yet, then may be it is a good idea to support it. >>> >>> Regards, Kalahasti >>> >>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> >>> >>> Hi all, >>> >>> >>> >>> It seems like XORP OSPFv2 does not fully manage to update the Erlend> routing >>> table >>> >>> when a neighbor connected through a p2p link goes down, >>> e.g. when an xorp >>> >>> OSPFv2 neighbour is stopped. The neighbour state is set >>> correctly to down, >>> >>> but the routes advertised by/through the neighbour are not >>> removed Erlend> from >>> the >>> >>> rest of the network. The LS DB is identical before and after the >>> neighbour >>> >>> has been stopped (only the age field differs, but is not set to Erlend> MaxAge). >>> >>> >>> >>> I have tested this in a very simple scenario with 3 routers >>> R1-R2-R3 Erlend> up >>> and >>> >>> running with p2p links configured over Ethernet. I have for >>> example stopped >>> >>> ospf on R2 and then observed that R1 and R3 still have routes to Erlend> each >>> other. >>> >>> However, when the same routers run with Broadcast links the >>> routes Erlend> are >>> correctly removed when one of the other routers goes down. >>> >>> >>> >>> I can see from the source code and debug output that the >>> difference Erlend> in >>> handling of the InactivityTimer Event (i.e. Hello timeout) >>> between Broadcast >>> >>> and p2p links seems to start in the method: >>> Neighbour ::tear_down_state; >>> >>> This method does not do any work for p2p (_peer.adjacency_change >>> >>> only works for DR or BDR). I therefore simply tried to add the >>> call: >>> >>> _peer.get_area_router()->refresh_router_lsa() >>> >>> to the end Neighbour ::tear_down_state. This causes a total Erlend> recompute >>> of the routing but the routes from/via the router that has been >>> shut down are >>> >>> not removed. >>> >>> >>> >>> It may be that p2p links should have some kind of special static Erlend> state, >>> but to me, it does not seem sane that the links to/via a router >>> that Erlend> has >>> gone down are not removed. The RFC 2178 is somewhat diffuse >>> when >>> >>> it comes to p2p and Hello timeout. (It may seem somewhat strange >>> >>> to run p2p over Ethernet but this is a requirement.) >>> >>> >>> >>> Anyway I hope someone can give me some hints on how to work >>> further Erlend> in >>> this. >>> >>> >>> >>> I can send debug logs and config setup if necessary. >>> >>> Thanks in advance! >>> >>> >>> >>> Regards, >>> >>> Erlend >>> >>> >>> >>> Erlend> ______________________________________________________________________ Erlend> ______________ >>> Luggage? GPS? Comic books? Check out fitting gifts for grads at >>> Yahoo! Search >>> Erlend> http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz >>> Erlend> ______________________________________________________________________ Erlend> ______________ Yahoo! oneSearch: Finally, mobile search that Erlend> gives answers, not web links. Erlend> http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC Erlend> _______________________________________________ Xorp-hackers Erlend> mailing list Xorp-hackers at icir.org Erlend> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers From pavlin at icir.org Thu Sep 13 16:30:15 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Thu, 13 Sep 2007 16:30:15 -0700 Subject: [Xorp-hackers] VLAN support In-Reply-To: Message from Kristian Larsson of "Thu, 13 Sep 2007 16:10:16 +0200." <46E944C8.8030909@spritelink.net> Message-ID: <200709132330.l8DNUFOO040899@possum.icir.org> Kristian Larsson wrote: > Hello everyone :) > > I've seen a few CVS commits recently relating to VLAN configuration. I > would like to know what the current status is of the interface naming > scheme. The current standard has been questioned on several occasions > and I would like to see that the project reaches some form of consensus > on this before just implementing things. > > I read through an old thread with the subject 'Some thoughts' which > Hasso started. What is your view on those ideas? > > Do you currently have in mind a naming scheme for VLAN and other > "sub-interfaces"? The VLAN changes are to the backend and they follow the existing interface/vif scheme: the VLAN is a vif to the parent interface. Nothing has been changed in the user front-end. Pavlin > Kristian. > > _______________________________________________ > Xorp-hackers mailing list > Xorp-hackers at icir.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers From kristian at spritelink.net Thu Sep 13 16:37:39 2007 From: kristian at spritelink.net (kristian at spritelink.net) Date: Fri, 14 Sep 2007 01:37:39 +0200 Subject: [Xorp-hackers] VLAN support In-Reply-To: <200709132330.l8DNUFOO040899@possum.icir.org> References: <200709132330.l8DNUFOO040899@possum.icir.org> Message-ID: <0874978cf27df3337e8a08176c752b1d@Mail.SpriteLink.NET> On Thu, 13 Sep 2007 16:30:15 -0700, Pavlin Radoslavov wrote: > Kristian Larsson wrote: > >> Hello everyone :) >> >> I've seen a few CVS commits recently relating to VLAN configuration. I >> would like to know what the current status is of the interface naming >> scheme. The current standard has been questioned on several occasions >> and I would like to see that the project reaches some form of consensus >> on this before just implementing things. >> >> I read through an old thread with the subject 'Some thoughts' which >> Hasso started. What is your view on those ideas? >> >> Do you currently have in mind a naming scheme for VLAN and other >> "sub-interfaces"? > > The VLAN changes are to the backend and they follow the existing > interface/vif scheme: the VLAN is a vif to the parent interface. > Nothing has been changed in the user front-end. I understand that nothing has been changed so far, what I'm interested in is if it will be. And I'm not certain how VLANs fit in under the current naming scheme, since it's not currently implemented... Under linux a vlan interface by default is named . and under FreeBSD a vlan is named vlan, where the sequence number has no correlation to the vlan id. Is XORP supposed to somehow follow this? interface eth0 { vif eth0.123 { } } or on freebsd interface fxp0 { vid vlan2 { } } ?? How do I know the tag which is used on FreeBSD? Could you please provide a few examples of how it may look ? :) -K From pavlin at icir.org Thu Sep 13 17:05:51 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Thu, 13 Sep 2007 17:05:51 -0700 Subject: [Xorp-hackers] VLAN support In-Reply-To: Message from of "Fri, 14 Sep 2007 01:37:39 +0200." <0874978cf27df3337e8a08176c752b1d@Mail.SpriteLink.NET> Message-ID: <200709140005.l8E05pGD041355@possum.icir.org> wrote: > On Thu, 13 Sep 2007 16:30:15 -0700, Pavlin Radoslavov > wrote: > > Kristian Larsson wrote: > > > >> Hello everyone :) > >> > >> I've seen a few CVS commits recently relating to VLAN configuration. I > >> would like to know what the current status is of the interface naming > >> scheme. The current standard has been questioned on several occasions > >> and I would like to see that the project reaches some form of consensus > >> on this before just implementing things. > >> > >> I read through an old thread with the subject 'Some thoughts' which > >> Hasso started. What is your view on those ideas? > >> > >> Do you currently have in mind a naming scheme for VLAN and other > >> "sub-interfaces"? > > > > The VLAN changes are to the backend and they follow the existing > > interface/vif scheme: the VLAN is a vif to the parent interface. > > Nothing has been changed in the user front-end. > > I understand that nothing has been changed so far, what I'm interested in > is if it will be. > And I'm not certain how VLANs fit in under the current naming scheme, since > it's not currently implemented... > Under linux a vlan interface by default is named . and > under FreeBSD a vlan is named vlan, where the sequence > number has no correlation to the vlan id. Is XORP supposed to somehow > follow this? > interface eth0 { > vif eth0.123 { > } > } > or on freebsd > interface fxp0 { > vid vlan2 { > } > } > ?? > How do I know the tag which is used on FreeBSD? > Could you please provide a few examples of how it may look ? :) No, until the implementation is completed :) Regards, Pavlin > -K > > _______________________________________________ > Xorp-hackers mailing list > Xorp-hackers at icir.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers From kristian at spritelink.net Fri Sep 14 00:34:39 2007 From: kristian at spritelink.net (Kristian Larsson) Date: Fri, 14 Sep 2007 09:34:39 +0200 Subject: [Xorp-hackers] VLAN support In-Reply-To: <200709140005.l8E05pGD041355@possum.icir.org> References: <200709140005.l8E05pGD041355@possum.icir.org> Message-ID: <46EA398F.5050600@spritelink.net> Pavlin Radoslavov wrote: > wrote: > >> On Thu, 13 Sep 2007 16:30:15 -0700, Pavlin Radoslavov >> wrote: >>> Kristian Larsson wrote: >>> >>>> Hello everyone :) >>>> >>>> I've seen a few CVS commits recently relating to VLAN configuration. I >>>> would like to know what the current status is of the interface naming >>>> scheme. The current standard has been questioned on several occasions >>>> and I would like to see that the project reaches some form of consensus >>>> on this before just implementing things. >>>> >>>> I read through an old thread with the subject 'Some thoughts' which >>>> Hasso started. What is your view on those ideas? >>>> >>>> Do you currently have in mind a naming scheme for VLAN and other >>>> "sub-interfaces"? >>> The VLAN changes are to the backend and they follow the existing >>> interface/vif scheme: the VLAN is a vif to the parent interface. >>> Nothing has been changed in the user front-end. >> I understand that nothing has been changed so far, what I'm interested in >> is if it will be. >> And I'm not certain how VLANs fit in under the current naming scheme, since >> it's not currently implemented... >> Under linux a vlan interface by default is named . and >> under FreeBSD a vlan is named vlan, where the sequence >> number has no correlation to the vlan id. Is XORP supposed to somehow >> follow this? >> interface eth0 { >> vif eth0.123 { >> } >> } >> or on freebsd >> interface fxp0 { >> vid vlan2 { >> } >> } >> ?? >> How do I know the tag which is used on FreeBSD? >> Could you please provide a few examples of how it may look ? :) > > No, until the implementation is completed :) If you go ahead and implement, which of course is nothing I object to - I would love VLAN support in XORP, I think the discussion will be raised on how the naming scheme should look and there is a slight risk that someone will have to re-implement and change things due to that we reach concensus on some other solution than what is currently on roadmap. I'm having difficult understanding just why you can't provide me with an example of what you have in mind? Is it a secret? ;) -K From aswinnen at etro.vub.ac.be Fri Sep 21 00:48:11 2007 From: aswinnen at etro.vub.ac.be (Arnout Swinnen) Date: Fri, 21 Sep 2007 09:48:11 +0200 Subject: [Xorp-hackers] PIM-SM: Register Decapsulation Message-ID: <6292968AF9ACED4D962326A8958DC7CCA5E446@etropcs03.etro.vub.ac.be> Hi All, At the Vrije Universiteit Brussel, a university in Brussels, Belgium; we are experimenting with modifying the PIM-SM protocol. For this purpose we are also trying to implement a prototype of the Anycast-RP (RFC 4610), using XORP. Currently our prototype is currently not working as expecting. So for debugging reasons (and to gain a better understanding of the Xorp's workflow), we are also investigating the current XORP source code. At some point in the file pim_proto_register.cpp we encountered the following comment: . // "decapsulate and forward the inner packet to // inherited_olis(S, G, rpt)" // // XXX: This will happen inside the kernel. // Here we only install the forwarding entry // . We were unable to locate the code where this decapsulation actually happens. So my question is quiete simple: Where do I have to look to understand the decapsulation's implementation? Kind Regards, Arnout Swinnen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20070921/c1679910/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3090 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20070921/c1679910/attachment.bin From pavlin at icir.org Fri Sep 21 10:28:10 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Fri, 21 Sep 2007 10:28:10 -0700 Subject: [Xorp-hackers] PIM-SM: Register Decapsulation In-Reply-To: Message from "Arnout Swinnen" of "Fri, 21 Sep 2007 09:48:11 +0200." <6292968AF9ACED4D962326A8958DC7CCA5E446@etropcs03.etro.vub.ac.be> Message-ID: <200709211728.l8LHSAlW081830@possum.icir.org> > At the Vrije Universiteit Brussel, a university in Brussels, Belgium; we are > experimenting with modifying the PIM-SM protocol. For this purpose we are > also trying to implement a prototype of the Anycast-RP (RFC 4610), using > XORP. Currently our prototype is currently not working as expecting. So for > debugging reasons (and to gain a better understanding of the Xorp's > workflow), we are also investigating the current XORP source code. > > > > At some point in the file pim_proto_register.cpp we encountered the > following comment: > > . > > // "decapsulate and forward the inner packet to > > // inherited_olis(S, G, rpt)" FYI, this is text from the PIM-SM spec. > // XXX: This will happen inside the kernel. > > // Here we only install the forwarding entry. This is text from the implementor how the spec action is translated into the XORP implementation. > We were unable to locate the code where this decapsulation actually happens. > So my question is quiete simple: Where do I have to look to understand the > decapsulation's implementation? In the UNIX kernel. For *BSD systems this will be /usr/src/sys/netinet/ip_mroute.c function pim_input(): if (PIM_VT_T(pim->pim_vt) == PIM_REGISTER) { ... } or /usr/src/sys/netinet6/ip6_mroute.c function pim6_input(): if (pim->pim_type == PIM_REGISTER) { ... } for IPv4 and IPv6 respectively. BTW, the above code is from FreeBSD-4.10 so it might look slightly different for other versions or *BSD flavors. For Linux see /usr/src/linux/net/ipv4/ipmr.c function pim_rcv(). Hope that helps, Pavlin From pavlin at icir.org Wed Sep 26 01:10:46 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Wed, 26 Sep 2007 01:10:46 -0700 Subject: [Xorp-hackers] VLAN support In-Reply-To: Message from Kristian Larsson of "Fri, 14 Sep 2007 09:34:39 +0200." <46EA398F.5050600@spritelink.net> Message-ID: <200709260810.l8Q8AkQr003129@possum.icir.org> Kristian Larsson wrote: > Pavlin Radoslavov wrote: > > wrote: > > > >> On Thu, 13 Sep 2007 16:30:15 -0700, Pavlin Radoslavov > >> wrote: > >>> Kristian Larsson wrote: > >>> > >>>> Hello everyone :) > >>>> > >>>> I've seen a few CVS commits recently relating to VLAN configuration. I > >>>> would like to know what the current status is of the interface naming > >>>> scheme. The current standard has been questioned on several occasions > >>>> and I would like to see that the project reaches some form of consensus > >>>> on this before just implementing things. > >>>> > >>>> I read through an old thread with the subject 'Some thoughts' which > >>>> Hasso started. What is your view on those ideas? > >>>> > >>>> Do you currently have in mind a naming scheme for VLAN and other > >>>> "sub-interfaces"? > >>> The VLAN changes are to the backend and they follow the existing > >>> interface/vif scheme: the VLAN is a vif to the parent interface. > >>> Nothing has been changed in the user front-end. > >> I understand that nothing has been changed so far, what I'm interested in > >> is if it will be. > >> And I'm not certain how VLANs fit in under the current naming scheme, since > >> it's not currently implemented... > >> Under linux a vlan interface by default is named . and > >> under FreeBSD a vlan is named vlan, where the sequence > >> number has no correlation to the vlan id. Is XORP supposed to somehow > >> follow this? > >> interface eth0 { > >> vif eth0.123 { > >> } > >> } > >> or on freebsd > >> interface fxp0 { > >> vid vlan2 { > >> } > >> } > >> ?? > >> How do I know the tag which is used on FreeBSD? > >> Could you please provide a few examples of how it may look ? :) > > > > No, until the implementation is completed :) > > If you go ahead and implement, which of course is nothing I object to - > I would love VLAN support in XORP, I think the discussion will be raised > on how the naming scheme should look and there is a slight risk that > someone will have to re-implement and change things due to that we reach > concensus on some other solution than what is currently on roadmap. > I'm having difficult understanding just why you can't provide me with an > example of what you have in mind? Is it a secret? ;) Kristian, Nothing is secret, it is just question of choosing the right time for such discussion. For example, I wanted to understand first the details of the VLAN creation API on both BSD and Linux because it has impact on the interface naming. Anyway, I just committed the first-cut implementation, and I will start new thread on the subject on xorp-users ML for input what the final configuration scheme should look like. There I will address your question about the naming on FreeBSD and Linux. Regards, Pavlin P.S. BTW, I read the old "Some thoughts" thread. The thread is very long and there were a number of ideas what the VLAN setup should look like, but at the end I didn't see any consensus. > -K > > _______________________________________________ > Xorp-hackers mailing list > Xorp-hackers at icir.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers From arjun at ceeyes.com Wed Sep 26 03:19:46 2007 From: arjun at ceeyes.com (arjun at ceeyes.com) Date: Wed, 26 Sep 2007 06:19:46 -0400 Subject: [Xorp-hackers] How to start with the downloaded XORP source code for RIP Message-ID: <380-22007932610194670@M2W040.mail2web.com> Hi! I have downloaded the XORP source code for RIP. Please tell me the detailed steps to complile the sourcecode. Regards, Arjun -------------------------------------------------------------------- mail2web.com ? What can On Demand Business Solutions do for you? http://link.mail2web.com/Business/SharePoint From pavlin at icir.org Wed Sep 26 09:32:12 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Wed, 26 Sep 2007 09:32:12 -0700 Subject: [Xorp-hackers] How to start with the downloaded XORP source code for RIP In-Reply-To: Message from "arjun@ceeyes.com" of "Wed, 26 Sep 2007 06:19:46 EDT." <380-22007932610194670@M2W040.mail2web.com> Message-ID: <200709261632.l8QGWCFk009058@possum.icir.org> arjun at ceeyes.com wrote: > Hi! > > I have downloaded the XORP source code for RIP. > Please tell me the detailed steps to complile the sourcecode. The "Getting Started" Web page contains basic information how to do it and how to configure XORP: http://www.xorp.org/getting_started.html The XORP User Manual (available from the XORP Web site) contains more detailed information on the subject. Regards, Pavlin From xonia10 at yahoo.es Thu Sep 27 01:16:11 2007 From: xonia10 at yahoo.es (Sonia) Date: Thu, 27 Sep 2007 10:16:11 +0200 (CEST) Subject: [Xorp-hackers] IGMP in XORP Message-ID: <927326.75736.qm@web23105.mail.ird.yahoo.com> Hi!! I've recently compiled xorp package because and I need it to implement IGMP in an embedded system. I only need IGMP protocol and I don't know which binaries or libraries I have to include. I hope not to need all compiled binaries because they are too big for my system. Can anyone help me??? Best Regards, Alex ____________________________________________________________________________________ S? un Mejor Amante del Cine ?Quieres saber c?mo? ?Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html From tungpth at yahoo.com Thu Sep 27 00:40:57 2007 From: tungpth at yahoo.com (Tung Pham Thanh) Date: Thu, 27 Sep 2007 00:40:57 -0700 (PDT) Subject: [Xorp-hackers] XORP Configuration Message-ID: <358733.63514.qm@web50304.mail.re2.yahoo.com> Hi, I'm newbie with XORP. So, many think I don't understand. My question: 1, I have 1 Server (windows 2003), It have two network card. 10.192.254.92/93, 10.1.254.10 2, I have four ADSL Connection (10.1.254.1/4). My Local Network conect to Internet over 10.192.254.92/92. So, If I use XORP, can I config xorp to use four adsl, and loadbalancing with four ADSL. We really appreciate your help Thanks Tungpth ____________________________________________________________________________________ Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545469 From pavlin at icir.org Thu Sep 27 11:35:10 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Thu, 27 Sep 2007 11:35:10 -0700 Subject: [Xorp-hackers] XORP Configuration In-Reply-To: Message from Tung Pham Thanh of "Thu, 27 Sep 2007 00:40:57 PDT." <358733.63514.qm@web50304.mail.re2.yahoo.com> Message-ID: <200709271835.l8RIZAG3002727@possum.icir.org> Tung Pham Thanh wrote: > Hi, I'm newbie with XORP. > So, many think I don't understand. > > My question: > 1, I have 1 Server (windows 2003), It have two network > card. 10.192.254.92/93, 10.1.254.10 > 2, I have four ADSL Connection (10.1.254.1/4). > > My Local Network conect to Internet over > 10.192.254.92/92. > > So, If I use XORP, can I config xorp to use four adsl, > and loadbalancing with four ADSL. XORP doesn't support load balancing (yet). You could use it for routing among the network interfaces, but this is not the question you are asking :) Regards, Pavlin > > > We really appreciate your help > Thanks > Tungpth > > > > ____________________________________________________________________________________ > Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. > http://answers.yahoo.com/dir/?link=list&sid=396545469 > > _______________________________________________ > Xorp-hackers mailing list > Xorp-hackers at icir.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers From pavlin at icir.org Thu Sep 27 13:18:50 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Thu, 27 Sep 2007 13:18:50 -0700 Subject: [Xorp-hackers] IGMP in XORP In-Reply-To: Message from Sonia of "Thu, 27 Sep 2007 10:16:11 +0200." <927326.75736.qm@web23105.mail.ird.yahoo.com> Message-ID: <200709272018.l8RKIo8X003692@possum.icir.org> > I've recently compiled xorp package because and I need > it to implement IGMP in an embedded system. > > I only need IGMP protocol and I don't know which > binaries or libraries I have to include. I hope not to > need all compiled binaries because they are too big > for my system. The answer is depends how much of XORP (and in what form) you want to use in your system. Out-of-the-box (i.e., if you don't want to do any programming or integration at source code level), you need the following binaries: * The FEA (fea/xorp_fea) which talks to the system/kernel. * The IGMP (mld6igmp/xorp_igmp) which is the protocol implementation itself. * The XORP router manager (rtrmgr/xorp_rtrmgr) which binds things together so you can startup and configure things. Note that it also includes the XORP Finder which is used for our IPC (XRLs). * The CLI (rtrmgr/xorpsh) which can be used to monitor and configure the system on-the-fly. * You also need the rtrmgr/xorpsh template files inside xorp/etc/templates. Actually, in your case you will need just a subset of them: fea.tp, igmp.tp, interfaces.tp, mfea4.tp, protocols.tp, rtrmgr.tp, fea.cmds, igmp.cmds, mfea.cmds, xorpsh.cmds If you don't want to use the router manager for example, then you will need instead the XORP Finder (libxipc/xorp_finder) so the FEA and IGMP processes can still communicate with each other. Of course then you will lose the ability to configure XORP using xorpsh, and you will need to use, say, shell scripts that directly send the XRLs to the FEA and IGMP processes. If you want to go even further and include directly the FEA, IGMP and the XORP Finder inside some other binary, you can do it, but it will be a bit tricky because it requires linking with a relatively long list of internal XORP libraries. The Makefile.am files in each directory (fea, mld6igmp, libxipc) will give you idea about the list of libraries you will need. Typically this list is in the LDADD variable. Please let us know if the above doesn't answer your question and/or if you had something else in mind for integrating IGMP in your system. Regards, Pavlin P.S. FYI, debugging is enabled by default when compiling XORP hence you get very large binaries. See "Section 4. Performance optimization" inside xorp/BUILD_NOTES for some hints how to turn it off and enable optimization. From arjun at ceeyes.com Fri Sep 28 03:33:32 2007 From: arjun at ceeyes.com (arjun at ceeyes.com) Date: Fri, 28 Sep 2007 06:33:32 -0400 Subject: [Xorp-hackers] How to test the working of RIP on stand alone computer system Message-ID: <380-22007952810333212@M2W010.mail2web.com> Hi all! I want to test the Working of XORP RIP on my computer system (Linux plateform) So plz tell me that, is it possible, if yes then plz write the steps to be taken in order to perform this test. Also plz tell me that, can we compile this XORP source code on RTlinux,VxWorks,e-cos. if yes the how? Regards, Arjun -------------------------------------------------------------------- mail2web - Check your email from the web at http://link.mail2web.com/mail2web From pavlin at icir.org Fri Sep 28 10:15:03 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Fri, 28 Sep 2007 10:15:03 -0700 Subject: [Xorp-hackers] How to test the working of RIP on stand alone computer system In-Reply-To: Message from "arjun@ceeyes.com" of "Fri, 28 Sep 2007 06:33:32 EDT." <380-22007952810333212@M2W010.mail2web.com> Message-ID: <200709281715.l8SHF3ff029362@possum.icir.org> arjun at ceeyes.com wrote: > Hi all! > > I want to test the Working of XORP RIP on my computer system (Linux > plateform) > So plz tell me that, is it possible, if yes then plz write the steps to be > taken in order to > perform this test. The simplest test that comes to mind is to connect two Linux boxes and then configure and run RIP on both. The use the CLI to see whether RIP is working between them. See the XORP User Manual for information how to configure RIP and use the CLI. > Also plz tell me that, can we compile > this XORP source code on RTlinux,VxWorks,e-cos. > if yes the how? I haven't used RTLinux, but if it hasn't removed the network-related API used by XORP, I don't see any reason why it shouldn't work. I doubt that XORP will compile on VxWorks and e-cos as-is, but I have to admit that I have zero experience with them so I don't know how difficult will be to get it working. If you have access to any of those systems I'd recommend to give it a try and let us know how it goes. It will be even better if you fix the problems and send us a patch :) Regards, Pavlin > Regards, > Arjun > > -------------------------------------------------------------------- > mail2web - Check your email from the web at > http://link.mail2web.com/mail2web > > > > _______________________________________________ > Xorp-hackers mailing list > Xorp-hackers at icir.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers