From zamfiranca at gmail.com Thu Jul 9 07:44:54 2015 From: zamfiranca at gmail.com (Anca Zamfir) Date: Thu, 9 Jul 2015 16:44:54 +0200 Subject: [Xorp-users] Latest XORP release/ tarball file Message-ID: Hi, I have been using xorp 1.8.5 and need some of the changes that went in around routing and policies. Is there a plan to release 1.8.6 soon? I see xorp 1.8.5-4 being mentioned. Is there a way to get access to a minor release maybe? Thanks in advance, Anca -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20150709/9fc9eaff/attachment.html From greearb at candelatech.com Thu Jul 9 07:50:30 2015 From: greearb at candelatech.com (Ben Greear) Date: Thu, 09 Jul 2015 07:50:30 -0700 Subject: [Xorp-users] Latest XORP release/ tarball file In-Reply-To: References: Message-ID: <559E8A36.1020103@candelatech.com> On 07/09/2015 07:44 AM, Anca Zamfir wrote: > Hi, > I have been using xorp 1.8.5 and need some of the changes that went in around routing and policies. Is there a plan to release 1.8.6 soon? I see xorp 1.8.5-4 > being mentioned. Is there a way to get access to a minor release maybe? Just grab the latest from the git repo and use that. Thanks, Ben > > Thanks in advance, > Anca > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > -- Ben Greear Candela Technologies Inc http://www.candelatech.com From zamfiranca at gmail.com Thu Jul 9 08:01:05 2015 From: zamfiranca at gmail.com (Anca Zamfir) Date: Thu, 9 Jul 2015 17:01:05 +0200 Subject: [Xorp-users] Latest XORP release/ tarball file In-Reply-To: <559E8A36.1020103@candelatech.com> References: <559E8A36.1020103@candelatech.com> Message-ID: Hi, Thanks for the quick reply! Yes, I picked the latest up and looks good so far with my testing, but "latest" is a moving target and would have liked a "release" reference point (other than the git commit hash :))...if there is any plan for it. What is the XORP release plan and process? And also curious on the level of testing done on latest. thanks again, -anca On Thu, Jul 9, 2015 at 4:50 PM, Ben Greear wrote: > On 07/09/2015 07:44 AM, Anca Zamfir wrote: > >> Hi, >> I have been using xorp 1.8.5 and need some of the changes that went in >> around routing and policies. Is there a plan to release 1.8.6 soon? I see >> xorp 1.8.5-4 >> being mentioned. Is there a way to get access to a minor release maybe? >> > > Just grab the latest from the git repo and use that. > > Thanks, > Ben > > >> Thanks in advance, >> Anca >> >> >> _______________________________________________ >> Xorp-users mailing list >> Xorp-users at xorp.org >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> >> > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20150709/0bd4c208/attachment.html From greearb at candelatech.com Thu Jul 9 09:22:27 2015 From: greearb at candelatech.com (Ben Greear) Date: Thu, 09 Jul 2015 09:22:27 -0700 Subject: [Xorp-users] Latest XORP release/ tarball file In-Reply-To: References: <559E8A36.1020103@candelatech.com> Message-ID: <559E9FC3.8090901@candelatech.com> On 07/09/2015 08:01 AM, Anca Zamfir wrote: > Hi, > Thanks for the quick reply! Yes, I picked the latest up and looks good so far with my testing, but "latest" is a moving target and would have liked a "release" > reference point (other than the git commit hash :))...if there is any plan for it. What is the XORP release plan and process? And also curious on the level of > testing done on latest. The project is mostly idle..I don't really have much time or interest to make changes, and the current code works fine for our needs. I'm not sure it is worth going through the work to package up a 'release'. We do testing on xorp (we use it to make virtual routers in our network testing equipment), but aside from that, I'm not sure how much it is being used, and mostly our own testing involves xorp <-> xorp communication, so it may not get a lot of third-party router interaction. If you find a release you like, save the hash and/or tag it locally... If you find bugs, send bug reports and/or patches. Thanks, Ben > > thanks again, > -anca > > > On Thu, Jul 9, 2015 at 4:50 PM, Ben Greear > wrote: > > On 07/09/2015 07:44 AM, Anca Zamfir wrote: > > Hi, > I have been using xorp 1.8.5 and need some of the changes that went in around routing and policies. Is there a plan to release 1.8.6 soon? I see xorp > 1.8.5-4 > being mentioned. Is there a way to get access to a minor release maybe? > > > Just grab the latest from the git repo and use that. > > Thanks, > Ben > > > Thanks in advance, > Anca > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > > -- > Ben Greear > > Candela Technologies Inc http://www.candelatech.com > > -- Ben Greear Candela Technologies Inc http://www.candelatech.com From reinhard.frank at siemens.com Fri Jul 10 08:35:17 2015 From: reinhard.frank at siemens.com (Frank, Reinhard) Date: Fri, 10 Jul 2015 15:35:17 +0000 Subject: [Xorp-users] xorp Multicast REGISTER/STOP Message-ID: <96B148F7466A744BA2ABE6F3B6480DFB12A758AE@DEFTHW99EH5MSX.ww902.siemens.net> Hello all, perhaps some has a hint for me ? Currently I am working with XORP multicast functionality and the multicast network is up and running, works fine(PIM-SM) The n3 router has different interface eth0,eth1,eth2,eth3 (the picture below) and one loopback interface 172.16.255.3 configured. [cid:image001.png at 01D0BB2E.CF7C1650] Now following problem occurs: The border router sends PIM Register messages to the n3 node loopback interface (SRC_IP 10.1.0.2 -> DST_IP 172.16.255.3) and the n3 nodes sends the REGISTER STOP back (SRC_IP 10.0.0.13 -> DST 10.1.0.2). The xorp routing instance accepts this REGISTER STOP message but my current vEOS Arista version does NOT. I think this depends on the fact that the response Source IP address was not the SENT destination IP. (RPF reverse path forwarding topic should not be happen on the Arista, because this device is with one interface connected to the backbone.) My feeling is that the XORP instance always sends the REGISTER Stop message back with the Source IP Address of the first interface on that the REGISTER message arrives the XORP instance (in my case node n3). But why not from the Loopback address? And the same problem occurs if the RP address is configured with an "ethx" ip address instead of the loopback address. Short tcpdump trace: [cid:image002.png at 01D0BB2E.CF7C1650] Thx for any feedback Reinhard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20150710/5157d43f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 37568 bytes Desc: image001.png Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20150710/5157d43f/attachment-0002.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 11695 bytes Desc: image002.png Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20150710/5157d43f/attachment-0003.bin