From philippe.vanhecke@belnet.be Sat Jun 5 11:18:18 2004 From: philippe.vanhecke@belnet.be (Philippe Van Hecke) Date: Sat, 5 Jun 2004 12:18:18 +0200 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. Message-ID: <200406051218.21487.philippe.vanhecke@belnet.be> Hello all, I have downloaded and compiled xorp on a linux box and i would like use it as multicast gateway. I would like to know if some one can provide an sample config.boot for my test. I have two interfaces on which i want to run pim (eth3 and eth2 ) and the RP i should use is any cast static RP. I have try to use sample config.boot provided by the source code but there no sample for the pim part of xorp. I have already test this doing modification on configure_pim file and running test_pim and it work well. but I would like also test rtrmgr. Any helps are welcome. regards, Philippe. From pavlin@icir.org Sat Jun 5 18:37:34 2004 From: pavlin@icir.org (Pavlin Radoslavov) Date: Sat, 05 Jun 2004 10:37:34 -0700 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: Message from Philippe Van Hecke of "Sat, 05 Jun 2004 12:18:18 +0200." <200406051218.21487.philippe.vanhecke@belnet.be> Message-ID: <200406051737.i55HbYKh091956@possum.icir.org> > I have downloaded and compiled xorp on a linux box and i would like use it > as multicast gateway. I would like to know if some one can provide an > sample config.boot for my test. I have two interfaces on which i want to run > pim (eth3 and eth2 ) and the RP i should use is any cast static RP. > > I have try to use sample config.boot provided by the source code but there > no sample for the pim part of xorp. > > I have already test this doing modification on configure_pim file and running > test_pim and it work well. but I would like also test rtrmgr. Philippe, Below I am including a sample config file that you can use for multicast routing. If you are going to use static RPs, then you need only to uncomment the static-rps section and add your RPs. Please let us know whether it works for you or whether you have any comments/suggestions/etc, because we are very close to rolling-out our 1.0 Release Candidate. Thanks, Pavlin interfaces { interface eth2 { default-system-config } interface eth3 { default-system-config } } fea { enable-unicast-forwarding4: true /* enable-unicast-forwarding6: true */ } plumbing { mfea4 { interface eth2 { vif eth2 { enabled: true } } interface eth3 { vif eth2 { enabled: true } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { igmp { interface eth2 { vif eth2 { enabled: true } } interface eth3 { vif eth3 { enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { pimsm4 { interface eth2 { vif eth2 { enabled: true } } interface eth3 { vif eth3 { enabled: true } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ enabled: true } } /* static-rps { rp 10.10.10.1 { group-prefix 224.0.0.0/4 { rp-priority: 192 hash-mask-len: 30 } } rp 10.10.10.2 { group-prefix 224.0.0.0/4 { rp-priority: 192 hash-mask-len: 30 } } } */ /* bootstrap { cand-bsr { scope-zone 224.0.0.0/4 { cand-bsr-by-vif-name: "eth2" bsr-priority: 1 } } cand-rp { group-prefix 224.0.0.0/4 { cand-rp-by-vif-name: "eth2" rp-priority: 192 rp-holdtime: 150 } } } */ switch-to-spt-threshold { enabled: true interval-sec: 100 bytes: 102400 } traceoptions { flag all { enabled: true } } } } /* protocols { static { route4 10.10.0.0/16 { nexthop: 10.20.0.1 } } } */ protocols { fib2mrib { enabled: true } } From pavlin@icir.org Sat Jun 5 18:43:28 2004 From: pavlin@icir.org (Pavlin Radoslavov) Date: Sat, 05 Jun 2004 10:43:28 -0700 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: Message from Pavlin Radoslavov of "Sat, 05 Jun 2004 10:37:34 PDT." <200406051737.i55HbYKh091956@possum.icir.org> Message-ID: <200406051743.i55HhSKh092005@possum.icir.org> > > I have downloaded and compiled xorp on a linux box and i would like use it > > as multicast gateway. I would like to know if some one can provide an > > sample config.boot for my test. I have two interfaces on which i want to run > > pim (eth3 and eth2 ) and the RP i should use is any cast static RP. > > > > I have try to use sample config.boot provided by the source code but there > > no sample for the pim part of xorp. > > > > I have already test this doing modification on configure_pim file and running > > test_pim and it work well. but I would like also test rtrmgr. > > Philippe, > > Below I am including a sample config file that you can use for > multicast routing. If you are going to use static RPs, then you need > only to uncomment the static-rps section and add your RPs. Opps, I forgot to mention that you must use the lastest code from the CVS repository. In other words, release-0.5 won't work with the configuration I sent you. Pavlin From gernot.schmied@chello.at Sun Jun 6 00:46:50 2004 From: gernot.schmied@chello.at (Gernot W. Schmied) Date: Sun, 06 Jun 2004 01:46:50 +0200 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: <200406051743.i55HhSKh092005@possum.icir.org> References: <200406051743.i55HhSKh092005@possum.icir.org> Message-ID: <40C25B6A.1070209@chello.at> Pavlin Radoslavov wrote: >>>I have downloaded and compiled xorp on a linux box and i would like use it >>>as multicast gateway. I would like to know if some one can provide an >>>sample config.boot for my test. I have two interfaces on which i want to run >>>pim (eth3 and eth2 ) and the RP i should use is any cast static RP. >>> >>>I have try to use sample config.boot provided by the source code but there >>>no sample for the pim part of xorp. >>> >>>I have already test this doing modification on configure_pim file and running >>>test_pim and it work well. but I would like also test rtrmgr. >> >>Philippe, >> >>Below I am including a sample config file that you can use for >>multicast routing. If you are going to use static RPs, then you need >>only to uncomment the static-rps section and add your RPs. > > > Opps, I forgot to mention that you must use the lastest code from > the CVS repository. In other words, release-0.5 won't work with the > configuration I sent you. > > Pavlin > _______________________________________________ > Xorp-users mailing list > Xorp-users@xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > Hi Pavlin, Any hints about the release date of XORP 1.0 :-)))? Regards, Gernot From pavlin@icir.org Sun Jun 6 02:34:47 2004 From: pavlin@icir.org (Pavlin Radoslavov) Date: Sat, 05 Jun 2004 18:34:47 -0700 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: Message from "Gernot W. Schmied" of "Sun, 06 Jun 2004 01:46:50 +0200." <40C25B6A.1070209@chello.at> Message-ID: <200406060134.i561YlKh094390@possum.icir.org> > Any hints about the release date of XORP 1.0 :-)))? Hopefully, within few days or so we will have the 1.0 Release Candidate ready for evaluation/testing by the users and for feedbacks. If there are no significant problems during the evaluation period, then approximately two weeks after that we will have the official 1.0. Hence, the users' participation and evaluation during the test period will be extremely valuable for improving the robustness. Thanks, Pavlin From philippe.vanhecke@belnet.be Sun Jun 6 09:53:56 2004 From: philippe.vanhecke@belnet.be (Philippe Van Hecke) Date: Sun, 6 Jun 2004 10:53:56 +0200 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: <200406051737.i55HbYKh091956@possum.icir.org> References: <200406051737.i55HbYKh091956@possum.icir.org> Message-ID: <200406061053.59473.philippe.vanhecke@belnet.be> Hi Pavlin, Thanks a lot for this, i will try this today or tomorrow and will give you some feed back. Regards, Philippe. -- __________________________________________________________________ Philippe Van Hecke - BELNET, The Belgian Research Network "In a world without walls or fences, who needs Windows and Gates?" __________________________________________________________________ From philippe.vanhecke@belnet.be Sun Jun 6 12:58:33 2004 From: philippe.vanhecke@belnet.be (Philippe Van Hecke) Date: Sun, 6 Jun 2004 13:58:33 +0200 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: <200406061053.59473.philippe.vanhecke@belnet.be> References: <200406051737.i55HbYKh091956@possum.icir.org> <200406061053.59473.philippe.vanhecke@belnet.be> Message-ID: <200406061358.35221.philippe.vanhecke@belnet.be> --Boundary-00=_rbwwA456idoVhBv Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Le Sunday 06 June 2004 10:53, Philippe Van Hecke a =E9crit : > Hi Pavlin, > Thanks a lot for this, i will try this today or tomorrow and will > give you some feed back. > > Regards, > Philippe. Hi Pavlin, I have get last cvs source compiled and installed it using the sample you=20 provide me. So i will give you my first ( must make more) test result.=20 After changing the static RP address to the one define on our backbone and= =20 changed the litle typo error :) on the plumbing_mfea4 part for the eth3=20 interface. All the multicast routing seem to be working like the way it run= =20 when i use the test_pim program. The only thing i doesn't really understand= =20 is the following ERROR on the log output. [ 2004/06/06 13:22:52 ERROR xorp_rib:19257 XifRedistTransaction6 +641=20 redist_xrl.cc dispatch_complete ] Fatal error during start transaction "201= =20 Resolve failed" [ 2004/06/06 13:22:49 ERROR xorp_rtrmgr:19253 IPC +270 sockutil.cc=20 create_connected_ip_socket ] failed to connect to 127.0.0.1 port 4658:=20 Connection refused [ 2004/06/06 13:22:49 ERROR xorp_rtrmgr:19253 XRL +52 xrl_pf_factory.cc=20 create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError fr= om=20 line 549 of xrl_pf_stcp.cc: Could not connect to 127.0.0.1:4658 [ 2004/06/06 13:22:49 ERROR xorp_rtrmgr:19253 XRL +341 xrl_router.cc=20 send_resolved ] Could not create XrlPFSender for protocol =3D "stcp" addres= s =3D=20 "127.0.0.1:4658" [ 2004/06/06 13:22:54 ERROR xorp_rtrmgr:19253 IPC +270 sockutil.cc=20 create_connected_ip_socket ] failed to connect to 127.0.0.1 port 4634:=20 Connection refused [ 2004/06/06 13:22:54 ERROR xorp_rtrmgr:19253 XRL +52 xrl_pf_factory.cc=20 create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError fr= om=20 line 549 of xrl_pf_stcp.cc: Could not connect to 127.0.0.1:4634 [ 2004/06/06 13:22:54 ERROR xorp_rtrmgr:19253 XRL +341 xrl_router.cc=20 send_resolved ] Could not create XrlPFSender for protocol =3D "stcp" addres= s =3D=20 "127.0.0.1:4634" I should probably read a bit more manual about xorp design and infrastruct= ure=20 to understand this :-).=20 =46or information my configuration is the following. The Linux box is a Gentoo box with 4 interface eth0,eth1,eth2,eth3 this box is configured as firewall (using iptable chains) and mutlicast=20 gateway for our internal lan.=20 The eth3 is connect to a Junpier M20 configured as RP through a catalyst and it only forward mutlicast traffic to eth2. The eth1 interface is only u= sed=20 for unicast ipv4 and unicast ipv6.=20 I provide you the output log from my test and also the final config file i= =20 have used. I will probably make more deep testing this week and keep you informed and= =20 provide more remark. But before i would like to say that xorp is very impressing.=20 Regards, Philippe. =2D-=20 __________________________________________________________________ Philippe Van Hecke - BELNET, The Belgian Research Network "In a world without walls or fences, who needs Windows and Gates?" __________________________________________________________________ --Boundary-00=_rbwwA456idoVhBv Content-Type: text/x-csrc; charset="iso-8859-1"; name="config.boot" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="config.boot" interfaces { interface eth2 { default-system-config } interface eth3 { default-system-config } } fea { enable-unicast-forwarding4: true /* enable-unicast-forwarding6: true */ } plumbing { mfea4 { interface eth2 { vif eth2 { enabled: true } } interface eth3 { vif eth3 { enabled: true } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { igmp { interface eth2 { vif eth2 { enabled: true } } interface eth3 { vif eth3 { enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { pimsm4 { interface eth2 { vif eth2 { enabled: true } } interface eth3 { vif eth3 { enabled: true } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ enabled: true } } static-rps { rp 193.191.0.254 { group-prefix 224.0.0.0/4 { rp-priority: 192 hash-mask-len: 30 } } } /* bootstrap { cand-bsr { scope-zone 224.0.0.0/4 { cand-bsr-by-vif-name: "eth2" bsr-priority: 1 } } cand-rp { group-prefix 224.0.0.0/4 { cand-rp-by-vif-name: "eth2" rp-priority: 192 rp-holdtime: 150 } } } */ switch-to-spt-threshold { enabled: true interval-sec: 100 bytes: 102400 } traceoptions { flag all { enabled: true } } } } /* protocols { static { route4 10.10.0.0/16 { nexthop: 10.20.0.1 } } } */ protocols { fib2mrib { enabled: true } } --Boundary-00=_rbwwA456idoVhBv Content-Type: application/x-gzip; name="xorp_on_argos.txt.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xorp_on_argos.txt.gz" H4sICJX+wkAAA3hvcnBfb25fYXJnb3MudHh0AO1dbW+byhL+3l+xyqdWzSWwYGyQjnTdxEl95Lxc x+npUVUhYtYOqm18Aee0//7Ogm3A5mWBxXZ0q0aqA2afeWZmZ2eH3c03hEVRuRBV+EGSrGOstzBC veHwfoh+Ou7ScO1nXdJwq42+2pMhsWzPH7nmwjPHvu0sVPRRVSTkBteNn+5MGI8RfF6a/vjFGDvz 5Yz4BH1H16ZvzhBxXcdF1sq1F1Pk+abrIz9qDJ1hUUJD4jmzV4Impj0j1tk7QUSmZbk6ktpYwIoA wggy8lbPC+InLooXWELPrmNaY9OL39IE3GqhJSHQiCgE/9D1zJx6Orp9Goz6l93HEfo0vO9eBZ+e 7q56w8Hf/bsb40v/2nh6ePdtR0tSWweo/t31faijpT335gp66N8C0zvyD3q1Jzr6Yk++Ef9F/o6W 9sSwFxb5Cfj03uYXacNMk0FMUZAk+L8dcYtfVi+wlmAXu4nxcdjBHZdMs/nJa0FqQED74FnENeBK NhDedxEpzUWkCxmnugj9fqoKQSRj2LvpP456Q0bd4SxivYX5DC4dkgPPwOUefxx1hyPA3jgWztZH Spdh0seGfFIVR+5+CH76D68K6t11Pw16VyW1RqNMdaXv2kyuZ7NTDwZ8dV1SWQldxzt+DZ2fdvzI UHc63Rhf13fnUzcYl2U0HA1vb4booySrCvJN7wcdg93VwqCfaTx10NxxSXDL2zS9C4ElXRIR+qs7 vKOq20f56s6uqbbckelOiY8+KvDgJLhiPJseoaAv5sKaEWN9VTSw4YaDOc0MQJLP9D4d+ufgHI6F JpAMhF++EAV8Ef9yOPrrFPZybvWCvEESMbp05nNoZX0frYU5AzU/3hrqGbIc4qGF4yPyE+yO4Cl7 /XvoXMKeL1Hm2ttl/jxdVmSN5f8/1lhXtMKO1FI7237kvax8y/lnQeMKfPQpm+D3uWOtZkRHYeip igQMw4YMYGlOiUsxf9gzyvU7ug1uIfN54bhzczb7tb5VEfXrcIA+yrKIQOGG66z8EM4jC2tjOIr6 SKiFIIuH394vXcd3xs4M/YHOPH+8PDsPQiXxPHpFwu0g3Em6orY6Zx+yBIrPJ+IS9R8u0UfcFpHn jH+sfDuYPoxdYvoEJg+LBRnDcGLYS4PeB7t/3/iB76D1ffpxKwZaOjCloLLo4DnBfTqvcMlk5RGr rHSBvmA6RNW1nBgTmKU47q+YiF6oqe/Uax+uQ71dh9/S9fA7ccd+uAaZPN9d0W+ELj5xnTmCLkJQ CyRxJhssqmoAoixWMytw6jS+gdrfVeIlw7Qt3w9i0CGVGMugK+/5Ro5roCwh32oECkccpWIUaol8 o5A9nS+zcH5rOEPDSltNib5hrDUAy49CcHiRCuDnKFt6u8ru39w+VNV0cWpaypcn9jOeu/ZzFtZb VXFNfy7WclV/zlX4G04SN7yqalzh69dZGi6GqWrY8ojNpoiykp4iUoEOnSLKCmuKmCfdm0gRZSU1 RSzkdcgUEVwjNUWkQr7V+FMj9LT4hp75hJips0UK9FbVa09AUmNu0+/9q9VRxbbW0cbAUGxjMlZa WBoTyZI6bU2ckH9vna2qSdrFBTg1LUxD15nbCzN4CzZafw70kW8bWReLM9hqiABYEa/cnGQBgkBE JF5FtMr5eT6wxKeSSqMs3HtHU6TRsHvZCxukkwN0O7hSaUYNzwy/IvrJ+IKN297tp97w8XP/wRj2 Hu6HozC27xT8oVmMldBXZQRD06s9ySym88TGYoAtawIWJCwouBC8VRM89oYIayHxVkAcJm8Rduob m1aHI3EprvRi2hon2h1BxRtkqvK2gGG4yyXeof2GDzp9jZfla80i75hbKjR3R5dVFuwY8H+eesO/ i0wt5ZuaFbZK1y7wMoBuHyuq8MUuGVVYwfmbujF9/zZ1FnjrOL26dVTOx/Oz5qCL/EzTpWOYmhW2 AW03Cc1L2414uKbLTGkhd1OzwTZiap7Q5dV9RD+DdPUYpmaDbcTUtec8dbR9TDfLH6tH+abOmnNw B8rWbnmoAvfN4pQ/lakJms2v0H51B/9o1toOe6sMMsBUXYJZa8H8jSt6C0e8JQZ11y0U1JitM6NL heig61act1qscl7E4b+Ep3VykbGoi40VxPKjFGfociGSgjc2LBWMDTywM8IZLjR2Q8AF9SieyGXr URT7WKVPwFakwyddzLDNeDdP7NLdujnixdD4OKZmgm3I1I1hc9J2I14m0ddShzc1K2wD6gboo6r7 aC4u0a1vxzA1G2xDlI9pa57gJX1cYXpnxt3URxwv+YKX9bOjjdWY8fUoZ1Ozwh6RcSNehhscuIq8 rAibVy2sLlCJWhizPnnWwuqCVqyF8fCdapNlzJp1cC8HsUOXn6cXlIM4INeIUHXLQdWLnjzQ64Qo fszLFFwpMscqWPlRoe7LsIrVKEDmV+EuW2em6LzWpJWuR2FdqhVNUxpMTlQmxES3170u+p62g/AI ywqYYZOU05rppBOlLVimb05mzj9oTjzPnBIdee4Y/QFPQh/sdAR60IOILM+Ha9u+mbXEO7bMH1CC 1a5KiPVRU6VgCbIxj5b5W4Se2mPMVzPfpgcd0MMTQCqP+HSThbP0398OR8ZVb0CPMTjfOseH7Qru /uLVnNkWMt3pak4WfhW5NBzKtXCsYKG55ztLw5zNqDAe3XtgLuiabXp5K4GOxuHVkAHyXwjasgi+ FVieXv5B3AWZHVVh8tEVJr8hhcVP8jiu4uKS8FJgYhMGjQRhILiBlldLK9glRPcpbFa2B9sV7EXw Ld8l4TkEIFcp+oP+J3j+ctDv3Y3CvQThlopgzw9ZzoCD7wTmWq68F5Cmu1zOfqFn00LjcEuGgPqT 26n7hZ4MNndeyfuzUIxztP6Qsd+rFVuBT8kmJAGcxfqkMGc8XrkusYKNR3SDgbmgu0NorK68/UNA mx0ktoeeCW3VDYS3Nlut6J6QSUzXawO4ZEzsV+J6WVt29mxI988Qs08FvQ3kXANn7IoBF4yTugBp L7ZSGKGQrJtkBs7YnG1PYgvVmSq2mts3JFXc77xAwfCmxthZLSgX2xn7s/eP/fvLm97o8ebybnSO 3ktyW6DJBAxTajKV+RB13k/gSRP4CJ3HG7v20j+wjLgDgyidSrUhqa8tZbspTWqQftJcWBFk6WSl BF22NCFITrSTFRIkxAoIRWdxSru2mJ2mLB6leFKU3J2QgKDDDqgwkLN+x2lKSpi0Q2IvnKYKYzbG tQTUmuvQUrtDqx24toWbkjHRnzv1xAy3JDYipoaFDgwxkgqy1YzggZTJ5Gk9Z7wKEtC8gw5LPJwy 62V8OPfcPtZG1smsAh6oBF5Id2dGc92t9tK25+FEISZxMmDXsgDuEsE8wf2l006YQDhPWgbZkL3D hBs5QUr4B7oXhP3ULx8RJvJ395fdy8895NnTBaRkQY5JORuKHh1BGOCsJ/jgLZoiqMFJjg1wjjV/ KoRloQVRRhTUViOEo+ZPhDANrRJkc4LaboJwrPkTIQzeJkntMGEQm6CcADgR0nR2IbboACp1lIbs HAFUJq1xJS3TnqYKNDlkj9jZIuxH7Fj7J0J57XuqJnTYA3YJyvH2T4SyTN9/gRhtlb4faMLMcYAT IR3rbm32uF2CdAKgKmlZ5Ekai22hDSKpIIvCPDrnyLBLOglQmbTE171jtStWytkS7Dt31Hxlwpgr 4Z26CCvnbCH2OCcRKtOWudJOljFYWWfLsMc6AXAipLdVkaJ3hyW5bto9j4oZx6JY6hVpSZrxtitR VZrruR1mH84WIr/ndio7cYv3HDlWUWFlnS1D2iw5AqhMWuVJugOpb0sSFCzI7CNxtgS7lOPNnwbh mBHYSyElGCfaPxHKsdco7ONwCcrx9o9LWdxQTi492nDe7MQrKcDoa/AnN7qPj726J16VU2yCxXkk /0at4latgnBfVq1rVn/e9++Mh+HTXa/+yXEy9xpebNHe2ojxxZIlZUir4kUA54mmS3huNmATKu7w Dg3rsh77rCRbgpyqYeVZicJ17knrHnQ6jEES5vpZjgi7jBPtV6bMdyKWeIvOSrnENCzefmXKnMuk WjACqy2BuWCYI8E+46j5qoRbfFP21FBZRDlHhqJQyZ10A6GyGO1zbzC4rzug51tyFyZ7fXAxn8Kx PAOotOL41jijjJh5ipEjQU7CXXGKsXsKKY+AS2c8gYWZCOdKkBZvN81XJsx35gzxUIGQCFbQGAfV XBHS4u22/aqUJb7lXPrX+ZQOhAwY+RjqQbn4aS4dNV6+IARgfIfTxLoiFq5llkvE2q5CFTdW5mOo ZubC51GtUNEsosptpAGgQ4ycAHOYAY0FiF/eAWh8p2gwheoE+4dYvLHE3GzTbhVP5PxuDOI7Xq+0 kBmz11wZ0gaQCKDqCJI/LbvqjrrXg/u/1qx15Dkrd0zQzlqkqeuslrv0kP/iEu/FmVlGsDb/1ZwZ HglUA4lBys1VeFdEc2J6K5ekPrd/b/tY1OTSpH/hxtu5+vzLJ17QDFbiLUXfVtqd6PL261JbkjvI 9oy4zAmM3XvbR+mdKfmvsVqOzdlsc2UWv5JS7wmsktgjkbDLn469uCKeDUK+fzy/+QCN+O6K6Gi1 9HyXmHO0IPb05dkJ/7LM2mQJg9H9D6HREibTg90yE2e12P/7PvRY5Fxf4RiqDzLJ2T1Vu8FQnQNU r/ahMtY+ckXIqX2oFWsf2s7W1MZ8RTvMsK4dalhnAeI3rGuNvU9mffGWK0F2rln1xZt2kpFVo38Q 8zC95SCRdffo3gZ7S4tvWhqbzMjFqWkufN5ESS6dnmIRfg7hIxToAD5CYQ7iI0xA3CIqoOXEM36v XMMzGE8tkFGpcms0HJ30EIGMwhzGSaWdw2DqL9iT6MrJjii02aae+RLsL9eLmq80EAMc59Jlcu8v I+Uy5csEQGXSfNOt+M5DVsol0q1Y85UJ59bkucUD6TCDlnSoQYsFiN+gJRWshc+pAsXfCpWsAmGp WhWIPsehCpRaABL3yz/71Z3o61Jm5Ufcq/yIe5WflEOIci0Rbvzk+9qMngR6gokESHWQ1wIUKDdj yXH9xPujuO+Hh7/99vtSfp9jhjS/r/WCDeAOkj5Kh0ofdw/qLBPAE28pfofw2q6ca4vUEF77Nc7e KZZcdvBF5/0wpZa5MqTu4NsCVCWdP4XgNkbsnrNY5iVZbJXQ777FoW/lWCKtb9VdRkURDzFS4ENN LFiA+E0scIP71YrX7OTD812zQ7FyS9Eco9EpJuy7R7RWy6PF33l03QCZY4aCPLr8mjwKl72mlWd0 BJjoLKQEykPv7or2hMfR/QP6Yk++0Sa+o+UmeuiguNf4L6ZluXpcFAguq+cF8ZMXL2SMnl3HtOjx pPBcIKiIloS40W97bclpbYkX0MNjbcV3QLVaO01ez8ypp6Pbp8Gof9l9HKFPw/vuVfDp6e6qNxz8 DWzpWa/G08OGvHF1/9cd6j+8Kqh31/006F3VN1WNmF/OWHK2saSNgpPCbFUcv6xeYC2h5HiAxYdU Miv3+Plf2TrAFR028f1U9tTiw95N/3HUGx7WtxoIA1SrD72r/7sI8FZ6/o59Tr7T1+zscbon3s9r MmU4TLHM4yXdqsSBiszNLDPPB8/pR2m5Fcs5H+/+B9alN7NYqAAA --Boundary-00=_rbwwA456idoVhBv-- From pavlin@icir.org Sun Jun 6 22:52:10 2004 From: pavlin@icir.org (Pavlin Radoslavov) Date: Sun, 06 Jun 2004 14:52:10 -0700 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: Message from Philippe Van Hecke of "Sun, 06 Jun 2004 13:58:33 +0200." <200406061358.35221.philippe.vanhecke@belnet.be> Message-ID: <200406062152.i56LqAKh002190@possum.icir.org> Philippe, > interface. All the multicast routing seem to be working like the way it run= > =20 > when i use the test_pim program. The only thing i doesn't really understand= > =20 > is the following ERROR on the log output. Can you send the complete config file and the complete log from the moment you start the rtrmgr to the moment you stop it. By looking in the "xorp_on_argos.txt" log file it appears that there are some XRLs with target PIMSM_6, which is the IPv6 PIM-SM target, but the configuration file I sent you doesn't contain the section for configuring PIM-SM for IPv6. In general, the Linux kernel doesn't support multicast routing for IPv6, so if you have enabled IPv6 multicast in your XORP config file then you should disable it. Pavlin From pavlin@icir.org Mon Jun 7 16:07:57 2004 From: pavlin@icir.org (Pavlin Radoslavov) Date: Mon, 07 Jun 2004 08:07:57 -0700 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: Message from Philippe Van Hecke of "Mon, 07 Jun 2004 09:50:15 +0200." <200406070950.15882.philippe.vanhecke@belnet.be> Message-ID: <200406071508.i57F7vKh007751@possum.icir.org> > you can find my config.boot and a log attached to this mail. > Also for your information when i a do a ps to see which process > are running i see the following output. Philippe, This time the log appears OK. Indeed, there are some warning or error messages during shutdown, but there is nothing to worry about (e.g., some of those messages are normal transient warnings during shutdown). Indeed, there are other warnings/errors which appear to be triggered by inappropriate cleanup ordering during shutdown, but they also can be safely ignored (anyway, I will fix them sometime soon). BTW, some of the warnings were during normal operation like: 2004/06/07 09:37:14 WARNING xorp_pimsm4 PIM ] JoinDesired(S,G) = true: upstream neighbor for source 193.50.20.65 and group 224.2.127.254: not found ... [ 2004/06/07 09:37:28 WARNING xorp_pimsm4 PIM ] JoinDesired(S,G) = true: upstream neighbor for source 193.191.130.193 and group 233.10.51.14: not found Those messages indicate that the next-hop router toward 193.50.20.65 and 193.191.130.193 is not a PIM-SM router. Is this correct? Thanks, Pavlin From philippe.vanhecke@belnet.be Mon Jun 7 16:43:01 2004 From: philippe.vanhecke@belnet.be (Philippe Van Hecke) Date: Mon, 7 Jun 2004 17:43:01 +0200 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: <200406071508.i57F7vKh007751@possum.icir.org> References: <200406071508.i57F7vKh007751@possum.icir.org> Message-ID: <200406071743.01534.philippe.vanhecke@belnet.be> On Monday 07 June 2004 17:07, you wrote: > Philippe, > > This time the log appears OK. > Indeed, there are some warning or error messages during shutdown, > but there is nothing to worry about (e.g., some of those messages > are normal transient warnings during shutdown). Indeed, there are > other warnings/errors which appear to be triggered by inappropriate > cleanup ordering during shutdown, but they also can be safely > ignored (anyway, I will fix them sometime soon). > > > BTW, some of the warnings were during normal operation like: > > 2004/06/07 09:37:14 WARNING xorp_pimsm4 PIM ] JoinDesired(S,G) = > true: upstream neighbor for source 193.50.20.65 and group 224.2.127.254: > not found > ... > [ 2004/06/07 09:37:28 WARNING xorp_pimsm4 PIM ] JoinDesired(S,G) = > true: upstream neighbor for source 193.191.130.193 and group 233.10.51.14: > not found > > Those messages indicate that the next-hop router toward 193.50.20.65 > and 193.191.130.193 is not a PIM-SM router. Is this correct? Hum the 193.191.130.193 is a host of one of our customer and it this customer is connected on the same Junpier M20 as my eth3 interface. The Junpier is configured with PIM-SM. the 193.50.20.65 is a source behind GEANT network. and the next hope router should be the Juniper M20 at 193.190.113.21. Regards, Philippe. -- ___________________________________________________________________ Philippe Van Hecke - BELNET, The Belgian Research Network "In a world without walls and fences, who needs windows and gates?" ___________________________________________________________________ From pavlin@icir.org Mon Jun 7 17:38:03 2004 From: pavlin@icir.org (Pavlin Radoslavov) Date: Mon, 07 Jun 2004 09:38:03 -0700 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: Message from Philippe Van Hecke of "Mon, 07 Jun 2004 17:43:01 +0200." <200406071743.01534.philippe.vanhecke@belnet.be> Message-ID: <200406071638.i57Gc3Kh009671@possum.icir.org> > > 2004/06/07 09:37:14 WARNING xorp_pimsm4 PIM ] JoinDesired(S,G) = > > true: upstream neighbor for source 193.50.20.65 and group 224.2.127.254: > > not found > > ... > > [ 2004/06/07 09:37:28 WARNING xorp_pimsm4 PIM ] JoinDesired(S,G) = > > true: upstream neighbor for source 193.191.130.193 and group 233.10.51.14: > > not found > > > > Those messages indicate that the next-hop router toward 193.50.20.65 > > and 193.191.130.193 is not a PIM-SM router. Is this correct? > > Hum the 193.191.130.193 is a host of one of our customer and it this customer > is connected on the same Junpier M20 as my eth3 interface. The Junpier is > configured with PIM-SM. the 193.50.20.65 is a source behind GEANT network. > and the next hope router should be the Juniper M20 at 193.190.113.21. Can you verify by running "netstat -rn" that the Juniper router is indeed the next-hop router toward those source addresses. For, example, if the next-hop router is connected to, say, eth0 which is not enabled for multicast routing then this is one possible reason for the warning. Also, if "netstat -rn" indeed shows that the Juniper router is the next-hop router, then can you use the "show pim mrib" xorpsh operational command to verify whether PIM-SM itself has learned about that route. Finally, you may want to look into the "show pim join" output to check the (S,G) multicast routing state. Thanks, Pavlin From philippe.vanhecke@belnet.be Mon Jun 7 08:50:15 2004 From: philippe.vanhecke@belnet.be (Philippe Van Hecke) Date: Mon, 7 Jun 2004 09:50:15 +0200 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: <200406062152.i56LqAKh002190@possum.icir.org> References: <200406062152.i56LqAKh002190@possum.icir.org> Message-ID: <200406070950.15882.philippe.vanhecke@belnet.be> --Boundary-00=_34BxAllCGZFlI6x Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Pavlin, you can find my config.boot and a log attached to this mail. Also for your information when i a do a ps to see which process are running i see the following output. root 20793 7781 1 09:44 pts/1 00:00:03 ./xorp_rtrmgr root 20794 7781 0 09:44 pts/1 00:00:00 cat root 20795 20793 0 09:44 ? 00:00:01 /usr/local/xorp/fea/xorp_fea root 20800 20793 0 09:44 ? 00:00:00 /usr/local/xorp/rib/xorp_rib root 20802 20793 0 09:44 ? 00:00:00 /usr/local/xorp/fib2mrib/xorp_fib2mrib root 20805 20793 0 09:44 ? 00:00:00 /usr/local/xorp/mld6igmp/xorp_igmp root 20809 20793 0 09:44 ? 00:00:00 /usr/local/xorp/pim/xorp_pimsm4 So it seem that the mld6igmp processe are started. But i never enable any ipv6 unicast or multicast feature in my config. The linux kernel used is the 2.4.25. I have also attached the log file from start to end. If this one is too short i can provide you a log for a whole day As i have started xorp now and let it running. Hope that can help you Regards, Philippe. -- ___________________________________________________________________ Philippe Van Hecke - BELNET, The Belgian Research Network "In a world without walls and fences, who needs windows and gates?" ___________________________________________________________________ --Boundary-00=_34BxAllCGZFlI6x Content-Type: text/x-csrc; charset="iso-8859-1"; name="config.boot" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="config.boot" interfaces { interface eth2 { default-system-config } interface eth3 { default-system-config } } fea { enable-unicast-forwarding4: true } plumbing { mfea4 { interface eth2 { vif eth2 { enabled: true } } interface eth3 { vif eth3 { enabled: true } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { igmp { interface eth2 { vif eth2 { enabled: true } } interface eth3 { vif eth3 { enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { pimsm4 { interface eth2 { vif eth2 { enabled: true } } interface eth3 { vif eth3 { enabled: true } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ enabled: true } } static-rps { rp 193.191.0.254 { group-prefix 224.0.0.0/4 { rp-priority: 192 hash-mask-len: 30 } } } switch-to-spt-threshold { enabled: true interval-sec: 100 bytes: 102400 } traceoptions { flag all { enabled: true } } } } protocols { fib2mrib { enabled: true } } --Boundary-00=_34BxAllCGZFlI6x Content-Type: text/x-log; charset="iso-8859-1"; name="xorp.log" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xorp.log" [ 2004/06/07 09:35:37 INFO xorp_rtrmgr:20733 RTRMGR +134 master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, rib, fib2mrib, igmp, pimsm4 [ 2004/06/07 09:35:37 INFO xorp_rtrmgr:20733 RTRMGR +356 module_manager.cc run ] Running module: interfaces (/usr/local/xorp/fea/xorp_fea) [ 2004/06/07 09:35:39 INFO xorp_rtrmgr:20733 RTRMGR +356 module_manager.cc run ] Running module: fea (/usr/local/xorp/fea/xorp_fea) [ 2004/06/07 09:35:45 INFO xorp_rtrmgr:20733 RTRMGR +356 module_manager.cc run ] Running module: mfea4 (/usr/local/xorp/fea/xorp_fea) [ 2004/06/07 09:35:45 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: >finder://MFEA_4/mfea/0.1/start_mfea< [ 2004/06/07 09:35:46 INFO xorp_fea MFEA ] New vif: Vif[eth2] pif_index: 4 vif_index: 0 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 0.0.0.0 peer: 0.0.0.0 addr: 172.24.192.3 subnet: 172.24.192.0/21 broadcast: 172.24.199.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2004/06/07 09:35:46 INFO xorp_fea MFEA ] New vif: Vif[register_vif] pif_index: 4 vif_index: 2 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 172.24.192.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP [ 2004/06/07 09:35:46 INFO xorp_fea MFEA ] New vif: Vif[eth3] pif_index: 5 vif_index: 1 addr: 193.190.113.17 subnet: 193.190.113.16/29 broadcast: 193.190.113.22 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2004/06/07 09:35:46 INFO xorp_fea MFEA ] Enabled vif: eth2 [ 2004/06/07 09:35:46 INFO xorp_fea MFEA ] Started vif: eth2 [ 2004/06/07 09:35:46 INFO xorp_fea MFEA ] Enabled vif: eth3 [ 2004/06/07 09:35:46 INFO xorp_fea MFEA ] Started vif: eth3 [ 2004/06/07 09:35:46 INFO xorp_fea MFEA ] Enabled vif: register_vif [ 2004/06/07 09:35:46 INFO xorp_fea MFEA ] Started vif: register_vif [ 2004/06/07 09:35:46 WARNING xorp_fea FEA ] Got update for interface not in FEA tree: pimreg [ 2004/06/07 09:35:46 WARNING xorp_fea FEA ] Got update for vif on interface not in tree:pimreg/(pimreg) [ 2004/06/07 09:35:46 WARNING xorp_fea FEA ] Got update for interface not in FEA tree: pimreg [ 2004/06/07 09:35:46 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.190.113.20 dst = 233.10.51.252 [ 2004/06/07 09:35:46 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.190.113.20 dst = 239.2.12.42 [ 2004/06/07 09:35:46 INFO xorp_rtrmgr:20733 RTRMGR +356 module_manager.cc run ] Running module: rib (/usr/local/xorp/rib/xorp_rib) [ 2004/06/07 09:35:46 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.190.113.20 dst = 233.10.51.250 [ 2004/06/07 09:35:46 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.190.113.20 dst = 233.10.51.254 [ 2004/06/07 09:35:46 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.191.130.193 dst = 233.10.51.14 [ 2004/06/07 09:35:46 INFO xorp_fea MFEA ] New vif: Vif[pimreg] pif_index: 0 vif_index: 3 Flags: [ 2004/06/07 09:35:48 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 0 src = 172.24.199.229 dst = 225.0.1.50 [ 2004/06/07 09:35:48 INFO xorp_rtrmgr:20733 RTRMGR +356 module_manager.cc run ] Running module: fib2mrib (/usr/local/xorp/fib2mrib/xorp_fib2mrib) [ 2004/06/07 09:35:50 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 0 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:35:50 INFO xorp_rtrmgr:20733 RTRMGR +356 module_manager.cc run ] Running module: igmp (/usr/local/xorp/mld6igmp/xorp_igmp) [ 2004/06/07 09:35:50 WARNING xorp_rtrmgr:20733 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "IGMP" does not exist or is not enabled. [ 2004/06/07 09:35:52 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: >finder://IGMP/mld6igmp/0.1/start_mld6igmp< [ 2004/06/07 09:35:52 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth2] pif_index: 0 vif_index: 0 Flags: [ 2004/06/07 09:35:52 INFO xorp_igmp MLD6IGMP ] Added new address to vif eth2: addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 0.0.0.0 peer: 0.0.0.0 [ 2004/06/07 09:35:52 INFO xorp_igmp MLD6IGMP ] Added new address to vif eth2: addr: 172.24.192.3 subnet: 172.24.192.0/21 broadcast: 172.24.199.255 peer: 0.0.0.0 [ 2004/06/07 09:35:52 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[eth2] pif_index: 0 vif_index: 0 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 0.0.0.0 peer: 0.0.0.0 addr: 172.24.192.3 subnet: 172.24.192.0/21 broadcast: 172.24.199.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2004/06/07 09:35:52 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth3] pif_index: 0 vif_index: 1 Flags: [ 2004/06/07 09:35:52 INFO xorp_igmp MLD6IGMP ] Added new address to vif eth3: addr: 193.190.113.17 subnet: 193.190.113.16/29 broadcast: 193.190.113.22 peer: 0.0.0.0 [ 2004/06/07 09:35:52 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[eth3] pif_index: 0 vif_index: 1 addr: 193.190.113.17 subnet: 193.190.113.16/29 broadcast: 193.190.113.22 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2004/06/07 09:35:52 INFO xorp_igmp MLD6IGMP ] New vif: Vif[register_vif] pif_index: 0 vif_index: 2 Flags: [ 2004/06/07 09:35:52 INFO xorp_igmp MLD6IGMP ] Added new address to vif register_vif: addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 172.24.192.1 peer: 0.0.0.0 [ 2004/06/07 09:35:52 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[register_vif] pif_index: 0 vif_index: 2 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 172.24.192.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP [ 2004/06/07 09:35:52 INFO xorp_igmp MLD6IGMP ] New vif: Vif[pimreg] pif_index: 0 vif_index: 3 Flags: [ 2004/06/07 09:35:53 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth2 [ 2004/06/07 09:35:53 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth2] pif_index: 0 vif_index: 0 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 0.0.0.0 peer: 0.0.0.0 addr: 172.24.192.3 subnet: 172.24.192.0/21 broadcast: 172.24.199.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2004/06/07 09:35:53 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 224.0.0.1 [ 2004/06/07 09:35:53 INFO xorp_igmp MLD6IGMP ] Started vif: eth2 [ 2004/06/07 09:35:53 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth3 [ 2004/06/07 09:35:53 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth3] pif_index: 0 vif_index: 1 addr: 193.190.113.17 subnet: 193.190.113.16/29 broadcast: 193.190.113.22 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2004/06/07 09:35:53 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 193.190.113.17 to 224.0.0.1 [ 2004/06/07 09:35:53 INFO xorp_igmp MLD6IGMP ] Started vif: eth3 [ 2004/06/07 09:35:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 224.0.0.1 on vif eth2 [ 2004/06/07 09:35:53 INFO xorp_rtrmgr:20733 RTRMGR +356 module_manager.cc run ] Running module: pimsm4 (/usr/local/xorp/pim/xorp_pimsm4) [ 2004/06/07 09:35:53 WARNING xorp_rtrmgr:20733 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "PIMSM_4" does not exist or is not enabled. [ 2004/06/07 09:35:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 193.190.113.17 to 224.0.0.1 on vif eth3 [ 2004/06/07 09:35:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.192.3 to 224.0.0.2 on vif eth2 [ 2004/06/07 09:35:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.2 on vif eth3 [ 2004/06/07 09:35:54 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: >finder://PIMSM_4/pim/0.1/start_pim< [ 2004/06/07 09:35:54 INFO xorp_pimsm4 PIM ] New vif: Vif[eth2] pif_index: 0 vif_index: 0 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 0.0.0.0 peer: 0.0.0.0 addr: 172.24.192.3 subnet: 172.24.192.0/21 broadcast: 172.24.199.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2004/06/07 09:35:54 INFO xorp_pimsm4 PIM ] New vif: Vif[eth3] pif_index: 0 vif_index: 1 addr: 193.190.113.17 subnet: 193.190.113.16/29 broadcast: 193.190.113.22 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2004/06/07 09:35:54 INFO xorp_pimsm4 PIM ] New vif: Vif[pimreg] pif_index: 0 vif_index: 3 Flags: [ 2004/06/07 09:35:54 INFO xorp_pimsm4 PIM ] New vif: Vif[register_vif] pif_index: 0 vif_index: 2 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 172.24.192.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP [ 2004/06/07 09:35:54 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 224.2.127.254 on vif eth2 [ 2004/06/07 09:35:54 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.2 on vif eth3 [ 2004/06/07 09:35:54 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.52 to 224.0.1.1 on vif eth2 [ 2004/06/07 09:35:55 INFO xorp_pimsm4 PIM ] Enabled vif: eth2 [ 2004/06/07 09:35:55 INFO xorp_pimsm4 PIM ] STARTING Vif[eth2] pif_index: 0 vif_index: 0 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 0.0.0.0 peer: 0.0.0.0 addr: 172.24.192.3 subnet: 172.24.192.0/21 broadcast: 172.24.199.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2004/06/07 09:35:55 INFO xorp_pimsm4 PIM ] Started vif: eth2 [ 2004/06/07 09:35:55 INFO xorp_pimsm4 PIM ] Enabled vif: eth3 [ 2004/06/07 09:35:55 INFO xorp_pimsm4 PIM ] STARTING Vif[eth3] pif_index: 0 vif_index: 1 addr: 193.190.113.17 subnet: 193.190.113.16/29 broadcast: 193.190.113.22 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2004/06/07 09:35:55 INFO xorp_pimsm4 PIM ] Started vif: eth3 [ 2004/06/07 09:35:55 INFO xorp_pimsm4 PIM ] Enabled vif: register_vif [ 2004/06/07 09:35:55 INFO xorp_pimsm4 PIM ] STARTING Vif[register_vif] pif_index: 0 vif_index: 2 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 172.24.192.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2004/06/07 09:35:55 INFO xorp_pimsm4 PIM ] Started vif: register_vif [ 2004/06/07 09:35:55 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,224.2.127.254) on vif eth2 [ 2004/06/07 09:35:55 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:35:55 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 224.2.127.254: not found [ 2004/06/07 09:35:55 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,224.0.1.1) on vif eth2 [ 2004/06/07 09:35:55 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 224.0.1.1: not found [ 2004/06/07 09:35:55 INFO xorp_rtrmgr:20733 RTRMGR +1364 task.cc run_task ] No more tasks to run [ 2004/06/07 09:35:55 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:35:55 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:35:55 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V1_MEMBERSHIP_REPORT from 172.24.193.15 to 224.0.1.60 on vif eth2 [ 2004/06/07 09:35:55 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,224.0.1.60) on vif eth2 [ 2004/06/07 09:35:55 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: upstream neighbor for RP 193.191.0.254 for group 224.0.1.60: not found [ 2004/06/07 09:35:56 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.192.2 to 224.0.0.18 on vif eth2 [ 2004/06/07 09:35:56 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.199.229 to 225.0.0.50 on vif eth2 [ 2004/06/07 09:35:56 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,225.0.0.50) on vif eth2 [ 2004/06/07 09:35:56 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: upstream neighbor for RP 193.191.0.254 for group 225.0.0.50: not found [ 2004/06/07 09:35:56 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 233.10.51.14 on vif eth3 [ 2004/06/07 09:35:56 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,233.10.51.14) on vif eth3 [ 2004/06/07 09:35:56 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: upstream neighbor for RP 193.191.0.254 for group 233.10.51.14: not found [ 2004/06/07 09:35:56 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.2 on vif eth3 [ 2004/06/07 09:35:56 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.14 on vif eth2 [ 2004/06/07 09:35:56 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,233.10.51.14) on vif eth2 [ 2004/06/07 09:35:56 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.192.3 to 224.0.0.2 on vif eth2 [ 2004/06/07 09:35:57 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:35:57 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.250 on vif eth2 [ 2004/06/07 09:35:57 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,233.10.51.250) on vif eth2 [ 2004/06/07 09:35:57 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: upstream neighbor for RP 193.191.0.254 for group 233.10.51.250: not found [ 2004/06/07 09:35:59 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:35:59 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 193.190.113.21 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:35:59 TRACE xorp_pimsm4 PIM ] Added new neighbor 193.190.113.21 on vif eth3 [ 2004/06/07 09:35:59 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:35:59 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:35:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:35:59 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.50.20.65 dst = 224.2.127.254 [ 2004/06/07 09:35:59 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 193.50.20.65 dst = 224.2.127.254 [ 2004/06/07 09:35:59 TRACE xorp_pimsm4 PIM ] Add MFC entry: (193.50.20.65,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:35:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:35:59 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 128.205.10.184 dst = 224.2.127.254 [ 2004/06/07 09:35:59 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 128.205.10.184 dst = 224.2.127.254 [ 2004/06/07 09:35:59 TRACE xorp_pimsm4 PIM ] Add MFC entry: (128.205.10.184,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:00 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 134.174.178.253 dst = 224.2.127.254 [ 2004/06/07 09:36:00 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 134.174.178.253 dst = 224.2.127.254 [ 2004/06/07 09:36:00 TRACE xorp_pimsm4 PIM ] Add MFC entry: (134.174.178.253,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:00 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 192.87.116.22 dst = 224.2.127.254 [ 2004/06/07 09:36:00 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 192.87.116.22 dst = 224.2.127.254 [ 2004/06/07 09:36:00 TRACE xorp_pimsm4 PIM ] Add MFC entry: (192.87.116.22,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:00 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 129.116.65.3 dst = 224.2.127.254 [ 2004/06/07 09:36:00 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 129.116.65.3 dst = 224.2.127.254 [ 2004/06/07 09:36:00 TRACE xorp_pimsm4 PIM ] Add MFC entry: (129.116.65.3,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:00 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 129.132.183.162 dst = 224.2.127.254 [ 2004/06/07 09:36:00 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 129.132.183.162 dst = 224.2.127.254 [ 2004/06/07 09:36:00 TRACE xorp_pimsm4 PIM ] Add MFC entry: (129.132.183.162,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:36:01 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 137.99.23.26 dst = 224.2.127.254 [ 2004/06/07 09:36:01 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 137.99.23.26 dst = 224.2.127.254 [ 2004/06/07 09:36:01 TRACE xorp_pimsm4 PIM ] Add MFC entry: (137.99.23.26,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.199.229 to 225.0.1.50 on vif eth2 [ 2004/06/07 09:36:01 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,225.0.1.50) on vif eth2 [ 2004/06/07 09:36:01 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:36:01 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 128.114.3.67 dst = 224.2.127.254 [ 2004/06/07 09:36:01 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 128.114.3.67 dst = 224.2.127.254 [ 2004/06/07 09:36:01 TRACE xorp_pimsm4 PIM ] Add MFC entry: (128.114.3.67,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 239.2.12.42 on vif eth3 [ 2004/06/07 09:36:01 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,239.2.12.42) on vif eth3 [ 2004/06/07 09:36:02 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 192.94.63.22 dst = 224.2.127.254 [ 2004/06/07 09:36:02 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 192.94.63.22 dst = 224.2.127.254 [ 2004/06/07 09:36:02 TRACE xorp_pimsm4 PIM ] Add MFC entry: (192.94.63.22,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:02 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 128.205.10.177 dst = 224.2.127.254 [ 2004/06/07 09:36:02 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 128.205.10.177 dst = 224.2.127.254 [ 2004/06/07 09:36:02 TRACE xorp_pimsm4 PIM ] Add MFC entry: (128.205.10.177,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:03 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 163.117.69.82 dst = 224.2.127.254 [ 2004/06/07 09:36:03 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 163.117.69.82 dst = 224.2.127.254 [ 2004/06/07 09:36:03 TRACE xorp_pimsm4 PIM ] Add MFC entry: (163.117.69.82,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:03 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 147.83.131.180 dst = 224.2.127.254 [ 2004/06/07 09:36:03 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 147.83.131.180 dst = 224.2.127.254 [ 2004/06/07 09:36:03 TRACE xorp_pimsm4 PIM ] Add MFC entry: (147.83.131.180,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:03 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 130.206.3.133 dst = 224.2.127.254 [ 2004/06/07 09:36:03 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 130.206.3.133 dst = 224.2.127.254 [ 2004/06/07 09:36:03 TRACE xorp_pimsm4 PIM ] Add MFC entry: (130.206.3.133,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:04 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 163.117.131.10 dst = 224.2.127.254 [ 2004/06/07 09:36:04 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 163.117.131.10 dst = 224.2.127.254 [ 2004/06/07 09:36:04 TRACE xorp_pimsm4 PIM ] Add MFC entry: (163.117.131.10,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:04 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 192.87.116.121 dst = 224.2.127.254 [ 2004/06/07 09:36:04 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 192.87.116.121 dst = 224.2.127.254 [ 2004/06/07 09:36:04 TRACE xorp_pimsm4 PIM ] Add MFC entry: (192.87.116.121,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:05 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 131.252.176.50 dst = 224.2.127.254 [ 2004/06/07 09:36:05 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 131.252.176.50 dst = 224.2.127.254 [ 2004/06/07 09:36:05 TRACE xorp_pimsm4 PIM ] Add MFC entry: (131.252.176.50,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:06 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.192.3 to 224.0.0.2 on vif eth2 [ 2004/06/07 09:36:06 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 207.75.164.245 dst = 224.2.127.254 [ 2004/06/07 09:36:06 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 207.75.164.245 dst = 224.2.127.254 [ 2004/06/07 09:36:06 TRACE xorp_pimsm4 PIM ] Add MFC entry: (207.75.164.245,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:07 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 159.247.233.148 dst = 224.2.127.254 [ 2004/06/07 09:36:07 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 159.247.233.148 dst = 224.2.127.254 [ 2004/06/07 09:36:07 TRACE xorp_pimsm4 PIM ] Add MFC entry: (159.247.233.148,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:08 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 141.99.80.70 dst = 224.2.127.254 [ 2004/06/07 09:36:08 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 141.99.80.70 dst = 224.2.127.254 [ 2004/06/07 09:36:08 TRACE xorp_pimsm4 PIM ] Add MFC entry: (141.99.80.70,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:10 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 129.49.17.194 dst = 224.2.127.254 [ 2004/06/07 09:36:10 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 129.49.17.194 dst = 224.2.127.254 [ 2004/06/07 09:36:10 TRACE xorp_pimsm4 PIM ] Add MFC entry: (129.49.17.194,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:11 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 80.251.42.35 dst = 224.2.127.254 [ 2004/06/07 09:36:11 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 80.251.42.35 dst = 224.2.127.254 [ 2004/06/07 09:36:11 TRACE xorp_pimsm4 PIM ] Add MFC entry: (80.251.42.35,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:19 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 128.114.3.66 dst = 224.2.127.254 [ 2004/06/07 09:36:19 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 128.114.3.66 dst = 224.2.127.254 [ 2004/06/07 09:36:19 TRACE xorp_pimsm4 PIM ] Add MFC entry: (128.114.3.66,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:24 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 224.0.0.1 [ 2004/06/07 09:36:24 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 193.190.113.17 to 224.0.0.1 [ 2004/06/07 09:36:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 224.0.0.1 on vif eth2 [ 2004/06/07 09:36:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 193.190.113.17 to 224.0.0.1 on vif eth3 [ 2004/06/07 09:36:24 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 192.148.249.30 dst = 224.0.1.1 [ 2004/06/07 09:36:24 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 192.148.249.30 dst = 224.0.1.1 [ 2004/06/07 09:36:24 TRACE xorp_pimsm4 PIM ] Add MFC entry: (192.148.249.30,224.0.1.1) iif = 1 olist = O... [ 2004/06/07 09:36:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.192.3 to 224.0.0.18 on vif eth2 [ 2004/06/07 09:36:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.52 to 224.0.1.1 on vif eth2 [ 2004/06/07 09:36:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 233.10.51.14 on vif eth3 [ 2004/06/07 09:36:25 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V1_MEMBERSHIP_REPORT from 172.24.193.16 to 224.0.1.60 on vif eth2 [ 2004/06/07 09:36:25 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.199.229 to 225.0.0.50 on vif eth2 [ 2004/06/07 09:36:27 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:36:27 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 128.59.31.187 dst = 224.2.127.254 [ 2004/06/07 09:36:27 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 128.59.31.187 dst = 224.2.127.254 [ 2004/06/07 09:36:27 TRACE xorp_pimsm4 PIM ] Add MFC entry: (128.59.31.187,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:27 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 193.190.113.21 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:36:28 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.14 on vif eth2 [ 2004/06/07 09:36:29 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:36:29 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.199.229 to 225.0.1.50 on vif eth2 [ 2004/06/07 09:36:29 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:36:29 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 131.188.3.222 dst = 224.0.1.1 [ 2004/06/07 09:36:29 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 131.188.3.222 dst = 224.0.1.1 [ 2004/06/07 09:36:29 TRACE xorp_pimsm4 PIM ] Add MFC entry: (131.188.3.222,224.0.1.1) iif = 1 olist = O... [ 2004/06/07 09:36:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.2 on vif eth3 [ 2004/06/07 09:36:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 224.2.127.254 on vif eth2 [ 2004/06/07 09:36:31 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.250 on vif eth2 [ 2004/06/07 09:36:31 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 239.2.12.42 on vif eth3 [ 2004/06/07 09:36:32 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 128.59.31.189 dst = 224.2.127.254 [ 2004/06/07 09:36:32 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 128.59.31.189 dst = 224.2.127.254 [ 2004/06/07 09:36:32 TRACE xorp_pimsm4 PIM ] Add MFC entry: (128.59.31.189,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:32 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:36:32 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.190.113.20 dst = 224.2.127.254 [ 2004/06/07 09:36:32 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 193.190.113.20 dst = 224.2.127.254 [ 2004/06/07 09:36:32 TRACE xorp_pimsm4 PIM ] Add MFC entry: (193.190.113.20,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:32 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:36:33 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.192.3 to 224.0.0.2 on vif eth2 [ 2004/06/07 09:36:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 172.24.198.71 to 224.0.0.2 on vif eth2 [ 2004/06/07 09:36:40 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 233.10.51.250 [ 2004/06/07 09:36:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 233.10.51.250 on vif eth2 [ 2004/06/07 09:36:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.250 on vif eth2 [ 2004/06/07 09:36:41 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 18.18.0.1 dst = 224.0.1.1 [ 2004/06/07 09:36:41 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 18.18.0.1 dst = 224.0.1.1 [ 2004/06/07 09:36:41 TRACE xorp_pimsm4 PIM ] Add MFC entry: (18.18.0.1,224.0.1.1) iif = 1 olist = O... [ 2004/06/07 09:36:49 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.250 on vif eth2 [ 2004/06/07 09:36:49 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.250 on vif eth2 [ 2004/06/07 09:36:49 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 131.188.3.220 dst = 224.0.1.1 [ 2004/06/07 09:36:49 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 131.188.3.220 dst = 224.0.1.1 [ 2004/06/07 09:36:49 TRACE xorp_pimsm4 PIM ] Add MFC entry: (131.188.3.220,224.0.1.1) iif = 1 olist = O... [ 2004/06/07 09:36:50 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 18.7.21.1 dst = 224.0.1.1 [ 2004/06/07 09:36:50 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 18.7.21.1 dst = 224.0.1.1 [ 2004/06/07 09:36:50 TRACE xorp_pimsm4 PIM ] Add MFC entry: (18.7.21.1,224.0.1.1) iif = 1 olist = O... [ 2004/06/07 09:36:52 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 128.91.56.3 dst = 224.2.127.254 [ 2004/06/07 09:36:52 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 128.91.56.3 dst = 224.2.127.254 [ 2004/06/07 09:36:52 TRACE xorp_pimsm4 PIM ] Add MFC entry: (128.91.56.3,224.2.127.254) iif = 1 olist = O... [ 2004/06/07 09:36:56 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 193.190.113.21 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:36:57 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:36:59 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:36:59 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:01 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:02 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.190.113.20 dst = 239.2.12.42 [ 2004/06/07 09:37:02 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.190.113.20 dst = 233.10.51.250 [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 193.190.113.20 dst = 239.2.12.42 [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] Add MFC entry: (193.190.113.20,239.2.12.42) iif = 1 olist = .... [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 193.190.113.20 dst = 233.10.51.250 [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] Add MFC entry: (193.190.113.20,233.10.51.250) iif = 1 olist = O... [ 2004/06/07 09:37:02 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.190.113.20 dst = 233.10.51.254 [ 2004/06/07 09:37:02 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.190.113.20 dst = 233.10.51.252 [ 2004/06/07 09:37:02 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 0 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:02 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 172.24.198.71 to 224.0.0.2 on vif eth2 [ 2004/06/07 09:37:02 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 233.10.51.250 [ 2004/06/07 09:37:02 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 233.10.51.250 on vif eth2 [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 193.190.113.20 dst = 233.10.51.254 [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] Add MFC entry: (193.190.113.20,233.10.51.254) iif = 1 olist = .... [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 193.190.113.20 dst = 233.10.51.252 [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] Add MFC entry: (193.190.113.20,233.10.51.252) iif = 1 olist = .... [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 0 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] TX PIM_ASSERT from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] Add MFC entry: (172.24.198.71,233.10.51.250) iif = 0 olist = ..O. [ 2004/06/07 09:37:02 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:02 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:03 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 193.191.130.193 dst = 233.10.51.14 [ 2004/06/07 09:37:03 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:03 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:37:03 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 193.191.130.193 dst = 233.10.51.14 [ 2004/06/07 09:37:03 TRACE xorp_pimsm4 PIM ] Add MFC entry: (193.191.130.193,233.10.51.14) iif = 1 olist = O... [ 2004/06/07 09:37:03 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 0 src = 172.24.199.229 dst = 225.0.1.50 [ 2004/06/07 09:37:03 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 0 src = 172.24.199.229 dst = 225.0.1.50 [ 2004/06/07 09:37:03 TRACE xorp_pimsm4 PIM ] TX PIM_ASSERT from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:37:03 TRACE xorp_pimsm4 PIM ] Add MFC entry: (172.24.199.229,225.0.1.50) iif = 0 olist = ..O. [ 2004/06/07 09:37:03 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:03 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 233.10.51.250 [ 2004/06/07 09:37:03 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 233.10.51.250 on vif eth2 [ 2004/06/07 09:37:04 TRACE xorp_pimsm4 PIM ] Delete membership for (0.0.0.0,233.10.51.250) on vif eth2 [ 2004/06/07 09:37:04 TRACE xorp_pimsm4 PIM ] TX PIM_ASSERT from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:37:04 TRACE xorp_pimsm4 PIM ] Add MFC entry: (193.190.113.20,233.10.51.250) iif = 1 olist = .... [ 2004/06/07 09:37:04 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:05 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.254 on vif eth2 [ 2004/06/07 09:37:05 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,233.10.51.254) on vif eth2 [ 2004/06/07 09:37:05 TRACE xorp_pimsm4 PIM ] Add MFC entry: (193.190.113.20,233.10.51.254) iif = 1 olist = O... [ 2004/06/07 09:37:05 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:05 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.254 on vif eth2 [ 2004/06/07 09:37:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 193.190.113.21 to 224.0.0.1 on vif eth3 [ 2004/06/07 09:37:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 239.2.12.42 on vif eth3 [ 2004/06/07 09:37:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.2 on vif eth3 [ 2004/06/07 09:37:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 233.10.51.14 on vif eth3 [ 2004/06/07 09:37:10 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 193.190.113.21 to 224.0.0.1 on vif eth3 [ 2004/06/07 09:37:10 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:10 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.2 on vif eth3 [ 2004/06/07 09:37:10 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 233.10.51.14 on vif eth3 [ 2004/06/07 09:37:11 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 239.2.12.42 on vif eth3 [ 2004/06/07 09:37:14 TRACE xorp_fea MFEA ] RX dataflow message: src = 193.50.20.65 dst = 224.2.127.254 [ 2004/06/07 09:37:14 TRACE xorp_pimsm4 PIM ] RX DATAFLOW signal: source = 193.50.20.65 group = 224.2.127.254 threshold_interval_sec = 100 threshold_interval_usec = 0 measured_interval_sec = 100 measured_interval_usec = 0 threshold_packets = 0 threshold_bytes = 102400 measured_packets = 446 measured_bytes = 109359 is_threshold_in_packets = 0 is_threshold_in_bytes = 1 is_geq_upcall = 1 is_leq_upcall = 0 [ 2004/06/07 09:37:14 WARNING xorp_pimsm4 PIM ] JoinDesired(S,G) = true: upstream neighbor for source 193.50.20.65 and group 224.2.127.254: not found [ 2004/06/07 09:37:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 172.24.198.71 to 224.0.0.2 on vif eth2 [ 2004/06/07 09:37:15 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 233.10.51.254 [ 2004/06/07 09:37:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 233.10.51.254 on vif eth2 [ 2004/06/07 09:37:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.250 on vif eth2 [ 2004/06/07 09:37:15 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,233.10.51.250) on vif eth2 [ 2004/06/07 09:37:15 TRACE xorp_pimsm4 PIM ] Add MFC entry: (193.190.113.20,233.10.51.250) iif = 1 olist = O... [ 2004/06/07 09:37:15 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:15 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:16 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 233.10.51.254 [ 2004/06/07 09:37:16 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 172.24.192.3 to 233.10.51.254 on vif eth2 [ 2004/06/07 09:37:17 TRACE xorp_pimsm4 PIM ] Delete membership for (0.0.0.0,233.10.51.254) on vif eth2 [ 2004/06/07 09:37:17 TRACE xorp_pimsm4 PIM ] Add MFC entry: (193.190.113.20,233.10.51.254) iif = 1 olist = .... [ 2004/06/07 09:37:17 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:18 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:18 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:18 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:37:21 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.250 on vif eth2 [ 2004/06/07 09:37:24 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:24 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:24 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:37:25 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.24.198.71 to 233.10.51.250 on vif eth2 [ 2004/06/07 09:37:25 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 193.190.113.21 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:26 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:26 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:26 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:37:27 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:37:28 TRACE xorp_fea MFEA ] RX dataflow message: src = 193.191.130.193 dst = 233.10.51.14 [ 2004/06/07 09:37:28 TRACE xorp_pimsm4 PIM ] RX DATAFLOW signal: source = 193.191.130.193 group = 233.10.51.14 threshold_interval_sec = 100 threshold_interval_usec = 0 measured_interval_sec = 100 measured_interval_usec = 0 threshold_packets = 0 threshold_bytes = 102400 measured_packets = 309 measured_bytes = 400155 is_threshold_in_packets = 0 is_threshold_in_bytes = 1 is_geq_upcall = 1 is_leq_upcall = 0 [ 2004/06/07 09:37:28 WARNING xorp_pimsm4 PIM ] JoinDesired(S,G) = true: upstream neighbor for source 193.191.130.193 and group 233.10.51.14: not found [ 2004/06/07 09:37:29 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:29 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 193.190.113.21 to 224.0.0.1 on vif eth3 [ 2004/06/07 09:37:29 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.2 on vif eth3 [ 2004/06/07 09:37:29 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:29 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:29 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:37:29 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 233.10.51.14 on vif eth3 [ 2004/06/07 09:37:29 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 239.2.12.42 on vif eth3 [ 2004/06/07 09:37:35 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:35 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:35 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:37:39 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 131.188.3.221 dst = 224.0.1.1 [ 2004/06/07 09:37:39 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 131.188.3.221 dst = 224.0.1.1 [ 2004/06/07 09:37:39 TRACE xorp_pimsm4 PIM ] Add MFC entry: (131.188.3.221,224.0.1.1) iif = 1 olist = O... [ 2004/06/07 09:37:40 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:40 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:40 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:37:46 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:46 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:46 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:37:48 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 193.190.113.21 to 224.0.0.1 on vif eth3 [ 2004/06/07 09:37:49 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 239.2.12.42 on vif eth3 [ 2004/06/07 09:37:49 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.2 on vif eth3 [ 2004/06/07 09:37:49 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 233.10.51.14 on vif eth3 [ 2004/06/07 09:37:49 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:50 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:50 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:50 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:37:54 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 193.190.113.21 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:55 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:55 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:37:55 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:37:57 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:37:59 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:37:59 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:38:00 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:38:00 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:38:00 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:38:01 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:38:04 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:38:04 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:38:04 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:38:07 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 193.190.113.21 to 224.0.0.1 on vif eth3 [ 2004/06/07 09:38:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 233.10.51.14 on vif eth3 [ 2004/06/07 09:38:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.20 to 239.2.12.42 on vif eth3 [ 2004/06/07 09:38:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.2 on vif eth3 [ 2004/06/07 09:38:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:38:09 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:38:09 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:38:09 TRACE xorp_pimsm4 PIM ] TX PIM_REGISTER from 172.24.192.1 to 193.191.0.254 on vif register_vif [ 2004/06/07 09:38:11 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 131.188.3.223 dst = 224.0.1.1 [ 2004/06/07 09:38:11 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 131.188.3.223 dst = 224.0.1.1 [ 2004/06/07 09:38:11 TRACE xorp_pimsm4 PIM ] Add MFC entry: (131.188.3.223,224.0.1.1) iif = 1 olist = O... [ 2004/06/07 09:38:12 INFO xorp_rtrmgr:20733 RTRMGR +568 task.cc shutdown ] Shutting down module: pimsm4 [ 2004/06/07 09:38:12 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:38:12 INFO xorp_pimsm4 PIM ] PENDING STOP Vif[eth2] pif_index: 0 vif_index: 0 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 0.0.0.0 peer: 0.0.0.0 addr: 172.24.192.3 subnet: 172.24.192.0/21 broadcast: 172.24.199.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP PENDING_DOWN IPv4 ENABLED [ 2004/06/07 09:38:12 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:38:12 INFO xorp_pimsm4 PIM ] PENDING STOP Vif[eth3] pif_index: 0 vif_index: 1 addr: 193.190.113.17 subnet: 193.190.113.16/29 broadcast: 193.190.113.22 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP PENDING_DOWN IPv4 ENABLED [ 2004/06/07 09:38:12 INFO xorp_pimsm4 PIM ] PENDING STOP Vif[register_vif] pif_index: 0 vif_index: 2 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 172.24.192.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP PENDING_DOWN IPv4 ENABLED [ 2004/06/07 09:38:12 WARNING xorp_pimsm4 PIM ] JoinDesired(S,G) = false: upstream neighbor for source 193.50.20.65 and group 224.2.127.254: not found [ 2004/06/07 09:38:12 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 172.24.192.3 to 224.0.0.13 on vif eth2 [ 2004/06/07 09:38:12 INFO xorp_pimsm4 PIM ] STOPPED Vif[eth2] pif_index: 0 vif_index: 0 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 0.0.0.0 peer: 0.0.0.0 addr: 172.24.192.3 subnet: 172.24.192.0/21 broadcast: 172.24.199.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP DOWN IPv4 ENABLED [ 2004/06/07 09:38:12 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 193.190.113.17 to 224.0.0.13 on vif eth3 [ 2004/06/07 09:38:12 INFO xorp_pimsm4 PIM ] STOPPED Vif[eth3] pif_index: 0 vif_index: 1 addr: 193.190.113.17 subnet: 193.190.113.16/29 broadcast: 193.190.113.22 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP DOWN IPv4 ENABLED [ 2004/06/07 09:38:12 INFO xorp_pimsm4 PIM ] STOPPED Vif[register_vif] pif_index: 0 vif_index: 2 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 172.24.192.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP DOWN IPv4 ENABLED [ 2004/06/07 09:38:12 INFO xorp_pimsm4 PIM ] Deleted vif: eth2 [ 2004/06/07 09:38:12 INFO xorp_pimsm4 PIM ] Deleted vif: eth3 [ 2004/06/07 09:38:12 INFO xorp_pimsm4 PIM ] Deleted vif: register_vif [ 2004/06/07 09:38:12 INFO xorp_pimsm4 PIM ] Deleted vif: pimreg [ 2004/06/07 09:38:12 TRACE xorp_pimsm4 PIM ] Delete MFC entry: (18.7.21.1,224.0.1.1) iif = 1 olist = pure virtual method called [ 2004/06/07 09:38:12 INFO xorp_rtrmgr:20733 RTRMGR +502 module_manager.cc killed ] Module abnormally killed: pimsm4 [ 2004/06/07 09:38:12 INFO xorp_rtrmgr:20733 XRL +330 xrl_router.cc send_resolved ] Sender died (protocol = "stcp", address = "127.0.0.1:4657") [ 2004/06/07 09:38:12 ERROR xorp_rtrmgr:20733 IPC +270 sockutil.cc create_connected_ip_socket ] failed to connect to 127.0.0.1 port 4657: Connection refused [ 2004/06/07 09:38:12 ERROR xorp_rtrmgr:20733 XRL +52 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 549 of xrl_pf_stcp.cc: Could not connect to 127.0.0.1:4657 [ 2004/06/07 09:38:12 ERROR xorp_rtrmgr:20733 XRL +341 xrl_router.cc send_resolved ] Could not create XrlPFSender for protocol = "stcp" address = "127.0.0.1:4657" [ 2004/06/07 09:38:12 WARNING xorp_rtrmgr:20733 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "PIMSM_4" does not exist or is not enabled. [ 2004/06/07 09:38:13 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 3 vif_index = 2 src = 172.24.198.71 dst = 233.10.51.250 [ 2004/06/07 09:38:13 WARNING xorp_rtrmgr:20733 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "PIMSM_4" does not exist or is not enabled. [ 2004/06/07 09:38:13 ERROR xorp_fea:20735 MFEA +626 xrl_mfea_node.cc mfea_client_client_send_recv_kernel_signal_message_cb ] Failed to send a kernel signal message to a protocol: 201 Resolve failed [ 2004/06/07 09:38:13 INFO xorp_rtrmgr:20733 RTRMGR +568 task.cc shutdown ] Shutting down module: igmp [ 2004/06/07 09:38:13 INFO xorp_igmp MLD6IGMP ] STOPPED Vif[eth2] pif_index: 0 vif_index: 0 addr: 172.24.192.1 subnet: 172.24.192.1/32 broadcast: 0.0.0.0 peer: 0.0.0.0 addr: 172.24.192.3 subnet: 172.24.192.0/21 broadcast: 172.24.199.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP DOWN IPv4 ENABLED [ 2004/06/07 09:38:13 INFO xorp_igmp MLD6IGMP ] STOPPED Vif[eth3] pif_index: 0 vif_index: 1 addr: 193.190.113.17 subnet: 193.190.113.16/29 broadcast: 193.190.113.22 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP DOWN IPv4 ENABLED [ 2004/06/07 09:38:13 WARNING xorp_rtrmgr:20733 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "PIMSM_4" does not exist or is not enabled. [ 2004/06/07 09:38:14 INFO xorp_igmp MLD6IGMP ] Deleted vif: eth2 [ 2004/06/07 09:38:14 INFO xorp_igmp MLD6IGMP ] Deleted vif: eth3 [ 2004/06/07 09:38:14 INFO xorp_igmp MLD6IGMP ] Deleted vif: register_vif [ 2004/06/07 09:38:14 INFO xorp_igmp MLD6IGMP ] Deleted vif: pimreg [ 2004/06/07 09:38:14 INFO xorp_rtrmgr:20733 RTRMGR +476 module_manager.cc normal_exit ] Module normal exit: igmp [ 2004/06/07 09:38:14 WARNING xorp_rtrmgr:20733 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "IGMP" does not exist or is not enabled. [ 2004/06/07 09:38:15 INFO xorp_rtrmgr:20733 RTRMGR +568 task.cc shutdown ] Shutting down module: fib2mrib [ 2004/06/07 09:38:15 WARNING xorp_rtrmgr:20733 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "PIMSM_4" does not exist or is not enabled. [ 2004/06/07 09:38:15 ERROR xorp_rib:20737 XifRedistTransaction6 +641 redist_xrl.cc dispatch_complete ] Fatal error during start transaction "201 Resolve failed" [ 2004/06/07 09:38:15 INFO xorp_rtrmgr:20733 RTRMGR +476 module_manager.cc normal_exit ] Module normal exit: fib2mrib [ 2004/06/07 09:38:16 WARNING xorp_rtrmgr:20733 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "fib2mrib" does not exist or is not enabled. [ 2004/06/07 09:38:17 INFO xorp_rtrmgr:20733 RTRMGR +568 task.cc shutdown ] Shutting down module: rib [ 2004/06/07 09:38:18 INFO xorp_rtrmgr:20733 XRL +330 xrl_router.cc send_resolved ] Sender died (protocol = "stcp", address = "127.0.0.1:4633") [ 2004/06/07 09:38:18 INFO xorp_rtrmgr:20733 RTRMGR +476 module_manager.cc normal_exit ] Module normal exit: rib [ 2004/06/07 09:38:19 INFO xorp_rtrmgr:20733 RTRMGR +568 task.cc shutdown ] Shutting down module: mfea4 [ 2004/06/07 09:38:19 ERROR xorp_fea:20735 MFEA +961 mfea_mrouter.cc delete_multicast_vif ] setsockopt(MRT_DEL_VIF, vif eth2) failed: Invalid argument [ 2004/06/07 09:38:19 ERROR xorp_fea:20735 MFEA +992 mfea_node.cc stop_all_vifs ] Cannot stop vif eth2: cannot delete the multicast vif from the kernel [ 2004/06/07 09:38:19 ERROR xorp_fea:20735 MFEA +961 mfea_mrouter.cc delete_multicast_vif ] setsockopt(MRT_DEL_VIF, vif eth3) failed: Invalid argument [ 2004/06/07 09:38:19 ERROR xorp_fea:20735 MFEA +992 mfea_node.cc stop_all_vifs ] Cannot stop vif eth3: cannot delete the multicast vif from the kernel [ 2004/06/07 09:38:19 ERROR xorp_fea:20735 MFEA +961 mfea_mrouter.cc delete_multicast_vif ] setsockopt(MRT_DEL_VIF, vif register_vif) failed: Invalid argument [ 2004/06/07 09:38:19 ERROR xorp_fea:20735 MFEA +992 mfea_node.cc stop_all_vifs ] Cannot stop vif register_vif: cannot delete the multicast vif from the kernel [ 2004/06/07 09:38:19 WARNING xorp_fea FEA ] Got update for interface not in FEA tree: pimreg [ 2004/06/07 09:38:19 ERROR xorp_fea:20735 LIBFEACLIENT +166 ifmgr_xrl_replicator.cc push ] Apply bad command. IfMgrVifRemove("pimreg, "pimreg") [ 2004/06/07 09:38:19 WARNING xorp_rtrmgr:20733 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "ifmgr_mirror-e4e4b14097a44c37ee63f699d797b664@127.0.0.1" does not exist or is not enabled. [ 2004/06/07 09:38:19 INFO xorp_fea LIBFEACLIENT ] An error occurred sending an Xrl to "ifmgr_mirror-e4e4b14097a44c37ee63f699d797b664@127.0.0.1". Target is being removed from list of interface update receivers. [ 2004/06/07 09:38:19 WARNING xorp_fea XrlFeaIfmgrMirrorTarget ] Handling method for fea_ifmgr_mirror/0.1/interface_remove failed: XrlCmdError 102 Command failed Local dispatch error [ 2004/06/07 09:38:21 INFO xorp_rtrmgr:20733 RTRMGR +166 module_manager.cc terminate ] Terminating module: mfea4 [ 2004/06/07 09:38:21 ERROR xorp_fea:20735 MFEA +1601 mfea_mrouter.cc get_sg_count ] ioctl(SIOCGETSGCNT, (18.18.0.1 224.0.1.1)) failed: Bad file descriptor [ 2004/06/07 09:38:24 INFO xorp_rtrmgr:20733 RTRMGR +166 module_manager.cc terminate ] Terminating module: fea [ 2004/06/07 09:38:24 INFO xorp_rtrmgr:20733 RTRMGR +568 task.cc shutdown ] Shutting down module: interfaces [ 2004/06/07 09:38:24 INFO xorp_fea MFEA ] Deleted vif: eth2 [ 2004/06/07 09:38:24 INFO xorp_fea MFEA ] Deleted vif: eth3 [ 2004/06/07 09:38:24 INFO xorp_fea MFEA ] Deleted vif: register_vif [ 2004/06/07 09:38:24 INFO xorp_fea MFEA ] Deleted vif: pimreg [ 2004/06/07 09:38:24 INFO xorp_rtrmgr:20733 RTRMGR +476 module_manager.cc normal_exit ] Module normal exit: interfaces [ 2004/06/07 09:38:25 INFO xorp_rtrmgr:20733 RTRMGR +1364 task.cc run_task ] No more tasks to run --Boundary-00=_34BxAllCGZFlI6x-- From philippe.vanhecke@belnet.be Mon Jun 7 21:04:48 2004 From: philippe.vanhecke@belnet.be (Philippe Van Hecke) Date: Mon, 7 Jun 2004 22:04:48 +0200 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: <200406071638.i57Gc3Kh009671@possum.icir.org> References: <200406071638.i57Gc3Kh009671@possum.icir.org> Message-ID: <200406072204.49961.philippe.vanhecke@belnet.be> Pavlin, forget to ask you in my last mail. What this ERROR mean ? [ 2004/06/07 22:06:24 ERROR xorp_pimsm4:20809 PIM +1452 xrl_pim_node.cc mfea_client_send_add_delete_dataflow_monitor_cb ] Cannot add a dataflow monitor with the MFEA: 102 Command failed Cannot add dataflow monitoring for source 131.188.3.222 and group 224.0.1.1 [ 2004/06/07 22:07:08 ERROR xorp_pimsm4:20809 PIM +1452 xrl_pim_node.cc mfea_client_send_add_delete_dataflow_monitor_cb ] Cannot add a dataflow monitor with the MFEA: 102 Command failed Cannot add dataflow monitoring for source 207.75.164.44 and group 224.2.127.254 Philippe. -- __________________________________________________________________ Philippe Van Hecke - BELNET, The Belgian Research Network "In a world without walls or fences, who needs Windows and Gates?" __________________________________________________________________ From pavlin@icir.org Mon Jun 7 21:08:34 2004 From: pavlin@icir.org (Pavlin Radoslavov) Date: Mon, 07 Jun 2004 13:08:34 -0700 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: Message from Philippe Van Hecke of "Mon, 07 Jun 2004 21:41:23 +0200." <200406072141.25628.lephiloux@skynet.be> Message-ID: <200406072008.i57K8YKh011036@possum.icir.org> > Le Monday 07 June 2004 18:38, Pavlin Radoslavov a écrit : > > Can you verify by running "netstat -rn" that the Juniper router is > > indeed the next-hop router toward those source addresses. For, > > example, if the next-hop router is connected to, say, eth0 which is > > not enabled for multicast routing then this is one possible reason > > for the warning. Also, if "netstat -rn" indeed shows that the > > Juniper router is the next-hop router, then can you use the > > "show pim mrib" xorpsh operational command to verify whether PIM-SM > > itself has learned about that route. Finally, you may want to look > > into the "show pim join" output to check the (S,G) multicast routing > > state. > > Pavlin, > My mistake, when i say that the next-hop 193.191.130.193 should be > the juniper router i talk on the multicast point of view. So you right > my default unicast route is through the eth0 as i want that unicast and > multicast traffic travel through different interface. As i have say in > previous post, the box acting as firewall. I want to disociate traffic on > different interface because the firewall is on the same subnet as others > BELNET server. And i doesn't want that multicast traffic pollute statistic of > unicast traffic of the servers (we are not able to use IGMP snooping on the > switch) > > So there is a possibility to have on linux, different table for unicast and > multicast routing. What i mean here is there is a way to let multicast use > other routing table to make RPF ? Does XORP permit this ? Yes, there is a way to do this in XORP. The XORP RIB (Routing Information Base) basically keeps two separate tables: one for unicast routes, and one for multicast routes. The fib2mrib module populates the multicast RIB table with the unicast routes from the kernel. However, you can modify the MRIB table by adding/overwriting values by using static routes. To do that you need to add entries like: protocols { static { mrib-route4 10.10.0.0/16 { nexthop: 10.20.0.1 } /* The default entry */ mrib-route4 0.0.0.0/0 { nexthop: 10.30.0.1 } } } Sorry, I didn't know that you have a fancy setup like that so I tried to keep the sample config file a bit simpler :) > Also , i doen't know if this is the best way or if this is needed or if it is > completely silly do make this. > > echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter To the best of my knowledge, the purpose of rp_filter is for Reverse Path Filtering: if it is set to 1, then the host/router will ignore packets if they don't arrive on the reverse-path interface. For a better description see http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.kernel.rpf.html Long time ago a fellow who was playing with GRE tunnels and PIM-SM told me that "echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter" is needed if you run PIM-SM over tunnels, but myself I haven't played yet with that particular option to verify whether it is really mandatory. If you want to avoid any unexpected behavior, then it may be simpler if you indeed set rp_filter to 0. Regards, Pavlin From philippe.vanhecke@belnet.be Mon Jun 7 21:09:46 2004 From: philippe.vanhecke@belnet.be (Philippe Van Hecke) Date: Mon, 7 Jun 2004 22:09:46 +0200 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: <200406071638.i57Gc3Kh009671@possum.icir.org> References: <200406071638.i57Gc3Kh009671@possum.icir.org> Message-ID: <200406072209.47896.philippe.vanhecke@belnet.be> Le Monday 07 June 2004 18:38, Pavlin Radoslavov a écrit : > Can you verify by running "netstat -rn" that the Juniper router is > indeed the next-hop router toward those source addresses. For, > example, if the next-hop router is connected to, say, eth0 which is > not enabled for multicast routing then this is one possible reason > for the warning. Also, if "netstat -rn" indeed shows that the > Juniper router is the next-hop router, then can you use the > "show pim mrib" xorpsh operational command to verify whether PIM-SM > itself has learned about that route. Finally, you may want to look > into the "show pim join" output to check the (S,G) multicast routing > state. Pavlin, My mistake, when i say that the next-hop 193.191.130.193 should be the juniper router i talk on the multicast point of view. So you right my default unicast route is through the eth0 as i want that unicast and multicast traffic travel through different interface. As i have say in previous post, the box acting as firewall. I want to disociate traffic on different interface because the firewall is on the same subnet as others BELNET server. And i doesn't want that multicast traffic pollute statistic of unicast traffic of the servers (we are not able to use IGMP snooping on the switch) So there is a possibility to have on linux, different table for unicast and multicast routing. What i mean here is there is a way to let multicast use other routing table to make RPF ? Does XORP permit this ? Also , i doen't know if this is the best way or if this is needed or if it is completely silly do make this. echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter Thanks a lot for your help. Philippe. __________________________________________________________________ Philippe Van Hecke - BELNET, The Belgian Research Network "In a world without walls or fences, who needs Windows and Gates?" __________________________________________________________________ From pavlin@icir.org Mon Jun 7 21:22:50 2004 From: pavlin@icir.org (Pavlin Radoslavov) Date: Mon, 07 Jun 2004 13:22:50 -0700 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: Message from Philippe Van Hecke of "Mon, 07 Jun 2004 22:04:48 +0200." <200406072204.49961.philippe.vanhecke@belnet.be> Message-ID: <200406072022.i57KMoKh011145@possum.icir.org> > Pavlin, > forget to ask you in my last mail. What this ERROR mean ? > > [ 2004/06/07 22:06:24 ERROR xorp_pimsm4:20809 PIM +1452 xrl_pim_node.cc > mfea_client_send_add_delete_dataflow_monitor_cb ] Cannot add a dataflow > monitor with the MFEA: 102 Command failed Cannot add dataflow monitoring for > source 131.188.3.222 and group 224.0.1.1 > > [ 2004/06/07 22:07:08 ERROR xorp_pimsm4:20809 PIM +1452 xrl_pim_node.cc > mfea_client_send_add_delete_dataflow_monitor_cb ] Cannot add a dataflow > monitor with the MFEA: 102 Command failed Cannot add dataflow monitoring for > source 207.75.164.44 and group 224.2.127.254 This error means that I need to modify the source code to print a better error message with the real reason for the error :) I guess this may have happened if PIM-SM has just deleted a (S,G) Multicast Forwarding Entry (MFE), but then there is an attempt to install a dataflow monitoring entry for the same (S,G). Ideally, this shoudn't happen, but even if it happens it shoudn't affect anything and can be ignored. How often do you see this message? To verify the reason for the error can you send me the log message from the moment XORP was started (if the log is too long you don't need to cc the ML) Pavlin From philippe.vanhecke@belnet.be Mon Jun 7 21:28:13 2004 From: philippe.vanhecke@belnet.be (Philippe Van Hecke) Date: Mon, 7 Jun 2004 22:28:13 +0200 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: <200406072008.i57K8YKh011036@possum.icir.org> References: <200406072008.i57K8YKh011036@possum.icir.org> Message-ID: <200406072228.16352.philippe.vanhecke@belnet.be> Le Monday 07 June 2004 22:08, Pavlin Radoslavov a écrit : See my comment inline. > > Yes, there is a way to do this in XORP. The XORP RIB (Routing > Information Base) basically keeps two separate tables: one for > unicast routes, and one for multicast routes. The fib2mrib module > populates the multicast RIB table with the unicast routes from the > kernel. > However, you can modify the MRIB table by adding/overwriting values > by using static routes. To do that you need to add entries like: > > protocols { > static { > mrib-route4 10.10.0.0/16 { > nexthop: 10.20.0.1 > } > > /* The default entry */ > mrib-route4 0.0.0.0/0 { > nexthop: 10.30.0.1 > } > } > } Ok i will try this and keep you informed. > > > Sorry, I didn't know that you have a fancy setup like that so I > tried to keep the sample config file a bit simpler :) I know the setup is a bit complicate. But what we try also to do is to find a way to push multicast configuration to our users that are school, university and research center. If we are able to provide a good guideline to let hem have multicast passing a simple linux or freebsd firewall may be more of our users will do the step. And for me xorp is the best way to do it. > > echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter > To the best of my knowledge, the purpose of rp_filter is for Reverse > Path Filtering: if it is set to 1, then the host/router will ignore > packets if they don't arrive on the reverse-path interface. For a > better description see > http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.kernel.rpf.html > Long time ago a fellow who was playing with GRE tunnels and PIM-SM > told me that "echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter" is > needed if you run PIM-SM over tunnels, but myself I haven't played > yet with that particular option to verify whether it is really > mandatory. If you want to avoid any unexpected behavior, then it may > be simpler if you indeed set rp_filter to 0. Ok i admit that the best practice is to let the flags to 1. But when i had try pimd it was the only way for me to be able to forward multicast (i this time i don't really know why and probably due to an other issue). Any way our firewall is behind a firewall on juniper router where an anti spoofing rule is. The problem is that on juniper if you want a state full firewall you need a dedicated PIC for that like you need a dedicated PIC to be able to run RP. Thanks Philippe. -- __________________________________________________________________ Philippe Van Hecke - BELNET, The Belgian Research Network "In a world without walls or fences, who needs Windows and Gates?" __________________________________________________________________ From pavlin@icir.org Mon Jun 7 21:42:03 2004 From: pavlin@icir.org (Pavlin Radoslavov) Date: Mon, 07 Jun 2004 13:42:03 -0700 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: Message from Philippe Van Hecke of "Mon, 07 Jun 2004 22:28:13 +0200." <200406072228.16352.philippe.vanhecke@belnet.be> Message-ID: <200406072042.i57Kg3Kh011299@possum.icir.org> > > protocols { > > static { > > mrib-route4 10.10.0.0/16 { > > nexthop: 10.20.0.1 > > } > > > > /* The default entry */ > > mrib-route4 0.0.0.0/0 { > > nexthop: 10.30.0.1 > > } > > } > > } > Ok i will try this and keep you informed. Thanks! > > > > > > Sorry, I didn't know that you have a fancy setup like that so I > > tried to keep the sample config file a bit simpler :) > > I know the setup is a bit complicate. But what we try also to do is to find > a way to push multicast configuration to our users that are school, university > and research center. If we are able to provide a good guideline to let hem > have multicast passing a simple linux or freebsd firewall may be more of > our users will do the step. And for me xorp is the best way to do it. Unfortunately, right now there is no documentation how to configure multicast through xorpsh and the rtrmgr, but it will be included with the 1.0 release. > > > echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter > > > To the best of my knowledge, the purpose of rp_filter is for Reverse > > Path Filtering: if it is set to 1, then the host/router will ignore > > packets if they don't arrive on the reverse-path interface. For a > > better description see > > http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.kernel.rpf.html > > Long time ago a fellow who was playing with GRE tunnels and PIM-SM > > told me that "echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter" is > > needed if you run PIM-SM over tunnels, but myself I haven't played > > yet with that particular option to verify whether it is really > > mandatory. If you want to avoid any unexpected behavior, then it may > > be simpler if you indeed set rp_filter to 0. > > Ok i admit that the best practice is to let the flags to 1. But when i had try > pimd it was the only way for me to be able to forward multicast (i this time i > don't really know why and probably due to an other issue). Any way our > firewall is behind a firewall on juniper router where an anti spoofing rule > is. The problem is that on juniper if you want a state full firewall you need > a dedicated PIC for that like you need a dedicated PIC to be able to run RP. I will try to do some tests to determine whether setting the flag to 0 is mandatory or it can be set to 1, and I will reflect that in the configuration documentation. If you find something while testing it, please let me know. Thanks, Pavlin From lephiloux@skynet.be Mon Jun 7 20:41:23 2004 From: lephiloux@skynet.be (Philippe Van Hecke) Date: Mon, 7 Jun 2004 21:41:23 +0200 Subject: [Xorp-users] A sample config.boot for linux to test pim part of xorp. In-Reply-To: <200406071638.i57Gc3Kh009671@possum.icir.org> References: <200406071638.i57Gc3Kh009671@possum.icir.org> Message-ID: <200406072141.25628.lephiloux@skynet.be> Le Monday 07 June 2004 18:38, Pavlin Radoslavov a écrit : > Can you verify by running "netstat -rn" that the Juniper router is > indeed the next-hop router toward those source addresses. For, > example, if the next-hop router is connected to, say, eth0 which is > not enabled for multicast routing then this is one possible reason > for the warning. Also, if "netstat -rn" indeed shows that the > Juniper router is the next-hop router, then can you use the > "show pim mrib" xorpsh operational command to verify whether PIM-SM > itself has learned about that route. Finally, you may want to look > into the "show pim join" output to check the (S,G) multicast routing > state. Pavlin, My mistake, when i say that the next-hop 193.191.130.193 should be the juniper router i talk on the multicast point of view. So you right my default unicast route is through the eth0 as i want that unicast and multicast traffic travel through different interface. As i have say in previous post, the box acting as firewall. I want to disociate traffic on different interface because the firewall is on the same subnet as others BELNET server. And i doesn't want that multicast traffic pollute statistic of unicast traffic of the servers (we are not able to use IGMP snooping on the switch) So there is a possibility to have on linux, different table for unicast and multicast routing. What i mean here is there is a way to let multicast use other routing table to make RPF ? Does XORP permit this ? Also , i doen't know if this is the best way or if this is needed or if it is completely silly do make this. echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter Thanks a lot for your help. Philippe. __________________________________________________________________ Philippe Van Hecke - BELNET, The Belgian Research Network "In a world without walls or fences, who needs Windows and Gates?" __________________________________________________________________ From atanu@ICSI.Berkeley.EDU Tue Jun 15 23:48:34 2004 From: atanu@ICSI.Berkeley.EDU (Atanu Ghosh) Date: Tue, 15 Jun 2004 15:48:34 -0700 Subject: [Xorp-users] Announcing XORP Release Candidate 1.0 Message-ID: <98317.1087339714@tigger.icir.org> On behalf of the entire XORP team, I'm delighted to announce the XORP 1.0 Release Candidate, which is now available from . Once the release candidate has proven to be stable, the actual 1.0 release will be prepared. This is planned to occur in the next two weeks. In the intervening period we will be fixing minor problems and updating the documentation. The XORP router is now totally configurable through the XORP shell (xorpsh). A quick start guide is available from . Please note that a XORP Live CD is also available. This is a bootable CD that allows you to experiment with XORP without having to build or install it. There are still a number of non-critical bugs that we know about which will not be addressed until the 1.1 release; these are documented in the errata section below. In general, to test XORP, we run automated regression tests on a daily basis with various operating systems and compilers. We also run a number of PCs as XORP routers. We have enabled as many protocols as feasible on those routers to test protocol interactions (for example a BGP IPv6 multicast feed being used by PIM-SM). In addition, automated scripts are run to externally toggle BGP peerings. Finally, we have automated scripts that interact directly with the xorpsh to change the configuration settings. We have put significant effort into testing but obviously we have not found all the problems. This is where you can help us to make XORP more stable, by downloading and using it! As always we'd welcome your comments - xorp-users@xorp.org is the right place for general discussion, and private feedback to the XORP core team can be sent to feedback@xorp.org. - The XORP Team P.S. Release notes and errata are included below. ------------------------------------------------------------------ XORP RELEASE NOTES This file contains XORP release notes (most recent releases first). Release 1.0RC (2004/06/15) ========================= ALL: - All the routing processes can now be started and configured via the RTRMGR/XORPSH. LIBXORP: - Addition of support for safe callbacks (e.g., if an object is destroyed, all callbacks that refer to that object are invalidated). LIBXIPC: - Addition of support for event notification if the status of a target changes. LIBFEACLIENT: - Few bug fixes. XRL: - No significant changes. RTRMGR: - Addition of new command-line option "-v" to print verbose information. - Removal of command-line option "-d" that prints default information, because the same information is printed with the "-h" flag. - Addition of support for explicit configuration of the XRL target name of a module. - Addition of support for %help command in the rtrmgr template files. - Addition of support for new methods per module: "startup_method" and "shutdown_method". - Numerous other improvements and bug fixes. XORPSH: - Addition of new command-line option "-v" to print verbose information. - Removal of command-line option "-d" that prints default information, because the same information is printed with the "-h" flag. - Addition of support for help string in the xorpsh operational commands template files. - Addition of support for positional arguments in the xorpsh operational commands template files. - Addition of support to interrupt an operational command. Now if a command is interrupted from the command line by typing Ctrl-C, then the executed binary command itself (and its forked children, if any) is killed. - Numerous other improvements and bug fixes. FEA/MFEA: - Addition of support for propagating the Forwarding Information Base from the underlying system to clients interested in that information. - Addition of support for opening TCP or UDP sockets via the FEA. - Modification to the MFEA to use "libfeaclient" to obtain the interface information from the FEA. - Numerious bug fixes. RIB: - Addition of support for redistributing routes between two internal tables. - Addition of support for obtaining routes directly from some of the internal tables. - Modification to the RIB to use "libfeaclient" to obtain the interface information from the FEA. - Modification to the RIB to use the new RedistTable to propagate the final routes to the FEA and anyone else interested (e.g., PIM-SM). - Few bug fixes. RIP: - Packet forwarding and reception via FEA written for RIPv2 and RIPng. RIPv2 should be usable. BGP: - IPv6 has now been tested with peerings to the 6Bone; unicast and multicast SAFIs. - Route origination is now possible from BGP. - The memory leaks from the previous release have been found and fixed. STATIC_ROUTES: - This is a new module for configuring static routes to the unicast or multicast RIB. MLD/IGMP: - During startup, a primary address is selected per configured interface, and this primary address should be the link-local unicast address of that interface. - New CLI commands: "show igmp interface address" and "show mld interface address" - Resend some of the XRLs (e.g., those who do not carry soft-state such as protocol control messages) if there is an error. - Few bug fixes. PIM-SM: - Updated to support the lastest PIM-SM specification (draft-ietf-pim-sm-v2-new-09.{ps,txt}). - Addition of support for "alternative subnet" configuration such that non-local senders appear as senders connected to the same subnet. It is needed as a work-around solution when there are uni-directional interfaces for sending and receiving traffic (e.g., satellite links). - During startup, a primary address and a domain-wide address are selected per configured interface. The primary address should be the link-local unicast address of that interface, and the domain-wide address should be a domain-wide reachable unicast address. - Resend some of the XRLs (e.g., those who do not carry soft-state such as protocol control messages) if there is an error. - Several bug fixes. FIB2MRIB: - This is a new module for propagating the unicast forwarding information obtained from the underlying system via the FEA to the multicast RIB. CLI: - Addition of support to propagate command interruption (e.g., Ctrl-C) from the CLI to the object that handles the command processing by calling a pre-defined callback. - During startup, if the input is a terminal (e.g., xorpsh), then read the terminal size instead of using the default values. - A bug fix related to the CLI paging output: now it can handle properly lines that are longer than the width of the CLI output terminal. - Several other bug fixes. SNMP: - No significant changes. ------------------------------------------------------------------ XORP ERRATA ALL: - Parallel building (e.g., "gmake -j 4") may fail on multi-CPU machines. The simplest work-around is to rerun gmake or not to use the -j flag. - Overwriting the default installation prefix by running "./configure --prefix=/path/to/xorp" currently does not work. This will be fixed for XORP Release 1.0. - Some of the design documentation in ${XORP}/docs/ hasn't been updated for this release candidate. This will be fixed for XORP Release 1.0. LIBXORP: - No known issues. LIBXIPC: - No known issues. LIBFEACLIENT: - No known issues. XRL: - No known issues. RTRMGR: - There are several known issues, but none of them is considered critical. The list of known issues is available from http://www.xorp.org/bugzilla/query.cgi XORPSH: - A problem was noticed very late in the release process; rather than delay the release we have choosen to document the problem. The xorpsh provides the command line to the XORP router. The router configuration is structured as a tree, for instance configuring a new protocol essentially adds a new node to the tree. Removing a protocol involves deleting a node from the tree. In some cases deleting a node does not remove all the associated state; worse putting the same node back seems to fail in the majority of cases. FEA/MFEA: - On Linux, the following error message may appear during graceful shutdown (if PIM-SM is also running): [ 2004/06/09 14:50:40 ERROR xorp_fea:14359 MFEA +1676 mfea_mrouter.cc get_sg_count ] ioctl(SIOCGETSGCNT, (10.10.10.10 224.0.1.20)) failed: Bad file descriptor The error is harmless and can be ignored. RIB: - If an interface address is deleted, the RIB may trigger the following error in the FEA: [ 2004/06/07 16:08:57 ERROR xorp_fea:1605 FEA +259 fticonfig_entry_set_rtsock.cc delete_entry ] error writing to routing socket: No such process [ 2004/06/07 16:08:57 ERROR xorp_fea:1605 FEA +61 fti_transaction.cc operation_result ] FTI transaction commit failed on DeleteEntry4: net = 172.16.124.0/24 gateway = 0.0.0.0 ifname = vifname = metric = 0 admin_distance = 0 xorp_route = false is_deleted = false [ 2004/06/07 16:08:57 ERROR xorp_fea:1605 FEA +259 This error has no side effects, and can be ignored. - In some rare cases, the RIB may fail to delete an existing route (See http://www.xorp.org/bugzilla/show_bug.cgi?id=62). We are aware of the issue and will attempt to fix it in the near future. RIP: - No known issues. BGP: - Once BGP selects a route it is taking too long to install it in the kernel. - The RIB bug above where deleting an existing route can fail is sometimes triggered by BGP. When BGP receives the deletion failure error from the RIB it considers this to be a fatal error and exits. This problem will be fixed before the XORP 1.0 Release. STATIC_ROUTES: - If the FEA or RIB exit unexpected, then STATIC_ROUTES may start printing lots of error messages. MLD/IGMP: - If MLD/IGMP is started with a relatively large number of interfaces (e.g., on the order of 20), then it may fail with the following error: [ 2004/06/14 12:58:56 ERROR test_pim:16548 MFEA +666 mfea_proto_comm.cc join_multicast_group ] Cannot join group 224.0.0.2 on vif eth8: No buffer space available The solution is to increase the multicast group membership limit. E.g., to increase the value from 20 (the default) to 200, run as a root: echo 200 > /proc/sys/net/ipv4/igmp_max_memberships PIM-SM: - If the kernel does not support PIM-SM, or if PIM-SM is not enabled in the kernel, then running PIM-SM will fail with the following error message: [ 2004/06/12 10:26:41 ERROR xorp_fea:444 MFEA +529 mfea_mrouter.cc start_mrt ] setsockopt(MRT_INIT, 1) failed: Operation not supported FIB2MRIB: - If the FEA or RIB exit unexpected, then STATIC_ROUTES may start printing lots of error messages. CLI: - No known issues. SNMP: - net-snmp-5.1.* may have problems with some of its header files, hence the XORP SNMP support won't be compiled if those problems exist. Instead, use an earlier net-snmp version from the 5.0.x branch. ------------------------------------------------------------------