From vincent@brindille.org Wed May 4 13:25:28 2005 From: vincent@brindille.org (Vincent Gauthier) Date: Wed, 04 May 2005 14:25:28 +0200 Subject: [Xorp-hackers] create Xorp LiveCD Message-ID: <4278BF38.3090003@brindille.org> Hi all, I want to modify the LiveCD in order to change the keymap from qwerty to azerty. I have copied the iso image from the Xorp LiveCD on my hard disk and modified the rc.conf to change the default keymap. After that I have created the new iso image with mkisofs (mkisofs -b boot/boot0 -o /tmp/new_iso.iso /new_iso/master/) But I am unable to boot with this new iso image ? Could anybody say me how to create a bootable iso image of xorp liveCD Best Regards. Vincent From pavlin@icir.org Wed May 4 18:59:11 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 04 May 2005 10:59:11 -0700 Subject: [Xorp-hackers] create Xorp LiveCD In-Reply-To: Message from Vincent Gauthier of "Wed, 04 May 2005 14:25:28 +0200." <4278BF38.3090003@brindille.org> Message-ID: <200505041759.j44HxB8n015563@possum.icir.org> > Hi all, > I want to modify the LiveCD in order to change the keymap from qwerty to > azerty. I have copied the iso image from the Xorp LiveCD on my hard disk > and modified the rc.conf to change the default keymap. After that I > have created the new iso image with mkisofs > (mkisofs -b boot/boot0 -o /tmp/new_iso.iso /new_iso/master/) > > But I am unable to boot with this new iso image ? > > Could anybody say me how to create a bootable iso image of xorp liveCD Vincent, You can get the scripts we use for the LiveCD generation from the anon. CVS. E.g., if you use csh/tcsh: setenv CVSROOT :pserver:xorpcvs@cvs.xorp.org:/cvs cvs login [press for an empty password] cvs checkout other/LiveCD The scripts are in the other/LiveCD directory. There is a README there to tell you how to use it. Note that the scripts are for FreeBSD-4.9 or higher, but they may not work for FreeBSD-5.x. Also, note that currently we have kernel config patches only for 4.9 and 4.10. If you are using a different 4.x distribution, then you have to create a kernel config patch similar to files/patch_generic_freebsd4.9 or files/patch_generic_freebsd4.10. To do so, copy GENERIC to LIVECD, edit LIVECD similar to one of the above two patches, and then generate the patch by "diff -u GENERIC LIVECD". Finally, you have to edit livecd.sh to add an entry for your OS distribution: search for, say, 4.10-RELEASE and add a similar entry with your new kernel patch. Note that the LiveCD build process has a number of steps and you can stop at any moment and continue later. Try to play a bit with the system to get the feeling how it works and then decide where/when to apply the rc.conf modifications. Regards, Pavlin From mehdi.bensaid@rd.francetelecom.com Mon May 9 13:09:44 2005 From: mehdi.bensaid@rd.francetelecom.com (zze-BEN SAID Mehdi RD-CORE-ISS) Date: Mon, 9 May 2005 14:09:44 +0200 Subject: [Xorp-hackers] error Message-ID: <3418F3471F1CA4409901547349FFAE2E03C3F4CC@FTRDMEL2.rd.francetelecom.fr> I had this displayed on my xorp_rtrmgr debug window, when trying to chage the configuration via an indirect script: [ 2005/05/09 14:03:18 ERROR xorp_rtrmgr:3578 RTRMGR +569 xrl_rtrmgr_interface.cc client_updated ] Failed to notify client that config changed: Transport failed What's the 3578 error? Does anybody have a possible interpretation of this? From atanu@ICSI.Berkeley.EDU Mon May 9 18:07:39 2005 From: atanu@ICSI.Berkeley.EDU (Atanu Ghosh) Date: Mon, 09 May 2005 10:07:39 -0700 Subject: [Xorp-hackers] Re: [Xorp-users] Erreur In-Reply-To: Message from "zze-BEN SAID Mehdi RD-CORE-ISS" of "Mon, 09 May 2005 14:07:09 +0200." <3418F3471F1CA4409901547349FFAE2E03C3F4BF@FTRDMEL2.rd.francetelecom.fr> Message-ID: <6517.1115658459@tigger.icir.org> The number after the process name is its process id, not an error number. Atanu. >>>>> "zze-BEN" == zze-BEN SAID Mehdi > writes: zze-BEN> I had this displayed on my xorp_rtrmgr debug window, when zze-BEN> trying to chage the configuration via an indirect script: [ zze-BEN> 2005/05/09 14:03:18 ERROR xorp_rtrmgr:3578 RTRMGR +569 zze-BEN> xrl_rtrmgr_interface.cc client_updated ] Failed to notify zze-BEN> client that config changed: Transport failed What's the zze-BEN> 3578 error? Does anybody have a possible interpretation of zze-BEN> this? zze-BEN> _______________________________________________ Xorp-users zze-BEN> mailing list Xorp-users@xorp.org zze-BEN> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From jer_log@hotmail.com Wed May 11 01:31:13 2005 From: jer_log@hotmail.com (jer log) Date: Wed, 11 May 2005 00:31:13 +0000 Subject: [Xorp-hackers] FW: RE: [Xorp-users] using XORP (bgp) to test third party router Message-ID: Can someone help me on this please? >From: "jer log" >To: jer_log@hotmail.com, xorp-users@xorp.org >Subject: RE: [Xorp-users] using XORP (bgp) to test third party router >Date: Wed, 11 May 2005 00:02:27 +0000 > > >Folks, > I have since got some peering (bgp test harness) with a third party >router going... > But i have problems in specifying multiple peers. > Specifically the router requires these peers to come from multiple ip >addresses. > > How do i specify a test peer's ip address? > I am assuming configure_bgp() {} routine configures the peers in XORP. > >Thanks, >-Jer > > So how do i specify the peer programs to >>From: "jer log" >>To: xorp-users@xorp.org >>Subject: [Xorp-users] using XORP (bgp) to test third party router >>Date: Tue, 10 May 2005 16:27:22 +0000 >> >>Hi, >> I am (a newbie) trying to use the bgp harness test suite of XORP to test >> a third party router. >> Has this been done? >> What are the processes i need to run to achieve this? >> I have been able to compile xorp in a redhat linux. >> >> If i just modify bgp/harness/test1.sh it just stops at coord reset. >> I guess i must start the coordinator process... >> >> Thanks for your help >>-Jer >> >>_________________________________________________________________ >>Express yourself instantly with MSN Messenger! Download today - it's FREE! >>http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ >> >>_______________________________________________ >>Xorp-users mailing list >>Xorp-users@xorp.org >>http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > >_________________________________________________________________ >Express yourself instantly with MSN Messenger! Download today - it's FREE! >http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ > >_______________________________________________ >Xorp-users mailing list >Xorp-users@xorp.org >http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users _________________________________________________________________ Is your PC infected? Get a FREE online computer virus scan from McAfee Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 From asornaoglu@yahoo.com Wed May 11 22:39:10 2005 From: asornaoglu@yahoo.com (abidin sornaoglu) Date: Wed, 11 May 2005 14:39:10 -0700 (PDT) Subject: [Xorp-hackers] How can we handle this error? Message-ID: <20050511213910.59825.qmail@web52809.mail.yahoo.com> --0-2125306221-1115847550=:57833 Content-Type: text/plain; charset=us-ascii Content-Id: Content-Disposition: inline hi, I am a student at cal state fullerton.we are working on a class project right now.Our project is related to xorp and rip. We have: 1) 2 PCs stations (with one ethernet card for each). Every pc connect to one PC-Router 2) 3 PC-Routers, two have three ethernet cards that connect to each other, with the third one, and with one of the two stations. and the third PC-Router has two ehternet cards that connect only the first two PC-routers. See the attached picture for the topology. We gave an ip number to each ethernet card in pcs and then installed the xorp on the three PC-routers. When we try to run RIP, two of the PC-Routers gives this error continuasly. xorp-rip:511 RIP +526 port.cc port_io_send_completion But the first one (which is connected to the Pc station) works fine. My questiones are: 1-)How can we handle that error? we configure the three PC-router with the same way!! 2-)To test the working RIP-XORP PC-Router, we ping the IPs assigned to every ethernet card in it from the PC station connected to it. but we only got reply from the IP that is from same zone of the station !! as it looks like that RIP is not running to route to the other IPs at the same router machine from different zone!!! Any suggesting !!! We really appreciate your help thank you abidin __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-2125306221-1115847550=:57833 Content-Type: image/pjpeg; name="Our Topology.jpg" Content-Transfer-Encoding: base64 Content-Description: 68820072-Our Topology.jpg Content-Disposition: inline; filename="Our Topology.jpg" /9j/4AAQSkZJRgABAQEBLAEsAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsL DBkSEw8UHRofHh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/ 2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIy MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCACvAioDASIAAhEBAxEB/8QA HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1 dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU 1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD3+iiigAoo ooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiii gAooooAKKKKACiiigAooooAKKKKACiiigDjNA0UaxpbX13qmsedJdXIPl6jK igLM6gBQ2AAABWp/wiVr/wBBTXP/AAaT/wDxVN8EusnhiNkYMpurvBByD/pE ldDQByraJpa3DQf2xrxdHWNiuo3DKrNjClgcA8jgnuPUVb/4RK1/6Cmuf+DS f/4qpotGuLeHUrW3uzHDeySyrKv+thZxzg9/myQe3AxxWc3g7fJNJ58KPJDK ibYBtgkdIVDoM8YMRbqDlzz3IAt9oOm6dCstzqviAI7rGuzULmQlj0GFJNQR 6bok6q8Oua5MrIr7otRuXChuhYg/L+OOhrVGg7dGtbBDHEIrlZ28ouF4k3kL liRn6/4VLp2jLpF3dfYvLW0uWRzEV5jZUVOD3BVF4PQ5POcUAVv+EStf+gpr n/g0n/8AiqP+EStf+gprn/g0n/8Aiq36KAMTwdcT3Xg3SJ7mV5pntULySNuZ jjqT3Nbdc/4G/wCRG0X/AK9E/lXQUAFFFFABRRRQAUUUUAFFFFABRRRQAUUU UAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQ AUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAB RRRQAVia5czXM0Wh2MjR3N0u6eZOtvBnDNnsx+6vuSf4TWhqeow6Vp8t5PuK oAFRBlpGJwqqO7EkAD1NVdD06a0hmu77a2pXjCW5KnITjCxqf7qjgepyepNA GH4bM+neBbePS4UBS+khRPKZ1SM3bKx2qQflUk9e1SHXNfaeS3Wy2skpQymx lKkb5xuHOPuxwnqfvn1GE0c+IdFsWsRoC3CpcTusq3qKGV5XcHBHHDCr/wDa 3iH/AKFn/wAn4/8ACgDNbW/EMkc++wIVoGaMLZzBt4SBtuQ2eTJKO3KexFPf xBrls04nsd48zbB5dnLuYeZOvA3fMdscTdRwxPpV/wDtbxD/ANCz/wCT8f8A hUNzd6xeRrHdeEIp0VgwWW8iYBh0IBHWgB2sNf3GlWNzYPKdSVPPQW5cQSfJ 86t2IIJ27ud209jVCWXUXs9Ta1GppKbSM6SJVlzv2EgSA/xeZ94P/DjPGa0l 1TX0QKvhcKqjAAvowAPypf7W8Q/9Cz/5Px/4UAZDJqy3+pSk6ksbQ3scIRpW DPuBTjomFHyFeuSMjgHo9Es57W1kae5ml89lkSOVmYwjYoK5b5j8wZucY3Yx xVP+1vEP/Qs/+T8f+FH9reIf+hZ/8n4/8KAE8Df8iNov/Xon8q6CsjwvYXGl +FtMsbtVW4gt0SRVbIDAcgHvWvQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQA UUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABR RRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFc 9d+KojK9vo9s2pzoxV3R9kEZHUNLgjI6YUMR3A61Qu/Ew1eWDw/ALjTdTvMi YTja0UI++0bD5XY9F2kkE5IG0ii4WNC2/wCJ/rRvm503T5GS1HaacZV5fcLy i++4/wB010FRW1tDZ2sVtbRLFBCgSONBgKoGABUtABRRRQAUUUUAFFFFABRR RQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFF ABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUA FFFFABRRRQAUUUUAFFFFABRRRQAUUVj+LJZLfwbrk0MjRyx6fO6OhwVYRsQQ exoATUPElra3LWVpFJqGoL962tsHy/eRj8qDvycnsDWZNpuoawCdcnBgP/MP tSRD9Hbhpfxwp/u8Zqt4U1Kxt9JitIVtzDBhHe2AOx+MiRV5DdyfxOK6yIRT RrJE6Oh5DIQRWampLQbVjOjtlgiWKKJY40G1UVcBR6AdqivNNg1GA213bJPE SDsdc4I6EehHY9RWpK0UAy5564A5rF1C+mOEjby0PVV6/iaibjBXGot6lGLU Lnw/rFhpy6ib61upxAYLgl5bfIJBEvVhx0fLc/e4xXZ15bIc+KNG5B/09On0 b/P+FepVpTk5RuxNWCiiirEFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFA BRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAF FFc2+r67da1qVlpljpzQ2MiRtJc3LozFo1fgKhGPmx17UAdJRXP+d4v/AOfH Q/8AwNm/+NUed4v/AOfHQ/8AwNm/+NUAdBRXP+d4v/58dD/8DZv/AI1R53i/ /nx0P/wNm/8AjVAHQUVz/neL/wDnx0P/AMDZv/jVHneL/wDnx0P/AMDZv/jV AHQUVz/neL/+fHQ//A2b/wCNVY8P6pealHfpf28EFzZ3RtnEEhdGwiNkEqD/ AB46dqANiiiigAooooAKKKKACiiigAooooAKKKKAKyXi/bmtJUMcmN0ZPSVc ckH1B6j8e9Wagu7SK8h8uTIIO5HU4ZGHRgexrhtf8WagZJfD+msv9oI3l3N/ FjbGuM/KO0hB5B4XrzwC4xcnZClJRV2a2r/EXw5omrHTru5maVP9c8MDSJCf RioPPPQZx3xVnxPd2998PdburSeOe3l0u4aOWNgysDE3IIrldI02PQoxPHAs 8fltHcQP83noxyRz1bPOT1yc9cjDu9SttLufEOj6Q7yaRqej3dwICjKbSZYj uyCMgEdfcr3yTpOny7EwmpEq21v4b1NfEM+lzPa3Nqsb6hpzMJLdsAZmiGRI AeQxBx0IPFbXgjWb3V2uJrr+xrkwrmO/02QhpMhuJI2G5GwM8+vFOn8R23hj QrG8uopWjkKoWiA+UBCxJzjPCngZJ6AHpW1Hpthb6tPqkMCRXEsPlymNAoYD JyQByeev0rijJOCub8updaXcCCOtZ96eUGR34qUXUXGT9eOlV7mVZdm09M5G KwqSTjuaPlUbI5PWtTg0fU9P1G5LNFb3iuVjGWbCthR6knAH1HSrGrw+JtW0 6PWL7W7zTZLlx9g0vT5DGADjl2GCwC5JJ46cDO05nivTJ9ZnsbO1kRbhr1TF v+7uCtgHr+fOPTjFa2jarJd3M6ak051SM+VOlzgOmOdoAACjv8oweozmvQwc U43OSvPkR0PhHxdJeyro2ssE1RAfKlxtW7UdSB0DgdV/EcZC9lXmGtaLHfwi RNyyKQySISrKw5BBHRgeQRW74R8XSXsq6NrLBNUQHypcbVu1HUgdA4HVfxHG Qu9Wlb3o7GdKrf3ZbnZUVWvb2OyhDuGd3bZFEnLSN2UD/IABJwATRZJdLCWv JFaZ23FEHyxj+6DjJx6nqc9BgDCxuWaKKKQBRRRQAUUUUAFFFFABRRRQAUUU UAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQ AVyvhLUIdT1rxPdW2TA19GqORjeFgjXcPUEg4PcYPermtyyaldJ4ftXZTMnm X0qHBhtySMA9mcgqPQBz1UVSgt9W0TWdVaw0WO5s7p4nh8u5SLYFhSPbtI/2 PyxQB1dFYH9reIf+hZ/8n4/8KP7W8Q/9Cz/5Px/4UAT6/FLMunpGJSpvF8wx qxAXa3LbcHGcd6p6NbXdlNNY6pNe3ckbQi2usPh40jTJLDhSZBIWBOSDzkYq X+1vEP8A0LP/AJPx/wCFH9reIf8AoWf/ACfj/wAKAN+isD+1vEP/AELP/k/H /hR/a3iH/oWf/J+P/CgDfrn/AAz/AMf3iT/sKt/6Ihpf7W8Q/wDQs/8Ak/H/ AIU/w1Z31uNUuL+2W2lvb5rhYlkEm1fLROSOM5Q0AblFFFABRRRQAUUUUAFF FFABRRUN1bJd27QuXUNjDI21lIOQQfUEUATUVnWd5LHOLC/IFyATHKBhZ1Hc ejDuv4jiuZ8V+K5muX0LQpP9M+7dXS8i2H91exkx+Cjk84BpQbdkJySV2Hiv xXM1y+haFJ/pn3bq6XkWw/ur2MmPwUcnnAObpOkwaZahQuPUk5LHqeTyeeST 35PNGk6TBplqFVfqc5LHqeTyeeST16nmqmq6rO9zFp2nRNcX852RRIcH357K Opbt9cV1xgoqy+b/AK/r57cc5uT/ACQuratM9zFp2nRNcX052RRIcH357KOp Y9PrgVrT+FYfD3w/8RTTOtxqk+mXH2i4AwAPLbCIOyD9ep5rb8KeFIfD1u80 zrcapOB9ouMYAHZEHZB+vU81s6hYw6npt1YXG7yLmF4ZNpwdrAg4P0Nc9Spz aLY6KdPl1e55haeKrO0nGnanbr5CKjRzBd2MKrfMuOxOdwzjjdt4z1sF5bX1 mZ7S4inhdDtkicMp4PQiuK8SeHBpw26xGY4UCrFrMMQKMBwonUfdYf3jgd1Z c4E3hTTJdOTVLgT208NxBujuLd93mYDckkFu/eR/qK4GlFWe51Rk9joaRmVE LuwVVGSScACuehvLq/kaLS4TdOp2tIDshjP+0+DyPRQSOOK2bXwxHIyzavML 6ReVh2bYEPsn8R4HLE+2OlYexfVgot7GZZmXWNcsbuwjZ7S2uBM10wxGwAOA pPL5yORx15BGK3PEehHxTcLf6KI4b61XabpiQk5H/LE46gHPz/wngZ+YDWk0 q6v1SJJPs9sf9a4yHK/3V9M+vbt6joIYY7eBIYUVIo1CqqjAAHQCu+jeCuiK iT0PMtH1g3JktLuJoL2FvLmgkGGVh2P88jgjkcUus6NHfw703LKpDI6NtZWH III6MDyCK6bxb4SGtBdQ09lt9YgXEch4WZRz5b47eh6qfbIPL6PrBuWktLuJ oL2FvLmgkGGVh2P88jgjkcV306nNqt/6/r+tOCpT5PT8jV8G+IfteptY65IT rQUpbzOAqzRgchAOFfjLDv1HAwveV5hrOjR38O9NyyqQyOjbWVhyCCOjA8gi t3wj4ukvZV0bWWCaogPlS42rdqOpA6BwOq/iOMhcqtK3vR2/I2pVb+7Lc7Ki iobi6htvKEr4MriNFAJLMewA/En0AJPArnNyaiiigAooooAKKKKACiiigAoo ooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACqOr anHpOnvcujSvkJFCn3pZGOFQe5JHsOp4Bq9XP6b/AMT7Vv7Zfmwti0enKejn o8/48qp/u7j0egC7ommSafaO906y390/nXcq9GkIAwP9lQAq+yjvmtOiigAo oooAKKKKACiiigAooooAKKKKACiiigAooqlBrGm3V/NYW+oWst5D/rYElUun 1AORQBdooqot6BftaTRmJjzCxOVlGMnHuOePTn1wAW6KK4jxX4rma5fQtCk/ 0z7t1dLyLYf3V7GTH4KOTzgFxi5OyFKSirsh8Z+Ivtcx0DSPmu1cG4u1/wCX UjkBD/z0/wDQQcnqAaek6TBplqFVfqc5LHqeTyeeST16nmjSdJg0y1Cqv1Oc lj1PJ5PPJJ69TzVTVdVne5i07TomuL+c7IokOD789lHUt2+uK7IxUVb+v6/r fbjnNyf5INV1Wd7mLTtOia4v5zsiiQ4Pvz2UdS3b64ro9C8LTeFY/wC0Vb7f fSoFvcLyVzkCHuAv93+Lqeav+FPCkPh63eaZ1uNUnA+0XGMADsiDsg/Xqea6 KsKlXm0Wx0U6fLq9yO3uIrq3SeCQSROMqw71JVaGxjt7uaeFmQTcvEMbC397 HY+vrVmsnboahXP3Hgfwzc3RuW0a2SVjlzCDEJPXeEID/wDAs10FFICtFp9p DEsUVtFHGgwqIuAB6AVKkESHKxoD64qSiiw7sKKKKBBXLeLfCQ1oLqGnstvr EC4jkPCzKOfLfHb0PVT7ZB6msqWWTVZntbV2jtEYrcXCHBcjrGh/RmHToOcl ai2ndCaTVmcDouuC8MltcIYruFjFNE3VXHUHHH49D1HFSazo0d/DvTcsqkMj o21lYcggjowPIIro/FHgyHVLeO50pYrTU7WMJCQNqSoOkb47eh6qfbIPM6Nr DTvJaXkTw3kLeXNDKMMrdSCBx06EcEYI4rshUUtVv/X9f1px1KfJ6fkbPhvx u7p/Zeso7asgxA0aY+2/QdFcfxDgYywwM7eqsrKRZje3pV7x12gLysK/3E/T J6sR2AAHn+taLHfwiSMssikMjo21lYcggjkEHkGt3wj4ukvZV0bWWCaogPlS 42rdqOpA6BwOq/iOMhcatOy5o7G1Kpf3ZbnZUUUVzm4UUViah4mtba5eysop NRv0OHgtyMRH/po5+VPXBO4joDQBt0VyYv8AxTBJ9qkXTrpD96xj3IUH+xKf vH/eVQePu1saX4gsNVla3jZ4L1BmS0uF2SoPXH8Q/wBpSV96SaewGpRRRTAK KKKACiiigAooooAKKKKACiiigAooqtqN9Dpel3eoXG7yLWF55NgydqqWOB64 FAFmiuN03xlqOs2qanp+jxS6aesRugLr8UxsVhx8pfv1GOX6p47XTrcXDaVP Bb/899RmjtEbHUKHO4n6qB70AdfRWJ4e8V6R4mtll0+5BcruML4DgevBIYdt ykj3rboAKKKKACiiigDjvH+sanpkOkwaZdJateXTpNMxUFY0hkkOGYMq52dS Diqmj+bcIz6Drt1DcLj7VbanuuipP8RVnDKeOCrbD2BFHxJ/13h//r4uf/SO es+28IzDRdNu9ICnbbowgaZoWiJUEmGVQSme6EFDxwOaAMD4j+IPEnhfaJJN ZurCchLi+CxC38s/eQIihlJ6ZLK3XBNdn4N+JPh/xFaQW8Tw2UwCxpEG/dE4 wFVsDHTAVgpOOARzVSy8S39tcDT9UhW6jMkUE8N3AIrhFlLKrEpuimUlWHy7 eh44xU0fhbwpokU1/p/huwSe6jYSBlLIFbqu08AcdBgUAd7RXN+AppJ/CFu0 jsxW4uY13MThVuJFVeewAAHsK6SgAoorJ8MSyT+GNNllkaSRoFLO5ySfc07a XA1qKKKQBRWVfyyJr+kRq7BH87eoPDYTjNatNqwBRRRSAKKyfDcsk2iq8sjO /nzjcxycCZwP0AFa1NqzsAVk6n4hstNn+yASXd+V3LZ2y75Mdi3ZAf7zED3r F1zVrqTxWdEN49lp6WcdzNNbr+9Yu8i7dxztX93yQN3PBGM1tadpNhY2oSwh RInO8shyZCf4mbqxPqSSanmV7DsZEsGq6zn+1Lj7Jan/AJcbKQjcP+mkvDN9 F2jqDuFOl0DTJrKG0NlEkMHMAiHlmE+qFcFD7gg10H2ZfQ1FMsNuuZGxx071 DXVsFfoYsNzrmjkDL6zZ/wB1iqXSD2PCyfQ7T7sa2Le4sfEWmebEZDEXK/Mj RyRSKcHggFWBFc/qmrzG3ZbbECHjcD8x9s/4f/q5HTvEt5b6M3h/Sd0d9NcX E01yP+WMTTSKNv8Atkq2CeBgnngU6UvaPliKVoq7Og1/xZqPmy+HtNcNfIdl xqEeMRqR0A7S469l69wtVtJ0mDTLUKq/U5yWPU8nk88knr1PNGk6TBplqFVf qc5LHqeTyeeST16nmqmq6tM9zFp2nRNcX852RRIccjrz2Ud27fXivQhBRVl8 3/X9fPbinNyf5IbrOsTiVbHToHur+XKxQRfeOOT9AO57fXFdf4N8OWmj2H2z zku9QulHnXQGBgf8s0B5VQe3XOSeaXw14Zg8L2M13cMLnUpE3XNwF7DnYgPR B6dzyea0F3pHHqlhGzR3CLLNbd3BA+ZewcD8/wAjXPUqc2i2OinT5dXua1FN RxJGrrnawBGQQfyPIp1ZGoUUUUAFFFFABRVbT72PUdOtr2JWWO4iWRVcYIBG eas0AFFFFABTURIkVI1VEUYCqMACnUUAFct4u8Irrai/sGSDV4Vwkh4WZevl vjt6Hqp9sg9TVexvEv7RbiNWVWLDDdeGI/pTTad0JpPRnmujay07yWl3G8N5 C3lzQyDDK3UggcdMEHoRgjin61osd/CJIyyyKQyOjbWVhyCCOQQeQa1/E/h8 +J7s3mjiKG8s1KG6fIS5I/5YnHUA5+f+E8DPzAYujay07yWl3G8N5C3lzQyD DK3UggcdMEHoRgjiu2E+bVb/ANf1/WnHUp8np+R0HhHxdJeyro2ssE1RAfKl xtW7UdSB0DgdV/EcZC7+p67aaZKlsRLc30i7o7O3XfK46Zx0Vc/xMQvvXm3i rTvtkNvb2JI1S7mWOzKEhlkznzOORsALk+i+9afivWLfQfH02o3UksUUemW4 aWOMv5YM03LAA/L61yYi0HeJ00W5L3joZbXWdZ51Kc2Nof8Alys5CHYf9NJR g/gmP95hV2102Gxtkt7SCOCFB8scabVH4AVHpmvQXtpFcHbLBKAY7m1/eRuP XjJH6getaont2iEqyqyHoVOc44/p+lYXUjZqxU8hvSszW7XTHth/aUYkMZ3x hCRJG3TKsMFD7gg1oXN6/Kx4jXHXvXL3pJtnJ6+prGpUUWkh8ul2bvgrULnU NDle5mkmaK6lhR5CC+xW+UMQBkgcZxziujrz/wAFeI9C0zSLq3v9a060nF9M xjnukjbBbg4JzXSf8Jn4V/6GXRv/AAPi/wDiq6VsS9y7o91LeaeZpiC/nzpw McLK6j9AKv1yGg+L/DMOllJfEWkI32m4bDXsYODM5B69wQa0/wDhM/Cv/Qy6 N/4Hxf8AxVU9xG5RWH/wmfhX/oZdG/8AA+L/AOKo/wCEz8K/9DLo3/gfF/8A FUgLdzeTRa/p9opHkzwzs4x1K7Mc/wDAjWjXG3ni7w03ifS5V8Q6SY0guA7i 9jwpPl4yd3GcH8q1v+Ez8K/9DLo3/gfF/wDFU30A3KKw/wDhM/Cv/Qy6N/4H xf8AxVH/AAmfhX/oZdG/8D4v/iqQGnqEz2+m3U0Zw8cTupxnkAkUunzPcaba zSHLyQo7EDuQCawNU8Y+GJNJvETxHpDO0DgKt9ESTtPH3qXTPGPhiPSbNH8S aQrLAgZWvogQdo6/NT6AdNWH4z/5EbxB/wBg25/9FtTk8YeGJJFjTxHpDOxw qrfREk/TdTfGfHgXxBzj/iW3P/otqQHmugw6ukEupWcsmy1EEOYI90iL9mhf 5k6TJlzxw4H3TziujfWNJ8QaQ1r4j0uK509jhrm3U3EAPqcDzIWHfIG3+91q T4bYNlfA4/1tvkf9udvVrxRZWtvq+k6jBCkV419FE88Y2u6HIKsR94exoA4e 3+Dgs9Xgv/CviwW+ksFuNkgMpTcOGRlZeo6MCrY7nNej+H9VuX1u90ae8+3R 20Ec0d08QjkIZmUqwHDEbfvAL16dzheEZhF4H01j3tLVf/IZqx4WZR441JSw Bawh2jPXEkmcfTI/MUAd3RRRQAUUUUAeb+NdUtda1DRY9Pcz28F1Mk14o/0e N3t5Y1XzOhJZgOM4PBwSAek8L6lbvpMVi2Yr21iSOe3kGHQgYzjupwcMMg9j XiPgbxhLpLQ6E9rHPa3ahRbS5McxfqOh2sScdNp7gcsPRFtI7/C6W0l21sN3 2Cac2+oWWeojfPzqcDhjtOPvMMAAEfiRtnjViem3TT/5HuK6G6ElwYbSFdzt CpAH48+1edNeXd5rbi/kmS+N5a2lta3sKxXMqRySHeVGFYHzByAPp0J9iijS wsI2uTHHIIwHYcliO3vQBieFbuPQLOPQdVza3P2mdoJX/wBVcCSV3UI/Tdhv unDcHAI5rU1/xXpPhsxJfyymeZS0cEELyuyggE4UHA5HJxXB/EPxLLNoGr6d bwqkBsZSzsNzN8hIx6dKsyNFqPjvxDNc/MYRbQRB1zsj8vfge253NVCN5WZM 5csbmx/wtPQP+fbWP/BdJ/hWdoPxH0bT9BsbOe11YSwxKj7dPkIyPwqf7HZD /lnH/wB8D/Paj7HZD/lnH/3wP89q6PZR7nP7aXkWv+Fp6B/z7ax/4LpP8KP+ Fp6B/wA+2sf+C6T/AAqr9jsh/wAs4/8Avgf57UfY7If8s4/++B/ntS9jDuw9 tLyILz4j6NNrGm3KWureXb+b5hOnyZG5cDtWj/wtPQP+fbWP/BdJ/hVX7HZD /lnH/wB8D/Paj7HZD/lnH/3wP89qbpRD20vItf8AC09A/wCfbWP/AAXSf4Uf 8LT0D/n21j/wXSf4VV+x2Q/5Zx/98D/Paj7HZD/lnH/3wP8APal7GHdh7aXk V9C+I+jWGlrbz2mriQTTNgafIeGkZh29CK3tK+Inh/VtSi0+OW6trqY4iS7t XiEh9ASMZ46Z57Vk/Y7If8s4/wDvgf57VzHiuGC38CaxqMeyO9tNUja3kVcM jIiMijjjk7vqaU6cbXLhUlJ2NTx415F4r1G5sb2SzlttKtJTKsAmAUTXGdyd SvPOORjI6Va/4S200DT9Nu9Uv47eK+Xcb7Tg09nvGMg8EoSfUDvzwa0NRZl+ JlztJz/ZNsOP+utx+lZl34RsX+3X3hu9l0zUsOGS0kBt5JQvAkiOV9M/XpXF 7rk7nUr20O4W/drWI+bE5Zc+bGMKwzwRye1UpmyzNu5xyTSEv5UPmY8zb82O mcnNNJwCc49yKzk2zWMUtTAvv9Rn5R2yf5f5/wDrjL0XQriTSE17ToDPdQXN 1BcWysAbiHzmYBc8b1JJGcA7mHcEal9/qM/KO2T/AC/z/wDXGFYazqaaVa6D o119kuJ7m8ubm5UAtHEsxUBdwIyzN17BT6ilg03LQwnbkdxbrxOmpXS6Xo6y T6nIdn2XaY5Iz3DKwygHckce5rvfCnhSHw9bvNM63GqTgfaLjGAB2RB2Qfr1 PNcP9g8Uf9DZqf8A38j/APjdH2DxR/0Nmp/9/I//AI3XqzhUkrHHCdOLv1PU r/8A5B1z/wBcm/kah0bjQ9P4x/o0fT/dFeYvpviaRGR/FeplWGCPMj5B/wC2 dJDpfiSCGOGLxVqaRxqFVRJHwBwB/q6z+rzNfbwPXaK8l+weKP8AobNT/wC/ kf8A8bo+weKP+hs1P/v5H/8AG6Pq8w9vA9aoryX7B4o/6GzU/wDv5H/8bo+w eKP+hs1P/v5H/wDG6Pq8w9vA9aoryX7B4o/6GzU/+/kf/wAbo+weKP8AobNT /wC/kf8A8bo+rzD28D0PwqMeEdHGMYs4uPT5R9K168gttH8RWdrDbW/ijUo4 IUCRoskeFUDAH+rqX7B4o/6GzU/+/kf/AMbpyoTbbD28D1qivJfsHij/AKGz U/8Av5H/APG6PsHij/obNT/7+R//ABul9XmHt4HrVFeS/YPFH/Q2an/38j/+ N0fYPFH/AENmp/8AfyP/AON0fV5h7eB61XP6TazXegW0CTeTA0kvnFCQ7L5j fKp/hz3PXHTBORwv2DxR/wBDZqf/AH8j/wDjdRQaR4jtoVih8U6kkYJIUSR4 GTk/8s/Umj6vMPbwPXIoo4IkiiRY40UKqKMBQOgArnPE/g228RSR3UN1JYaj GNouokDb0/uup4Ydx3HY8nPF/YPFH/Q2an/38j/+N0jWXiZFLN4t1MADJ/eR /wDxumqFRO6F7eD0O90Dwra6HI909xNfajKu17u4xuC9diAABFzzgdeMk4Fc 34itBf8Aj28tfPlgaTR4Ak0X3o282Yg47jI5B4IyDVfwhruu2HiHTdJ1u9lv rbWLL7VaSSqu+F8F9hZQM5QMTkHBAAPPGhqgz8S5RjP/ABKoOD/11mrlr3in fyOiC2RyOst4i0yK2+0JdaULFSiavolusttLHjrPbnGNoH4ZOOK9HWZntrd/ NWQtGCXVdobk8gds1iaPf6pf3Or2eqaasFqjmOFsHE0ZLDByfm+UKSRx8+Oq mtWaWO2SCNY8KI+AowAMkYrKc1bU1jFLV7EjMSCSQOOprmdduWs9DvbpVDND C0gB6EgE81ufbVx90g1k6lEk1hLFIoZHUqwPQg8GuWUk5Kw5tPYw9D8K6eNE snmijlnkhWWWRyCZHYAsxPuSfz/K+PC+l/8APtCfy/z/APrrE0G38YvpaQaf psd5bWjG1Sf7SkZcJ8oyrDg4AzWn9h8f/wDQBT/wOir3o1Vyq0vzPMlRk27x LA8L6X/z7Qn8v8//AK6B4X0v/n2hP5f5/wD11X+w+P8A/oAp/wCB0VH2Hx// ANAFP/A6Kq9qv5vzJ9i/5SwPC+l/8+0J/L/P/wCugeF9L/59oT+X+f8A9dUI 4/HMt1NbLoSmWEKXBvYuN3T+Rqf7D4//AOgCn/gdFR7VfzfmHsX/AClgeF9L /wCfaE/l/n/9dA8L6X/z7Qn8v8//AK6r/YfH/wD0AU/8DoqPsPj/AP6AKf8A gdFR7VfzfmHsX/KWB4X0v/n2hP5f5/8A10Dwvpf/AD7Qn8v8/wD66oXSeObO NJJtCUK0iRDF5Efmdgq9Pcip/sPj/wD6AKf+B0VHtV/N+Yexf8pYHhfS/wDn 2hP5f5//AF0Dwvpf/PtCfy/z/wDrqv8AYfH/AP0AU/8AA6Kj7D4//wCgCn/g dFR7VfzfmHsX/KOXwjpN9qq6dJbReW9jcTZAH3lMarn6F8+nFcbofiz7U9tp viJ2vtItolto7WQldx8yZQ3UB2CxqMN6fKQ3B2o7rxpdXE76dpMZngSS2a4F 1GYxvGGQNwCwKg8ZwyjI7Vmal8P7a40dFsJLma9gt1/tCzeMrdQuGdjKkf8A y0QtI2QMk4G1iRg89aSl1udNKPLG1rHaLEbGGPUdOupJrNF8uHU7dPMeFV48 q5j4Lqp4z95ec7DljHqPiN9SudEtJY4Hme8injnsplmikjUkFh/Eo5GcjGTj cazdHhvIfB9lqGhX6f2tHEA80c37u428bZMgjtjLDK9Pl5xkDxZpTarb3Xij w1daFq0nypq2mMFWXcBuYA5jccDu5OOlYGp23gO1XUvBunxO7KkdvbMcDkgI 3Ge1b2vQaNBp8Z1JRGsPNuYiVlRvWNhhlPvkd81Dp9zZ6Fo1rpOmBjBbRLEJ ZANz4AG44AGTj0rmNbl/tS5+x2qyXd4rB3jjx8gx1djwg578nHANAHY+DdUu NV0id7iZpmgupIUkkCh2QY2ltoA3YPYCuirkPCem3Gi2ghnkRpppmlkEedq7 iPlBPJAx1wM+g7dfQBjan4gitLhrGyi+26kACYEbCxA8hpWwdgxz0JPOAay/ s2tq/wBsGsuL1uTC8QNsw/uCP7wHX5w27J544GX4k8GatFr934j8PXRa5uSj z2xYRuSqBBscjawwq/JICM5IZCc1DpHjqFpJLTW4WtLmEjz5CjIY+mDKjHdG M4+bJT0c5xQBha1oNudXtL2HTY7K+juBL/Z7TBYZ5M7t1rPjaGJHMbBd3Jwp +Y5njTUdM1a0tr+ObWbXULCQq4s4v9Isty8tNEcNgY4II6nB5r16S3gv7No5 VW5tZhtKugZHB9F6Nwe/p3rldd8KwC2NyUF1BaIWWKadkuLUDr5Nyvzp3+Ri QeB8ooA5LwT441e61JLK51qx1uy8p5YZ9h82FlKgblZQynk8ktnPB4rrbzX/ ADLj7Oqy3l44yLeEbnxzgnOAo92IFU9N+GUNxeW2s2ev3ItJ7cNh7SIXLhwp +aZQM9AOVJGTznmuzsPDdtpVv5FjHHEmck8lnPqzHljx1JJoA5aLws2oyGbX DEyMMfY4c7Mf9NGwC/04Xkgg9atap4NuNY1L+0tO1JNOuDGIpy9sZVlCklTg OhBGW5z0PTgY66PTkUgu5b2AxVxVCKFUAAdAKabTuhNJqzPO/wDhXniAdPFN n/4K5P8A5I9h+VH/AArzxAOnimz/APBXJ/8AJHsPyr0WitPbVO5Hsodjy/Uv BXiDTrFrn/hJbN9rIu3+zZB1ZV/57/T8qt/8K88QDp4ps/8AwVyf/JHsPyrs PEn/ACA5v+ukX/oxa1aPbVO4eyh2POv+FeeIB08U2f8A4K5P/kj2H5Uf8K88 QDp4ps//AAVyf/JHsPyr0Wij21TuHsodjy+DwT4gm1G7tB4ls1+zrGd/9myf NuB7efxjaKt/8K88QDp4ps//AAVyf/JHsPyrsLH/AJGPVv8Acg/k1atHtqnc PZQ7HnX/AArzxAOnimz/APBXJ/8AJHsPyp1r8Nb1r+3fVtfjvLCKdLh7OGya ISyJ9wsTK/A4zxyBivQ6KTqzas2NU4p3SPPdfvbew+IV3cXT7IU0q13MVJCj zrjk4BwPU9B3IqfQ/D9ho897d2Msri/cStucMo5ZvlwOmXY5OTyOcAAUfH+l P/bUmo3TmHTri0gt/tYUMsEsckjAyd1U+YMMCMEfeU4J4vd4g8MSfuZJorfO S0YDwNz1xgqO3XyvdmOSeSXxNXN4SS3PT7x2WVMEj5P6mqwkYY+Y8cVDqV20 UsALYzFuPHuf8P8APbKXV5bi4NrYQveXKnDpHjbF/vv0XscdcZwD25ZQlKWg 3e5fvv8AUZ+Udsn+X+f/AK44+zul0Y2niB/+PF3u7OaYEbYiZ96MT6H5xnpk D1FdhF4ce9Ky65OtyB0tIhiBf97vJ+OF/wBkV1+k23kjciBIguxFAwMew9K6 cOuRrqKcG4O+h5l/wsLQ/wDoKWf/AIFJ/j/nA/A/4WFof/QUs/8AwKT/AB/z gfh7DRXoe2X8pyexf8zPHv8AhYWh/wDQUs//AAKT/H/OB+B/wsLQ/wDoKWf/ AIFJ/j/nA/D2Gij2y/lD2L/mZ49/wsLQ/wDoKWf/AIFJ/j/nA/A/4WFof/QU s/8AwKT/AB/zgfh7DRR7Zfyh7F/zM8e/4WFof/QUs/8AwKT/AB/zgfgf8LC0 P/oKWf8A4FJ/j/nA/D0mYf8AFY2Jx/y4XHP/AG0g9v8AP8tim6sVb3Q9i/5m ePf8LC0P/oKWf/gUn+P+cD8D/hYWh/8AQUs//ApP8f8AOB+HsNFL2y/lD2L/ AJmePf8ACwtD/wCgpZ/+BSf4/wCcD8D/AIWFof8A0FLP/wACk/x/zgfh7DRR 7Zfyh7F/zM8e/wCFhaH/ANBSz/8AApP8f84H4H/CwtD/AOgpZ/8AgUn+P+cD 8PYayr3/AJGPSeP+Wc/8lo9sv5Q9i/5meZ/8LC0P/oKWf/gUn+P+cD8D/hYW h/8AQUs//ApP8f8AOB+HsNFHtl/KHsX/ADM8e/4WFof/AEFLP/wKT/H/ADgf gf8ACwtD/wCgpZ/+BSf4/wCcD8PYaKPbL+UPYv8AmZ49/wALC0P/AKCln/4F J/j/AJwPwZJ4/wBClieM6pZgMpH/AB8xnGfx/wA4H4eyUUe2X8oexf8AMeS+ GL//AIS7xv4eubBlks9D08i6mQhkMxRowoYcHIYsPYHIHFWvHNzdWni29uLN nWaPSrZgVTdgCeXORtbjGc8D6r1HqFYmveHY9XMd1bzfZNShG2K5C7gV67JF yN6e2QR1BBrmq++tDdaHCaT8QbWcCHUYminChjJCpdCp6MVGWUe/K+jt1rpd QmQPDlxzHn8NxriNb0FLVmOt6dc6cwJc3dpH9psnb+/t2nYT3JVG/wBo8GtG 51WHVntl0dhqbiEKTasGVDub775wvrgnPoDXLON1axrzOWjNsTISADye2D/n /wDUfSsyTUG1PfbaRAbyQHDTE7IIz33Pjk+yhiD2FWLTwo1wA+syCcH/AJdI ciEezHrJ+OFP92uqttOkCLFHCIo1GFGNoUegFTGik+41HuVvB+nS6RZvaSzi Z5Hed2VdqhmOcAZJx+NdNUFtbJbJgcsepqeuuKaWpnJpvQKKKKokyrH/AJGP Vv8Acg/k1atQR2sUV3PcqD5kwUPzx8ucfzNT0AFFFFAGP4jH+gWv/X/ads/8 t09q2Kgu7SG9iSOYEqkqSjB/iRgy/qBU9O+lgCuI+I515bTT30uOSbTllb+0 ookZmdMDbwhDlc5ztyfVWGRXb0UgOE8OeKtJ1WC2hi8m0kZdkKBwY2A/hiYD aQOfl4IHVVrZvtKttQVFuYTuiO6KaPMbwk8bkcfMD05Bx61W8Q+AtM1t5rq3 P9n6hL/rJoY1ZJiOnmxn5ZMepww7MK5U6x4g8ESLDrlt51huwlwJC0XOPuTM co3P3Zu44lPSgCTW/Cd2ss9ysk7faIys9xbQq0si4x/pFsMLOMEjcm18cYNc DN4K1Wz0yaXRYLufT5PlePR7n7TbSv0w0MmJI2Bxn75XHUV60PGOm3NvENKj kv7yQFhawr80fJGZScBeQRkkA4xzxV7wpY6jay6hc38kTz384uJViHyRERog UHA3cIOcDr0oAwbfw9q+oAPqXmWFqf8Al3hP71vZnHC/ReenzDpXSWOlx2Vu tvZWiwwqeFRMDPcn1J9a6GigCnbWQiIdzlh0A6CrlFFABWTrnhvTPEMUa30B 86LJguYXMc0BPdHHI+nQ9wa1qKAPLZdE8WeDLlW0iM6vp0kqh4oFRHKs/wA2 +M4UHBPzxlRnlk/iHQSaBrGvbTrhWC0HK6fbSYXH/TRxy30GB1BLCuyooAr2 VqtnbLCgVVUABVGAoAwAB6VYoooAKKKKACiiigBksMc8ZjlRXQ4JVhkcHI/W n0UUAFFFFADFijWV5VRRI4AZgOWx0z+dPoooAKKKKAGuiyIyOoZGBDKwyCPQ 1yV34EjicyaDqM2lZOTbbBNbevEZIKfRGUe1dfRSaT0YHFDwVfai6NrepxMs a7BDYxNEsgB6sxYt+AI9ya3rXQLeyt0t7URwwIMLHFEFUfQCteip5I9iueRU i0+CM5ILn/a6Vb6UUVSSWwm29wooopiCiiigAooooAoSWTvr1tfgr5cVrLCR 3y7RkY9vkP6Vfoop3AKKKKQBRRRQAVRuLOSbVrG7UrsgSUNnr8wXGPyq9RQA UUUUAFFFFABRRRQAUUUUAFIqqudqgZOTgdTS0UAFFFFABRRRQAUUUUAFFFFA BRRRQAUUUUAFFFFABTZI0ljaORFdGBVlYZBB6ginUUAUtP0bTNJtfs2nafa2 kAYt5cESouT1OAKuAADAGB7UtFABRRRQAUUUUAf/2Q== --0-2125306221-1115847550=:57833-- From pavlin@icir.org Wed May 11 22:49:09 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 11 May 2005 14:49:09 -0700 Subject: [Xorp-hackers] How can we handle this error? In-Reply-To: Message from abidin sornaoglu of "Wed, 11 May 2005 14:39:10 PDT." <20050511213910.59825.qmail@web52809.mail.yahoo.com> Message-ID: <200505112149.j4BLn9rX011183@possum.icir.org> > I am a student at cal state fullerton.we are working > on a class project right now.Our project is related to > xorp and rip. We have: > > 1) 2 PCs stations (with one ethernet card for each). > Every pc connect to one PC-Router > 2) 3 PC-Routers, two have three ethernet cards that > connect to each other, with the third one, and with > one of the two stations. and the third PC-Router has > two ehternet cards that connect only the first two > PC-routers. > > See the attached picture for the topology. > > We gave an ip number to each ethernet card in pcs and > then installed the xorp on the three PC-routers. > > When we try to run RIP, two of the PC-Routers gives > this error continuasly. > > xorp-rip:511 RIP +526 port.cc port_io_send_completion > > But the first one (which is connected to the Pc > station) works fine. > > My questiones are: > > 1-)How can we handle that error? we configure the > three PC-router with the same way!! > > 2-)To test the working RIP-XORP PC-Router, we ping the > IPs assigned to every ethernet card in it from the PC > station connected to it. but we only got reply from > the IP that is from same zone of the station !! as it > looks like that RIP is not running to route to the > other IPs at the same router machine from different > zone!!! > > Any suggesting !!! A quick question: did you specify the correct interface addresses inside the RIP configuration? If you use exactly same configuration on all RIP routers, then two out of three this configuration will be wrong. Another thing to check is whether you have any filtering/firewall rules on your routers that prevent them from sending or receiving the RIP packets. Regards, Pavlin From TTA Group Thu May 12 00:25:52 2005 From: TTA Group (TTA Group) Date: Wed, 11 May 2005 16:25:52 -0700 Subject: [Xorp-hackers] Xorp-rip strange error !! Message-ID: <9fa8f1af05051116252f54158@mail.gmail.com> Hi, I installed Xorp and enabled RIP in two FreeBSD Machines every one with three interfaces (Three IPs) The first one running ok. but the second one gives this error continually when I run xorp_rtrmgr: Xorp-rip:511 RIP+526 port.cc Port_io_Send_Completion even I used same config.boot for both (but with different IPs for every interface for sure) So any suggestions to solve the problem ? Also how i can test the working Xorp-Rip machine to be sure that it routes correctly? can I just ping other interface IP from different station that connect directly to one of Ethernet cards in the xorp-rip working machine ? Thanks From pavlin@icir.org Thu May 12 01:41:18 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 11 May 2005 17:41:18 -0700 Subject: [Xorp-hackers] Xorp-rip strange error !! In-Reply-To: Message from TTA Group of "Wed, 11 May 2005 16:25:52 PDT." <9fa8f1af05051116252f54158@mail.gmail.com> Message-ID: <200505120041.j4C0fIf2012481@possum.icir.org> > I installed Xorp and enabled RIP in two FreeBSD Machines every one > with three interfaces (Three IPs) > The first one running ok. but the second one gives this error > continually when I run xorp_rtrmgr: > > Xorp-rip:511 RIP+526 port.cc Port_io_Send_Completion > > even I used same config.boot for both (but with different IPs for > every interface for sure) Please send your configuration (the router that was failing), and a copy of all XORP log messages. You don't have to CC the list with all that info. > So any suggestions to solve the problem ? Also how i can test the > working Xorp-Rip machine to be sure that it routes correctly? can I > just ping other interface IP from different station that connect > directly to one of Ethernet cards in the xorp-rip working machine ? You should use a sheet of paper and a pencil, and then "traceroute" to each IP address in your testbed. The first two to calculate by hand what the routing paths should be, and traceroute to verify that the paths are indeed correct. And, of course, don't forget "netstat -rn" to view the routes installed in the kernel. BTW, how many people share this email account, because I have the feeling it is more than one person. You may want to read some of the recent emails to xorp-hackers and xorp-users, because it may be that RIP itself is not the best choice for your project. The archives are: http://mailman.icsi.berkeley.edu/pipermail/xorp-hackers/2005-May/thread.html and http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2005-May/thread.html Regards, Pavlin From php.net@alienbill.com Wed May 18 18:06:21 2005 From: php.net@alienbill.com (php.net@alienbill.com) Date: Wed, 18 May 2005 22:36:21 +0530 Subject: [Xorp-hackers] something for you Message-ID: <200505181700.j4IH0Iua045999@wyvern.icir.org> This is a multi-part message in MIME format. ------=_NextPart_000_0007_717B506A.EC7C0C44 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit }k94_iͬ;>beL`hS&'ia(Kz #z'[3 4'1QQPfi95zV Hi! I have been working with both asic based routers from cisco, juniper, extreme and so forth as well as with computer/unix based routers for a few years now. Up until a few months ago the latter has been limited to the zebra/quagga suite of routing daemons. They don't leave a very good impression although with a few modifications of my own I've learned to live with them. Anyway, a few months ago I first found out about xorp and having taken a look at it I must say it looks good. I have done some basic testing which looks promising. What I lack the most is the lack of ways to configure interfaces from within xorp. I don't think we have a single router not using VLANs and it would be really neat to be able to do all configuration from within xorp. Is there anyone working on this? I'm no programmer but I would like work on this to make xorp even better. Also, why do one have to `create` before configuring an interface? Would it not be easier to check what interfaces exist at system startup? This is something I'm also interested in writing unless it's a deliberate design choice not to. Regards, Kristian From pavlin@icir.org Fri May 20 21:31:28 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Fri, 20 May 2005 13:31:28 -0700 Subject: [Xorp-hackers] Interface configuration under xorp. In-Reply-To: Message from Kristian larsson of "Wed, 18 May 2005 19:49:42 +0200." <1116438582.428b803622914@mail.juniks.net> Message-ID: <200505202031.j4KKVSOO008740@possum.icir.org> > I have been working with both asic based routers from cisco, juniper, extreme > and so forth as well as with computer/unix based routers for a few years now. > Up until a few months ago the latter has been limited to the zebra/quagga suite > of routing daemons. > They don't leave a very good impression although with a few modifications of my > own I've learned to live with them. > Anyway, a few months ago I first found out about xorp and having taken a look at > it I must say it looks good. I have done some basic testing which looks > promising. > What I lack the most is the lack of ways to configure interfaces from within > xorp. > I don't think we have a single router not using VLANs and it would be really > neat to be able to do all configuration from within xorp. > Is there anyone working on this? I'm no programmer but I would like work on this > to make xorp even better. Kristian, Currently XORP cannot be used to directly configure VLANs. Those should be configured before starting XORP, and then in your XORP configuration you can include the VLAN interfaces you want to use. The "default-system-config" per-interface configuration statement basically says: "use this network interface and take all configuration about it from the underlying system". In the future we would like to add support for configuring VLANs inside the XORP configuration. However, due to lack of resources and given the fact that our hands are already full with a number of items (see http://www.xorp.org/roadmap.html) we cannot give you good estimate when we can add this feature. > Also, why do one have to `create` before configuring an interface? Would it not > be easier to check what interfaces exist at system startup? > This is something I'm also interested in writing unless it's a deliberate design > choice not to. Probably I don't understand your question correctly, but the "default-system-config" statement mentioned above allows you to implicitly configure an interface, though you should explicitly mention the interfaces inside the XORP configuration. Do you mean that: - We should have a single (per system) "default-system-config" statement that instructs XORP to take all existing network interfaces from the system? OR - Inside xorpsh the system should assist you with information about interfaces that already exist in the underlying system before starting XORP so it can provide better command-line completion, etc. Thanks, Pavlin From kristian@juniks.net Sat May 21 14:10:00 2005 From: kristian@juniks.net (Kristian larsson) Date: Sat, 21 May 2005 15:10:00 +0200 Subject: [Xorp-hackers] Interface configuration under xorp. In-Reply-To: <200505202031.j4KKVSOO008740@possum.icir.org> References: <200505202031.j4KKVSOO008740@possum.icir.org> Message-ID: <1116681000.428f3328364e1@mail.juniks.net> Quoting Pavlin Radoslavov : > > I have been working with both asic based routers from cisco, juniper, > extreme > > and so forth as well as with computer/unix based routers for a few years > now. > > Up until a few months ago the latter has been limited to the zebra/quagga > suite > > of routing daemons. > > They don't leave a very good impression although with a few modifications > of my > > own I've learned to live with them. > > Anyway, a few months ago I first found out about xorp and having taken a > look at > > it I must say it looks good. I have done some basic testing which looks > > promising. > > What I lack the most is the lack of ways to configure interfaces from > within > > xorp. > > I don't think we have a single router not using VLANs and it would be > really > > neat to be able to do all configuration from within xorp. > > Is there anyone working on this? I'm no programmer but I would like work on > this > > to make xorp even better. > > Kristian, > > Currently XORP cannot be used to directly configure VLANs. Those > should be configured before starting XORP, and then in your XORP > configuration you can include the VLAN interfaces you want to use. > The "default-system-config" per-interface configuration statement > basically says: "use this network interface and take all > configuration about it from the underlying system". I wasn't aware of the "default-system-config", perhaps I should have looked into the matter at hand before complaining of missing functionality. > In the future we would like to add support for configuring > VLANs inside the XORP configuration. However, due to lack of > resources and given the fact that our hands are already full with a > number of items (see http://www.xorp.org/roadmap.html) we cannot > give you good estimate when we can add this feature. This is exactly what I want to implement. I have been familiarizing myself with the xorp code during the last few days, so far I've written a simple xrl interface to the ntp daemon so that it's possible to configure ntp from inside xorp - just as a test. > > Also, why do one have to `create` before configuring an interface? Would it > not > > be easier to check what interfaces exist at system startup? > > This is something I'm also interested in writing unless it's a deliberate > design > > choice not to. > > Probably I don't understand your question correctly, but the > "default-system-config" statement mentioned above allows you to > implicitly configure an interface, though you should explicitly > mention the interfaces inside the XORP configuration. I'm sorry for being cryptic, my last mail was written in a haste. > > Do you mean that: > > - We should have a single (per system) "default-system-config" > statement that instructs XORP to take all existing network > interfaces from the system? > OR > - Inside xorpsh the system should assist you with information about > interfaces that already exist in the underlying system before > starting XORP so it can provide better command-line completion, > etc. The latter. I don't understand the reason for having the "create" command. Is it in-lack-of-a-better-way or is it intentional? Regards, Kristian From pavlin@icir.org Tue May 24 08:54:49 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Tue, 24 May 2005 00:54:49 -0700 Subject: [Xorp-hackers] Interface configuration under xorp. In-Reply-To: Message from Kristian larsson of "Sat, 21 May 2005 15:10:00 +0200." <1116681000.428f3328364e1@mail.juniks.net> Message-ID: <200505240754.j4O7snf8070667@possum.icir.org> > > In the future we would like to add support for configuring > > VLANs inside the XORP configuration. However, due to lack of > > resources and given the fact that our hands are already full with a > > number of items (see http://www.xorp.org/roadmap.html) we cannot > > give you good estimate when we can add this feature. > This is exactly what I want to implement. > I have been familiarizing myself with the xorp code during the last few days, so > far I've written a simple xrl interface to the ntp daemon so that it's possible > to configure ntp from inside xorp - just as a test. If you would like, you can send us your changes and we can have look at them. > > > Also, why do one have to `create` before configuring an interface? Would it > > not > > > be easier to check what interfaces exist at system startup? > > > This is something I'm also interested in writing unless it's a deliberate > > design > > > choice not to. > > > > Probably I don't understand your question correctly, but the > > "default-system-config" statement mentioned above allows you to > > implicitly configure an interface, though you should explicitly > > mention the interfaces inside the XORP configuration. > I'm sorry for being cryptic, my last mail was written in a haste. > > > > > Do you mean that: > > > > - We should have a single (per system) "default-system-config" > > statement that instructs XORP to take all existing network > > interfaces from the system? > > OR > > - Inside xorpsh the system should assist you with information about > > interfaces that already exist in the underlying system before > > starting XORP so it can provide better command-line completion, > > etc. > The latter. > I don't understand the reason for having the "create" command. Is it > in-lack-of-a-better-way or is it intentional? The "create" command is intentional. The way configuration is handled (inside xorpsh and the rtrmgr) is that you start with an empty configuration tree, and then new nodes are added to that tree. The "create" command is the one used to add new nodes to the configuration tree. For example, "create protocols rip" creates a RIP instance, while "create protocols rip interface eth0" will create a new interface instance inside the RIP instance. Extending the command completion for the "create" command to provide, say, only the names of existing interfaces in the kernel may be possible, but practically speaking it won't be easy and the gain may be too small. For example, such enhancement may be in conflict with being able to create and configure new VLAN interfaces within xorpsh. Regards, Pavlin From Suresh Satapati Tue May 24 23:59:11 2005 From: Suresh Satapati (Suresh Satapati) Date: Tue, 24 May 2005 15:59:11 -0700 Subject: [Xorp-hackers] compile error on MIPS Message-ID: <9852189205052415595b7057c1@mail.gmail.com> Hello, I was trying to build for linux on MIPS, and my build fails with the following errors :- /libxorp/heap.cc heap.cc:129: warning: cast from `char*' to `int*' increases required alignment heap.cc:132: warning: cast from `char*' to `int*' increases required alignment heap.cc:152: warning: cast from `char*' to `int*' increases required alignment heap.cc:163: warning: cast from `char*' to `int*' increases required alignment heap.cc:169: warning: cast from `char*' to `int*' increases required alignment heap.cc:200: warning: cast from `char*' to `int*' increases required alignment heap.cc:206: warning: cast from `char*' to `int*' increases required alignment heap.cc:215: warning: cast from `char*' to `int*' increases required alignment heap.cc:221: warning: cast from `char*' to `int*' increases required alignment /mrt/random.c random.c:461: warning: cast increases required alignment of target type random.c:526: warning: cast increases required alignment of target type My g++ compiler options for MIPS are: MIPS Options -mabicalls -march=cpu-type -mtune=cpu=type -mcpu=cpu-type -membedded-data -muninit-const-in-rodata -membedded-pic -mfp32 -mfp64 -mfused-madd -mno-fused-madd -mgas -mgp32 -mgp64 -mgpopt -mhalf-pic -mhard-float -mint64 -mips1 -mips2 -mips3 -mips4 -mlong64 -mlong32 -mlong-calls -mmemcpy -mmips-as -mmips-tfile -mno- abicalls -mno-embedded-data -mno-uninit-const-in- rodata -mno-embedded-pic -mno-gpopt -mno-long-calls -mno-memcpy -mno-mips-tfile -mno-rnames -mno-stats -mrnames -msoft-float -m4650 -msingle-float -mmad -mstats -EL -EB -G num -nocpp -mabi=32 -mabi=n32 -mabi=64 -mabi=eabi -mfix7000 -mno-crt0 -mflush- func=func -mno-flush-func -mbranch-likely -mno- branch-likely I am not sure any of the above will help. How do I get around this ? Thanks in advance Suresh.. From kristian@juniks.net Wed May 25 19:07:04 2005 From: kristian@juniks.net (Kristian larsson) Date: Wed, 25 May 2005 20:07:04 +0200 Subject: [Xorp-hackers] Interface configuration under xorp. In-Reply-To: <200505251631.j4PGVfGt028301@possum.icir.org> References: <200505251631.j4PGVfGt028301@possum.icir.org> Message-ID: <1117044424.4294bec858848@mail.juniks.net> Quoting Pavlin Radoslavov : > > > The "create" command is intentional. The way configuration is > > > handled (inside xorpsh and the rtrmgr) is that you start with an > > > empty configuration tree, and then new nodes are added to that > > > tree. The "create" command is the one used to add new nodes to the > > > configuration tree. For example, "create protocols rip" creates a > > > RIP instance, while "create protocols rip interface eth0" > > > will create a new interface instance inside the RIP instance. > > > > > > Extending the command completion for the "create" command to > > > provide, say, only the names of existing interfaces in the kernel > > > may be possible, but practically speaking it won't be easy and the > > > gain may be too small. For example, such enhancement may be in > > > conflict with being able to create and configure new VLAN interfaces > > > within xorpsh. > > I see and I somewhat agree, it's understandable that one would need to > "create" > > the interface within xorps configuration tree since just as you've said > it's > > difficult to implement cli completion of interface names. What I still > don't > > understand is why there is a create commmand. It would be easier (at least > from > > the user perspective) to merge the create and set commands. > > If a configuration node (such as interfaces interface fxp0) doesn't exist > it > > should be created when running the command: set interfaces interface fxp0 > vif > > fxp0 address 10.0.0.1 prefix-length 24; > > I see. Yes, we can merge the create and set commands. The original > reason why we have two separate commands is because each command has > clear semantics: "create" is used to create/add new nodes, while > "set" is used to modify existing nodes. > I will discuss your suggestion with other folks. >From a developer point of view it's quite clear why there are two commands. I beleive it would greatly improve workflow by joining these into one. > > > And I still would like to see some more cli completion, when having > written: > > create interfaces interface fxp0 vif fxp0
> > I think it should be possible to help me out with "address" right? > > or even "vif" at: > > create interfeaces interface fxp0 > > If you are creating/adding a new address or a vif to an interface, > how xorpsh can assist you with the command line completion? > The xorpsh doesn't know what vif name or an address value you want > to choose; furthermore, it cannot narrow those to just few choices > (note that in case of UNIX the vif name has to be same as the > interface name, but in general they don't have to be the same). I'm sorry I got it a bit wrong. It shouldn't help filling in "vif" it should just give the option when pressing . if I write: create interfaces interface fxp0 xorp should respond with a small list: Possible completions: vif create virtual interface right now, the list is empty. Regards, Kristian From pavlin@icir.org Wed May 25 19:34:11 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 25 May 2005 11:34:11 -0700 Subject: [Xorp-hackers] Interface configuration under xorp. In-Reply-To: Message from Kristian larsson of "Wed, 25 May 2005 20:07:04 +0200." <1117044424.4294bec858848@mail.juniks.net> Message-ID: <200505251834.j4PIYBHO031611@possum.icir.org> > > > > The "create" command is intentional. The way configuration is > > > > handled (inside xorpsh and the rtrmgr) is that you start with an > > > > empty configuration tree, and then new nodes are added to that > > > > tree. The "create" command is the one used to add new nodes to the > > > > configuration tree. For example, "create protocols rip" creates a > > > > RIP instance, while "create protocols rip interface eth0" > > > > will create a new interface instance inside the RIP instance. > > > > > > > > Extending the command completion for the "create" command to > > > > provide, say, only the names of existing interfaces in the kernel > > > > may be possible, but practically speaking it won't be easy and the > > > > gain may be too small. For example, such enhancement may be in > > > > conflict with being able to create and configure new VLAN interfaces > > > > within xorpsh. > > > I see and I somewhat agree, it's understandable that one would need to > > "create" > > > the interface within xorps configuration tree since just as you've said > > it's > > > difficult to implement cli completion of interface names. What I still > > don't > > > understand is why there is a create commmand. It would be easier (at least > > from > > > the user perspective) to merge the create and set commands. > > > If a configuration node (such as interfaces interface fxp0) doesn't exist > > it > > > should be created when running the command: set interfaces interface fxp0 > > vif > > > fxp0 address 10.0.0.1 prefix-length 24; > > > > I see. Yes, we can merge the create and set commands. The original > > reason why we have two separate commands is because each command has > > clear semantics: "create" is used to create/add new nodes, while > > "set" is used to modify existing nodes. > > I will discuss your suggestion with other folks. > From a developer point of view it's quite clear why there are two commands. > I beleive it would greatly improve workflow by joining these into one. Understandable. Though, as I mentioned in a follow-up email, if we merge "create" and "set", and if you want to start configuring, say BGP, it is a little bit odd to use "set protocols bgp", because "protocols" is not a leaf node that takes a value. Any thoughts from other? > > > And I still would like to see some more cli completion, when having > > written: > > > create interfaces interface fxp0 vif fxp0
> > > I think it should be possible to help me out with "address" right? > > > or even "vif" at: > > > create interfeaces interface fxp0 > > > > If you are creating/adding a new address or a vif to an interface, > > how xorpsh can assist you with the command line completion? > > The xorpsh doesn't know what vif name or an address value you want > > to choose; furthermore, it cannot narrow those to just few choices > > (note that in case of UNIX the vif name has to be same as the > > interface name, but in general they don't have to be the same). > I'm sorry I got it a bit wrong. It shouldn't help filling in "vif" it should > just give the option when pressing . > if I write: > create interfaces interface fxp0 > xorp should respond with a small list: > Possible completions: > vif create virtual interface > > right now, the list is empty. Yes, this is a bug. Please add it to bugzilla and we will fix it later. Thanks, Pavlin From kristian@juniks.net Wed May 25 22:58:28 2005 From: kristian@juniks.net (Kristian larsson) Date: Wed, 25 May 2005 23:58:28 +0200 Subject: [Xorp-hackers] commit/load - rollback Message-ID: <1117058308.4294f5047cb86@mail.juniks.net> I have a few suggestions for these commands. when doing a "load", the configuration from the loaded file is commited right away, I think it would be great to load it into the current "session" first so that you may have a chance to edit parts of it. So you could load a template, do some local changes (such as ip address, AS..) and then do the commit. Then there's the commit command. First off, juniper has this great command "commit revert " (I think it is), anyway it commits the configuration and after minutes it reverts back to the previous. So when commiting and you loose connectivity due to your new config, the router will revert and after a few minutes you can go back and edit your config. If everything works out alright after your first commit you could just do a regular commit to make the changes permanent. Secondly, xorp's commit doesn't save the configuration to file. Once again I would like to look at junipers solution. At every commit the configuration is saved. The previous config is saved as config.1 the one before that as .2 and so forth up to a 100 or something like that. It is then possible to do a "rollback " to roll back number of configurations. It would be possible to add timestamps as well, so you could do rollback time 2004-05-06 14:30 and it would read the config that was current at that time. Great if you wanna know what has changed over the time. Perhaps you dig up in that old log of yours that bla bla date something happened. You do a diff between the current and the rollback conf of that date and voila you get the changes. I have written some pathces for this, but as my C++ are not what they should be it's some pretty ugly code. you can find the originals, the modified files as well as diffs at http://www.juniks.net/~ply/xorp/junos-stylish/ Have in mind that these files have not been cleaned up and thus are more of work in progress (and an example of my lousy C++) than actual patches. Thoughts? Regards, Kristian From pavlin@icir.org Wed May 25 23:20:17 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 25 May 2005 15:20:17 -0700 Subject: [Xorp-hackers] commit/load - rollback In-Reply-To: Message from Kristian larsson of "Wed, 25 May 2005 23:58:28 +0200." <1117058308.4294f5047cb86@mail.juniks.net> Message-ID: <200505252220.j4PMKHpG033187@possum.icir.org> Interesting ideas and all of them make sense. Can you fix the permission of the URL, because I get the following error: Forbidden You don't have permission to access /~ply/xorp/junos-stylish/ on this server. Thanks, Pavlin > I have a few suggestions for these commands. > when doing a "load", the configuration from the loaded file is commited right > away, I think it would be great to load it into the current "session" first so > that you may have a chance to edit parts of it. So you could load a template, > do some local changes (such as ip address, AS..) and then do the commit. > > Then there's the commit command. > First off, juniper has this great command "commit revert " (I think it is), > anyway it commits the configuration and after minutes it reverts back to > the previous. So when commiting and you loose connectivity due to your new > config, the router will revert and after a few minutes you can go back and edit > your config. > If everything works out alright after your first commit you could just do a > regular commit to make the changes permanent. > Secondly, xorp's commit doesn't save the configuration to file. Once again I > would like to look at junipers solution. > At every commit the configuration is saved. The previous config is saved as > config.1 the one before that as .2 and so forth up to a 100 or something like > that. > It is then possible to do a "rollback " to roll back number of > configurations. It would be possible to add timestamps as well, so you could do > rollback time 2004-05-06 14:30 and it would read the config that was current at > that time. Great if you wanna know what has changed over the time. > Perhaps you dig up in that old log of yours that bla bla date something > happened. You do a diff between the current and the rollback conf of that date > and voila you get the changes. > > I have written some pathces for this, but as my C++ are not what they should be > it's some pretty ugly code. > you can find the originals, the modified files as well as diffs at > http://www.juniks.net/~ply/xorp/junos-stylish/ > Have in mind that these files have not been cleaned up and thus are more of work > in progress (and an example of my lousy C++) than actual patches. > > Thoughts? > > Regards, > Kristian > _______________________________________________ > Xorp-hackers mailing list > Xorp-hackers@icir.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers From kristian@juniks.net Wed May 25 23:35:39 2005 From: kristian@juniks.net (Kristian larsson) Date: Thu, 26 May 2005 00:35:39 +0200 Subject: [Xorp-hackers] commit/load - rollback In-Reply-To: <4294F750.20003@exa-networks.co.uk> References: <1117058308.4294f5047cb86@mail.juniks.net> <4294F750.20003@exa-networks.co.uk> Message-ID: <1117060539.4294fdbb809ac@mail.juniks.net> Quoting Thomas Mangin : > Hello, > > >http://www.juniks.net/~ply/xorp/junos-stylish/ > > > > > > Forbidden > > You don't have permission to access /~ply/xorp/junos-stylish/ on this > server. > > ;) > > Thomas > > Whops, directory listings denied.. should be fixed now ;) From atanu@ICSI.Berkeley.EDU Fri May 27 21:29:04 2005 From: atanu@ICSI.Berkeley.EDU (Atanu Ghosh) Date: Fri, 27 May 2005 13:29:04 -0700 Subject: [Xorp-hackers] compile error on MIPS In-Reply-To: Message from Suresh Satapati of "Tue, 24 May 2005 15:59:11 PDT." <9852189205052415595b7057c1@mail.gmail.com> Message-ID: <14908.1117225744@tigger.icir.org> Hi, Some code has just been checked into cvs that should fix this specific problem: Atanu. >>>>> "Suresh" == Suresh Satapati writes: Suresh> Hello, Suresh> I was trying to build for linux on MIPS, and my build fails with Suresh> the following errors :- Suresh> /libxorp/heap.cc Suresh> heap.cc:129: warning: cast from `char*' to `int*' increases required alignment Suresh> heap.cc:132: warning: cast from `char*' to `int*' increases required alignment Suresh> heap.cc:152: warning: cast from `char*' to `int*' increases required alignment Suresh> heap.cc:163: warning: cast from `char*' to `int*' increases required alignment Suresh> heap.cc:169: warning: cast from `char*' to `int*' increases required alignment Suresh> heap.cc:200: warning: cast from `char*' to `int*' increases required alignment Suresh> heap.cc:206: warning: cast from `char*' to `int*' increases required alignment Suresh> heap.cc:215: warning: cast from `char*' to `int*' increases required alignment Suresh> heap.cc:221: warning: cast from `char*' to `int*' increases required alignment Suresh> /mrt/random.c Suresh> random.c:461: warning: cast increases required alignment of target type Suresh> random.c:526: warning: cast increases required alignment of target type Suresh> My g++ compiler options for MIPS are: Suresh> MIPS Options -mabicalls -march=cpu-type Suresh> -mtune=cpu=type -mcpu=cpu-type -membedded-data Suresh> -muninit-const-in-rodata -membedded-pic -mfp32 Suresh> -mfp64 -mfused-madd -mno-fused-madd -mgas -mgp32 Suresh> -mgp64 -mgpopt -mhalf-pic -mhard-float -mint64 Suresh> -mips1 -mips2 -mips3 -mips4 -mlong64 -mlong32 Suresh> -mlong-calls -mmemcpy -mmips-as -mmips-tfile -mno- Suresh> abicalls -mno-embedded-data -mno-uninit-const-in- Suresh> rodata -mno-embedded-pic -mno-gpopt -mno-long-calls Suresh> -mno-memcpy -mno-mips-tfile -mno-rnames -mno-stats Suresh> -mrnames -msoft-float -m4650 -msingle-float -mmad Suresh> -mstats -EL -EB -G num -nocpp -mabi=32 -mabi=n32 Suresh> -mabi=64 -mabi=eabi -mfix7000 -mno-crt0 -mflush- Suresh> func=func -mno-flush-func -mbranch-likely -mno- Suresh> branch-likely Suresh> I am not sure any of the above will help. How do I get around this ? Suresh> Thanks in advance Suresh> Suresh.. Suresh> _______________________________________________ Suresh> Xorp-hackers mailing list Suresh> Xorp-hackers@icir.org Suresh> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers From mehdi.bensaid@rd.francetelecom.com Mon May 30 10:03:53 2005 From: mehdi.bensaid@rd.francetelecom.com (zze-BEN SAID Mehdi RD-CORE-ISS) Date: Mon, 30 May 2005 11:03:53 +0200 Subject: [Xorp-hackers] MIB Message-ID: Hi, I want to extract information from RIB (Routing Information Base) such as: routes, flow sources and destinations; IGMP groups, how many time a multicast flow is replicated, etc... To be clearer, I want to query the RIB. Is that possible? Thanks for help. Best Regards Mehdi From pavlin@icir.org Mon May 30 18:04:24 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Mon, 30 May 2005 10:04:24 -0700 Subject: [Xorp-hackers] Re: [Xorp-users] MIB In-Reply-To: Message from "zze-BEN SAID Mehdi RD-CORE-ISS" of "Mon, 30 May 2005 11:03:53 +0200." Message-ID: <200505301704.j4UH4OkV049590@possum.icir.org> > I want to extract information from RIB (Routing Information Base) such > as: routes, flow sources and destinations; IGMP groups, how many time a > multicast flow is replicated, etc... To be clearer, I want to query the > RIB. Is that possible? Can you clarify what you mean by "routes". The RIB contains only the routes used for unicast routing (URIB), and the MRIB routes used by multicast routing protocols to obtain the Reverse Path Forwarding information. That information can be obtained by the "show route table ..." xorpsh commands. The PIM-SM module itself contains the PIM-SM derived multicast routing information (the so-called Tree Information Base (TIB)). You can see that information by the "show pim join" xorpsh command. The PIM-SM module also contains the multicast forwarding information that is installed in the kernel. That information is per source-group and can be obtained by the "show pim mfc" xorpsh command. The info contains the incoming interface and the set of outgoing interfaces. The IGMP group information can be obtained from the IGMP module by the "show igmp group" xorpsh command. Currently, the only MIB implemented in XORP is for BGP so if you want to use SNMP to obtain the above information you have to implement the corresponding MIBs. The mibs/README, the "XORP SNMP Agent" document (http://www.xorp.org/design_docs.html), and the BGP MIB implementation can be a starting point. Regards, Pavlin