From pavlin@icir.org Tue Mar 1 17:48:31 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Tue, 01 Mar 2005 09:48:31 -0800 Subject: [Xorp-users] igmp In-Reply-To: Message from =?koi8-r?B?5M3J1NLJyiDi1drZy8nO?= of "Tue, 01 Mar 2005 18:01:47 +0300." <20050301150146.779C246A61@mail.comreg.ru> Message-ID: <200503011748.j21HmVqH032379@possum.icir.org> [Note: changed again the CC from xorp-users-admin to xorp-users] > I'm fix errors and copy xorp dump - nothing changes > > In what my mistake? See inlined comments. > boot.conf > > interfaces { > interface eth0 { > enabled: true > default-system-config > } > interface eth2 { > enabled: true > default-system-config > } > } > > fea { > enable-unicast-forwarding4: true > } > > protocols { > static { > mrib-route4 224.0.0.0/4 { > nexthop: 192.168.100.29 > metric: 1 > } > } The mrib-route4 routes in "static" are suppose to be used for unicast network prefixes only, hence the above statement is bogus (but probably harmless). E.g, if your RP address is 123.45.6.7, and if you have a statement like "mrib-route4 123.45.0.0/16", then the PIM-SM Join/Prune messages will be send on the reverse path (toward the RP) as defined by the "mrib-route4 123.45.0.0/16" entry. Typically, the mrib-route4 entries are used only if there are reasons for the unicast and multicast paths to be different. Otherwise, you could delete the above "static" statement. > > } > > > plumbing { > mfea4 { > enabled: true > interface eth0 { > vif eth0 { > enabled: true > } > } > interface eth2 { > vif eth2 { > enabled: true > } > } > > interface register_vif { > vif register_vif { > enabled: true > } > } > traceoptions { > flag all { > enabled: true > } > } > } > > } > > protocols { > igmp { > enabled: true > interface eth0 { > vif eth0 { > enabled: true > } > } > interface eth2 { > vif eth2 { > enabled: true > } > } > > traceoptions { > flag all { > enabled: true > } > } > } > } > > protocols { > pimsm4 { > enabled: true > interface eth0 { > vif eth0 { > enabled: true > } > } > interface eth2 { > vif eth2 { > enabled: true > } > } > > interface register_vif { > vif register_vif { > enabled: true > } > } > > static-rps { > rp 192.168.101.1 { > group-prefix 224.0.0.0/4 { > } > } > } > > bootstrap { > enabled: true > cand-bsr { > scope-zone 224.0.0.0/4 { > cand-bsr-by-vif-name: "eth0" > } > } > cand-rp { > group-prefix 224.0.0.0/4 { > cand-rp-by-vif-name: "eth0" > } > } > } With the above "static-rps" and "bootstrap" statements you have configured the local PIM-SM router as the Cand-RP practically on both eth0 and eth2. If you have only one PIM-SM router, probably it doesn't matter and should not have impact on the operation, but for clarity you may want to use only one of them. I'd recommend to use only the "static-rps" setup, unless you have more than one PIM-SM router and static RP configuration on all of them is not an option. Otherwise, if you use the "bootstrap" statement only, make sure that on startup you wait up to 2-3 minutes or so until the Bootstrap information converges. Only after that you could expect to see any multicast forwarding. > switch-to-spt-threshold { > enabled: true > interval-sec: 100 > bytes: 102400 > } > > traceoptions { > flag all { > enabled: true > } > } > } > > } > > protocols { > fib2mrib { > enabled: true > } > } > > > ----------------------- ifconfig > > eth0 Link encap:Ethernet HWaddr 00:11:2F:86:2A:CA > inet addr:192.168.100.29 Bcast:192.168.100.31 > Mask:255.255.255.224 > inet6 addr: fe80::211:2fff:fe86:2aca/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:85664 errors:0 dropped:0 overruns:0 frame:0 > TX packets:14137 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:83427206 (79.5 MiB) TX bytes:4341681 (4.1 MiB) > Interrupt:11 Memory:fbffc000-0 > > eth2 Link encap:Ethernet HWaddr 00:80:48:31:3D:78 > inet addr:192.168.101.1 Bcast:192.168.101.255 Mask:255.255.255.0 > inet6 addr: fe80::280:48ff:fe31:3d78/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:2334 (2.2 KiB) > Interrupt:3 Base address:0xd800 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:91070 errors:0 dropped:0 overruns:0 frame:0 > TX packets:91070 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:9113979 (8.6 MiB) TX bytes:9113979 (8.6 MiB) > > pimreg Link encap:UNSPEC HWaddr > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > UP RUNNING NOARP MTU:1472 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > ---------------------- > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 192.168.100.0 0.0.0.0 255.255.255.224 U 0 0 0 eth0 > 192.168.101.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 > 0.0.0.0 192.168.100.2 0.0.0.0 UG 0 0 0 eth0 > > --------------------------- > > [root@fedora bin]# > [root@fedora bin]# ./xorp_rtrmgr > [ 2005/03/01 17:49:03 INFO xorp_rtrmgr:5547 RTRMGR +134 master_conf_tree.cc > execute ] Changed modules: interfaces, fea, mfea4, rib, static_routes, > fib2mrib, igmp, pimsm4 > [ 2005/03/01 17:49:03 INFO xorp_rtrmgr:5547 RTRMGR +356 module_manager.cc > run ] Running module: interfaces (/usr/local/xorp/fea/xorp_fea) > [ 2005/03/01 17:49:05 INFO xorp_rtrmgr:5547 RTRMGR +356 module_manager.cc > run ] Running module: fea (/usr/local/xorp/fea/xorp_fea) > [ 2005/03/01 17:49:11 INFO xorp_rtrmgr:5547 RTRMGR +356 module_manager.cc > run ] Running module: mfea4 (/usr/local/xorp/fea/xorp_fea) > [ 2005/03/01 17:49:11 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: > >finder://MFEA_4/mfea/0.1/start_mfea< > [ 2005/03/01 17:49:11 INFO xorp_fea MFEA ] New vif: Vif[eth0] pif_index: 2 > vif_index: 0 addr: 192.168.100.29 subnet: 192.168.100.0/27 broadcast: > 192.168.100.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/01 17:49:11 INFO xorp_fea MFEA ] New vif: Vif[eth2] pif_index: 5 > vif_index: 1 addr: 192.168.101.1 subnet: 192.168.101.0/24 broadcast: > 192.168.101.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/01 17:49:12 INFO xorp_fea MFEA ] Enabled vif: eth0 > [ 2005/03/01 17:49:12 INFO xorp_fea MFEA ] Started vif: eth0 > [ 2005/03/01 17:49:12 INFO xorp_fea MFEA ] New vif: Vif[register_vif] > pif_index: 2 vif_index: 2 addr: 192.168.100.29 subnet: 192.168.100.29/32 > broadcast: 192.168.100.29 peer: 0.0.0.0 Flags: PIM_REGISTER > UNDERLYING_VIF_UP > [ 2005/03/01 17:49:12 INFO xorp_fea MFEA ] Enabled vif: eth2 > [ 2005/03/01 17:49:12 INFO xorp_fea MFEA ] Started vif: eth2 > [ 2005/03/01 17:49:12 INFO xorp_fea MFEA ] Enabled vif: register_vif > [ 2005/03/01 17:49:12 INFO xorp_fea MFEA ] Started vif: register_vif > [ 2005/03/01 17:49:12 TRACE xorp_fea MFEA ] RX kernel signal: message_type = > 1 vif_index = 0 src = 192.168.100.8 dst = 225.0.0.1 > [ 2005/03/01 17:49:12 INFO xorp_rtrmgr:5547 RTRMGR +356 module_manager.cc > run ] Running module: rib (/usr/local/xorp/rib/xorp_rib) > [ 2005/03/01 17:49:14 INFO xorp_rtrmgr:5547 RTRMGR +356 module_manager.cc > run ] Running module: static_routes > (/usr/local/xorp/static_routes/xorp_static_routes) > [ 2005/03/01 17:49:16 INFO xorp_rtrmgr:5547 RTRMGR +356 module_manager.cc > run ] Running module: fib2mrib (/usr/local/xorp/fib2mrib/xorp_fib2mrib) > [ 2005/03/01 17:49:18 INFO xorp_rtrmgr:5547 RTRMGR +356 module_manager.cc > run ] Running module: igmp (/usr/local/xorp/mld6igmp/xorp_igmp) > [ 2005/03/01 17:49:18 WARNING xorp_rtrmgr:5547 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. > [ 2005/03/01 17:49:19 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth0] > pif_index: 0 vif_index: 0 Flags: > [ 2005/03/01 17:49:19 INFO xorp_igmp MLD6IGMP ] Added new address to vif > eth0: addr: 192.168.100.29 subnet: 192.168.100.0/27 broadcast: > 192.168.100.31 peer: 0.0.0.0 > [ 2005/03/01 17:49:19 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[eth0] > pif_index: 0 vif_index: 0 addr: 192.168.100.29 subnet: 192.168.100.0/27 > broadcast: 192.168.100.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP > [ 2005/03/01 17:49:19 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth2] > pif_index: 0 vif_index: 1 Flags: > [ 2005/03/01 17:49:19 INFO xorp_igmp MLD6IGMP ] Added new address to vif > eth2: addr: 192.168.101.1 subnet: 192.168.101.0/24 broadcast: > 192.168.101.255 peer: 0.0.0.0 > [ 2005/03/01 17:49:19 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[eth2] > pif_index: 0 vif_index: 1 addr: 192.168.101.1 subnet: 192.168.101.0/24 > broadcast: 192.168.101.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP > [ 2005/03/01 17:49:19 INFO xorp_igmp MLD6IGMP ] New vif: Vif[register_vif] > pif_index: 0 vif_index: 2 Flags: > [ 2005/03/01 17:49:19 INFO xorp_igmp MLD6IGMP ] Added new address to vif > register_vif: addr: 192.168.100.29 subnet: 192.168.100.29/32 broadcast: > 192.168.100.29 peer: 0.0.0.0 > [ 2005/03/01 17:49:19 INFO xorp_igmp MLD6IGMP ] Vif flags changed: > Vif[register_vif] pif_index: 0 vif_index: 2 addr: 192.168.100.29 subnet: > 192.168.100.29/32 broadcast: 192.168.100.29 peer: 0.0.0.0 Flags: > PIM_REGISTER UNDERLYING_VIF_UP > [ 2005/03/01 17:49:20 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth0 > [ 2005/03/01 17:49:20 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth0] > pif_index: 0 vif_index: 0 addr: 192.168.100.29 subnet: 192.168.100.0/27 > broadcast: 192.168.100.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP UP IPv4 ENABLED > [ 2005/03/01 17:49:20 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 224.0.0.1 > [ 2005/03/01 17:49:20 INFO xorp_igmp MLD6IGMP ] Started vif: eth0 > [ 2005/03/01 17:49:20 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth2 > [ 2005/03/01 17:49:20 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth2] > pif_index: 0 vif_index: 1 addr: 192.168.101.1 subnet: 192.168.101.0/24 > broadcast: 192.168.101.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP UP IPv4 ENABLED > [ 2005/03/01 17:49:20 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.101.1 to 224.0.0.1 > [ 2005/03/01 17:49:20 INFO xorp_igmp MLD6IGMP ] Started vif: eth2 > [ 2005/03/01 17:49:20 INFO xorp_rtrmgr:5547 RTRMGR +356 module_manager.cc > run ] Running module: pimsm4 (/usr/local/xorp/pim/xorp_pimsm4) > [ 2005/03/01 17:49:20 WARNING xorp_rtrmgr:5547 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. > [ 2005/03/01 17:49:20 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 224.0.0.1 on vif eth0 > [ 2005/03/01 17:49:20 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.2 on vif eth0 > [ 2005/03/01 17:49:20 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.2 on vif eth2 > [ 2005/03/01 17:49:21 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.2 on vif eth2 > [ 2005/03/01 17:49:21 INFO xorp_pimsm4 PIM ] New vif: Vif[eth0] pif_index: 0 > vif_index: 0 addr: 192.168.100.29 subnet: 192.168.100.0/27 broadcast: > 192.168.100.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/01 17:49:21 INFO xorp_pimsm4 PIM ] New vif: Vif[eth2] pif_index: 0 > vif_index: 1 addr: 192.168.101.1 subnet: 192.168.101.0/24 broadcast: > 192.168.101.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/01 17:49:21 INFO xorp_pimsm4 PIM ] New vif: Vif[register_vif] > pif_index: 0 vif_index: 2 addr: 192.168.100.29 subnet: 192.168.100.29/32 > broadcast: 192.168.100.29 peer: 0.0.0.0 Flags: PIM_REGISTER > UNDERLYING_VIF_UP > [ 2005/03/01 17:49:22 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.8 to 239.255.255.250 on vif eth0 > [ 2005/03/01 17:49:22 TRACE xorp_fea MFEA ] RX kernel signal: message_type = > 1 vif_index = 0 src = 192.168.100.8 dst = 225.0.0.1 > [ 2005/03/01 17:49:22 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: > vif_index = 0 src = 192.168.100.8 dst = 225.0.0.1 > [ 2005/03/01 17:49:22 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.251 on vif eth0 > [ 2005/03/01 17:49:22 INFO xorp_pimsm4 PIM ] Enabled vif: eth0 > [ 2005/03/01 17:49:22 INFO xorp_pimsm4 PIM ] STARTING Vif[eth0] pif_index: 0 > vif_index: 0 addr: 192.168.100.29 subnet: 192.168.100.0/27 broadcast: > 192.168.100.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP > IPv4 ENABLED > [ 2005/03/01 17:49:22 INFO xorp_pimsm4 PIM ] Started vif: eth0 > [ 2005/03/01 17:49:22 INFO xorp_pimsm4 PIM ] Enabled vif: eth2 > [ 2005/03/01 17:49:22 INFO xorp_pimsm4 PIM ] STARTING Vif[eth2] pif_index: 0 > vif_index: 1 addr: 192.168.101.1 subnet: 192.168.101.0/24 broadcast: > 192.168.101.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > UP IPv4 ENABLED > [ 2005/03/01 17:49:22 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:49:22 INFO xorp_pimsm4 PIM ] Started vif: eth2 > [ 2005/03/01 17:49:22 INFO xorp_pimsm4 PIM ] Enabled vif: register_vif > [ 2005/03/01 17:49:22 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:49:22 INFO xorp_pimsm4 PIM ] STARTING Vif[register_vif] > pif_index: 0 vif_index: 2 addr: 192.168.100.29 subnet: 192.168.100.29/32 > broadcast: 192.168.100.29 peer: 0.0.0.0 Flags: PIM_REGISTER > UNDERLYING_VIF_UP UP IPv4 ENABLED > [ 2005/03/01 17:49:22 INFO xorp_pimsm4 PIM ] Started vif: register_vif > [ 2005/03/01 17:49:22 TRACE xorp_pimsm4 PIM ] Add membership for > (0.0.0.0,239.255.255.250) on vif eth0 > [ 2005/03/01 17:49:22 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP > for group 239.255.255.250: not found > [ 2005/03/01 17:49:22 INFO xorp_rtrmgr:5547 RTRMGR +1366 task.cc run_task ] > No more tasks to run > [ 2005/03/01 17:49:24 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:49:24 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.2 on vif eth2 > [ 2005/03/01 17:49:26 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:49:27 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:49:29 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:49:30 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.2 on vif eth0 > [ 2005/03/01 17:49:30 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.251 on vif eth2 > [ 2005/03/01 17:49:31 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:49:32 TRACE xorp_fea MFEA ] RX kernel signal: message_type = > 1 vif_index = 0 src = 192.168.100.8 dst = 225.0.0.1 > [ 2005/03/01 17:49:32 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: > vif_index = 0 src = 192.168.100.8 dst = 225.0.0.1 > [ 2005/03/01 17:49:32 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (192.168.100.8,225.0.0.1) iif = 0 olist = ... > [ 2005/03/01 17:49:33 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.2 on vif eth0 > [ 2005/03/01 17:49:37 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:49:51 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 224.0.0.1 > [ 2005/03/01 17:49:51 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 224.0.0.1 on vif eth0 > [ 2005/03/01 17:49:51 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.101.1 to 224.0.0.1 > [ 2005/03/01 17:49:51 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY > from 192.168.101.1 to 224.0.0.1 on vif eth2 > [ 2005/03/01 17:49:52 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.251 on vif eth0 > [ 2005/03/01 17:49:53 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:49:53 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.2 on vif eth0 > [ 2005/03/01 17:49:54 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.2 on vif eth2 > [ 2005/03/01 17:49:54 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:49:56 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.251 on vif eth2 > [ 2005/03/01 17:49:56 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:49:59 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.8 to 239.255.255.250 on vif eth0 > [ 2005/03/01 17:50:00 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:50:24 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:50:26 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:50:54 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:50:56 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:51:24 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:51:26 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:51:54 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:51:56 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:51:56 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 224.0.0.1 > [ 2005/03/01 17:51:56 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 224.0.0.1 on vif eth0 > [ 2005/03/01 17:51:56 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.101.1 to 224.0.0.1 > [ 2005/03/01 17:51:56 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY > from 192.168.101.1 to 224.0.0.1 on vif eth2 > [ 2005/03/01 17:51:57 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.251 on vif eth2 > [ 2005/03/01 17:51:57 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:52:00 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.8 to 239.255.255.250 on vif eth0 > [ 2005/03/01 17:52:03 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.251 on vif eth0 > [ 2005/03/01 17:52:04 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.2 on vif eth0 > [ 2005/03/01 17:52:04 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:52:05 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.2 on vif eth2 > [ 2005/03/01 17:52:09 TRACE xorp_fea MFEA ] RX kernel signal: message_type = > 1 vif_index = 1 src = 192.168.101.1 dst = 225.0.0.1 > [ 2005/03/01 17:52:09 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 225.0.0.1 on vif eth2 > [ 2005/03/01 17:52:09 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: > vif_index = 1 src = 192.168.101.1 dst = 225.0.0.1 > [ 2005/03/01 17:52:09 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (192.168.101.1,225.0.0.1) iif = 1 olist = ... > [ 2005/03/01 17:52:09 TRACE xorp_pimsm4 PIM ] Add membership for > (0.0.0.0,225.0.0.1) on vif eth2 > [ 2005/03/01 17:52:09 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (192.168.100.8,225.0.0.1) iif = 0 olist = .O. > [ 2005/03/01 17:52:11 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (192.168.100.8,225.0.0.1) iif = 0 olist = .O. The above log message indicates that PIM-SM correctly adds the Multicast Forwarding Cache entry for source 192.168.100.8 and group 225.0.0.1 : the incoming interface is eth0, and the outgoing interface is eth2 At this moment the "cat /proc/net/ip_mr_cache" command should show the corresponding entry in the kernel. If you have such entry in the kernel, then make sure that the multicast packets from the directly connected source 192.168.100.8 have TTL of at least 2 (otherwise the packets will be dropped because of the small TTL). > [ 2005/03/01 17:52:11 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (192.168.101.1,225.0.0.1) iif = 1 olist = ... > [ 2005/03/01 17:52:18 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 225.0.0.1 on vif eth2 > [ 2005/03/01 17:52:24 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:52:26 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:52:27 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 225.0.0.1 on vif eth2 > [ 2005/03/01 17:52:54 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:52:56 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:53:24 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:53:26 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:53:43 TRACE xorp_fea MFEA ] RX kernel signal: message_type = > 1 vif_index = 0 src = 192.168.100.29 dst = 225.0.0.1 > [ 2005/03/01 17:53:43 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 225.0.0.1 on vif eth0 > [ 2005/03/01 17:53:43 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: > vif_index = 0 src = 192.168.100.29 dst = 225.0.0.1 > [ 2005/03/01 17:53:43 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (192.168.100.29,225.0.0.1) iif = 0 olist = .O. Similar to my previous comment, at this moment you should have in the kernel a MFC entry for source 192.168.100.29 and 225.0.0.1. Again, make sure that this source also has a large enough TTL, and give it a try again. Regards, Pavlin > [ 2005/03/01 17:53:43 TRACE xorp_pimsm4 PIM ] Add membership for > (0.0.0.0,225.0.0.1) on vif eth0 > [ 2005/03/01 17:53:43 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (192.168.101.1,225.0.0.1) iif = 1 olist = O.. > [ 2005/03/01 17:53:43 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 225.0.0.1 on vif eth0 > [ 2005/03/01 17:53:50 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 225.0.0.1 on vif eth0 > [ 2005/03/01 17:53:54 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:53:56 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:54:01 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 224.0.0.1 > [ 2005/03/01 17:54:01 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.101.1 to 224.0.0.1 > [ 2005/03/01 17:54:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 224.0.0.1 on vif eth0 > [ 2005/03/01 17:54:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY > from 192.168.101.1 to 224.0.0.1 on vif eth2 > [ 2005/03/01 17:54:03 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.251 on vif eth0 > [ 2005/03/01 17:54:03 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:54:04 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.251 on vif eth2 > [ 2005/03/01 17:54:07 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:54:08 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 224.0.0.2 on vif eth0 > [ 2005/03/01 17:54:09 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 224.0.0.2 on vif eth2 > [ 2005/03/01 17:54:10 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.29 to 225.0.0.1 on vif eth0 > [ 2005/03/01 17:54:11 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.101.1 to 225.0.0.1 on vif eth2 > [ 2005/03/01 17:54:11 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.100.8 to 239.255.255.250 on vif eth0 > [ 2005/03/01 17:54:24 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:54:26 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:54:54 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:54:56 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:55:14 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from > 192.168.100.29 to 224.0.0.2 on vif eth0 > [ 2005/03/01 17:55:14 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 225.0.0.1 > [ 2005/03/01 17:55:14 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 225.0.0.1 on vif eth0 > [ 2005/03/01 17:55:15 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 225.0.0.1 > [ 2005/03/01 17:55:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 225.0.0.1 on vif eth0 > [ 2005/03/01 17:55:16 TRACE xorp_pimsm4 PIM ] Delete membership for > (0.0.0.0,225.0.0.1) on vif eth0 > [ 2005/03/01 17:55:16 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (192.168.101.1,225.0.0.1) iif = 1 olist = ... > [ 2005/03/01 17:55:24 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:55:26 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > > ------ > > [ 2005/03/01 17:57:18 INFO xorp_rtrmgr:5547 RTRMGR +568 task.cc shutdown ] > Shutting down module: pimsm4 > [ 2005/03/01 17:57:18 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:57:18 INFO xorp_pimsm4 PIM ] PENDING STOP Vif[eth0] > pif_index: 0 vif_index: 0 addr: 192.168.100.29 subnet: 192.168.100.0/27 > broadcast: 192.168.100.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP PENDING_DOWN IPv4 ENABLED > [ 2005/03/01 17:57:18 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:57:18 INFO xorp_pimsm4 PIM ] PENDING STOP Vif[eth2] > pif_index: 0 vif_index: 1 addr: 192.168.101.1 subnet: 192.168.101.0/24 > broadcast: 192.168.101.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP PENDING_DOWN IPv4 ENABLED > [ 2005/03/01 17:57:18 INFO xorp_pimsm4 PIM ] PENDING STOP Vif[register_vif] > pif_index: 0 vif_index: 2 addr: 192.168.100.29 subnet: 192.168.100.29/32 > broadcast: 192.168.100.29 peer: 0.0.0.0 Flags: PIM_REGISTER > UNDERLYING_VIF_UP PENDING_DOWN IPv4 ENABLED > [ 2005/03/01 17:57:18 INFO xorp_pimsm4 PIM ] STOPPED Vif[register_vif] > pif_index: 0 vif_index: 2 addr: 192.168.100.29 subnet: 192.168.100.29/32 > broadcast: 192.168.100.29 peer: 0.0.0.0 Flags: PIM_REGISTER > UNDERLYING_VIF_UP DOWN IPv4 ENABLED > [ 2005/03/01 17:57:18 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (192.168.100.8,225.0.0.1) iif = 0 olist = .O. > [ 2005/03/01 17:57:18 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (192.168.100.29,225.0.0.1) iif = 0 olist = .O. > [ 2005/03/01 17:57:18 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (192.168.101.1,225.0.0.1) iif = 1 olist = ... > [ 2005/03/01 17:57:18 TRACE xorp_pimsm4 PIM ] Delete MFC entry: > (192.168.100.8,225.0.0.1) iif = 0 olist = .O. > [ 2005/03/01 17:57:18 TRACE xorp_pimsm4 PIM ] Delete MFC entry: > (192.168.100.29,225.0.0.1) iif = 0 olist = .O. > [ 2005/03/01 17:57:18 TRACE xorp_pimsm4 PIM ] Delete MFC entry: > (192.168.101.1,225.0.0.1) iif = 1 olist = ... > [ 2005/03/01 17:57:18 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.100.29 to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:57:18 INFO xorp_pimsm4 PIM ] STOPPED Vif[eth0] pif_index: 0 > vif_index: 0 addr: 192.168.100.29 subnet: 192.168.100.0/27 broadcast: > 192.168.100.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > DOWN IPv4 ENABLED > [ 2005/03/01 17:57:18 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.101.1 to 224.0.0.13 on vif eth2 > [ 2005/03/01 17:57:18 INFO xorp_pimsm4 PIM ] STOPPED Vif[eth2] pif_index: 0 > vif_index: 1 addr: 192.168.101.1 subnet: 192.168.101.0/24 broadcast: > 192.168.101.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > DOWN IPv4 ENABLED > [ 2005/03/01 17:57:18 WARNING xorp_fea XrlMfeaTarget ] Handling method for > mfea/0.1/send_protocol_message4 failed: XrlCmdError 102 Command failed > Cannot send PIMSM_4 protocol message from 192.168.100.29 to 224.0.0.13 on > vif eth0 > [ 2005/03/01 17:57:18 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from > 192.168.101.1 to 224.0.0.2 on vif eth2 > [ 2005/03/01 17:57:18 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.101.1 to 224.0.0.13 > [ 2005/03/01 17:57:18 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from > 192.168.100.29 to 224.0.0.2 on vif eth0 > [ 2005/03/01 17:57:18 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.100.29 to 224.0.0.13 > [ 2005/03/01 17:57:18 WARNING xorp_fea XrlMfeaTarget ] Handling method for > mfea/0.1/send_protocol_message4 failed: XrlCmdError 102 Command failed > Cannot send PIMSM_4 protocol message from 192.168.101.1 to 224.0.0.13 on vif > eth2 > [ 2005/03/01 17:57:18 ERROR xorp_pimsm4:5641 PIM +1746 xrl_pim_node.cc > mfea_client_send_protocol_message_cb ] Failed to send a protocol message: > 102 Command failed Cannot send PIMSM_4 protocol message from 192.168.100.29 > to 224.0.0.13 on vif eth0 > [ 2005/03/01 17:57:18 INFO xorp_pimsm4 PIM ] Deleted vif: eth0 > [ 2005/03/01 17:57:18 INFO xorp_pimsm4 PIM ] Deleted vif: eth2 > [ 2005/03/01 17:57:18 INFO xorp_pimsm4 PIM ] Deleted vif: register_vif > [ 2005/03/01 17:57:18 INFO xorp_rtrmgr:5547 RTRMGR +502 module_manager.cc > killed ] Module abnormally killed: pimsm4 > [ 2005/03/01 17:57:19 INFO xorp_rtrmgr:5547 RTRMGR +568 task.cc shutdown ] > Shutting down module: igmp > [ 2005/03/01 17:57:19 INFO xorp_igmp MLD6IGMP ] STOPPED Vif[eth0] pif_index: > 0 vif_index: 0 addr: 192.168.100.29 subnet: 192.168.100.0/27 broadcast: > 192.168.100.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > DOWN IPv4 ENABLED > [ 2005/03/01 17:57:19 INFO xorp_igmp MLD6IGMP ] STOPPED Vif[eth2] pif_index: > 0 vif_index: 1 addr: 192.168.101.1 subnet: 192.168.101.0/24 broadcast: > 192.168.101.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > DOWN IPv4 ENABLED > [ 2005/03/01 17:57:19 WARNING xorp_rtrmgr:5547 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. > [ 2005/03/01 17:57:19 INFO xorp_igmp MLD6IGMP ] Deleted vif: eth0 > [ 2005/03/01 17:57:19 INFO xorp_igmp MLD6IGMP ] Deleted vif: eth2 > [ 2005/03/01 17:57:19 INFO xorp_igmp MLD6IGMP ] Deleted vif: register_vif > [ 2005/03/01 17:57:19 INFO xorp_rtrmgr:5547 RTRMGR +476 module_manager.cc > normal_exit ] Module normal exit: igmp > [ 2005/03/01 17:57:20 WARNING xorp_rtrmgr:5547 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. > [ 2005/03/01 17:57:21 INFO xorp_rtrmgr:5547 RTRMGR +568 task.cc shutdown ] > Shutting down module: fib2mrib > [ 2005/03/01 17:57:21 INFO xorp_rtrmgr:5547 RTRMGR +476 module_manager.cc > normal_exit ] Module normal exit: fib2mrib > [ 2005/03/01 17:57:22 WARNING xorp_rtrmgr:5547 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. > [ 2005/03/01 17:57:23 INFO xorp_rtrmgr:5547 RTRMGR +568 task.cc shutdown ] > Shutting down module: static_routes > [ 2005/03/01 17:57:23 ERROR xorp_rib:5551 RIB +1163 rib.cc > delete_origin_table ] Got delete_origin_table for wrong target name > [ 2005/03/01 17:57:23 WARNING xorp_rib XrlRibTarget ] Handling method for > rib/0.1/delete_igp_table4 failed: XrlCmdError 102 Command failed Could not > delete unicast IPv4 igp table "static" > [ 2005/03/01 17:57:23 ERROR xorp_static_routes:5552 STATIC_ROUTES +307 > xrl_static_routes_node.cc rib_client_send_delete_igp_table4_cb ] Failed to > deregister IPv4 IGP table with the RIB: 102 Command failed Could not delete > unicast IPv4 igp table "static". Will give up. > [ 2005/03/01 17:57:23 INFO xorp_rtrmgr:5547 RTRMGR +476 module_manager.cc > normal_exit ] Module normal exit: static_routes > [ 2005/03/01 17:57:24 WARNING xorp_rtrmgr:5547 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 > "static_routes" does not exist or is not enabled. > [ 2005/03/01 17:57:25 INFO xorp_rtrmgr:5547 RTRMGR +568 task.cc shutdown ] > Shutting down module: rib > [ 2005/03/01 17:57:25 INFO xorp_rtrmgr:5547 RTRMGR +476 module_manager.cc > normal_exit ] Module normal exit: rib > [ 2005/03/01 17:57:25 INFO xorp_rtrmgr:5547 XRL +330 xrl_router.cc > send_resolved ] Sender died (protocol = "stcp", address = "127.0.0.1:33354") > [ 2005/03/01 17:57:25 ERROR xorp_rtrmgr:5547 IPC +270 sockutil.cc > create_connected_ip_socket ] failed to connect to 127.0.0.1 port 33354: > Connection refused > [ 2005/03/01 17:57:25 ERROR xorp_rtrmgr:5547 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:33354 > > [ 2005/03/01 17:57:25 ERROR xorp_rtrmgr:5547 XRL +341 xrl_router.cc > send_resolved ] Could not create XrlPFSender for protocol = "stcp" address = > "127.0.0.1:33354" > [ 2005/03/01 17:57:25 WARNING xorp_rtrmgr:5547 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 "rib" > does not exist or is not enabled. > [ 2005/03/01 17:57:26 INFO xorp_rtrmgr:5547 RTRMGR +568 task.cc shutdown ] > Shutting down module: mfea4 > [ 2005/03/01 17:57:26 INFO xorp_fea MFEA ] STOPPED Vif[eth0] pif_index: 2 > vif_index: 0 addr: 192.168.100.29 subnet: 192.168.100.0/27 broadcast: > 192.168.100.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > DOWN IPv4 ENABLED > [ 2005/03/01 17:57:26 INFO xorp_fea MFEA ] STOPPED Vif[eth2] pif_index: 5 > vif_index: 1 addr: 192.168.101.1 subnet: 192.168.101.0/24 broadcast: > 192.168.101.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > DOWN IPv4 ENABLED > [ 2005/03/01 17:57:26 INFO xorp_fea MFEA ] STOPPED Vif[register_vif] > pif_index: 2 vif_index: 2 addr: 192.168.100.29 subnet: 192.168.100.29/32 > broadcast: 192.168.100.29 peer: 0.0.0.0 Flags: PIM_REGISTER > UNDERLYING_VIF_UP DOWN IPv4 ENABLED > [ 2005/03/01 17:57:28 INFO xorp_rtrmgr:5547 RTRMGR +166 module_manager.cc > terminate ] Terminating module: mfea4 > [ 2005/03/01 17:57:31 INFO xorp_rtrmgr:5547 RTRMGR +166 module_manager.cc > terminate ] Terminating module: fea > [ 2005/03/01 17:57:31 INFO xorp_rtrmgr:5547 RTRMGR +568 task.cc shutdown ] > Shutting down module: interfaces > [ 2005/03/01 17:57:31 INFO xorp_fea MFEA ] Deleted vif: eth0 > [ 2005/03/01 17:57:31 INFO xorp_fea MFEA ] Deleted vif: eth2 > [ 2005/03/01 17:57:31 INFO xorp_fea MFEA ] Deleted vif: register_vif > [ 2005/03/01 17:57:31 INFO xorp_rtrmgr:5547 RTRMGR +476 module_manager.cc > normal_exit ] Module normal exit: interfaces > [ 2005/03/01 17:57:32 INFO xorp_rtrmgr:5547 RTRMGR +1366 task.cc run_task ] > No more tasks to run > From felix.engel@beanpower.de Tue Mar 8 14:20:39 2005 From: felix.engel@beanpower.de (Felix Engel) Date: Tue, 8 Mar 2005 15:20:39 +0100 Subject: [Xorp-users] multicast problem Message-ID: <200503081520.39299.felix.engel@beanpower.de> hi, i am trying to get multicast working. it is an easy setup with only two network interfaces under gentoo linux. my application is vlc (with ttl > 1). i use the bootstrap method for the rp. the "show pim join" command shows the sender and the reciever. but "show pim mfc" shows not the needed outgoing interface i think. does anybody konw what is wrong? i have read most of the mailing-list-archive an tried all configurations that seems possible to me. but i did not get the poin. thanks a lot. felix my configuration: /* deklarieren der vorhandenen netzwerkkarten und uebernahme der parameter aus dem system */ interfaces { interface eth0 { default-system-config } interface eth1 { default-system-config } } /* ip4 forwarding aktivieren */ fea { enable-unicast-forwarding4: true } plumbing { /*ip4 multicast forwarding fuer die beiden netzwerkkarten aktivieren mittels*/ mfea4 { interface eth0 { vif eth0 { enabled: true } } interface eth1 { vif eth1 { enabled: true } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { /* statische unicast routen festlegen */ static { route4 55.66.77.1/24 { nexthop: 20.40.60.1 metric: 1 } route4 20.40.60.1/24 { nexthop: 55.66.77.1 metric: 1 } } } protocols { /* igmp fuer die netzwerkinterfaces aktivieren */ igmp { interface eth0 { vif eth0 { enabled: true } } interface eth1 { vif eth1 { enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { /* ip4 multicast-protokol pim-sm aktivieren */ pimsm4 { interface eth0 { vif eth0 { enabled: true } } interface eth1 { vif eth1 { enabled: true } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ enabled: true } } /* alternativ automatische rp's mittels bootstrap */ bootstrap { cand-bsr { scope-zone 224.0.0.0/4 { cand-bsr-by-vif-name: "eth0" bsr-priority: 1 } } cand-rp { group-prefix 224.0.0.0/4 { cand-rp-by-vif-name: "eth0" rp-priority: 192 rp-holdtime: 150 } } } switch-to-spt-threshold { enabled: true interval-sec: 100 bytes: 102400 } traceoptions { flag all { enabled: true } } } } /* liest die schon im system gesetzten routen in die xorp configuration ein */ protocols { fib2mrib { enabled: true } } ---------------------------------------------------- show pim join 224.0.1.10 0.0.0.0 20.40.60.1 WC Upstream interface (RP): register_vif Upstream MRIB next hop (RP): UNKNOWN Upstream RPF'(*,G): UNKNOWN Upstream state: Joined Join timer: 31 Local receiver include WC: O.. Joins RP: ... Joins WC: ... Join state: ... Prune state: ... Prune pending state: ... I am assert winner state: ... I am assert loser state: ... Assert winner WC: ... Assert lost WC: ... Assert tracking WC: O.O Could assert WC: O.. I am DR: OOO Immediate olist RP: ... Immediate olist WC: O.. Inherited olist SG: O.. Inherited olist SG_RPT: O.. PIM include WC: O.. 239.255.255.250 0.0.0.0 20.40.60.1 WC Upstream interface (RP): register_vif Upstream MRIB next hop (RP): UNKNOWN Upstream RPF'(*,G): UNKNOWN Upstream state: Joined Join timer: 46 Local receiver include WC: OO. Joins RP: ... Joins WC: ... Join state: ... Prune state: ... Prune pending state: ... I am assert winner state: ... I am assert loser state: ... Assert winner WC: ... Assert lost WC: ... Assert tracking WC: OOO Could assert WC: OO. I am DR: OOO Immediate olist RP: ... Immediate olist WC: OO. Inherited olist SG: OO. Inherited olist SG_RPT: OO. PIM include WC: OO. 224.0.1.10 55.66.77.2 20.40.60.1 SG SPT DirectlyConnectedS Upstream interface (S): eth1 Upstream interface (RP): register_vif Upstream MRIB next hop (RP): UNKNOWN Upstream MRIB next hop (S): UNKNOWN Upstream RPF'(S,G): UNKNOWN Upstream state: Joined Register state: RegisterNoinfo RegisterNotCouldRegister Join timer: 31 Local receiver include WC: O.. Local receiver include SG: ... Local receiver exclude SG: ... Joins RP: ... Joins WC: ... Joins SG: ... Join state: ... Prune state: ... Prune pending state: ... I am assert winner state: ... I am assert loser state: ... Assert winner WC: ... Assert winner SG: ... Assert lost WC: ... Assert lost SG: ... Assert lost SG_RPT: ... Assert tracking SG: OO. Could assert WC: O.. Could assert SG: O.. I am DR: OOO Immediate olist RP: ... Immediate olist WC: O.. Immediate olist SG: ... Inherited olist SG: O.. Inherited olist SG_RPT: O.. PIM include WC: O.. PIM include SG: ... PIM exclude SG: ... ----------------------------------------- Xorp> show pim rps RP Type Pri Holdtime Timeout ActiveGroups GroupPrefix 20.40.60.1 bootstrap 192 150 -1 2 224.0.0.0/4 ----------------------------------------- Xorp> show pim mfc 224.0.1.10 55.66.77.2 20.40.60.1 Incoming interface : eth1 Outgoing interfaces: O.. ----------------------------------------- cat /proc/net/ip_mr_cache Group Origin Iif Pkts Bytes Wrong Oifs 0A0100E0 024D4237 1 94007 126345408 0 0:1 ----------------------------------------- log: /usr/local/xorp/bin/xorp_rtrmgr [ 2005/03/08 15:03:44 INFO xorp_rtrmgr:8190 RTRMGR +134 master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, rib, static_routes, igmp, pimsm4 [ 2005/03/08 15:03:44 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc run ] Running module: interfaces (/usr/local/xorp/fea/xorp_fea) [ 2005/03/08 15:03:46 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc run ] Running module: fea (/usr/local/xorp/fea/xorp_fea) [ 2005/03/08 15:03:52 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc run ] Running module: mfea4 (/usr/local/xorp/fea/xorp_fea) [ 2005/03/08 15:03:52 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: >finder://MFEA_4/mfea/0.1/start_mfea< [ 2005/03/08 15:03:52 INFO xorp_fea MFEA ] New vif: Vif[eth0] pif_index: 1 vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: 192.168.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/08 15:03:52 INFO xorp_fea MFEA ] New vif: Vif[eth1] pif_index: 3 vif_index: 1 addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: 55.66.77.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Enabled vif: eth0 [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Started vif: eth0 [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] New vif: Vif[register_vif] pif_index: 1 vif_index: 2 addr: 20.40.60.1 subnet: 20.40.60.1/32 broadcast: 20.40.60.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Enabled vif: eth1 [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Started vif: eth1 [ 2005/03/08 15:03:53 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 55.66.77.2 dst = 224.0.1.10 [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Enabled vif: register_vif [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Started vif: register_vif [ 2005/03/08 15:03:53 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc run ] Running module: rib (/usr/local/xorp/rib/xorp_rib) [ 2005/03/08 15:03:55 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc run ] Running module: static_routes (/usr/local/xorp/static_routes/xorp_static_routes) [ 2005/03/08 15:03:57 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc run ] Running module: igmp (/usr/local/xorp/mld6igmp/xorp_igmp) [ 2005/03/08 15:03:57 WARNING xorp_rtrmgr:8190 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. [ 2005/03/08 15:03:58 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: >finder://IGMP/mld6igmp/0.1/start_mld6igmp< [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth0] pif_index: 0 vif_index: 0 Flags: [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Added new address to vif eth0: addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: 192.168.1.255 peer: 0.0.0.0 [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[eth0] pif_index: 0 vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: 192.168.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth1] pif_index: 0 vif_index: 1 Flags: [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Added new address to vif eth1: addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: 55.66.77.255 peer: 0.0.0.0 [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[eth1] pif_index: 0 vif_index: 1 addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: 55.66.77.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] New vif: Vif[register_vif] pif_index: 0 vif_index: 2 Flags: [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Added new address to vif register_vif: addr: 20.40.60.1 subnet: 20.40.60.1/32 broadcast: 20.40.60.1 peer: 0.0.0.0 [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[register_vif] pif_index: 0 vif_index: 2 addr: 20.40.60.1 subnet: 20.40.60.1/32 broadcast: 20.40.60.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth0 [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth0] pif_index: 0 vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: 192.168.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.0.1 [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] Started vif: eth0 [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth1 [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth1] pif_index: 0 vif_index: 1 addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: 55.66.77.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 55.66.77.1 to 224.0.0.1 [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] Started vif: eth1 [ 2005/03/08 15:03:59 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc run ] Running module: pimsm4 (/usr/local/xorp/pim/xorp_pimsm4) [ 2005/03/08 15:03:59 WARNING xorp_rtrmgr:8190 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. [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.0.1 on vif eth0 [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 55.66.77.1 to 224.0.0.1 on vif eth1 [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.2 on vif eth0 [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.2 on vif eth1 [ 2005/03/08 15:04:00 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.2 to 239.255.255.250 on vif eth0 [ 2005/03/08 15:04:00 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: >finder://PIMSM_4/pim/0.1/start_pim< [ 2005/03/08 15:04:00 INFO xorp_pimsm4 PIM ] New vif: Vif[eth0] pif_index: 0 vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: 192.168.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/08 15:04:00 INFO xorp_pimsm4 PIM ] New vif: Vif[eth1] pif_index: 0 vif_index: 1 addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: 55.66.77.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/08 15:04:00 INFO xorp_pimsm4 PIM ] New vif: Vif[register_vif] pif_index: 0 vif_index: 2 addr: 20.40.60.1 subnet: 20.40.60.1/32 broadcast: 20.40.60.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Enabled vif: eth0 [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] STARTING Vif[eth0] pif_index: 0 vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: 192.168.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Started vif: eth0 [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Enabled vif: eth1 [ 2005/03/08 15:04:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.2 on vif eth0 [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] STARTING Vif[eth1] pif_index: 0 vif_index: 1 addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: 55.66.77.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Started vif: eth1 [ 2005/03/08 15:04:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Enabled vif: register_vif [ 2005/03/08 15:04:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] STARTING Vif[register_vif] pif_index: 0 vif_index: 2 addr: 20.40.60.1 subnet: 20.40.60.1/32 broadcast: 20.40.60.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Started vif: register_vif [ 2005/03/08 15:04:01 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,239.255.255.250) on vif eth0 [ 2005/03/08 15:04:01 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 239.255.255.250: not found [ 2005/03/08 15:04:01 INFO xorp_rtrmgr:8190 RTRMGR +1366 task.cc run_task ] No more tasks to run [ 2005/03/08 15:04:02 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.2 on vif eth1 [ 2005/03/08 15:04:02 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:04:03 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 1 src = 55.66.77.2 dst = 224.0.1.10 [ 2005/03/08 15:04:03 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 1 src = 55.66.77.2 dst = 224.0.1.10 [ 2005/03/08 15:04:03 TRACE xorp_pimsm4 PIM ] Add MFC entry: (55.66.77.2,224.0.1.10) iif = 1 olist = ..O [ 2005/03/08 15:04:03 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:04:04 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.2 on vif eth0 [ 2005/03/08 15:04:05 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:04:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:04:06 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.2 to 224.0.1.10 on vif eth0 [ 2005/03/08 15:04:06 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,224.0.1.10) on vif eth0 [ 2005/03/08 15:04:06 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 224.0.1.10: not found [ 2005/03/08 15:04:06 TRACE xorp_pimsm4 PIM ] Add MFC entry: (55.66.77.2,224.0.1.10) iif = 1 olist = O.O [ 2005/03/08 15:04:08 WARNING xorp_fea MFEA ] proto_socket_read() failed: RX packet from 192.168.1.1 to 239.255.255.250: no vif found [ 2005/03/08 15:04:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.2 on vif eth1 [ 2005/03/08 15:04:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:04:11 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:04:30 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.0.1 [ 2005/03/08 15:04:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.0.1 on vif eth0 [ 2005/03/08 15:04:30 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 55.66.77.1 to 224.0.0.1 [ 2005/03/08 15:04:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 55.66.77.1 to 224.0.0.1 on vif eth1 [ 2005/03/08 15:04:31 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.2 to 239.255.255.250 on vif eth0 [ 2005/03/08 15:04:33 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.2 to 224.0.1.10 on vif eth0 [ 2005/03/08 15:04:33 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:04:35 WARNING xorp_fea MFEA ] proto_socket_read() failed: RX packet from 192.168.1.1 to 239.255.255.250: no vif found [ 2005/03/08 15:04:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:04:36 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:04:37 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.2 on vif eth1 [ 2005/03/08 15:04:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:04:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.2 on vif eth0 [ 2005/03/08 15:05:01 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 239.255.255.250: not found [ 2005/03/08 15:05:03 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:05:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:05:06 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 224.0.1.10: not found [ 2005/03/08 15:05:33 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:05:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:06:01 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 239.255.255.250: not found [ 2005/03/08 15:06:03 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:06:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:06:06 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 224.0.1.10: not found [ 2005/03/08 15:06:33 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:06:35 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.0.1 [ 2005/03/08 15:06:35 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.0.1 on vif eth0 [ 2005/03/08 15:06:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:06:35 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 55.66.77.1 to 224.0.0.1 [ 2005/03/08 15:06:35 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 55.66.77.1 to 224.0.0.1 on vif eth1 [ 2005/03/08 15:06:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.2 to 239.255.255.250 on vif eth0 [ 2005/03/08 15:06:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.2 to 239.255.255.250 on vif eth1 [ 2005/03/08 15:06:40 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,239.255.255.250) on vif eth1 [ 2005/03/08 15:06:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:06:42 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.2 on vif eth0 [ 2005/03/08 15:06:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:06:44 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.2 to 224.0.1.10 on vif eth0 [ 2005/03/08 15:06:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.2 on vif eth1 [ 2005/03/08 15:06:50 TRACE xorp_pimsm4 PIM ] Add MFC entry: (55.66.77.2,224.0.1.10) iif = 1 olist = O.O [ 2005/03/08 15:06:50 TRACE xorp_pimsm4 PIM ] Add MFC entry: (55.66.77.2,224.0.1.10) iif = 1 olist = O.. [ 2005/03/08 15:07:03 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:07:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:07:33 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:07:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:07:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 20.40.60.2 to 224.0.0.2 on vif eth0 [ 2005/03/08 15:07:43 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.1.10 [ 2005/03/08 15:07:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.1.10 on vif eth0 [ 2005/03/08 15:07:44 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.1.10 [ 2005/03/08 15:07:44 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.1.10 on vif eth0 [ 2005/03/08 15:07:45 TRACE xorp_pimsm4 PIM ] Delete membership for (0.0.0.0,224.0.1.10) on vif eth0 [ 2005/03/08 15:07:45 TRACE xorp_pimsm4 PIM ] Add MFC entry: (55.66.77.2,224.0.1.10) iif = 1 olist = ... [ 2005/03/08 15:07:47 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.2 to 224.0.1.10 on vif eth0 [ 2005/03/08 15:07:47 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,224.0.1.10) on vif eth0 [ 2005/03/08 15:07:47 TRACE xorp_pimsm4 PIM ] Add MFC entry: (55.66.77.2,224.0.1.10) iif = 1 olist = O.. [ 2005/03/08 15:07:48 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.2 to 224.0.1.10 on vif eth0 [ 2005/03/08 15:07:49 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.2 to 224.0.1.10 on vif eth0 [ 2005/03/08 15:08:03 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:08:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:08:33 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:08:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:08:40 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.0.1 [ 2005/03/08 15:08:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 20.40.60.1 to 224.0.0.1 on vif eth0 [ 2005/03/08 15:08:40 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 55.66.77.1 to 224.0.0.1 [ 2005/03/08 15:08:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 55.66.77.1 to 224.0.0.1 on vif eth1 [ 2005/03/08 15:08:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.2 on vif eth0 [ 2005/03/08 15:08:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.2 to 239.255.255.250 on vif eth1 [ 2005/03/08 15:08:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.13 on vif eth1 [ 2005/03/08 15:08:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.2 to 239.255.255.250 on vif eth0 [ 2005/03/08 15:08:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.1 to 224.0.0.13 on vif eth0 [ 2005/03/08 15:08:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 20.40.60.2 to 224.0.1.10 on vif eth0 [ 2005/03/08 15:08:49 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 55.66.77.1 to 224.0.0.2 on vif eth1 From pavlin@icir.org Tue Mar 8 16:16:22 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Tue, 08 Mar 2005 08:16:22 -0800 Subject: [Xorp-users] multicast problem In-Reply-To: Message from Felix Engel of "Tue, 08 Mar 2005 15:20:39 +0100." <200503081520.39299.felix.engel@beanpower.de> Message-ID: <200503081616.j28GGMxR025061@possum.icir.org> > i am trying to get multicast working. it is an easy setup with only two > network interfaces under gentoo linux. my application is vlc (with ttl > 1). > i use the bootstrap method for the rp. the "show pim join" command shows the > sender and the reciever. but "show pim mfc" shows not the needed outgoing > interface i think. does anybody konw what is wrong? i have read most of the The info below shows that for source 55.66.77.2 and group 224.0.1.10 the eth1 is the incoming interface, and eth0 is the outgoing interface. This seems right to me, given that your router is the RP, the sender is directly connected to eth1, and the receiver is on eth0. Why do you think the oif set is wrong? Also, did the receiver get the multicast traffic? > mailing-list-archive an tried all configurations that seems possible to me. > but i did not get the poin. BTW, there are two things in your configuration that you may want to fix. First, in your static routes configuration you have what seems like a cyclic dependency. The nexthop for the first route matches into the second route, and the nexthop for the second route matches into the first route: > route4 55.66.77.1/24 { > nexthop: 20.40.60.1 > metric: 1 > } > route4 20.40.60.1/24 { > nexthop: 55.66.77.1 > metric: 1 > } Given that both routes are actually the directly-connected subnets, you don't need them in your static routes configuration, so you can delete them. Second, the IP interface configuration for eth0 shows a mismatch between the IP address and the broadcast address: > [ 2005/03/08 15:03:52 INFO xorp_fea MFEA ] New vif: Vif[eth0] pif_index: 1 > vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: 192.168.1.255 > peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP Even though such assignment is legal, for practical purposes the broadcast address should be 20.40.60.255 (unless you have good reasons that the broadcast address should really be 192.168.1.255). Regards, Pavlin > > thanks a lot. > felix > > my configuration: > /* deklarieren der vorhandenen netzwerkkarten und uebernahme der parameter > aus dem system */ > interfaces { > interface eth0 { > default-system-config > } > interface eth1 { > default-system-config > } > } > /* ip4 forwarding aktivieren */ > fea { > enable-unicast-forwarding4: true > } > > plumbing { > /*ip4 multicast forwarding fuer die beiden netzwerkkarten aktivieren > mittels*/ > mfea4 { > interface eth0 { > vif eth0 { > enabled: true > } > } > interface eth1 { > vif eth1 { > enabled: true > } > } > > interface register_vif { > vif register_vif { > /* Note: this vif should be always enabled */ > enabled: true > } > } > traceoptions { > flag all { > enabled: true > } > } > > } > } > > > > protocols { > /* statische unicast routen festlegen */ > static { > > route4 55.66.77.1/24 { > nexthop: 20.40.60.1 > metric: 1 > } > route4 20.40.60.1/24 { > nexthop: 55.66.77.1 > metric: 1 > } > > } > } > > > protocols { > /* igmp fuer die netzwerkinterfaces aktivieren */ > igmp { > interface eth0 { > vif eth0 { > enabled: true > } > } > interface eth1 { > vif eth1 { > enabled: true > } > } > > traceoptions { > flag all { > enabled: true > } > } > } > } > > protocols { > /* ip4 multicast-protokol pim-sm aktivieren */ > pimsm4 { > interface eth0 { > vif eth0 { > enabled: true > } > } > interface eth1 { > vif eth1 { > enabled: true > } > } > > interface register_vif { > vif register_vif { > /* Note: this vif should be always enabled */ > enabled: true > } > } > > /* alternativ automatische rp's mittels bootstrap */ > > > bootstrap { > cand-bsr { > scope-zone 224.0.0.0/4 { > cand-bsr-by-vif-name: "eth0" > bsr-priority: 1 > } > } > > cand-rp { > group-prefix 224.0.0.0/4 { > cand-rp-by-vif-name: "eth0" > rp-priority: 192 > rp-holdtime: 150 > } > } > } > > switch-to-spt-threshold { > enabled: true > interval-sec: 100 > bytes: 102400 > } > traceoptions { > flag all { > enabled: true > } > } > } > } > > > /* liest die schon im system gesetzten routen in die xorp configuration ein */ > > protocols { > fib2mrib { > enabled: true > } > > } > ---------------------------------------------------- > > show pim join > 224.0.1.10 0.0.0.0 20.40.60.1 WC > Upstream interface (RP): register_vif > Upstream MRIB next hop (RP): UNKNOWN > Upstream RPF'(*,G): UNKNOWN > Upstream state: Joined > Join timer: 31 > Local receiver include WC: O.. > Joins RP: ... > Joins WC: ... > Join state: ... > Prune state: ... > Prune pending state: ... > I am assert winner state: ... > I am assert loser state: ... > Assert winner WC: ... > Assert lost WC: ... > Assert tracking WC: O.O > Could assert WC: O.. > I am DR: OOO > Immediate olist RP: ... > Immediate olist WC: O.. > Inherited olist SG: O.. > Inherited olist SG_RPT: O.. > PIM include WC: O.. > 239.255.255.250 0.0.0.0 20.40.60.1 WC > Upstream interface (RP): register_vif > Upstream MRIB next hop (RP): UNKNOWN > Upstream RPF'(*,G): UNKNOWN > Upstream state: Joined > Join timer: 46 > Local receiver include WC: OO. > Joins RP: ... > Joins WC: ... > Join state: ... > Prune state: ... > Prune pending state: ... > I am assert winner state: ... > I am assert loser state: ... > Assert winner WC: ... > Assert lost WC: ... > Assert tracking WC: OOO > Could assert WC: OO. > I am DR: OOO > Immediate olist RP: ... > Immediate olist WC: OO. > Inherited olist SG: OO. > Inherited olist SG_RPT: OO. > PIM include WC: OO. > 224.0.1.10 55.66.77.2 20.40.60.1 SG SPT DirectlyConnectedS > Upstream interface (S): eth1 > Upstream interface (RP): register_vif > Upstream MRIB next hop (RP): UNKNOWN > Upstream MRIB next hop (S): UNKNOWN > Upstream RPF'(S,G): UNKNOWN > Upstream state: Joined > Register state: RegisterNoinfo RegisterNotCouldRegister > Join timer: 31 > Local receiver include WC: O.. > Local receiver include SG: ... > Local receiver exclude SG: ... > Joins RP: ... > Joins WC: ... > Joins SG: ... > Join state: ... > Prune state: ... > Prune pending state: ... > I am assert winner state: ... > I am assert loser state: ... > Assert winner WC: ... > Assert winner SG: ... > Assert lost WC: ... > Assert lost SG: ... > Assert lost SG_RPT: ... > Assert tracking SG: OO. > Could assert WC: O.. > Could assert SG: O.. > I am DR: OOO > Immediate olist RP: ... > Immediate olist WC: O.. > Immediate olist SG: ... > Inherited olist SG: O.. > Inherited olist SG_RPT: O.. > PIM include WC: O.. > PIM include SG: ... > PIM exclude SG: ... > ----------------------------------------- > > Xorp> show pim rps > RP Type Pri Holdtime Timeout ActiveGroups GroupPrefix > 20.40.60.1 bootstrap 192 150 -1 2 224.0.0.0/4 > ----------------------------------------- > > Xorp> show pim mfc > 224.0.1.10 55.66.77.2 20.40.60.1 > Incoming interface : eth1 > Outgoing interfaces: O.. > ----------------------------------------- > > cat /proc/net/ip_mr_cache > Group Origin Iif Pkts Bytes Wrong Oifs > 0A0100E0 024D4237 1 94007 126345408 0 0:1 > ----------------------------------------- > > log: > /usr/local/xorp/bin/xorp_rtrmgr > [ 2005/03/08 15:03:44 INFO xorp_rtrmgr:8190 RTRMGR +134 master_conf_tree.cc > execute ] Changed modules: interfaces, fea, mfea4, rib, static_routes, igmp, > pimsm4 > [ 2005/03/08 15:03:44 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc > run ] Running module: interfaces (/usr/local/xorp/fea/xorp_fea) > [ 2005/03/08 15:03:46 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc > run ] Running module: fea (/usr/local/xorp/fea/xorp_fea) > [ 2005/03/08 15:03:52 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc > run ] Running module: mfea4 (/usr/local/xorp/fea/xorp_fea) > [ 2005/03/08 15:03:52 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: > >finder://MFEA_4/mfea/0.1/start_mfea< > [ 2005/03/08 15:03:52 INFO xorp_fea MFEA ] New vif: Vif[eth0] pif_index: 1 > vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: 192.168.1.255 > peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/08 15:03:52 INFO xorp_fea MFEA ] New vif: Vif[eth1] pif_index: 3 > vif_index: 1 addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: 55.66.77.255 > peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Enabled vif: eth0 > [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Started vif: eth0 > [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] New vif: Vif[register_vif] > pif_index: 1 vif_index: 2 addr: 20.40.60.1 subnet: 20.40.60.1/32 broadcast: > 20.40.60.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP > [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Enabled vif: eth1 > [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Started vif: eth1 > [ 2005/03/08 15:03:53 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 > vif_index = 1 src = 55.66.77.2 dst = 224.0.1.10 > [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Enabled vif: register_vif > [ 2005/03/08 15:03:53 INFO xorp_fea MFEA ] Started vif: register_vif > [ 2005/03/08 15:03:53 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc > run ] Running module: rib (/usr/local/xorp/rib/xorp_rib) > [ 2005/03/08 15:03:55 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc > run ] Running module: static_routes > (/usr/local/xorp/static_routes/xorp_static_routes) > [ 2005/03/08 15:03:57 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc > run ] Running module: igmp (/usr/local/xorp/mld6igmp/xorp_igmp) > [ 2005/03/08 15:03:57 WARNING xorp_rtrmgr:8190 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. > [ 2005/03/08 15:03:58 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: > >finder://IGMP/mld6igmp/0.1/start_mld6igmp< > [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth0] pif_index: > 0 vif_index: 0 Flags: > [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Added new address to vif eth0: > addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: 192.168.1.255 peer: 0.0.0.0 > [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[eth0] > pif_index: 0 vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: > 192.168.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth1] pif_index: > 0 vif_index: 1 Flags: > [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Added new address to vif eth1: > addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: 55.66.77.255 peer: 0.0.0.0 > [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[eth1] > pif_index: 0 vif_index: 1 addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: > 55.66.77.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] New vif: Vif[register_vif] > pif_index: 0 vif_index: 2 Flags: > [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Added new address to vif > register_vif: addr: 20.40.60.1 subnet: 20.40.60.1/32 broadcast: 20.40.60.1 > peer: 0.0.0.0 > [ 2005/03/08 15:03:58 INFO xorp_igmp MLD6IGMP ] Vif flags changed: > Vif[register_vif] pif_index: 0 vif_index: 2 addr: 20.40.60.1 subnet: > 20.40.60.1/32 broadcast: 20.40.60.1 peer: 0.0.0.0 Flags: PIM_REGISTER > UNDERLYING_VIF_UP > [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth0 > [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth0] pif_index: > 0 vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: > 192.168.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP > IPv4 ENABLED > [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.0.1 > [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] Started vif: eth0 > [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth1 > [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth1] pif_index: > 0 vif_index: 1 addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: 55.66.77.255 > peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED > [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from > 55.66.77.1 to 224.0.0.1 > [ 2005/03/08 15:03:59 INFO xorp_igmp MLD6IGMP ] Started vif: eth1 > [ 2005/03/08 15:03:59 INFO xorp_rtrmgr:8190 RTRMGR +356 module_manager.cc > run ] Running module: pimsm4 (/usr/local/xorp/pim/xorp_pimsm4) > [ 2005/03/08 15:03:59 WARNING xorp_rtrmgr:8190 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. > [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.0.1 on vif eth0 > [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from > 55.66.77.1 to 224.0.0.1 on vif eth1 > [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.2 on vif eth0 > [ 2005/03/08 15:03:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.2 on vif eth1 > [ 2005/03/08 15:04:00 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.2 to 239.255.255.250 on vif eth0 > [ 2005/03/08 15:04:00 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: > >finder://PIMSM_4/pim/0.1/start_pim< > [ 2005/03/08 15:04:00 INFO xorp_pimsm4 PIM ] New vif: Vif[eth0] pif_index: 0 > vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: 192.168.1.255 > peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/08 15:04:00 INFO xorp_pimsm4 PIM ] New vif: Vif[eth1] pif_index: 0 > vif_index: 1 addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: 55.66.77.255 > peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/08 15:04:00 INFO xorp_pimsm4 PIM ] New vif: Vif[register_vif] > pif_index: 0 vif_index: 2 addr: 20.40.60.1 subnet: 20.40.60.1/32 broadcast: > 20.40.60.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP > [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Enabled vif: eth0 > [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] STARTING Vif[eth0] pif_index: 0 > vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: 192.168.1.255 > peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED > [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Started vif: eth0 > [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Enabled vif: eth1 > [ 2005/03/08 15:04:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.2 on vif eth0 > [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] STARTING Vif[eth1] pif_index: 0 > vif_index: 1 addr: 55.66.77.1 subnet: 55.66.77.0/24 broadcast: 55.66.77.255 > peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED > [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Started vif: eth1 > [ 2005/03/08 15:04:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.13 on vif eth0 > [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Enabled vif: register_vif > [ 2005/03/08 15:04:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.13 on vif eth1 > [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] STARTING Vif[register_vif] > pif_index: 0 vif_index: 2 addr: 20.40.60.1 subnet: 20.40.60.1/32 broadcast: > 20.40.60.1 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP UP IPv4 > ENABLED > [ 2005/03/08 15:04:01 INFO xorp_pimsm4 PIM ] Started vif: register_vif > [ 2005/03/08 15:04:01 TRACE xorp_pimsm4 PIM ] Add membership for > (0.0.0.0,239.255.255.250) on vif eth0 > [ 2005/03/08 15:04:01 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP > for group 239.255.255.250: not found > [ 2005/03/08 15:04:01 INFO xorp_rtrmgr:8190 RTRMGR +1366 task.cc run_task ] > No more tasks to run > [ 2005/03/08 15:04:02 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.2 on vif eth1 > [ 2005/03/08 15:04:02 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.13 on vif eth1 > [ 2005/03/08 15:04:03 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 > vif_index = 1 src = 55.66.77.2 dst = 224.0.1.10 > [ 2005/03/08 15:04:03 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: > vif_index = 1 src = 55.66.77.2 dst = 224.0.1.10 > [ 2005/03/08 15:04:03 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (55.66.77.2,224.0.1.10) iif = 1 olist = ..O > [ 2005/03/08 15:04:03 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to > 224.0.0.13 on vif eth0 > [ 2005/03/08 15:04:04 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.2 on vif eth0 > [ 2005/03/08 15:04:05 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.13 on vif eth0 > [ 2005/03/08 15:04:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to > 224.0.0.13 on vif eth1 > [ 2005/03/08 15:04:06 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.2 to 224.0.1.10 on vif eth0 > [ 2005/03/08 15:04:06 TRACE xorp_pimsm4 PIM ] Add membership for > (0.0.0.0,224.0.1.10) on vif eth0 > [ 2005/03/08 15:04:06 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP > for group 224.0.1.10: not found > [ 2005/03/08 15:04:06 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (55.66.77.2,224.0.1.10) iif = 1 olist = O.O > [ 2005/03/08 15:04:08 WARNING xorp_fea MFEA ] proto_socket_read() failed: RX > packet from 192.168.1.1 to 239.255.255.250: no vif found > [ 2005/03/08 15:04:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.2 on vif eth1 > [ 2005/03/08 15:04:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.13 on vif eth1 > [ 2005/03/08 15:04:11 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.13 on vif eth0 > [ 2005/03/08 15:04:30 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.0.1 > [ 2005/03/08 15:04:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.0.1 on vif eth0 > [ 2005/03/08 15:04:30 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from > 55.66.77.1 to 224.0.0.1 > [ 2005/03/08 15:04:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from > 55.66.77.1 to 224.0.0.1 on vif eth1 > [ 2005/03/08 15:04:31 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.2 to 239.255.255.250 on vif eth0 > [ 2005/03/08 15:04:33 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.2 to 224.0.1.10 on vif eth0 > [ 2005/03/08 15:04:33 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to > 224.0.0.13 on vif eth0 > [ 2005/03/08 15:04:35 WARNING xorp_fea MFEA ] proto_socket_read() failed: RX > packet from 192.168.1.1 to 239.255.255.250: no vif found > [ 2005/03/08 15:04:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to > 224.0.0.13 on vif eth1 > [ 2005/03/08 15:04:36 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.13 on vif eth0 > [ 2005/03/08 15:04:37 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.2 on vif eth1 > [ 2005/03/08 15:04:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.13 on vif eth1 > [ 2005/03/08 15:04:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.2 on vif eth0 > [ 2005/03/08 15:05:01 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP > for group 239.255.255.250: not found > [ 2005/03/08 15:05:03 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to > 224.0.0.13 on vif eth0 > [ 2005/03/08 15:05:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to > 224.0.0.13 on vif eth1 > [ 2005/03/08 15:05:06 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP > for group 224.0.1.10: not found > [ 2005/03/08 15:05:33 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to > 224.0.0.13 on vif eth0 > [ 2005/03/08 15:05:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to > 224.0.0.13 on vif eth1 > [ 2005/03/08 15:06:01 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP > for group 239.255.255.250: not found > [ 2005/03/08 15:06:03 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to > 224.0.0.13 on vif eth0 > [ 2005/03/08 15:06:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to > 224.0.0.13 on vif eth1 > [ 2005/03/08 15:06:06 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP > for group 224.0.1.10: not found > [ 2005/03/08 15:06:33 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to > 224.0.0.13 on vif eth0 > [ 2005/03/08 15:06:35 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.0.1 > [ 2005/03/08 15:06:35 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.0.1 on vif eth0 > [ 2005/03/08 15:06:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to > 224.0.0.13 on vif eth1 > [ 2005/03/08 15:06:35 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from > 55.66.77.1 to 224.0.0.1 > [ 2005/03/08 15:06:35 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from > 55.66.77.1 to 224.0.0.1 on vif eth1 > [ 2005/03/08 15:06:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.2 to 239.255.255.250 on vif eth0 > [ 2005/03/08 15:06:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.2 to 239.255.255.250 on vif eth1 > [ 2005/03/08 15:06:40 TRACE xorp_pimsm4 PIM ] Add membership for > (0.0.0.0,239.255.255.250) on vif eth1 > [ 2005/03/08 15:06:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.13 on vif eth1 > [ 2005/03/08 15:06:42 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.2 on vif eth0 > [ 2005/03/08 15:06:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.13 on vif eth0 > [ 2005/03/08 15:06:44 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.2 to 224.0.1.10 on vif eth0 > [ 2005/03/08 15:06:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.2 on vif eth1 > [ 2005/03/08 15:06:50 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (55.66.77.2,224.0.1.10) iif = 1 olist = O.O > [ 2005/03/08 15:06:50 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (55.66.77.2,224.0.1.10) iif = 1 olist = O.. > [ 2005/03/08 15:07:03 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to > 224.0.0.13 on vif eth0 > [ 2005/03/08 15:07:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to > 224.0.0.13 on vif eth1 > [ 2005/03/08 15:07:33 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to > 224.0.0.13 on vif eth0 > [ 2005/03/08 15:07:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to > 224.0.0.13 on vif eth1 > [ 2005/03/08 15:07:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from > 20.40.60.2 to 224.0.0.2 on vif eth0 > [ 2005/03/08 15:07:43 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.1.10 > [ 2005/03/08 15:07:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.1.10 on vif eth0 > [ 2005/03/08 15:07:44 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.1.10 > [ 2005/03/08 15:07:44 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.1.10 on vif eth0 > [ 2005/03/08 15:07:45 TRACE xorp_pimsm4 PIM ] Delete membership for > (0.0.0.0,224.0.1.10) on vif eth0 > [ 2005/03/08 15:07:45 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (55.66.77.2,224.0.1.10) iif = 1 olist = ... > [ 2005/03/08 15:07:47 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.2 to 224.0.1.10 on vif eth0 > [ 2005/03/08 15:07:47 TRACE xorp_pimsm4 PIM ] Add membership for > (0.0.0.0,224.0.1.10) on vif eth0 > [ 2005/03/08 15:07:47 TRACE xorp_pimsm4 PIM ] Add MFC entry: > (55.66.77.2,224.0.1.10) iif = 1 olist = O.. > [ 2005/03/08 15:07:48 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.2 to 224.0.1.10 on vif eth0 > [ 2005/03/08 15:07:49 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.2 to 224.0.1.10 on vif eth0 > [ 2005/03/08 15:08:03 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to > 224.0.0.13 on vif eth0 > [ 2005/03/08 15:08:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to > 224.0.0.13 on vif eth1 > [ 2005/03/08 15:08:33 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 20.40.60.1 to > 224.0.0.13 on vif eth0 > [ 2005/03/08 15:08:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 55.66.77.1 to > 224.0.0.13 on vif eth1 > [ 2005/03/08 15:08:40 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.0.1 > [ 2005/03/08 15:08:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from > 20.40.60.1 to 224.0.0.1 on vif eth0 > [ 2005/03/08 15:08:40 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from > 55.66.77.1 to 224.0.0.1 > [ 2005/03/08 15:08:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from > 55.66.77.1 to 224.0.0.1 on vif eth1 > [ 2005/03/08 15:08:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.2 on vif eth0 > [ 2005/03/08 15:08:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.2 to 239.255.255.250 on vif eth1 > [ 2005/03/08 15:08:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.13 on vif eth1 > [ 2005/03/08 15:08:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.2 to 239.255.255.250 on vif eth0 > [ 2005/03/08 15:08:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.1 to 224.0.0.13 on vif eth0 > [ 2005/03/08 15:08:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 20.40.60.2 to 224.0.1.10 on vif eth0 > [ 2005/03/08 15:08:49 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT > from 55.66.77.1 to 224.0.0.2 on vif eth1 > > > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users@xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From felix.engel@beanpower.de Wed Mar 9 22:21:11 2005 From: felix.engel@beanpower.de (Felix Engel) Date: Wed, 9 Mar 2005 23:21:11 +0100 Subject: [Xorp-users] multicast problem In-Reply-To: <200503081616.j28GGMxR025061@possum.icir.org> References: <200503081616.j28GGMxR025061@possum.icir.org> Message-ID: <200503092321.11367.felix.engel@beanpower.de> On Tuesday 08 March 2005 17:16, you wrote: > > i am trying to get multicast working. it is an easy setup with only two > > network interfaces under gentoo linux. my application is vlc (with ttl > > > 1). i use the bootstrap method for the rp. the "show pim join" command > > shows the sender and the reciever. but "show pim mfc" shows not the > > needed outgoing interface i think. does anybody konw what is wrong? i > > have read most of the > > The info below shows that for source 55.66.77.2 and group 224.0.1.10 > the eth1 is the incoming interface, and eth0 is the outgoing > interface. This seems right to me, given that your router is the RP, > the sender is directly connected to eth1, and the receiver is on > eth0. Why do you think the oif set is wrong? ok. i missunderstood the output of "show pim mfc". > Also, did the receiver get the multicast traffic? no. in both directions the same. i can send but the receiver is getting no traffic. i also tried another gentoo box with the latest cvs-version of xorp. and another multicast-application. but the same result. > > > mailing-list-archive an tried all configurations that seems possible to > > me. but i did not get the poin. > > BTW, there are two things in your configuration that you may want to > fix. > > First, in your static routes configuration you have what seems like > a cyclic dependency. The nexthop for the first route matches into > the second route, and the nexthop for the second route matches into > > the first route: > > route4 55.66.77.1/24 { > > nexthop: 20.40.60.1 > > metric: 1 > > } > > route4 20.40.60.1/24 { > > nexthop: 55.66.77.1 > > metric: 1 > > } > > Given that both routes are actually the directly-connected subnets, > you don't need them in your static routes configuration, so you can > delete them. > > Second, the IP interface configuration for eth0 shows a mismatch > > between the IP address and the broadcast address: > > [ 2005/03/08 15:03:52 INFO xorp_fea MFEA ] New vif: Vif[eth0] pif_index: > > 1 vif_index: 0 addr: 20.40.60.1 subnet: 20.40.60.0/24 broadcast: > > 192.168.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > > Even though such assignment is legal, for practical purposes the > broadcast address should be 20.40.60.255 (unless you have good > reasons that the broadcast address should really be 192.168.1.255). this was my fault. its from the previous test-configuration. i corrected both. felix > > Regards, > Pavlin > > > thanks a lot. > > felix > > From pavlin@icir.org Wed Mar 9 23:17:43 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 09 Mar 2005 15:17:43 -0800 Subject: [Xorp-users] HEADS UP: XORP configuration syntax changes Message-ID: <200503092317.j29NHhjn057544@possum.icir.org> All, As of today, there are few changes in the XORP configuration syntax in XORP-current, and those changes will be in the forthcoming XORP-1.1 release as well. The changes are: * All "enabled: true/false" XORP configuration flags are now renamed to "disable: false/true". Furthermore, now all of them have default value of "false". In other words, if a configuration section doesn't contain the "disable" flag, it is implicitly enabled. [The reason for this renaming is for better consistency with the configuration of other router vendors.] Therefore, if you have "enabled: true" in your configuration, you should either change it to "disable: false" or you you can simply delete it (because it is same as the default). However, if you have "enabled: false", then you should change it it to "disable: true". * Change the syntax for configuring the IPv4/IPv6 forwarding (for consistency with the above renaming): OLD: fea { enable-unicast-forwarding4: true enable-unicast-forwarding6: true } NEW: fea { unicast-forwarding4 { disable: false } unicast-forwarding6 { disable: false } } OR JUST (if you want to enable the IPv4 and IPv6 forwarding): fea { unicast-forwarding4 { } unicast-forwarding6 { } } Now the old syntax is marked as %deprecated in the rtrmgr templates, so the appropriate error message is printed on startup if someone tries to use a configuration file with the old syntax. Please let us know if you find any problems because of the above change. Thanks, The XORP Team From pavlin@icir.org Wed Mar 9 23:55:49 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 09 Mar 2005 15:55:49 -0800 Subject: [Xorp-users] multicast problem In-Reply-To: Message from Felix Engel of "Wed, 09 Mar 2005 23:21:11 +0100." <200503092321.11367.felix.engel@beanpower.de> Message-ID: <200503092355.j29NtnGE057822@possum.icir.org> > > Also, did the receiver get the multicast traffic? > > no. in both directions the same. i can send but the receiver is getting no > traffic. i also tried another gentoo box with the latest cvs-version of xorp. > and another multicast-application. but the same result. This is odd. In your first email, you sent the following info: cat /proc/net/ip_mr_cache Group Origin Iif Pkts Bytes Wrong Oifs 0A0100E0 024D4237 1 94007 126345408 0 0:1 In other words, your kernel has the correct MFC entry for source 55.66.77.2 and group 224.0.1.10, the iif is eth1, and the oif is eth0 (with min ttl of 1 needed to forward a packet). Furthermore, the kernel has seen 94007 packets that match on that entry (and that are eventually forwarded, unless the ttl is not large enough). Three issues come to mind: * The TTL of the data packets is not large enough. You mentioned in your first email that it is large enough, but just double-check it by running tcpdump on both eth0 and eth1. Running tcpdump will also show you if the multicast packets are indeed forwarded out on eth0. * If the receiver is on the same host as the multicast router, there could be some kernel issues with delivering the multicast data packets to local receivers. I vaguely remember that there were some issues with local multicast receivers running on the same machine as the multicast router, but I don't have the notes with me to check the details (OS, setup, etc). To make sure this doesn't affect you, have your sender and receiver running on hosts directly connected to your multicast router. * You may have some filters in your kernel (firewall rules, etc) which are stopping the multicast traffic. At least, make sure that the "rp_filter" in the Linux kernel is reset to 0: cat /proc/sys/net/ipv4/conf/all/rp_filter echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter Regards, Pavlin From crobson@cmf.nrl.navy.mil Fri Mar 11 14:35:59 2005 From: crobson@cmf.nrl.navy.mil (Chris Robson Work Email) Date: Fri, 11 Mar 2005 09:35:59 -0500 Subject: [Xorp-users] XORP status Message-ID: <6.2.1.2.2.20050311093310.02269880@ginger.cmf.nrl.navy.mil> It seems the XORP web page has not changed much for sometime. Is there an up-to-date document detailing the state of the XORP suite? For exampling: Is BGP/MPLS supported yet? Thank You chris Robson From pavlin@icir.org Fri Mar 11 16:39:01 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Fri, 11 Mar 2005 08:39:01 -0800 Subject: [Xorp-users] XORP status In-Reply-To: Message from Chris Robson Work Email of "Fri, 11 Mar 2005 09:35:59 EST." <6.2.1.2.2.20050311093310.02269880@ginger.cmf.nrl.navy.mil> Message-ID: <200503111639.j2BGd1f2018430@possum.icir.org> > It seems the XORP web page has not changed much for sometime. Is there an > up-to-date document detailing the state of the XORP suite? For exampling: The "XORP Software Status" web page (http://www.xorp.org/status.html) contains the status for the last XORP release (1.0) and soon it will be updated with the status of the forthcoming 1.1 release. FYI, for the 1.1 release there are no new protocols. Also, the roadmap web page (http://www.xorp.org/roadmap.html) contains what we plan to implement within the next one year or so. > Is BGP/MPLS supported yet? BGP: yes MPLS: no Regards, Pavlin From felix.engel@beanpower.de Sat Mar 12 11:17:42 2005 From: felix.engel@beanpower.de (Felix Engel) Date: Sat, 12 Mar 2005 12:17:42 +0100 Subject: [Xorp-users] multicast problem (solved) In-Reply-To: <200503092355.j29NtnGE057822@possum.icir.org> References: <200503092355.j29NtnGE057822@possum.icir.org> Message-ID: <200503121217.42202.felix.engel@beanpower.de> On Thursday 10 March 2005 00:55, you wrote: > > > Also, did the receiver get the multicast traffic? > > > > no. in both directions the same. i can send but the receiver is getting > > no traffic. i also tried another gentoo box with the latest cvs-version > > of xorp. and another multicast-application. but the same result. > > This is odd. In your first email, you sent the following info: > > cat /proc/net/ip_mr_cache > Group Origin Iif Pkts Bytes Wrong Oifs > 0A0100E0 024D4237 1 94007 126345408 0 0:1 > > In other words, your kernel has the correct MFC entry for source > 55.66.77.2 and group 224.0.1.10, the iif is eth1, and the oif is > eth0 (with min ttl of 1 needed to forward a packet). Furthermore, > the kernel has seen 94007 packets that match on that entry (and that > are eventually forwarded, unless the ttl is not large enough). > > Three issues come to mind: > > * The TTL of the data packets is not large enough. You mentioned in > your first email that it is large enough, but just double-check > it by running tcpdump on both eth0 and eth1. Running > tcpdump will also show you if the multicast packets are indeed > forwarded out on eth0. the problem was the ttl. there is a problem in the vlc-streaming-gui i think. you can define the ttl, but it is not used. vlc uses only the default ttl=1. the solution was to run vlc in text-mode wih --ttl option. thank you very much for your help. felix > > * If the receiver is on the same host as the multicast router, > there could be some kernel issues with delivering the multicast > data packets to local receivers. I vaguely remember that there > were some issues with local multicast receivers running on the > same machine as the multicast router, but I don't have the notes > with me to check the details (OS, setup, etc). > To make sure this doesn't affect you, have your sender and > receiver running on hosts directly connected to your multicast > router. > > * You may have some filters in your kernel (firewall rules, etc) > which are stopping the multicast traffic. > At least, make sure that the "rp_filter" in the Linux kernel > is reset to 0: > cat /proc/sys/net/ipv4/conf/all/rp_filter > echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter > > > Regards, > Pavlin  Tel.: 040 / 632 95 886  e-mail: felix.engel@beanpower.de From smcdermott@questra.com Sun Mar 13 23:23:45 2005 From: smcdermott@questra.com (Scott Mcdermott) Date: Sun, 13 Mar 2005 15:23:45 -0800 Subject: [Xorp-users] PIM-SM routing over an IPSEC PF_KEY tunnel with no interface Message-ID: <20050313232342.GJ10218@questra.com> I am trying to set up Xorp to route PIM-SM over IPv4 with the neighbor I need to communicate with sitting across an IPSEC tunnel, implemented with PF_KEY in Linux 2.6. This tunnel has no route or interface exported by the operating system; instead the SPD is consulted directly and routing occurs only after the packet has been encapsulated (or decapsulated in the case of ingress packets). What this means is that I have no OS interface associated with the tunnel. Does Xorp require such an interface in order to function with PIM-SM? PIM messages will appear to arrive at the system magically, without being associated with an interface. I'm thinking Xorp cannot work this way, and I will need to set up a GRE tunnel or some such, over the IPSEC tunnel, so I have a named interface I can tell Xorp about, on which to run PIM. Is this a correct assumption? If possible I would like to avoid another encapsulation with GRE or IPIP inside the ESP, since the purpose of my multicast datagrams is to support multimedia applications which use them, and each additional layer of tunneling has performance implications and introduces difficulties implementing a proper queueing discipline. Any info is greatly appreciated. Thanks. From pavlin@icir.org Mon Mar 14 02:22:50 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Sun, 13 Mar 2005 18:22:50 -0800 Subject: [Xorp-users] PIM-SM routing over an IPSEC PF_KEY tunnel with no interface In-Reply-To: Message from Scott Mcdermott of "Sun, 13 Mar 2005 15:23:45 PST." <20050313232342.GJ10218@questra.com> Message-ID: <200503140222.j2E2Mot3052443@possum.icir.org> > I am trying to set up Xorp to route PIM-SM over IPv4 with > the neighbor I need to communicate with sitting across an > IPSEC tunnel, implemented with PF_KEY in Linux 2.6. This > tunnel has no route or interface exported by the operating > system; instead the SPD is consulted directly and routing > occurs only after the packet has been encapsulated (or > decapsulated in the case of ingress packets). > > What this means is that I have no OS interface associated > with the tunnel. > > Does Xorp require such an interface in order to function > with PIM-SM? PIM messages will appear to arrive at the > system magically, without being associated with an > interface. In general, when the PIM-SM module receives a PIM control message, it must know the interface it came from. However, even if somehow magically you can tell the XORP implementation that the packets have arrived on the IPSEC tunnel, there is another issue. The userland daemon needs to install the MFC (Multicast Forwarding Cache) entries in the kernel, and prior to that it needs to install in the kernel the set of interfaces that would be used for multicast forwarding. The UNIX system call for that is setsockopt(MRT_ADD_VIF). The "struct vifctl" argument to that system call requires the address of the local interface that the multicast vif will be associated with. I am not familiar with IPSEC configuration, but it appears that there is no IP address associated with that tunnel. Hence, the kernel itself cannot use that tunnel for multicast forwarding. > I'm thinking Xorp cannot work this way, and I will need to > set up a GRE tunnel or some such, over the IPSEC tunnel, so > I have a named interface I can tell Xorp about, on which to > run PIM. Yes, I am afraid that you would have to use tunnels such as GRE. I would be very interested to know if someone has a solution that doesn't require the extra tunnel, but maybe this is possible only for those router vendors who have their own IP stack implementation. FYI, XORP should work over GRE tunnels, but currently you would have to create and configure the tunnel before starting XORP. In any case, you may be the first one to try this solution, so please let us know if it works for you or if you run into some problems. Thanks, Pavlin > Is this a correct assumption? If possible I would like to > avoid another encapsulation with GRE or IPIP inside the ESP, > since the purpose of my multicast datagrams is to support > multimedia applications which use them, and each additional > layer of tunneling has performance implications and > introduces difficulties implementing a proper queueing > discipline. From bms@spc.org Mon Mar 14 02:40:42 2005 From: bms@spc.org (Bruce M Simpson) Date: Sun, 13 Mar 2005 18:40:42 -0800 Subject: [Xorp-users] PIM-SM routing over an IPSEC PF_KEY tunnel with no interface In-Reply-To: <20050313232342.GJ10218@questra.com> References: <20050313232342.GJ10218@questra.com> Message-ID: <20050314024042.GE755@empiric.icir.org> On Sun, Mar 13, 2005 at 03:23:45PM -0800, Scott Mcdermott wrote: ... > What this means is that I have no OS interface associated > with the tunnel. ... This is an old problem with IPSEC. There is no notion of 'interface mode IPSEC' in general -- OpenBSD has something called the 'enc' interface which roughly corresponds to what is needed here. As Pavlin points out the multicast forwarding code needs to be able to have a handle to a network interface with an assigned IP address. In the past, when working with mrouted, I have used IPIP in transport mode IPSEC to fulfil this role; IPIP is implemented in the other BSDs using the 'gif' interface, so once the necessary configuration is in place to bring up a gif, XORP should be able to run PIM on top of it. BMS From smcdermott@questra.com Mon Mar 14 02:47:33 2005 From: smcdermott@questra.com (Scott Mcdermott) Date: Sun, 13 Mar 2005 18:47:33 -0800 Subject: [Xorp-users] PIM-SM routing over an IPSEC PF_KEY tunnel with no interface In-Reply-To: <200503140222.j2E2Mot3052443@possum.icir.org> References: <20050313232342.GJ10218@questra.com> <200503140222.j2E2Mot3052443@possum.icir.org> Message-ID: <20050314024733.GN10218@questra.com> Pavlin Radoslavov on Sun 13/03 18:22 -0800: > However, even if somehow magically you can tell the XORP > implementation that the packets have arrived on the IPSEC > tunnel, there is another issue. The userland daemon needs > to install the MFC (Multicast Forwarding Cache) entries in > the kernel, and prior to that it needs to install in the > kernel the set of interfaces that would be used for > multicast forwarding. The UNIX system call for that is > setsockopt(MRT_ADD_VIF). The "struct vifctl" argument to > that system call requires the address of the local > interface that the multicast vif will be associated with. > > I am not familiar with IPSEC configuration, but it appears > that there is no IP address associated with that tunnel. > Hence, the kernel itself cannot use that tunnel for > multicast forwarding. Well, ultimately the packets do go out an interface once they are ESP encapsulated. I tried configuring that interface with PIM-SM (hoping that the MFC entries would be added, but then intercepted somewhere before the packets were routed, by the IPSEC code), but the kernel will only intercept the messages, encapsulate and send them over the IPSEC interface if they match the security policy description for the tunnel (e.g. as set by "setkey")...which in this case means source net and destination net. Since I can't add an IPSEC policy for net 224/4 (AFAIK) this won't work anyways (it just goes "underneath" the tunnel out the interface as regular multicast datagrams). So it seems that a GRE tunnel is the only solution. I suppose as long as I can pass the TOS bits up through to the encapsulating header, then I can do the same to the ESP header, I can still implement a queueing discipline based on this, so it should work in theory. We'll see how this works; I'll report back. Thanks. From smcdermott@questra.com Mon Mar 14 10:27:28 2005 From: smcdermott@questra.com (Scott Mcdermott) Date: Mon, 14 Mar 2005 02:27:28 -0800 Subject: [Xorp-users] PIM-SM routing over an IPSEC PF_KEY tunnel with no interface In-Reply-To: <20050314024733.GN10218@questra.com> References: <20050313232342.GJ10218@questra.com> <200503140222.j2E2Mot3052443@possum.icir.org> <20050314024733.GN10218@questra.com> Message-ID: <20050314102727.GG10889@questra.com> To xorp-users@xorp.org on Sun 13/03 18:47 -0800: > > However, even if somehow magically you can tell the XORP > > implementation that the packets have arrived on the > > IPSEC tunnel, [you still need an interface for > > MRT_ADD_VIF/MRT_ADD_MFC] > > > > I am not familiar with IPSEC configuration, but it > > appears that there is no IP address associated with that > > tunnel. Hence, the kernel itself cannot use that tunnel > > for multicast forwarding. > > Well, ultimately the packets do go out an interface once > they are ESP encapsulated [and I could use that one, > relying on ipsec code to intercept before routing...but] I > can't add an IPSEC policy for net 224/4 [...] So it seems > that a GRE tunnel is the only solution. [...] We'll see > how this works; I'll report back. Works fine. I set up a GRE tunnel on the IPSEC gateways, with the local/remote IPs within the existing encryption domain and a manufactured /30 for the tunnel, with Xorp set up to add MFCs thereon. It seems to have worked fine based on xorpsh output, although we'll see how the conference calling feature works tomorrow :) It took me a while to figure get the RP stuff right (I was using dense-mode on a Cisco before so RPs are new to me), and I had to add static routes (fib2mrib did not seem to populate the MRIB for some reason), and figure out that I wanted a different Multicast default route than Unicast default route. But once I got that working, seems to be running with no problems. Now if I could figure out how to properly run this xorp_rtrmgr thing out of my init scripts without doing nohup ... /dev/null & and get it to log TRACE/INFO to syslog, then I will be all set :) Thanks! From pavlin@icir.org Mon Mar 14 20:18:36 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Mon, 14 Mar 2005 12:18:36 -0800 Subject: [Xorp-users] PIM-SM routing over an IPSEC PF_KEY tunnel with no interface In-Reply-To: Message from Scott Mcdermott of "Mon, 14 Mar 2005 02:27:28 PST." <20050314102727.GG10889@questra.com> Message-ID: <200503142018.j2EKIa0s086074@possum.icir.org> > Now if I could figure out how to properly run this > xorp_rtrmgr thing out of my init scripts without doing > > nohup ... /dev/null & > > and get it to log TRACE/INFO to syslog, then I will be all > set :) I am afraid that you would have to wait until we have it implemented, but this won't happen before release-1.1 is out :( Thanks, Pavlin From pavlin@icir.org Mon Mar 14 20:31:18 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Mon, 14 Mar 2005 12:31:18 -0800 Subject: [Xorp-users] PIM-SM routing over an IPSEC PF_KEY tunnel with no interface In-Reply-To: Message from Pavlin Radoslavov of "Mon, 14 Mar 2005 12:18:36 PST." <200503142018.j2EKIa0s086074@possum.icir.org> Message-ID: <200503142031.j2EKVIpQ086231@possum.icir.org> > > Now if I could figure out how to properly run this > > xorp_rtrmgr thing out of my init scripts without doing > > > > nohup ... /dev/null & > > > > and get it to log TRACE/INFO to syslog, then I will be all > > set :) > > I am afraid that you would have to wait until we have it > implemented, but this won't happen before release-1.1 is out :( FYI, I've added a bugzilla entry for this feature: http://www.xorp.org/bugzilla/show_bug.cgi?id=119 If you want to get an automated email notification when it is fixed, then you may want to add yourself to the CC list for that entry. Regards, Pavlin From dalibor.kusic@zg.t-com.hr Tue Mar 15 14:07:04 2005 From: dalibor.kusic@zg.t-com.hr (Dalibor Kusic) Date: Tue, 15 Mar 2005 15:07:04 +0100 Subject: [Xorp-users] OSPF Message-ID: <6.2.0.14.2.20050315150600.0286b8d8@pop.htnet.hr> Hi! Is OSPF currently supported in latest version of XORP when using it through a downloadable LiveCD? I know there are some unofficial modules for it, but I really would like to recompile anything... Kind regards! From crobson@cmf.nrl.navy.mil Tue Mar 15 14:39:51 2005 From: crobson@cmf.nrl.navy.mil (Chris Robson Work Email) Date: Tue, 15 Mar 2005 09:39:51 -0500 Subject: [Xorp-users] IPv6 Multicast support Message-ID: <6.2.1.2.2.20050315093751.021f74d0@ginger.cmf.nrl.navy.mil> when kicking off xorp_rtrmgr, it terminates with an error saying it doesn't support IPv6. Have I mis-configured something or is IPv6 not there yet? Thank...chris From crobson@cmf.nrl.navy.mil Tue Mar 15 15:02:27 2005 From: crobson@cmf.nrl.navy.mil (Chris Robson Work Email) Date: Tue, 15 Mar 2005 10:02:27 -0500 Subject: [Xorp-users] IPv6 Multicast support In-Reply-To: <6.2.1.2.2.20050315093751.021f74d0@ginger.cmf.nrl.navy.mil> References: <6.2.1.2.2.20050315093751.021f74d0@ginger.cmf.nrl.navy.mil> Message-ID: <6.2.1.2.2.20050315095558.02274a20@ginger.cmf.nrl.navy.mil> My apologies for the lack of clarity in my last message. Specifically the rtrmgr error states: "ERROR xorp_fea:4837 MFEA +899 mfea_mrouter.cc add_multicast_vif ] add_multicast_vif() failed: IPv6 multicast routing not supported" OS: Linux 2.6.10-1.9_FC2smp Distro: Fedora Core 2 CVS: 12Mar05 pull from xorp cvs. Thanks....chris At 09:39 AM 3/15/2005, Chris Robson Work Email wrote: >when kicking off xorp_rtrmgr, it terminates with an error saying it >doesn't support IPv6. Have I mis-configured something or is IPv6 not >there yet? > >Thank...chris > >_______________________________________________ >Xorp-users mailing list >Xorp-users@xorp.org >http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From M.Handley@cs.ucl.ac.uk Tue Mar 15 15:13:15 2005 From: M.Handley@cs.ucl.ac.uk (Mark Handley) Date: Tue, 15 Mar 2005 15:13:15 +0000 Subject: [Xorp-users] IPv6 Multicast support In-Reply-To: Your message of "Tue, 15 Mar 2005 09:39:51 EST." <6.2.1.2.2.20050315093751.021f74d0@ginger.cmf.nrl.navy.mil> Message-ID: <56219.1110899595@aardvark.cs.ucl.ac.uk> >when kicking off xorp_rtrmgr, it terminates with an error saying it doesn't >support IPv6. Have I mis-configured something or is IPv6 not there yet? Sounds like a misconfiguration, although if it is, our error reporting should be better. Can you send the precise error, the config file you're using, and which version of XORP you're running? Thanks, Mark From pavlin@icir.org Tue Mar 15 16:21:59 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Tue, 15 Mar 2005 08:21:59 -0800 Subject: [Xorp-users] OSPF In-Reply-To: Message from Dalibor Kusic of "Tue, 15 Mar 2005 15:07:04 +0100." <6.2.0.14.2.20050315150600.0286b8d8@pop.htnet.hr> Message-ID: <200503151622.j2FGLxXC051680@possum.icir.org> > Hi! > > Is OSPF currently supported in latest version of XORP when using it through > a downloadable LiveCD? No. > I know there are some unofficial modules for it, but I really would like to > recompile anything... If you checkout the lastest CVS code, the third-party OSPF code is in xorp/contrib/ospfd, but for all practical purposes this code shoult be considered unsupported, and we do not recommend running it. See http://www.xorp.org/roadmap.html for info about OSPF support in the future. Regards, Pavlin From pavlin@icir.org Tue Mar 15 16:33:32 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Tue, 15 Mar 2005 08:33:32 -0800 Subject: [Xorp-users] IPv6 Multicast support In-Reply-To: Message from Chris Robson Work Email of "Tue, 15 Mar 2005 10:02:27 EST." <6.2.1.2.2.20050315095558.02274a20@ginger.cmf.nrl.navy.mil> Message-ID: <200503151633.j2FGXWfu051764@possum.icir.org> > My apologies for the lack of clarity in my last message. Specifically the > rtrmgr error states: > > "ERROR xorp_fea:4837 MFEA +899 mfea_mrouter.cc add_multicast_vif ] > add_multicast_vif() failed: IPv6 multicast routing not supported" > > OS: Linux 2.6.10-1.9_FC2smp > Distro: Fedora Core 2 > CVS: 12Mar05 pull from xorp cvs. Currently, the Linux kernel doesn't support IPv6 multicast routing. FYI, if you want to run IPv6 multicast routing on Linux, you would have to patch your kernel (see http://clarinet.u-strasbg.fr/~hoerdt/linux_ipv6_mforwarding/ and that code is already in the USAGI tree), but sadly I haven't had the time to test XORP with that kernel patch. If you don't need IPv6 multicast routing, then it seems you have misconfigured your router by including "plumbing mfea6", "protocols mld" and "protocols pimsm6". Remove those three sections and try again. Regards, Pavlin From mrim22.cb@wanadoo.fr Tue Mar 15 20:23:15 2005 From: mrim22.cb@wanadoo.fr (mrim22.cb) Date: Tue, 15 Mar 2005 21:23:15 +0100 Subject: [Xorp-users] Basic Multicast Router configuration Message-ID: <42374433.5010309@wanadoo.fr> Hi, I'm a newbie in Multicast Routing Domain. I'd like to make a basic Multicast Router configuration to work. Here it is : Workstation A --------------- Xorp Router -------------- Workstation B 192.168.0.2 192.168.0.199 / 172.20.16.199 172.20.16.22 eth0 eth0 eth1 eth0 Send Multicast Packets Wait for Multicast Packets using iperf -c (see below) using iperf -s (see below) Workstation B : iperf -s -u -B 224.0.55.55 -i 1 Workstation A : iperf -c 2240.0.55.55 -u -T 32 -t 10 -i 1 So TTL is set to 32 My router is a Linux Fedora Core 3 (I suppose MROUTE and PIM activate in kernel) unicast ip_forwardink is ok - Stations can ping to each other. cat /proc/sys/net/ipv4/conf/all/rp_filter --> 0 cat /proc/sys/net/ipv4/conf/all/mc_forward --> 0 When B start iperf Xorp router seems to take it into account. When A start sending Multicast Packet I can see them with tcpdump but nothing happened and Xorp Router don't forward them to B Thanks, help me ! Some questions about Multicast : =========================== Is IGMP needed when using PIMSM ? What is RP/RPS in PIM ? Where can i find nice documentation about PIM configuration (for beginners) ? what's about targetname: "MFEA_4", "IGMP",... ? Some other questions about my log : =========================== Why did i get this messages from xorp_rtrmgr running : [ 2005/03/15 18:34:36 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled. Running module: igmp (/usr/local/xorp/mld6igmp/xorp_igmp) [ 2005/03/15 18:34:50 WARNING xorp_rtrmgr:2657 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. [ 2005/03/15 18:34:53 WARNING xorp_rtrmgr:2657 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. Here my xorp configuration file and some dumps : ============================================================================= XORP> show fea { enable-unicast-forwarding4: true targetname: "fea" } interfaces { interface eth0 { description: "data interface" enabled: true vif eth0 { enabled: true address 192.168.0.199 { prefix-length: 24 broadcast: 192.168.0.255 enabled: true } } } interface eth1 { description: "data interface" enabled: true vif eth1 { enabled: true address 172.20.16.199 { prefix-length: 16 broadcast: 172.20.255.255 enabled: true } } } targetname: "fea" } plumbing { mfea4 { enabled: true interface eth1 { vif eth1 { enabled: true } } interface eth0 { vif eth0 { enabled: true } } interface register_vif { vif register_vif { enabled: true } } traceoptions { flag { all { enabled: true } } } targetname: "MFEA_4" } } protocols { igmp { interface eth0 { vif eth0 { enabled: true } } interface eth1 { vif eth1 { enabled: true } } traceoptions { flag { all { enabled: true } } } targetname: "IGMP" enabled: true } pimsm4 { enabled: true interface eth1 { vif eth1 { enabled: true dr-priority: 1 } } interface register_vif { vif register_vif { enabled: true dr-priority: 1 } } static-rps { rp 172.20.16.199 { 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 } } } targetname: "PIMSM_4" } fib2mrib { enabled: true targetname: "fib2mrib" } } ============================================================================= Xorp> show pim interface Interface State Mode V PIMstate Priority DRaddr Neighbors eth0 DISABLED Sparse 2 NotDR 1 0.0.0.0 0 eth1 UP Sparse 2 DR 1 172.20.16.199 0 register_vif UP Sparse 2 DR 1 0.0.0.0 0 ============================================================================= Xorp> show pim join Group Source RP Flags 224.0.55.55 0.0.0.0 172.20.16.199 WC Upstream interface (RP): register_vif Upstream MRIB next hop (RP): UNKNOWN Upstream RPF'(*,G): UNKNOWN Upstream state: Joined Join timer: 39 Local receiver include WC: .O. Joins RP: ... Joins WC: ... Join state: ... Prune state: ... Prune pending state: ... I am assert winner state: ... I am assert loser state: ... Assert winner WC: ... Assert lost WC: ... Assert tracking WC: .OO Could assert WC: .O. I am DR: .OO Immediate olist RP: ... Immediate olist WC: .O. Inherited olist SG: .O. Inherited olist SG_RPT: .O. PIM include WC: .O. ============================================================================= Xorp> show pim mrib DestPrefix NextHopRouter VifName VifIndex MetricPref Metric 172.20.0.0/16 172.20.16.199 eth1 1 0 0 192.168.0.0/24 192.168.0.199 eth0 0 0 0 ============================================================================= Xorp> show pim mfc Group Source RP ============================================================================= Xorp> show pim rps RP Type Pri Holdtime Timeout ActiveGroups GroupPrefix 172.20.16.199 static 192 -1 -1 1 224.0.0.0/4 Xorp> ============================================================================= ! Trace from xorp_rtrmgr ============================================================================= [root@rxy bin]# ./xorp_rtrmgr [ 2005/03/15 18:34:34 INFO xorp_rtrmgr:2657 RTRMGR +134 master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, rib, fib2mrib, igmp, pimsm4 [ 2005/03/15 18:34:34 INFO xorp_rtrmgr:2657 RTRMGR +356 module_manager.cc run ] Running module: interfaces (/usr/local/xorp/fea/xorp_fea) [ 2005/03/15 18:34:36 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled. [ 2005/03/15 18:34:38 INFO xorp_rtrmgr:2657 RTRMGR +356 module_manager.cc run ] Running module: fea (/usr/local/xorp/fea/xorp_fea) [ 2005/03/15 18:34:44 INFO xorp_rtrmgr:2657 RTRMGR +356 module_manager.cc run ] Running module: mfea4 (/usr/local/xorp/fea/xorp_fea) [ 2005/03/15 18:34:44 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: >finder://MFEA_4/mfea/0.1/start_mfea< [ 2005/03/15 18:34:45 INFO xorp_fea MFEA ] New vif: Vif[eth0] pif_index: 2 vif_index: 0 addr: 192.168.0.199 subnet: 192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/15 18:34:45 INFO xorp_fea MFEA ] New vif: Vif[eth1] pif_index: 3 vif_index: 1 addr: 172.20.16.199 subnet: 172.20.0.0/16 broadcast: 172.20.255.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Enabled vif: eth1 [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Started vif: eth1 [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] New vif: Vif[register_vif] pif_index: 3 vif_index: 2 addr: 172.20.16.199 subnet: 172.20.16.199/32 broadcast: 172.20.16.199 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Enabled vif: eth0 [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Started vif: eth0 [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Enabled vif: register_vif [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Started vif: register_vif [ 2005/03/15 18:34:46 INFO xorp_rtrmgr:2657 RTRMGR +356 module_manager.cc run ] Running module: rib (/usr/local/xorp/rib/xorp_rib) [ 2005/03/15 18:34:48 INFO xorp_rtrmgr:2657 RTRMGR +356 module_manager.cc run ] Running module: fib2mrib (/usr/local/xorp/fib2mrib/xorp_fib2mrib) [ 2005/03/15 18:34:50 INFO xorp_rtrmgr:2657 RTRMGR +356 module_manager.cc run ] Running module: igmp (/usr/local/xorp/mld6igmp/xorp_igmp) [ 2005/03/15 18:34:50 WARNING xorp_rtrmgr:2657 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. [ 2005/03/15 18:34:51 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: >finder://IGMP/mld6igmp/0.1/start_mld6igmp< [ 2005/03/15 18:34:52 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth0] pif_index: 0 vif_index: 0 Flags: [ 2005/03/15 18:34:52 INFO xorp_igmp MLD6IGMP ] Added new address to vif eth0: addr: 192.168.0.199 subnet: 192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 [ 2005/03/15 18:34:52 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[eth0] pif_index: 0 vif_index: 0 addr: 192.168.0.199 subnet: 192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/15 18:34:52 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth1] pif_index: 0 vif_index: 1 Flags: [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Added new address to vif eth1: addr: 172.20.16.199 subnet: 172.20.0.0/16 broadcast: 172.20.255.255 peer: 0.0.0.0 [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth0 [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[eth1] pif_index: 0 vif_index: 1 addr: 172.20.16.199 subnet: 172.20.0.0/16 broadcast: 172.20.255.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] New vif: Vif[register_vif] pif_index: 0 vif_index: 2 Flags: [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth0] pif_index: 0 vif_index: 0 addr: 192.168.0.199 subnet: 192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.0.199 to 224.0.0.1 [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Started vif: eth0 [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Added new address to vif register_vif: addr: 172.20.16.199 subnet: 172.20.16.199/32 broadcast: 172.20.16.199 peer: 0.0.0.0 [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth1 [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Vif flags changed: Vif[register_vif] pif_index: 0 vif_index: 2 addr: 172.20.16.199 subnet: 172.20.16.199/32 broadcast: 172.20.16.199 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth1] pif_index: 0 vif_index: 1 addr: 172.20.16.199 subnet: 172.20.0.0/16 broadcast: 172.20.255.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 172.20.16.199 to 224.0.0.1 [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Started vif: eth1 [ 2005/03/15 18:34:53 INFO xorp_rtrmgr:2657 RTRMGR +356 module_manager.cc run ] Running module: pimsm4 (/usr/local/xorp/pim/xorp_pimsm4) [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 192.168.0.199 to 224.0.0.1 on vif eth0 [ 2005/03/15 18:34:53 WARNING xorp_rtrmgr:2657 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. [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.199 to 224.0.0.251 on vif eth0 [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 172.20.16.199 to 224.0.0.1 on vif eth1 [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.199 to 224.0.0.2 on vif eth0 [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.2 on vif eth1 [ 2005/03/15 18:34:54 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled. [ 2005/03/15 18:34:55 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled. [ 2005/03/15 18:34:56 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled. [ 2005/03/15 18:34:57 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.1 to 239.255.255.250 on vif eth0 [ 2005/03/15 18:34:57 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled. [ 2005/03/15 18:34:58 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.251 on vif eth1 [ 2005/03/15 18:34:58 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: >finder://PIMSM_4/pim/0.1/start_pim< [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] New vif: Vif[eth0] pif_index: 0 vif_index: 0 addr: 192.168.0.199 subnet: 192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] New vif: Vif[eth1] pif_index: 0 vif_index: 1 addr: 172.20.16.199 subnet: 172.20.0.0/16 broadcast: 172.20.255.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] New vif: Vif[register_vif] pif_index: 0 vif_index: 2 addr: 172.20.16.199 subnet: 172.20.16.199/32 broadcast: 172.20.16.199 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] Enabled vif: eth1 [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] STARTING Vif[eth1] pif_index: 0 vif_index: 1 addr: 172.20.16.199 subnet: 172.20.0.0/16 broadcast: 172.20.255.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] Started vif: eth1 [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] Enabled vif: register_vif [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] STARTING Vif[register_vif] pif_index: 0 vif_index: 2 addr: 172.20.16.199 subnet: 172.20.16.199/32 broadcast: 172.20.16.199 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2005/03/15 18:34:59 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.13 on vif eth1 [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] Started vif: register_vif [ 2005/03/15 18:35:00 INFO xorp_rtrmgr:2657 RTRMGR +1366 task.cc run_task ] No more tasks to run [ 2005/03/15 18:35:00 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.13 on vif eth1 [ 2005/03/15 18:35:01 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 172.20.16.199 to 224.0.0.13 on vif eth1 [ 2005/03/15 18:35:02 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.199 to 224.0.0.2 on vif eth0 [ 2005/03/15 18:35:02 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.2 on vif eth1 [ 2005/03/15 18:35:06 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.13 on vif eth1 [ 2005/03/15 18:35:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.2 on vif eth1 [ 2005/03/15 18:35:11 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.199 to 224.0.0.2 on vif eth0 [ 2005/03/15 18:35:16 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.22 to 224.0.55.55 on vif eth1 [ 2005/03/15 18:35:16 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0,224.0.55.55) on vif eth1 [ 2005/03/15 18:35:19 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.22 to 224.0.55.55 on vif eth1 [ 2005/03/15 18:35:20 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1 vif_index = 0 src = 192.168.0.2 dst = 224.0.55.55 [ 2005/03/15 18:35:20 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 0 src = 192.168.0.2 dst = 224.0.55.55 [ 2005/03/15 18:35:24 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.0.199 to 224.0.0.1 [ 2005/03/15 18:35:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 192.168.0.199 to 224.0.0.1 on vif eth0 [ 2005/03/15 18:35:24 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 172.20.16.199 to 224.0.0.1 [ 2005/03/15 18:35:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 172.20.16.199 to 224.0.0.1 on vif eth1 [ 2005/03/15 18:35:25 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.13 on vif eth1 [ 2005/03/15 18:35:25 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.2 on vif eth1 [ 2005/03/15 18:35:27 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.199 to 224.0.0.2 on vif eth0 [ 2005/03/15 18:35:27 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.22 to 224.0.55.55 on vif eth1 [ 2005/03/15 18:35:28 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.251 on vif eth1 From pavlin@icir.org Wed Mar 16 10:24:10 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 16 Mar 2005 02:24:10 -0800 Subject: [Xorp-users] Basic Multicast Router configuration In-Reply-To: Message from "mrim22.cb" of "Tue, 15 Mar 2005 21:23:15 +0100." <42374433.5010309@wanadoo.fr> Message-ID: <200503161024.j2GAOA2W042435@possum.icir.org> > I'm a newbie in Multicast Routing Domain. > I'd like to make a basic Multicast Router configuration to work. > Here it is : > > Workstation A --------------- Xorp Router -------------- Workstation B > 192.168.0.2 192.168.0.199 / 172.20.16.199 172.20.16.22 > eth0 eth0 eth1 > eth0 > Send Multicast Packets > Wait for Multicast Packets > using iperf -c (see below) > using iperf -s (see below) > > Workstation B : iperf -s -u -B 224.0.55.55 -i 1 > Workstation A : iperf -c 2240.0.55.55 -u -T 32 -t 10 -i 1 ~~~~ I presume this is a typo, and in your test you used 224 instead. > So TTL is set to 32 > > My router is a Linux Fedora Core 3 (I suppose MROUTE and PIM activate in > kernel) > unicast ip_forwardink is ok - Stations can ping to each other. > cat /proc/sys/net/ipv4/conf/all/rp_filter --> 0 > cat /proc/sys/net/ipv4/conf/all/mc_forward --> 0 > > > When B start iperf Xorp router seems to take it into account. > When A start sending Multicast Packet I can see them with tcpdump > but nothing happened and Xorp Router don't forward them to B > > Thanks, help me ! > > Some questions about Multicast : > =========================== > Is IGMP needed when using PIMSM ? In theory, no, but for all practical purposes IGMP is needed. Otherwise, without IGMP the PIM-SM router cannot learn about directly-connected multicast receivers. > What is RP/RPS in PIM ? The RP (Rendezvous Point) in PIM-SM is the special router that is used by both senders and receivers: the PIM-SM routers directly connected to receivers join toward the RP and by doing so they create the multicast distribution tree. The multicast data from the senders is sent toward the RP, and then distributed down to all receivers. In other words, the RP is the special "meeting" point for the senders and the receivers. In reality, there can be more than one RP per domain. E.g., one or several Candidate-RPs per multicast prefix. If the current RP fails, another one is automatically elected and used instead. > Where can i find nice documentation about PIM configuration (for > beginners) ? The following URL contains some basic information about configuring XORP: http://www.xorp.org/getting_started.html In addition, you could check the xorpdev 101 document (currently, available only from xorp/docs/xorpdev_101 in the CVS repository). > what's about targetname: "MFEA_4", "IGMP",... ? You can (and should) ignore them so they will have their default values. Those are the default target names used by the XORP inter-process communcation mechanism (the XRLs). > Some other questions about my log : > =========================== > > Why did i get this messages from xorp_rtrmgr running : > > [ 2005/03/15 18:34:36 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 > finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for > finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target > is not enabled. > > Running module: igmp (/usr/local/xorp/mld6igmp/xorp_igmp) > [ 2005/03/15 18:34:50 WARNING xorp_rtrmgr:2657 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. > > [ 2005/03/15 18:34:53 WARNING xorp_rtrmgr:2657 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. You can ignore the above warnings. Those are transient warnings during startup. > > > Here my xorp configuration file and some dumps : It appears that you have forgotten to configure interface eth0 inside "protocols pimsm4". I hope that will fix the problem. Regards, Pavlin > > ============================================================================= > XORP> show > fea { > enable-unicast-forwarding4: true > targetname: "fea" > } > interfaces { > interface eth0 { > description: "data interface" > enabled: true > vif eth0 { > enabled: true > address 192.168.0.199 { > prefix-length: 24 > broadcast: 192.168.0.255 > enabled: true > } > } > } > interface eth1 { > description: "data interface" > enabled: true > vif eth1 { > enabled: true > address 172.20.16.199 { > prefix-length: 16 > broadcast: 172.20.255.255 > enabled: true > } > } > } > targetname: "fea" > } > plumbing { > mfea4 { > enabled: true > interface eth1 { > vif eth1 { > enabled: true > } > } > interface eth0 { > vif eth0 { > enabled: true > } > } > interface register_vif { > vif register_vif { > enabled: true > } > } > traceoptions { > flag { > all { > enabled: true > } > } > } > targetname: "MFEA_4" > } > } > protocols { > igmp { > interface eth0 { > vif eth0 { > enabled: true > } > } > interface eth1 { > vif eth1 { > enabled: true > } > } > traceoptions { > flag { > all { > enabled: true > } > } > } > targetname: "IGMP" > enabled: true > } > pimsm4 { > enabled: true > interface eth1 { > vif eth1 { > enabled: true > dr-priority: 1 > } > } > interface register_vif { > vif register_vif { > enabled: true > dr-priority: 1 > } > } > static-rps { > rp 172.20.16.199 { > 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 > } > } > } > targetname: "PIMSM_4" > } > fib2mrib { > enabled: true > targetname: "fib2mrib" > } > } > > ============================================================================= > > Xorp> show pim interface > Interface State Mode V PIMstate Priority DRaddr Neighbors > eth0 DISABLED Sparse 2 NotDR 1 0.0.0.0 0 > eth1 UP Sparse 2 DR 1 172.20.16.199 0 > register_vif UP Sparse 2 DR 1 0.0.0.0 0 > > ============================================================================= > Xorp> show pim join > Group Source RP Flags > 224.0.55.55 0.0.0.0 172.20.16.199 WC > Upstream interface (RP): register_vif > Upstream MRIB next hop (RP): UNKNOWN > Upstream RPF'(*,G): UNKNOWN > Upstream state: Joined > Join timer: 39 > Local receiver include WC: .O. > Joins RP: ... > Joins WC: ... > Join state: ... > Prune state: ... > Prune pending state: ... > I am assert winner state: ... > I am assert loser state: ... > Assert winner WC: ... > Assert lost WC: ... > Assert tracking WC: .OO > Could assert WC: .O. > I am DR: .OO > Immediate olist RP: ... > Immediate olist WC: .O. > Inherited olist SG: .O. > Inherited olist SG_RPT: .O. > PIM include WC: .O. > > ============================================================================= > > Xorp> show pim mrib > DestPrefix NextHopRouter VifName VifIndex MetricPref Metric > 172.20.0.0/16 172.20.16.199 eth1 1 0 0 > 192.168.0.0/24 192.168.0.199 eth0 0 0 0 > > ============================================================================= > > Xorp> show pim mfc > Group Source RP > > ============================================================================= > Xorp> show pim rps > RP Type Pri Holdtime Timeout ActiveGroups > GroupPrefix > 172.20.16.199 static 192 -1 -1 1 > 224.0.0.0/4 > Xorp> > > > ============================================================================= > ! Trace from xorp_rtrmgr > ============================================================================= > > [root@rxy bin]# ./xorp_rtrmgr > [ 2005/03/15 18:34:34 INFO xorp_rtrmgr:2657 RTRMGR +134 > master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, > rib, fib2mrib, igmp, pimsm4 > [ 2005/03/15 18:34:34 INFO xorp_rtrmgr:2657 RTRMGR +356 > module_manager.cc run ] Running module: interfaces > (/usr/local/xorp/fea/xorp_fea) > [ 2005/03/15 18:34:36 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 > finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for > finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target > is not enabled. > [ 2005/03/15 18:34:38 INFO xorp_rtrmgr:2657 RTRMGR +356 > module_manager.cc run ] Running module: fea (/usr/local/xorp/fea/xorp_fea) > [ 2005/03/15 18:34:44 INFO xorp_rtrmgr:2657 RTRMGR +356 > module_manager.cc run ] Running module: mfea4 (/usr/local/xorp/fea/xorp_fea) > [ 2005/03/15 18:34:44 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: > >finder://MFEA_4/mfea/0.1/start_mfea< > [ 2005/03/15 18:34:45 INFO xorp_fea MFEA ] New vif: Vif[eth0] pif_index: > 2 vif_index: 0 addr: 192.168.0.199 subnet: 192.168.0.0/24 broadcast: > 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/15 18:34:45 INFO xorp_fea MFEA ] New vif: Vif[eth1] pif_index: > 3 vif_index: 1 addr: 172.20.16.199 subnet: 172.20.0.0/16 broadcast: > 172.20.255.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP > [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Enabled vif: eth1 > [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Started vif: eth1 > [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] New vif: Vif[register_vif] > pif_index: 3 vif_index: 2 addr: 172.20.16.199 subnet: 172.20.16.199/32 > broadcast: 172.20.16.199 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP > [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Enabled vif: eth0 > [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Started vif: eth0 > [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Enabled vif: register_vif > [ 2005/03/15 18:34:46 INFO xorp_fea MFEA ] Started vif: register_vif > [ 2005/03/15 18:34:46 INFO xorp_rtrmgr:2657 RTRMGR +356 > module_manager.cc run ] Running module: rib (/usr/local/xorp/rib/xorp_rib) > [ 2005/03/15 18:34:48 INFO xorp_rtrmgr:2657 RTRMGR +356 > module_manager.cc run ] Running module: fib2mrib > (/usr/local/xorp/fib2mrib/xorp_fib2mrib) > [ 2005/03/15 18:34:50 INFO xorp_rtrmgr:2657 RTRMGR +356 > module_manager.cc run ] Running module: igmp > (/usr/local/xorp/mld6igmp/xorp_igmp) > [ 2005/03/15 18:34:50 WARNING xorp_rtrmgr:2657 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. > [ 2005/03/15 18:34:51 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: > >finder://IGMP/mld6igmp/0.1/start_mld6igmp< > [ 2005/03/15 18:34:52 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth0] > pif_index: 0 vif_index: 0 Flags: > [ 2005/03/15 18:34:52 INFO xorp_igmp MLD6IGMP ] Added new address to vif > eth0: addr: 192.168.0.199 subnet: 192.168.0.0/24 broadcast: > 192.168.0.255 peer: 0.0.0.0 > [ 2005/03/15 18:34:52 INFO xorp_igmp MLD6IGMP ] Vif flags changed: > Vif[eth0] pif_index: 0 vif_index: 0 addr: 192.168.0.199 subnet: > 192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST > BROADCAST UNDERLYING_VIF_UP > [ 2005/03/15 18:34:52 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth1] > pif_index: 0 vif_index: 1 Flags: > [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Added new address to vif > eth1: addr: 172.20.16.199 subnet: 172.20.0.0/16 broadcast: > 172.20.255.255 peer: 0.0.0.0 > [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth0 > [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Vif flags changed: > Vif[eth1] pif_index: 0 vif_index: 1 addr: 172.20.16.199 subnet: > 172.20.0.0/16 broadcast: 172.20.255.255 peer: 0.0.0.0 Flags: MULTICAST > BROADCAST UNDERLYING_VIF_UP > [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] New vif: > Vif[register_vif] pif_index: 0 vif_index: 2 Flags: > [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth0] > pif_index: 0 vif_index: 0 addr: 192.168.0.199 subnet: 192.168.0.0/24 > broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP UP IPv4 ENABLED > [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] TX > IGMP_MEMBERSHIP_QUERY from 192.168.0.199 to 224.0.0.1 > [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Started vif: eth0 > [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Added new address to vif > register_vif: addr: 172.20.16.199 subnet: 172.20.16.199/32 broadcast: > 172.20.16.199 peer: 0.0.0.0 > [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth1 > [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Vif flags changed: > Vif[register_vif] pif_index: 0 vif_index: 2 addr: 172.20.16.199 subnet: > 172.20.16.199/32 broadcast: 172.20.16.199 peer: 0.0.0.0 Flags: > PIM_REGISTER UNDERLYING_VIF_UP > [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth1] > pif_index: 0 vif_index: 1 addr: 172.20.16.199 subnet: 172.20.0.0/16 > broadcast: 172.20.255.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP UP IPv4 ENABLED > [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] TX > IGMP_MEMBERSHIP_QUERY from 172.20.16.199 to 224.0.0.1 > [ 2005/03/15 18:34:53 INFO xorp_igmp MLD6IGMP ] Started vif: eth1 > [ 2005/03/15 18:34:53 INFO xorp_rtrmgr:2657 RTRMGR +356 > module_manager.cc run ] Running module: pimsm4 > (/usr/local/xorp/pim/xorp_pimsm4) > [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_MEMBERSHIP_QUERY from 192.168.0.199 to 224.0.0.1 on vif eth0 > [ 2005/03/15 18:34:53 WARNING xorp_rtrmgr:2657 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. > [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.199 to 224.0.0.251 on vif eth0 > [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_MEMBERSHIP_QUERY from 172.20.16.199 to 224.0.0.1 on vif eth1 > [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.199 to 224.0.0.2 on vif eth0 > [ 2005/03/15 18:34:53 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.2 on vif eth1 > [ 2005/03/15 18:34:54 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 > finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for > finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target > is not enabled. > [ 2005/03/15 18:34:55 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 > finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for > finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target > is not enabled. > [ 2005/03/15 18:34:56 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 > finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for > finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target > is not enabled. > [ 2005/03/15 18:34:57 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.1 to 239.255.255.250 on vif eth0 > [ 2005/03/15 18:34:57 WARNING xorp_rtrmgr:2657 XrlFinderTarget +406 > finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for > finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target > is not enabled. > [ 2005/03/15 18:34:58 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.251 on vif eth1 > [ 2005/03/15 18:34:58 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: > >finder://PIMSM_4/pim/0.1/start_pim< > [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] New vif: Vif[eth0] > pif_index: 0 vif_index: 0 addr: 192.168.0.199 subnet: 192.168.0.0/24 > broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP > [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] New vif: Vif[eth1] > pif_index: 0 vif_index: 1 addr: 172.20.16.199 subnet: 172.20.0.0/16 > broadcast: 172.20.255.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP > [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] New vif: Vif[register_vif] > pif_index: 0 vif_index: 2 addr: 172.20.16.199 subnet: 172.20.16.199/32 > broadcast: 172.20.16.199 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP > [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] Enabled vif: eth1 > [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] STARTING Vif[eth1] > pif_index: 0 vif_index: 1 addr: 172.20.16.199 subnet: 172.20.0.0/16 > broadcast: 172.20.255.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP UP IPv4 ENABLED > [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] Started vif: eth1 > [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] Enabled vif: register_vif > [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] STARTING Vif[register_vif] > pif_index: 0 vif_index: 2 addr: 172.20.16.199 subnet: 172.20.16.199/32 > broadcast: 172.20.16.199 peer: 0.0.0.0 Flags: PIM_REGISTER > UNDERLYING_VIF_UP UP IPv4 ENABLED > [ 2005/03/15 18:34:59 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.13 on vif eth1 > [ 2005/03/15 18:34:59 INFO xorp_pimsm4 PIM ] Started vif: register_vif > [ 2005/03/15 18:35:00 INFO xorp_rtrmgr:2657 RTRMGR +1366 task.cc > run_task ] No more tasks to run > [ 2005/03/15 18:35:00 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.13 on vif eth1 > [ 2005/03/15 18:35:01 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 172.20.16.199 to 224.0.0.13 on vif eth1 > [ 2005/03/15 18:35:02 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.199 to 224.0.0.2 on vif eth0 > [ 2005/03/15 18:35:02 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.2 on vif eth1 > [ 2005/03/15 18:35:06 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.13 on vif eth1 > [ 2005/03/15 18:35:08 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.2 on vif eth1 > [ 2005/03/15 18:35:11 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.199 to 224.0.0.2 on vif eth0 > [ 2005/03/15 18:35:16 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.22 to 224.0.55.55 on vif eth1 > [ 2005/03/15 18:35:16 TRACE xorp_pimsm4 PIM ] Add membership for > (0.0.0.0,224.0.55.55) on vif eth1 > [ 2005/03/15 18:35:19 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.22 to 224.0.55.55 on vif eth1 > [ 2005/03/15 18:35:20 TRACE xorp_fea MFEA ] RX kernel signal: > message_type = 1 vif_index = 0 src = 192.168.0.2 dst = 224.0.55.55 > [ 2005/03/15 18:35:20 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from > MFEA_4: vif_index = 0 src = 192.168.0.2 dst = 224.0.55.55 > [ 2005/03/15 18:35:24 TRACE xorp_igmp MLD6IGMP ] TX > IGMP_MEMBERSHIP_QUERY from 192.168.0.199 to 224.0.0.1 > [ 2005/03/15 18:35:24 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_MEMBERSHIP_QUERY from 192.168.0.199 to 224.0.0.1 on vif eth0 > [ 2005/03/15 18:35:24 TRACE xorp_igmp MLD6IGMP ] TX > IGMP_MEMBERSHIP_QUERY from 172.20.16.199 to 224.0.0.1 > [ 2005/03/15 18:35:24 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_MEMBERSHIP_QUERY from 172.20.16.199 to 224.0.0.1 on vif eth1 > [ 2005/03/15 18:35:25 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.13 on vif eth1 > [ 2005/03/15 18:35:25 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.2 on vif eth1 > [ 2005/03/15 18:35:27 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.199 to 224.0.0.2 on vif eth0 > [ 2005/03/15 18:35:27 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.22 to 224.0.55.55 on vif eth1 > [ 2005/03/15 18:35:28 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 172.20.16.199 to 224.0.0.251 on vif eth1 > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users@xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From fjvilanova@inf.ufrgs.br Fri Mar 18 14:20:53 2005 From: fjvilanova@inf.ufrgs.br (fjvilanova@inf.ufrgs.br) Date: Fri, 18 Mar 2005 11:20:53 -0300 Subject: [Xorp-users] telnet Message-ID: <1111155653.423ae3c559ee5@webmail.inf.ufrgs.br> Hi, can I have access via telnet to a xorp router (running on LiveCD)? How? tks Felipe Jung Vilanova ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From M.Handley@cs.ucl.ac.uk Fri Mar 18 14:51:32 2005 From: M.Handley@cs.ucl.ac.uk (Mark Handley) Date: Fri, 18 Mar 2005 14:51:32 +0000 Subject: [Xorp-users] telnet In-Reply-To: Your message of "Fri, 18 Mar 2005 11:20:53 -0300." <1111155653.423ae3c559ee5@webmail.inf.ufrgs.br> Message-ID: <30601.1111157492@aardvark.cs.ucl.ac.uk> >can I have access via telnet to a xorp router (running on LiveCD)? How? Not unless you roll your own LiveCD. Only ssh is supported on the one we distribute. - Mark From twike@ptd.net Wed Mar 23 05:11:11 2005 From: twike@ptd.net (Thomas R Wike) Date: Wed, 23 Mar 2005 00:11:11 -0500 Subject: [Xorp-users] Emulating multiple routers on the same host Message-ID: <4240FA6F.6000404@ptd.net> I have not yet attempted to compile or run XORP. I just have a question about a capability mentioned on the XORP Vision page on the website. I apologize if the answer is available somewhere I haven't looked yet, but I've tried looking through the FEA related stuff on the website and the XORP-users and XORP-hackers mailing lists without finding anything. (If the answer is in the Fine Manual, I'll gladly read it if you can point me to the right one.) The XORP Vision page mentions the ability to emulate multiple routers on the same host, saying this can be done if you modify the FEA. My question is how do you modify the FEA to do this? Do you have to hack code, or can this be done by configuration? From M.Handley@cs.ucl.ac.uk Wed Mar 23 09:43:36 2005 From: M.Handley@cs.ucl.ac.uk (Mark Handley) Date: Wed, 23 Mar 2005 09:43:36 +0000 Subject: [Xorp-users] Emulating multiple routers on the same host In-Reply-To: Your message of "Wed, 23 Mar 2005 00:11:11 EST." <4240FA6F.6000404@ptd.net> Message-ID: <23332.1111571016@aardvark.cs.ucl.ac.uk> >The XORP Vision page mentions the ability to emulate multiple routers on >the same host, saying this can be done if you modify the FEA. My >question is how do you modify the FEA to do this? Do you have to hack >code, or can this be done by configuration? Right now you'd have to hack code for it to be general. You could run multiple dummy FEA processes (each with its own finder and routing protocols) but there would be no way to exchange routing packets between the different virtual routers. As part of a project to implement IS-IS in XORP, I have a student who is looking to test his implementation by emulating multiple routers, so we've given some thought to how to make this work (but he was only looking at IS-IS). But right now, there's no code committed into CVS to do this. You can currently run multiple BGP instances on the same machine, as BGP uses TCP, and you can configure the peer address and port on a per-peer basis. So if you want to experiment with BGP, this is possible without code changes. But the resulting virtual routers won't actually forward packets to each other, so this is only useful for routing experiments, not a general solution. - Mark From atanu@ICSI.Berkeley.EDU Mon Mar 28 20:41:41 2005 From: atanu@ICSI.Berkeley.EDU (Atanu Ghosh) Date: Mon, 28 Mar 2005 12:41:41 -0800 Subject: [Xorp-users] Announcing XORP Release Candidate 1.1 Message-ID: <91277.1112042501@tigger.icir.org> On behalf of the entire XORP team, I'm delighted to announce the XORP 1.1 Release Candidate, which is now available from . Once the release candidate has proven to be stable, the actual 1.1 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. There are still a number of non-critical bugs that we know about which will not be addressed until the 1.2 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.1-RC (2005/03/24) ========================= ALL: - Numerous improvements, bug fixes and cleanup. - XORP now builds on amd64+OpenBSD-3.6-current. - The --enable-advanced-mcast-api flag to "./configure" has been replaced with the --disable-advanced-multicast-api flag. - Addition of support for code execution profiling. - Currently "gmake" does not build the regression tests. The command "gmake check" should be used to build and run the regression tests. - Addition of two new documents: * "An Introduction to Writing a XORP Process" * "XORP User Manual" CONFIGURATION: - All "enabled: true/false" XORP configuration flags are now renamed to "disable: false/true". - The syntax for configuring the IPv4/IPv6 forwarding has changed: OLD: fea { enable-unicast-forwarding4: true enable-unicast-forwarding6: true } NEW: fea { unicast-forwarding4 { disable: false } unicast-forwarding6 { disable: false } } - The syntax for configuring the AFI/SAFI combinations in BGP has changed: OLD: bgp { peer { enable-ipv4-multicast enable-ipv6-unicast enable-ipv6-multicast } } NEW: bgp { peer { ipv4-unicast: true ipv4-multicast: true ipv6-unicast: true ipv6-multicast: true } } The new syntax allows IPv4 unicast to be disabled which was not previously possible. LIBXORP: - Bug fix in ordering events scheduled at exactly the same time and expiring at exactly the same time. - Various improvements to the eventloop implementation. - Addition of a mechanism for buffered asynchronous reads and writes. LIBXIPC: - Addition of XRL pipelining support. - The Finder client address can be defined by the following variable in the environment: XORP_FINDER_CLIENT_ADDRESS. This re-enables communicating with remote XORP processes. - Various other improvements (including performance) and bug fixes. LIBFEACLIENT: - Few bug fixes. XRL: - No significant changes. RTRMGR: - Addition of a new rtrmgr template keyword: %deprecated: "Reason". This keyword can be used to deprecate old configuration statements. - Addition of a new rtrmgr keyword: %update. It is similar to %activate, and is called whenever the configuration in the subtree has changed. - Modification to the rtrmgr template semantics: the XRLs per template nodes are sent in the order those nodes are declared in the template files. Previously, the order was alphabetical (by the name of the template nodes). - Various other improvements and bug fixes. XORPSH: - Addition of a mechanism to track the status of the modules, and to provide operational commands for only those modules that are running. - Various other improvements and bug fixes. POLICY: - Initial implementation of a policy manager. It is still being tested, and should not be used. FEA/MFEA: - Implementation of Click FEA support. - Addition of support for discard interfaces and discard routes. - Addition of support for ACLs, though currently there is no mechanism to configure them through the XORP configuration file. - Initial support for raw sockets. - Various bug fixes, improvements and cleanup. RIB: - Bug fix in adding point-to-point network interfaces. - Removal of the old mechanism (ExportTable) for propagating the routes to the FEA and all other interested parties. - Removal of hard-wired "static" table. - Various other improvements and bug fixes. RIP: - MD5 authentication now works properly. Previously, it was generating the wrong signature. - Cisco compatibility bug fix. BGP: - Addition of support for creating IPv6 TCP connections. - Few bug fixes in the Multi-protocol support. - Major improvements to the flow control mechanism. - Various improvements and bug fixes. STATIC_ROUTES: - Addition of configuration support for interface-specific static routes. - Improvements in handling stored routes if they are affected by network interface information updates. - Addition of support for tracking the state of the relevant processes, and for graceful registering/deregistering with them. - Addition of support for better checking of the XRL error codes. - Few other improvements and bug fixes. MLD/IGMP: - Bug fix in updating the primary address of an interface. - Addition of support for tracking the state of the relevant processes, and for graceful registering/deregistering with them. - Addition of support for better checking of the XRL error codes. - Few other improvements and bug fixes. PIM-SM: - Bug fixes in handling the MRIB entries and MRIB-related state. - Bug fix in scheduling the internal PimMre tasks. - Bug fix in updating the primary address of an interface. - Bug fix in the computation of the checksum of PIM Register packages received from a Cisco router that itself is not spec-compliant in the checksum computation. - Addition of support for tracking the state of the relevant processes, and for graceful registering/deregistering with them. - Addition of support for better checking of the XRL error codes. - Various other bug fixes, improvements and cleanup. FIB2MRIB: - Bug fix in deleting the Fib2Mrib entries. - Improvements in handling stored routes if they are affected by network interface information updates. - Addition of support for tracking the state of the relevant processes, and for graceful registering/deregistering with them. - Addition of support for better checking of the XRL error codes. - Few other bug fixes and improvements. CLI: - Bug fix in auto-completion for sub-commands. - Few other bug fixes and improvements. 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. - The following compiler is known to be buggy, and should not be used to compile XORP: gcc34 (GCC) 3.4.0 20040310 (prerelease) [FreeBSD] A newer compiler such as the following should be used instead: gcc34 (GCC) 3.4.2 20040827 (prerelease) [FreeBSD] - If you run BGP, RIB, FIB2MRIB, and PIM-SM at the same time, the propagation latency for the BGP routes to reach the kernel is increased. We are investigating the problem. 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 - Using the rtrmgr "-r" command-line option to restart processes that have failed does not work if a process fails while being reconfigured via xorpsh. If that happens, the rtrmgr itself may coredump. Therefore, using the "-r" command-line option is not recommended! Also, note that a process that has been killed by SIGTERM or SIGKILL will not be restarted (this is a feature rather than a bug). Ideally, we want to monitor the processes status using the finder rather than the forked children process status, therefore in the future when we have a more robust implementation the "-r" switch will be removed and will be enabled by default. XORPSH: - 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 FEA/MFEA: - On Linux with kernel 2.6 (e.g., RedHat FC2 with kernel 2.6.5-1.358), some of the tests may fail (with or without an error message), but no coredump image. Some of those failures can be contributed to a kernel problem. E.g., running "dmesg can show kernel "Oops" messages like: Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: 02235532 *pde = 00000000 Oops: 0000 [#15] CPU: 0 EIP: 0060:[<02235532>] Not tainted EFLAGS: 00010202 (2.6.5-1.358) EIP is at __dev_get_by_index+0x14/0x2b eax: 022db854 ebx: 1ae7aef8 ecx: 00000001 edx: 00000000 esi: 00000000 edi: 00008910 ebp: fee43e9c esp: 1ae7aef0 ds: 007b es: 007b ss: 0068 Process test_finder_eve (pid: 2026, threadinfo=1ae7a000 task=1406d7b0) Stack: 022365c7 00000000 009caffc 009cc780 0969ef28 fee43edc 00000001 009cc780 0969ef28 fee43ed8 00008910 00000000 00008910 fee43e9c 02236e50 fee43e9c 07aa4e00 3530355b 5d303637 00000000 0227a55b 021536b6 022cfa00 00000001 Call Trace: [<022365c7>] dev_ifname+0x30/0x66 [<02236e50>] dev_ioctl+0x83/0x283 [<0227a55b>] unix_create1+0xef/0xf7 [<021536b6>] alloc_inode+0xf9/0x175 [<0227c090>] unix_ioctl+0x72/0x7b [<022301a5>] sock_ioctl+0x268/0x280 [<0223054f>] sys_socket+0x2a/0x3d [<0214ea0e>] sys_ioctl+0x1f2/0x224 Code: 0f 18 02 90 2d 34 01 00 00 39 48 34 74 08 85 d2 89 d0 75 ea This appears to be a kernel bug triggered by ioctl(SIOCGIFNAME) which itself is called by if_indextoname(3). Currently, there is no known solution of the problem except to use a kernel that does not have the problem (at this stage it is not known whether all 2.6 Linux kernels are affected or only specific versions). It seems that a very similar problem has been reported to the Linux kernel developers, but the problem is still unsolved: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121697 RIB: - 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 future. RIP: - No known issues. BGP: - If the RIB bug above (failure to delete an existing route) is triggered by BGP, then the deletion failure error received by BGP from the RIB is considered by BGP as a fatal error. This is not a BGP problem, but a RIB problem that will be fixed in the future. - The BGP configuration mandates that an IPv4 nexthop must be supplied. Unfortunately it is necessary to provide an IPv4 nexthop even for an IPv6 only peering. Even more unfortunately it is not possible to force the IPv6 nexthop. - It is *essential* for an IPv6 peering that an IPv6 nexthop is provided. Unfortunately the configuration does not enforce this requrement. This will be fixed in the future. STATIC_ROUTES: - No known issues. 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 - On Linux, if the unicast Reverse Path Forwarding information is different from the multicast Reverse Path Forwarding information, the Reverse Path Filtering should be disabled. E.g., as root: echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter OR echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter echo 0 > /proc/sys/net/ipv4/conf/eth1/rp_filter ... Otherwise, the router will ignore packets if they don't arrive on the reverse-path interface. For more information about Reverse Path Filtering see http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.kernel.rpf.html FIB2MRIB: - No known issues. CLI: - No known issues. SNMP: - On some versions of Linux, there are some bugs in net-snmp versions 5.0.8 and 5.0.9, which prevent dynamic loading from working. See http://www.xorp.org/snmp.html for links to the net-snmp patches that solve the problems. - Version 5.1 of net-snmp requires a simple modification, otherwise XORP will fail to compile. See http://www.xorp.org/snmp.html for a link to the net-snmp patch that solves the problems. From fay@comreg.ru Wed Mar 30 08:08:23 2005 From: fay@comreg.ru (=?koi8-r?B?5M3J1NLJyiDi1drZy8nO?=) Date: Wed, 30 Mar 2005 12:08:23 +0400 Subject: [Xorp-users] Vlan 802.1q +fedora core Message-ID: <20050330080813.D1FA647062@mail.comreg.ru> Xorp can't resolv vlan name if it's name type DEV_PLUS_VID or DEV_PLUS_VID_NO_PAD. Default name-type for fedora DEV_PLUS_VID_NO_PAD. * name-type: VLAN_PLUS_VID (vlan0005), VLAN_PLUS_VID_NO_PAD (vlan5), DEV_PLUS_VID (eth0.0005), DEV_PLUS_VID_NO_PAD (eth0.5) From pavlin@icir.org Thu Mar 31 01:09:10 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 30 Mar 2005 17:09:10 -0800 Subject: [Xorp-users] Vlan 802.1q +fedora core In-Reply-To: Message from =?koi8-r?B?5M3J1NLJyiDi1drZy8nO?= of "Wed, 30 Mar 2005 12:08:23 +0400." <20050330080813.D1FA647062@mail.comreg.ru> Message-ID: <200503310109.j2V19ARH043367@possum.icir.org> > Xorp can't resolv vlan name if it's name type DEV_PLUS_VID or > DEV_PLUS_VID_NO_PAD. > > Default name-type for fedora DEV_PLUS_VID_NO_PAD. > > > > > * name-type: VLAN_PLUS_VID (vlan0005), VLAN_PLUS_VID_NO_PAD (vlan5), > DEV_PLUS_VID (eth0.0005), DEV_PLUS_VID_NO_PAD (eth0.5) Could you send some additional information about the problem, so we can try to replicate it. E.g., the command(s) you used to create the vlan, and the XORP configuration plus the error message you get. Also, what is the particular version of Fedora and the kernel you are using. Thanks, Pavlin