From bms at incunabulum.net Mon Jun 1 14:38:44 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 01 Jun 2009 22:38:44 +0100 Subject: [Xorp-users] Xorp system as DR in backbone = disaster In-Reply-To: <1B62E6082D9F034394DB2FBAC03D1A3860E7AB6DBC@lrccd-exch05.LRCCD.ad.losrios.edu> References: <1B62E6082D9F034394DB2FBAC03D1A3860E7AB6DB4@lrccd-exch05.LRCCD.ad.losrios.edu> <4A1FCC47.5010506@incunabulum.net> <1B62E6082D9F034394DB2FBAC03D1A3860E7AB6DBC@lrccd-exch05.LRCCD.ad.losrios.edu> Message-ID: <4A244A64.2040804@incunabulum.net> Mark, Thanks very much for your hard work, and diligence, in clarifying that this situation only arises when MD5 authentication is in use (off-list, Cc: ing list and Syed to pick up). Williams, Mark wrote: > The problem appears to be related to MD5 authentication on segments with multiple neighbors. When I have Xorp configured to use MD5 authentication, it will only peer with one other neighbor, even if the MD5 keys are correct on all systems. When the xorp system is the DR and I'm using MD5 authentication, problems arise. As soon as I turn MD5 off, all is well. > I have been busy finishing the Source-Specific Multicast (SSM) implementation (IGMPv3, MLDv2) in the FreeBSD kernel. This work should now be complete so I'll have more free time to look at XORP problems in detail for the time being. If you could raise a Bugzilla report that would be really helpful, as then we'll have audit trail to work from and work out why MD5 is breaking the DR behaviour. Off the top of my head, AreaRouter is probably the place to start looking. thanks, BMS From pcaldes at attglobal.net Mon Jun 1 16:40:48 2009 From: pcaldes at attglobal.net (pcaldes) Date: Mon, 01 Jun 2009 18:40:48 -0500 Subject: [Xorp-users] Using Xorp for PIM SSM Message-ID: <4A246700.7050205@attglobal.net> Our access router is not allowed to run IGMP and only PIM is enabled. Normally, we can connect our servers in the following manner: ( Cloud )-----PIM----[Cisco Access Router]-----PIM-----[Cisco Router]----IGMPv3----[ servers running IGMPv3 ] For some stupid reason they won't let us run IGMP on the Cisco Acess Router. Basically, we are trying to avoid having to install a Cisco Router to convert IGMPv3 <-> PIM between our CentOS server and the access router to save some $$$. We figure we should be able to run Xorp on one of the servers and it can convert IGMPv3 to PIM for other servers on the VLAN in addition to an IGMPv3 application on the same box ( Cloud )-----PIM----[Cisco Access Router]-----PIM---+-[Server1 with Xorp] | +----IGMPv3----[ servers running IGMPv3 ] Our servers are running CentOS 5.2/5.3 and one of them has Xorp Version 1.6 installed so we can talk PIM with the access router. Our software application (running on the same box as Xorp) uses SSM and issues IGMPv3 joins and we hoped that Xorp will take that and allow us to access multicast data on the other side of the access router. From the Cisco router, we can see the Xorp system show up as a neighbor: #sh ip pim neigh PIM Neighbor Table Neighbor Interface Uptime/Expires Ver DR Address Prio/Mode 10.96.114.33 FastEthernet1/1/0 7w0d/00:01:38 v2 1 / S 10.96.115.21 FastEthernet4/0/0 00:00:09/00:01:35 v2 1 / DR # The Xorp system and the other servers are on the VLAN subnet connected to FastEthernet4/0/0 on the Cisco router [Multicast Network]---PIM---[Cisco ACCESS ROUTER]---PIM---[XORP System] The Xorp router only needs to support SSM so no RP should be needed but we cannot get it to work. Hopefully it is just a configuration error. We know our applications send out IGMPv3 SSM joins since if we stop Xorp and enable IGMPv3 on the Cisco router, everything works. Also, is there a configuration command similar to Cisco's "ip pim ssm range" statement which allows you to specify non-standard SSM subnet ranges? Before we start XORP, we make sure to run: echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter Can you please look over my config file for any mistakes? All help is appreciated. Following is our Xorp config.boot file. interfaces { interface eth0 { /* Use the default setup as configured in the system */ description: "Public interface ETH0" default-system-config } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea4 { /* disable: false */ interface eth0 { vif eth0 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } traceoptions { flag all { disable: false } } } } protocols { igmp { /* disable: false */ interface eth0 { vif eth0 { version: 3 disable: false } } traceoptions { flag all { disable: false } } } } protocols { pimsm4 { interface eth0 { vif eth0 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } switch-to-spt-threshold { /* approx. 1K bytes/s (10Kbps) threshold */ disable: false interval: 100 bytes: 102400 } traceoptions { flag all { disable: false } } } } protocols { fib2mrib { disable: false } } Following are some of the IP addresses shown below 10.96.115.17 - Cisco Access Router 10.96.115.20 - CentOS 5.2 system with appl that issues IGMPv3 joins 10.96.115.21 - CentOS 5.2 system running Xorp that also has an appl that issues IGMPv3 joins. (10.97.116.117, 232.27.106.1) - Multicast SSM group (S,G) that we want to join. Following is the log output. [ 2009/06/01 17:56:06 INFO xorp_rtrmgr:7078 RTRMGR +249 master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea, mfea4, rib, fib2mrib, igmp, pimsm4 [ 2009/06/01 17:56:06 INFO xorp_rtrmgr:7078 RTRMGR +101 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2009/06/01 17:56:07 INFO xorp_fea MFEA ] MFEA enabled [ 2009/06/01 17:56:07 INFO xorp_fea MFEA ] CLI enabled [ 2009/06/01 17:56:07 INFO xorp_fea MFEA ] CLI started [ 2009/06/01 17:56:07 INFO xorp_fea MFEA ] MFEA enabled [ 2009/06/01 17:56:07 INFO xorp_fea MFEA ] CLI enabled [ 2009/06/01 17:56:07 INFO xorp_fea MFEA ] CLI started [ 2009/06/01 17:56:08 INFO xorp_rtrmgr:7078 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) [ 2009/06/01 17:56:12 INFO xorp_rtrmgr:7078 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2009/06/01 17:56:18 INFO xorp_rtrmgr:7078 RTRMGR +101 module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea) [ 2009/06/01 17:56:18 INFO xorp_fea MFEA ] Interface added: Vif[eth0] pif_index: 4 vif_index: 0 addr: 10.96.115.21 subnet: 10.96.115.16/28 broadcast: 10.96.115.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/06/01 17:56:18 INFO xorp_fea MFEA ] MFEA started [ 2009/06/01 17:56:18 INFO xorp_fea MFEA ] Interface enabled Vif[eth0] pif_index: 4 vif_index: 0 addr: 10.96.115.21 subnet: 10.96.115.16/28 broadcast: 10.96.115.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/06/01 17:56:18 INFO xorp_fea MFEA ] Interface started: Vif[eth0] pif_index: 4 vif_index: 0 addr: 10.96.115.21 subnet: 10.96.115.16/28 broadcast: 10.96.115.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/06/01 17:56:18 INFO xorp_fea MFEA ] Interface added: Vif[register_vif] pif_index: 4 vif_index: 1 addr: 10.96.115.21 subnet: 10.96.115.21/32 broadcast: 10.96.115.21 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 [ 2009/06/01 17:56:18 INFO xorp_fea MFEA ] Interface enabled Vif[register_vif] pif_index: 4 vif_index: 1 addr: 10.96.115.21 subnet: 10.96.115.21/32 broadcast: 10.96.115.21 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/06/01 17:56:18 INFO xorp_fea MFEA ] Interface started: Vif[register_vif] pif_index: 4 vif_index: 1 addr: 10.96.115.21 subnet: 10.96.115.21/32 broadcast: 10.96.115.21 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/06/01 17:56:18 INFO xorp_rtrmgr:7078 RTRMGR +101 module_manager.cc execute ] Executing module: rib (rib/xorp_rib) [ 2009/06/01 17:56:20 INFO xorp_rtrmgr:7078 RTRMGR +101 module_manager.cc execute ] Executing module: fib2mrib (fib2mrib/xorp_fib2mrib) [ 2009/06/01 17:56:22 INFO xorp_rtrmgr:7078 RTRMGR +101 module_manager.cc execute ] Executing module: igmp (mld6igmp/xorp_igmp) [ 2009/06/01 17:56:22 WARNING xorp_rtrmgr:7078 XrlFinderTarget +407 ../xrl/targets/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. [ 2009/06/01 17:56:22 INFO xorp_igmp MLD6IGMP ] Protocol enabled [ 2009/06/01 17:56:22 INFO xorp_igmp MLD6IGMP ] CLI enabled [ 2009/06/01 17:56:22 INFO xorp_igmp MLD6IGMP ] CLI started [ 2009/06/01 17:56:23 INFO xorp_igmp MLD6IGMP ] Protocol started [ 2009/06/01 17:56:23 INFO xorp_igmp MLD6IGMP ] Interface added: Vif[eth0] pif_index: 4 vif_index: 0 addr: 10.96.115.21 subnet: 10.96.115.16/28 broadcast: 10.96.115.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/06/01 17:56:24 INFO xorp_igmp MLD6IGMP ] Interface enabled: Vif[eth0] pif_index: 4 vif_index: 0 addr: 10.96.115.21 subnet: 10.96.115.16/28 broadcast: 10.96.115.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/06/01 17:56:24 INFO xorp_igmp MLD6IGMP ] Interface started: Vif[eth0] pif_index: 4 vif_index: 0 addr: 10.96.115.21 subnet: 10.96.115.16/28 broadcast: 10.96.115.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/06/01 17:56:24 INFO xorp_rtrmgr:7078 RTRMGR +101 module_manager.cc execute ] Executing module: pimsm4 (pim/xorp_pimsm4) [ 2009/06/01 17:56:24 WARNING xorp_rtrmgr:7078 XrlFinderTarget +407 ../xrl/targets/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. [ 2009/06/01 17:56:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:24 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.22) on vif eth0 [ 2009/06/01 17:56:24 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.2) on vif eth0 [ 2009/06/01 17:56:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.21 to 224.0.0.1 on vif eth0 [ 2009/06/01 17:56:24 INFO xorp_pimsm4 PIM ] Protocol enabled [ 2009/06/01 17:56:24 INFO xorp_pimsm4 PIM ] CLI enabled [ 2009/06/01 17:56:24 INFO xorp_pimsm4 PIM ] CLI started [ 2009/06/01 17:56:25 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:25 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:56:25 INFO xorp_pimsm4 PIM ] Protocol started [ 2009/06/01 17:56:25 INFO xorp_pimsm4 PIM ] Interface added: Vif[eth0] pif_index: 4 vif_index: 0 addr: 10.96.115.21 subnet: 10.96.115.16/28 broadcast: 10.96.115.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/06/01 17:56:25 INFO xorp_pimsm4 PIM ] Interface added: Vif[register_vif] pif_index: 0 vif_index: 1 addr: 10.96.115.21 subnet: 10.96.115.21/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 [ 2009/06/01 17:56:26 INFO xorp_pimsm4 PIM ] Interface enabled: Vif[eth0] pif_index: 4 vif_index: 0 addr: 10.96.115.21 subnet: 10.96.115.16/28 broadcast: 10.96.115.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/06/01 17:56:26 INFO xorp_pimsm4 PIM ] Interface started: Vif[eth0] pif_index: 4 vif_index: 0 addr: 10.96.115.21 subnet: 10.96.115.16/28 broadcast: 10.96.115.31 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/06/01 17:56:26 INFO xorp_pimsm4 PIM ] Interface enabled: Vif[register_vif] pif_index: 0 vif_index: 1 addr: 10.96.115.21 subnet: 10.96.115.21/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/06/01 17:56:26 INFO xorp_pimsm4 PIM ] Interface started: Vif[register_vif] pif_index: 0 vif_index: 1 addr: 10.96.115.21 subnet: 10.96.115.21/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED [ 2009/06/01 17:56:26 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:56:26 INFO xorp_rtrmgr:7078 RTRMGR +2233 task.cc run_task ] No more tasks to run [ 2009/06/01 17:56:26 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:26 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.13) on vif eth0 [ 2009/06/01 17:56:28 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:28 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:28 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0.5) on vif eth0 [ 2009/06/01 17:56:30 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.96.115.21 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:56:30 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.96.115.17 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:56:30 TRACE xorp_pimsm4 PIM ] Added new neighbor 10.96.115.17 on vif eth0 [ 2009/06/01 17:56:30 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.96.115.21 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:56:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:39 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 224.0.0.1 on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 232.27.106.1 on vif eth0 [ 2009/06/01 17:56:45 WARNING xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 232.27.106.1 on vif eth0: this interface is in IGMPv3 mode, but received IGMPv2 message [ 2009/06/01 17:56:45 WARNING xorp_igmp MLD6IGMP ] Please configure properly all routers on that subnet to use same IGMP version [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 232.27.106.1) on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:56:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:56:45 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0, 232.27.106.1) on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:56:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:56:45 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:56:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:56:46 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:47 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:49 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:56:59 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.96.115.17 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:57:00 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.96.115.21 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 232.27.106.1 on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:15 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:57:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:15 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:57:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:15 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:57:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:15 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:15 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:57:16 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:17 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:23 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:26 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:57:29 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.96.115.17 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:57:30 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.96.115.21 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:57:39 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 224.0.0.1 on vif eth0 [ 2009/06/01 17:57:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 232.27.106.1 on vif eth0 [ 2009/06/01 17:57:45 WARNING xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 232.27.106.1 on vif eth0: this interface is in IGMPv3 mode, but received IGMPv2 message [ 2009/06/01 17:57:45 WARNING xorp_igmp MLD6IGMP ] Please configure properly all routers on that subnet to use same IGMP version [ 2009/06/01 17:57:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:45 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:45 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:57:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:45 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:45 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:57:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:45 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:45 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:57:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.11 5.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:45 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:45 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:57:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:57:46 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:47 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:48 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:57:59 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.96.115.17 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:58:00 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.96.115.21 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 232.27.106.1 on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:15 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:58:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:15 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:58:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:15 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:58:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:15 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:15 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:58:20 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:22 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:26 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:58:29 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.96.115.17 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:58:30 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.96.115.21 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:58:39 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 224.0.0.1 on vif eth0 [ 2009/06/01 17:58:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 232.27.106.1 on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:58:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:58:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:58:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:45 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:58:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:58:47 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:48 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:51 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:58:59 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.96.115.17 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:59:00 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.96.115.21 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 232.27.106.1 on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:15 WARNING xorp_p imsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:15 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:15 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:15 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:16 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:26 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:59:29 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.96.115.17 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:59:30 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.96.115.21 to 224.0.0.13 on vif eth0 [ 2009/06/01 17:59:39 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 224.0.0.1 on vif eth0 [ 2009/06/01 17:59:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.96.115.17 to 232.27.106.1 on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_pimsm4 PIM ] Delete membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = true: RP for group 232.27.106.1: not found [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:45 TRACE xorp_pimsm4 PIM ] Add membership for (10.97.116.117, 232.27.106.1) on vif eth0 [ 2009/06/01 17:59:45 WARNING xorp_pimsm4 PIM ] PruneDesired(S,G,rpt) = false: RP for group 232.27.106.1: not found [ 2009/06/01 17:59:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.21 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:46 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:46 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.96.115.20 to 224.0.0.22 on vif eth0 [ 2009/06/01 17:59:59 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.96.115.17 to 224.0.0.13 on vif eth0 [ 2009/06/01 18:00:00 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.96.115.21 to 224.0.0.13 on vif eth0 From bms at incunabulum.net Tue Jun 2 08:11:40 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Tue, 02 Jun 2009 16:11:40 +0100 Subject: [Xorp-users] Using Xorp for PIM SSM In-Reply-To: <4A246700.7050205@attglobal.net> References: <4A246700.7050205@attglobal.net> Message-ID: <4A25412C.8040402@incunabulum.net> Hi, Thanks for your question regarding XORP's PIM-SM implementation. pcaldes wrote: > ... > We figure we should be able to run Xorp on one of the servers and it can > convert IGMPv3 to PIM > for other servers on the VLAN in addition to an IGMPv3 application on > the same box > I believe that should work. I should point out that XORP does not currently support IGMP proxy mode functionality, so if you intend to use XORP as the multicast topology intermediate hop, running PIM-SM is the only option supported. ... > > > The Xorp router only needs to support SSM so no RP should be needed but > we cannot get it to work. > Hopefully it is just a configuration error. > I believe this is a limitation of the configuration options for XORP's PIM-SM implementation. Not knowing the inner workings in detail, I can't say for sure -- I believe it assumes engineers will be deploying both ASM and SSM models, therefore an RP is required. A static RP configuration should be fine, providing it doesn't clash with an existing RP in the PIM-SM domain. > We know our applications send out IGMPv3 SSM joins since if we stop Xorp > and enable IGMPv3 on the Cisco router, everything works. > > Also, is there a configuration command similar to Cisco's "ip pim ssm > range" statement which allows > you to specify non-standard SSM subnet ranges? > > Unfortunately no, I believe this is a limitation of the current implementation for much the same reasons. I am sure this functionality can be added given xorp_pim's decent C++ abstractions. > Before we start XORP, we make sure to run: > > echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter > Just as an aside: I see this is recommended in the XORP User Manual. I believe this is conceptually similar to FreeBSD's net.inet.ip.check_interface feature, however I believe Linux doesn't fully implement the RFC 1122 Strong End-Station model for the same software stack limitations as FreeBSD has. I'd be curious to know why. > > > Can you please look over my config file for any mistakes? > All help is appreciated. > Your configuration looks OK, apart from the fact that there is no cand-rp or bootstrap blocks in the pim configuration block. I believe that the quickest way to resolve your issue may be to just add a cand-rp block to the XORP configuration with a scope-zone for the SSM range you intend to use, even though SSM actually requires no RP, unlike the ASM model. thanks, BMS From pcaldes at attglobal.net Tue Jun 2 09:02:09 2009 From: pcaldes at attglobal.net (pcaldes) Date: Tue, 02 Jun 2009 11:02:09 -0500 Subject: [Xorp-users] Using Xorp for PIM SSM In-Reply-To: <4A25412C.8040402@incunabulum.net> References: <4A246700.7050205@attglobal.net> <4A25412C.8040402@incunabulum.net> Message-ID: <4A254D01.9030409@attglobal.net> Bruce Simpson wrote: > Hi, > > Thanks for your question regarding XORP's PIM-SM implementation. > > pcaldes wrote: >> ... >> We figure we should be able to run Xorp on one of the servers and it >> can convert IGMPv3 to PIM >> for other servers on the VLAN in addition to an IGMPv3 application on >> the same box >> > > I believe that should work. I should point out that XORP does not > currently support IGMP proxy mode functionality, so if you intend to > use XORP as the multicast topology intermediate hop, running PIM-SM is > the only option supported. > > ... >> >> The Xorp router only needs to support SSM so no RP should be needed >> but we cannot get it to work. >> Hopefully it is just a configuration error. >> > > I believe this is a limitation of the configuration options for XORP's > PIM-SM implementation. Not knowing the inner workings in detail, I > can't say for sure -- I believe it assumes engineers will be deploying > both ASM and SSM models, therefore an RP is required. > > A static RP configuration should be fine, providing it doesn't clash > with an existing RP in the PIM-SM domain. > >> We know our applications send out IGMPv3 SSM joins since if we stop Xorp >> and enable IGMPv3 on the Cisco router, everything works. >> >> Also, is there a configuration command similar to Cisco's "ip pim ssm >> range" statement which allows >> you to specify non-standard SSM subnet ranges? >> >> > > Unfortunately no, I believe this is a limitation of the current > implementation for much the same reasons. I am sure this > functionality can be added given xorp_pim's decent C++ abstractions. > >> Before we start XORP, we make sure to run: >> >> echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter >> > > Just as an aside: I see this is recommended in the XORP User Manual. > > I believe this is conceptually similar to FreeBSD's > net.inet.ip.check_interface feature, however I believe Linux doesn't > fully implement the RFC 1122 Strong End-Station model for the same > software stack limitations as FreeBSD has. I'd be curious to know why. > >> >> >> Can you please look over my config file for any mistakes? >> All help is appreciated. >> > > Your configuration looks OK, apart from the fact that there is no > cand-rp or bootstrap blocks in the pim configuration block. > > I believe that the quickest way to resolve your issue may be to just > add a cand-rp block to the XORP configuration with a scope-zone for > the SSM range you intend to use, even though SSM actually requires no > RP, unlike the ASM model. > > thanks, > BMS > In our initial configuration we had added the following bootstrap config from a sample multicast config we found: bootstrap { disable: false 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" } } } However, this made us become the RP for other multicast traffic in the network which caused some trouble in our network and headaches for us. The problem is that we don't know in advance what the SSM groups we need to join. It is dynamic. While we could change the group-prefix under cand-rp{} to 232.0.0.0/8 to limit us to the default SSM range, I do not know feel I am knowledgeable about the ramifications of doing that since it might still affect other multicast traffic in the cloud. And I don't want to have to explain ... again .... why I interrupted our customer traffic.... again. Hopefully someone who knows more about the Xorp SSM internals can let us know if there is another workaround or how difficult it might be to fix. Do you think I should repost my original email to the xorp-hackers list? I assumed they also read xorp-users and didn't want to crosspost. From robertwerutsky at gmail.com Wed Jun 3 06:08:06 2009 From: robertwerutsky at gmail.com (Robert Werutsky) Date: Wed, 3 Jun 2009 10:08:06 -0300 Subject: [Xorp-users] problem with vif Message-ID: I'm trying to set up the xorp router with 2 virtual interfaces I have added them on my ubuntu and ifconfig returns: eth1 Link encap:Ethernet HWaddr 00:16:76:13:55:42 inet addr:172.20.5.37 Bcast:172.20.5.255 Mask:255.255.254.0 inet6 addr: fe80::216:76ff:fe13:5542/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8556 errors:0 dropped:0 overruns:0 frame:0 TX packets:5859 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:4764766 (4.5 MB) TX bytes:1366801 (1.3 MB) Base address:0x1000 Memory:93200000-93220000 eth1:0 Link encap:Ethernet HWaddr 00:16:76:13:55:42 inet addr:172.20.100.100 Bcast:172.20.101.255 Mask:255.255.254.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Base address:0x1000 Memory:93200000-93220000 eth1:2 Link encap:Ethernet HWaddr 00:16:76:13:55:42 inet addr:172.20.130.130 Bcast:172.20.131.255 Mask:255.255.254.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Base address:0x1000 Memory:93200000-93220000 my xorp config.boot: interfaces { interface eth1 { description: "data interface" disable: false vif eth0 { disable: false address 172.20.100.100 { prefix-length: 23 broadcast: 172.20.101.255 disable: false } } vif eth2 { disable: false address 172.20.130.130 { prefix-length: 23 broadcast: 172.20.132.255 disable: false } } } } but when I try to run xorp I get this: [ 2009/06/03 10:03:37 ERROR xorp_fea:7165 FEA +207 ifconfig_set.cc push_config ] Interface/Vif error on eth1/eth0: bad vif name [ 2009/06/03 10:03:37 WARNING xorp_fea XrlFeaTarget ] Handling method for ifmgr/0.1/commit_transaction failed: XrlCmdError 102 Command failed Interface/Vif error on eth1/eth0: bad vif name [ 2009/06/03 10:03:37 ERROR xorp_rtrmgr:7164 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Interface/Vif error on eth1/eth0: bad vif name [ 2009/06/03 10:03:37 ERROR xorp_rtrmgr:7164 RTRMGR +261 master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Interface/Vif error on eth1/eth0: bad vif name [ 2009/06/03 10:03:37 INFO xorp_rtrmgr:7164 RTRMGR +2233 task.cc run_task ] No more tasks to run why ??? what's wrong ?? I can ping the vifs, they seem ok -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090603/86e9574f/attachment.html From rays at maine.edu Thu Jun 4 07:15:00 2009 From: rays at maine.edu (Soucy, Ray) Date: Thu, 4 Jun 2009 10:15:00 -0400 Subject: [Xorp-users] XORP problems at boot Message-ID: <36243D984F88BA4ABD1E0EFC1E61B989796B8F@fudd.ad.maine.edu> Hi, When I run XORP at boot (as part of init) the log fills up with these messages: [ 2009/06/03 15:59:18 ?WARNING xorp_rtrmgr:1552 LIBXORP +94 eventloop.cc run ] 57601 seconds between calls to EventLoop::run [ 2009/06/03 15:59:18 ?WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.955934 seconds [ 2009/06/03 15:59:18 ?WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.940032 seconds [ 2009/06/03 15:59:18 ?WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.883755 seconds --8<-- These messages go on for 470,716 lines within a few min. If I kill XORP and restart it, or manually start it after the system is booted, I don't see these messages and XORP has no problems. Anyone else ever see this? I've also found that XORP will crash on boot if the interfaces it is trying to configure are not plugged in, is there a fix to this? Ray Soucy Communications Specialist +1 (207) 561-3526 Communications and Network Services University of Maine System http://www.maine.edu/ From bms at incunabulum.net Thu Jun 4 09:30:30 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 04 Jun 2009 17:30:30 +0100 Subject: [Xorp-users] Using Xorp for PIM SSM In-Reply-To: <4A254D01.9030409@attglobal.net> References: <4A246700.7050205@attglobal.net> <4A25412C.8040402@incunabulum.net> <4A254D01.9030409@attglobal.net> Message-ID: <4A27F6A6.8030500@incunabulum.net> pcaldes wrote: > ... > The problem is that we don't know in advance what the SSM groups we > need to join. It is dynamic. > While we could change the group-prefix under cand-rp{} to 232.0.0.0/8 > to limit us to the default SSM range, > I do not know feel I am knowledgeable about the ramifications of doing > that since it might still affect other multicast traffic in the cloud. I agree, this is undesirable for many reasons. It's a difficult one. 232/8 is the RFC 3171 SSM range. In theory if everything in your PIM domain is playing by the rules, advertising RP role for that range shouldn't matter, providing you tweak rp-priority as low as it can go. Of course, if you use the administrative scope 239/8, this should be filtered at PIM domain borders anyway, assuming carrier follows best practice. However this isn't exclusively an SSM range. > And I don't want to have to explain ... again .... why I interrupted > our customer traffic.... again. > > > Hopefully someone who knows more about the Xorp SSM internals can let > us know if there is another workaround or how difficult it might be to > fix. It's not really my call to say if it is behaving to spec or not at the moment... but I agree the issue needs to be revisited. I'm not familiar enough with the PIM code to say whether a simple solution is feasible or not. If you can raise a Bugzilla ticket about the 'ip pim ssm range' functionality being missing, that would be very helpful. > > Do you think I should repost my original email to the xorp-hackers > list? I assumed they also read xorp-users and didn't want to crosspost. > You will probably just get me again :-) cheers, BMS From bms at incunabulum.net Thu Jun 4 09:32:01 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 04 Jun 2009 17:32:01 +0100 Subject: [Xorp-users] problem with vif In-Reply-To: References: Message-ID: <4A27F701.2030406@incunabulum.net> Robert Werutsky wrote: > I'm trying to set up the xorp router with 2 virtual interfaces > I have added them on my ubuntu and ifconfig returns: > > eth1 Link encap:Ethernet HWaddr 00:16:76:13:55:42 > inet addr:172.20.5.37 Bcast:172.20.5.255 Mask:255.255.254.0 > inet6 addr: fe80::216:76ff:fe13:5542/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:8556 errors:0 dropped:0 overruns:0 frame:0 > TX packets:5859 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:4764766 (4.5 MB) TX bytes:1366801 (1.3 MB) > Base address:0x1000 Memory:93200000-93220000 > > eth1:0 Link encap:Ethernet HWaddr 00:16:76:13:55:42 > inet addr:172.20.100.100 Bcast:172.20.101.255 > Mask:255.255.254.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Base address:0x1000 Memory:93200000-93220000 > > eth1:2 Link encap:Ethernet HWaddr 00:16:76:13:55:42 > inet addr:172.20.130.130 Bcast:172.20.131.255 > Mask:255.255.254.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Base address:0x1000 Memory:93200000-93220000 > > I think you need to declare these as being *addresses*, not *vifs* of eth1. Here there is only one interface/vif: eth1/eth1. The eth1:0 and eth1:2 aliases are misnomers, you need to name each statically configured address in a single vif { } block. thanks, BMS From bms at incunabulum.net Thu Jun 4 09:35:29 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 04 Jun 2009 17:35:29 +0100 Subject: [Xorp-users] XORP problems at boot In-Reply-To: <36243D984F88BA4ABD1E0EFC1E61B989796B8F@fudd.ad.maine.edu> References: <36243D984F88BA4ABD1E0EFC1E61B989796B8F@fudd.ad.maine.edu> Message-ID: <4A27F7D1.9080008@incunabulum.net> Soucy, Ray wrote: > Hi, > > When I run XORP at boot (as part of init) the log fills up with these messages: > > [ 2009/06/03 15:59:18 WARNING xorp_rtrmgr:1552 LIBXORP +94 eventloop.cc run ] 57601 seconds between calls to EventLoop::run > [ 2009/06/03 15:59:18 WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.955934 seconds > [ 2009/06/03 15:59:18 WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.940032 seconds > [ 2009/06/03 15:59:18 WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.883755 seconds > > --8<-- > > These messages go on for 470,716 lines within a few min. > > If I kill XORP and restart it, or manually start it after the system > is booted, I don't see these messages and XORP has no problems. > Anyone else ever see this? > Is the host you're running XORP on NTP synchronized? How fast is the host? Which OS/version is it running? Does the output of the 'uptime' shell command change during system boot significantly? You should only see these messages if there's a timing problem. I refactored the code involved some time ago to use POSIX CLOCK_MONOTONIC, as there was a classic problem with the EventLoop being blown away as it used to depend on wallclock time. If your system doesn't support CLOCK_MONOTONIC then XORP will fall back to the wallclock time as the time base. If it does, then this shouldn't ever be an issue -- unless your OS does something to CLOCK_MONOTONIC. From jtc at acorntoolworks.com Thu Jun 4 09:40:44 2009 From: jtc at acorntoolworks.com (J.T. Conklin) Date: Thu, 04 Jun 2009 09:40:44 -0700 Subject: [Xorp-users] XORP problems at boot In-Reply-To: <36243D984F88BA4ABD1E0EFC1E61B989796B8F@fudd.ad.maine.edu> (Ray Soucy's message of "Thu, 4 Jun 2009 10:15:00 -0400") References: <36243D984F88BA4ABD1E0EFC1E61B989796B8F@fudd.ad.maine.edu> Message-ID: <87y6s8hrzn.fsf@orac.acorntoolworks.com> "Soucy, Ray" writes: > When I run XORP at boot (as part of init) the log fills up with these messages: > > [ 2009/06/03 15:59:18 ?WARNING xorp_rtrmgr:1552 LIBXORP +94 eventloop.cc run ] 57601 seconds between calls to EventLoop::run > [ 2009/06/03 15:59:18 ?WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.955934 seconds > [ 2009/06/03 15:59:18 ?WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.940032 seconds > [ 2009/06/03 15:59:18 ?WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.883755 seconds > > --8<-- > > These messages go on for 470,716 lines within a few min. > > If I kill XORP and restart it, or manually start it after the system > is booted, I don't see these messages and XORP has no problems. > > Anyone else ever see this? What system are you running XORP on? >From the log messages, it says that the event loop hasn't been run in 16 hours. I tend to doubt that's the case. Is there something in your boot process that resets the clock after XORP has been started? --jtc -- J.T. Conklin From ddavid.santiago at gmail.com Thu Jun 4 10:23:35 2009 From: ddavid.santiago at gmail.com (David Santiago Santos) Date: Thu, 4 Jun 2009 14:23:35 -0300 Subject: [Xorp-users] Error tryng to launch Net-SNMP via the router manager Message-ID: Hello, I installed the XORP 1.6 and Net-SNMP 5.4.1. Therefore, both of them were compiled without errors. Although I did the configurations according to the XORP manual, I got an erro tryng to launch it. Below is the output when I run the command shell "sudo xorp_rtrmgr": [ 2009/06/04 14:18:49 INFO xorp_rtrmgr:8376 RTRMGR +239 master_conf_tree.cc execute ] Changed modules: interfaces, xorp_if_mib, fea, rib, fib2mrib, policy, static_routes [ 2009/06/04 14:18:49 INFO xorp_rtrmgr:8376 RTRMGR +96 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] MFEA enabled [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] CLI enabled [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] CLI started [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] MFEA enabled [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] CLI enabled [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] CLI started [ 2009/06/04 14:18:51 INFO xorp_rtrmgr:8376 RTRMGR +96 module_manager.cc execute ] Executing module: xorp_if_mib (mibs/snmpdscripts/startsnmp) No log handling enabled - turning on stderr logging registered debug token xorp_if_mib_module, 1 registered debug token dlmod, 1 registered debug token usmUser, 1 netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load() netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load() netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load() dlmod: register mib dlmod: dlmod_path: /usr/local/lib/snmp/dlmod dlmod: dlmod_create_module dlmod: dlmod_load_module xorp_if_mib_module: /usr/local/xorp/mibs/xorp_if_mib_module.so xorp_if_mib_module: XorpIfMib created xorp_if_mib_module: Initialized... Error opening specified endpoint "" Server Exiting with code 1 xorp_if_mib_module: XorpIfMib destroyed [ 2009/06/04 14:18:51 ERROR xorp_rtrmgr:8376 RTRMGR +747 module_manager.cc done_cb ] Command "/usr/lib/xorp/mibs/snmpdscripts/startsnmp": exited with exit status 1. [ 2009/06/04 14:18:51 INFO xorp_rtrmgr:8376 RTRMGR +318 module_manager.cc module_exited ] Module abnormal exit: xorp_if_mib [ 2009/06/04 14:18:53 WARNING xorp_rtrmgr:8376 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does not exist or is not enabled. [ 2009/06/04 14:18:54 WARNING xorp_rtrmgr:8376 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does not exist or is not enabled. [ 2009/06/04 14:18:55 WARNING xorp_rtrmgr:8376 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does not exist or is not enabled. [ 2009/06/04 14:18:56 WARNING xorp_rtrmgr:8376 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does not exist or is not enabled. [ 2009/06/04 14:18:57 INFO xorp_rtrmgr:8376 RTRMGR +2228 task.cc run_task ] No more tasks to run [ 2009/06/04 14:18:57 INFO xorp_rtrmgr:8376 RTRMGR +171 module_manager.cc terminate ] Terminating module: interfaces [ 2009/06/04 14:18:57 INFO xorp_rtrmgr:8376 RTRMGR +194 module_manager.cc terminate ] Killing module: interfaces [ 2009/06/04 14:18:57 ERROR xorp_rtrmgr:8376 RTRMGR +747 module_manager.cc done_cb ] Command "/usr/lib/xorp/fea/xorp_fea": terminated with signal 15. [ 2009/06/04 14:18:57 INFO xorp_rtrmgr:8376 RTRMGR +282 module_manager.cc module_exited ] Module killed during shutdown: interfaces Can you help me? Best Regard, David Santiago -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090604/86e0b915/attachment.html From tom.gibson at ipvidnet.com Thu Jun 4 13:30:16 2009 From: tom.gibson at ipvidnet.com (Tom Gibson) Date: Thu, 4 Jun 2009 13:30:16 -0700 Subject: [Xorp-users] XORP 1.6 support Click 1.6.0 ? In-Reply-To: References: Message-ID: I don't think I ever got Xorp 1.6 working with Click in Linux, though I did get a version out of source control at one point that worked. I'm trying now with the latest code and having trouble. If anyone has advice on this please let me know. I've had minimal experience using cvs and have only so far used it to do a checkout of latest code. I should still have my code directory on my other computer with the version of Xorp that worked though. I'm guessing it shouldn't be too hard to figure out a cvs command to do a "get" of code current as of that date. If I can figure out a small window of time in which the Click support was fixed, what ways would be best to figure out what fixed it? On Thu, May 7, 2009 at 8:46 AM, dong yin wrote: > Hi all, > > Dose XORP 1.6 support Click v1.6.0? When I run XORP 1.6 to control the > remote Click forwarding data plane (click 1.6.0), errors happened. > > ///////////////////////////////////////////////////// > [ 2009/05/07 10:35:50 INFO xorp_rtrmgr:4428 RTRMGR +101 module_manager.cc > execute ] Executing module: firewall (fea/xorp_fea) > [ 2009/05/07 10:35:54 INFO xorp_rtrmgr:4428 RTRMGR +101 module_manager.cc > execute ] Executing module: fea (fea/xorp_fea) > [ 2009/05/07 10:35:59 ERROR xorp_fea:4429 FEA +710 ifconfig_set_click.cc > click_config_generator_done ] Failed to write the Click configuration: > User-level Click command error: 520-Write handler 'hotconfig' error: > 520-:1: '_xorp_ip4 :: Strip' input 0 unused > 520-:3: '_xorp_arpt :: Tee' input 0 unused > 520 Router could not be initialized! > > ///////////////////////////////////////////////////// > > My config file is below: > > ///////////////////////////////////////////////////// > interfaces { > interface eth1 { > description: "control interface" > disable: false > mac: 00:1b:21:2c:a5:06 > default-system-config > } > interface eth2 { > description: "data interface" > disable: false > mac: 00:04:76:2f:24:91 > default-system-config > /* vif eth2 { > disable: false > address 10.1.1.1 { > prefix-length: 24 > } > }*/ > } > } > fea { > unicast-forwarding4 { > disable: true > } > click { > disable: false > kernel-click { > disable: true > } > user-click { > disable: false > command-file: "/usr/local/bin/click" > /* command-extra-arguments: "-R"*/ > control-address: 10.0.0.2 > control-socket-port: 13000 > /*startup-config-file: "/root/xorptest/router-user.click" > *user-click-config-generator-file: > *"/usr/local/xorp/fea/xorp_fea_click_config_generator" > */ > } > } > } > protocols { > static { > route 4.4.4.0/24 { > next-hop: 5.5.5.1 > metric: 1 > } > route 5.5.5.0/24 { > next-hop: 4.4.4.1 > metric: 1 > } > } > } > ////////////////////////////////////////////////////// > > And my click config file is : > > ///////////////////////////////////////////////////// > AddressInfo ( > net2 192.168.2.0, > net3 192.168.3.0 > ) > > ControlSocket("TCP", 13000); > > c2 :: Classifier(12/0806 20/0001, 12/0806 20/0002, 12/0800, -); > > FromDevice(eth1) -> [0]c2; > > out2 :: Queue(1024) -> ToDevice(eth1); > > ar2 :: ARPResponder(eth1:ip eth1:eth) -> out2; > > aq2 :: ARPQuerier(eth1:ip, eth1:eth) -> out2; > > c2[0] -> ar2; > c2[1] -> [1]aq2; > c2[3] -> Discard; > > > _xorp_rt4 :: RangeIPLookup(net2/24 0, net3/24 1, 0.0.0.0/0 2); > > c2[2] -> Strip(14) -> CheckIPHeader2 -> [0]_xorp_rt4; > _xorp_rt4[0] -> [0]aq2; > _xorp_rt4[1] -> [0]aq2; > _xorp_rt4[2] -> Discard; > > > /////////////////////////////////////////////////////////////// > > Thanks a lot. > > Cheers, > Dong > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090604/53d6dcbe/attachment.html From xuhao_hank at yahoo.com.cn Thu Jun 4 23:24:59 2009 From: xuhao_hank at yahoo.com.cn (hao xu) Date: Fri, 5 Jun 2009 14:24:59 +0800 (CST) Subject: [Xorp-users] how to run with xorp-1.6+click-1.4.3(userlevel) in linux Message-ID: <318023.11612.qm@web15004.mail.cnb.yahoo.com> hi all, ??? i am trying to run xorp with click. and i know that xorp support click-1.4.3, so i use click-1.4.3 in userlevel. but when i run the programme, some problems appear. i find that my xorp can not connect with click in socket. what can i do. ??? these are the records of the results. and how can do. --------------------------------------------------------------------------------------- [ 2009/06/05 21:57:32? INFO xorp_rtrmgr:2953 RTRMGR +249 master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea [ 2009/06/05 21:57:32? INFO xorp_rtrmgr:2953 RTRMGR +101 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2009/06/05 21:57:33 INFO xorp_fea MFEA ] MFEA enabled [ 2009/06/05 21:57:33 INFO xorp_fea MFEA ] CLI enabled [ 2009/06/05 21:57:33 INFO xorp_fea MFEA ] CLI started [ 2009/06/05 21:57:33 INFO xorp_fea MFEA ] MFEA enabled [ 2009/06/05 21:57:33 INFO xorp_fea MFEA ] CLI enabled [ 2009/06/05 21:57:33 INFO xorp_fea MFEA ] CLI started [ 2009/06/05 21:57:34? INFO xorp_rtrmgr:2953 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) [ 2009/06/05 21:57:38? INFO xorp_rtrmgr:2953 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2009/06/05 21:57:42? ERROR xorp_fea:2954 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 10.10.10.10, remote_port = 13000): Connection refused [ 2009/06/05 21:57:42 WARNING xorp_fea FEA ] Could not open user-level Click socket: Connection refused. Trying again... [ 2009/06/05 21:57:42? ERROR xorp_fea:2954 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 10.10.10.10, remote_port = 13000): Connection refused [ 2009/06/05 21:57:42 WARNING xorp_fea FEA ] Could not open user-level Click socket: Connection refused. Trying again... [ 2009/06/05 21:57:43? ERROR xorp_fea:2954 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 10.10.10.10, remote_port = 13000): Connection refused [ 2009/06/05 21:57:43 WARNING xorp_fea FEA ] Could not open user-level Click socket: Connection refused. Trying again... [ 2009/06/05 21:57:43? ERROR xorp_fea:2954 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 10.10.10.10, remote_port = 13000): Connection refused [ 2009/06/05 21:57:43 WARNING xorp_fea XrlFeaTarget ] Handling method for fea_click/0.1/start_click failed: XrlCmdError 102 Command failed Could not open user-level Click socket: Connection refused [ 2009/06/05 21:57:43? ERROR xorp_rtrmgr:2953 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Could not open user-level Click socket: Connection refused [ 2009/06/05 21:57:43? ERROR xorp_rtrmgr:2953 RTRMGR +261 master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Could not open user-level Click socket: Connection refused [ 2009/06/05 21:57:43? INFO xorp_rtrmgr:2953 RTRMGR +2233 task.cc run_task ] No more tasks to run ------------------------------------------------- and i write the following words in the scripts of click : --------------------------------------------- ControlSocket("TCP",13000); --------------------------------------------- can you tell me what should i write. and what are detail steps to run the xorp with click. thanks a lot. xh ___________________________________________________________ ????????????????? http://card.mail.cn.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090605/e8c9e2f8/attachment.html From irfan_area47 at yahoo.co.id Fri Jun 5 06:21:14 2009 From: irfan_area47 at yahoo.co.id (irfan irfan) Date: Fri, 5 Jun 2009 21:21:14 +0800 (SGT) Subject: [Xorp-users] xorp connecting mrouted Message-ID: <289966.81724.qm@web76513.mail.sg1.yahoo.com> Any one can connecting xorp and mrouted for multicast routing ? Xorp use PIM-SM protocol and mrouted use DVMRP protocol.... thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090605/bccdc03a/attachment.html From vommwa at yahoo.com Thu Jun 4 10:18:44 2009 From: vommwa at yahoo.com (vommwa at yahoo.com) Date: Thu, 4 Jun 2009 10:18:44 -0700 (PDT) Subject: [Xorp-users] Error in make check Message-ID: <1526.19696.qm@web56607.mail.re3.yahoo.com> Hello, I've been trying to run make check, but some of the tests fail. I have attached the output as a text file. I am tring to install the latest stable version of XORP, xorp-1.6. on Netkit, a UML-based networking testbed which starts up Debina virtual machines. Debian version is 4.0 (etch), with kernel version 2.6.26-5 . I am ussing gcc 4.3.3-8 and g++ 4.3.3-8 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090604/fe9723e1/attachment-0001.html -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: log.txt Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090604/fe9723e1/attachment-0001.txt From bhavin81 at iitb.ac.in Fri Jun 5 23:03:07 2009 From: bhavin81 at iitb.ac.in (bhavin81 at iitb.ac.in) Date: Sat, 6 Jun 2009 11:33:07 +0530 Subject: [Xorp-users] Querry regarding domain wide address and primary address Message-ID: <36cdf71c38edc0a58d8044998ee2b860.squirrel@gpo.iitb.ac.in> Hello Friends, I have got querry related with Primary address and domain wide address? What is the difference between those two addresses with any example if possible. Are those two addresse are related with the primary addresses and secondary addresses mentioned in RFC 4601? If not then what is the difference between primary and secondary addresses of router? Regards, Bhavin, Networking Student. From bms at incunabulum.net Sun Jun 7 21:16:03 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 08 Jun 2009 05:16:03 +0100 Subject: [Xorp-users] Error in make check In-Reply-To: <1526.19696.qm@web56607.mail.re3.yahoo.com> References: <1526.19696.qm@web56607.mail.re3.yahoo.com> Message-ID: <4A2C9083.1050208@incunabulum.net> vommwa at yahoo.com wrote: > Hello, I've been trying to run make check, but some of the tests fail. > I have attached the output as a text file. > I am tring to install the latest stable version of XORP, xorp-1.6. on > Netkit, a UML-based networking testbed which starts up Debina virtual > machines. Debian version is 4.0 (etch), with kernel version 2.6.26-5 . > I am ussing gcc 4.3.3-8 and g++ 4.3.3-8 > > The most likely explanation for the regression test failure you are observing is timer aliasing in your UML instance. This is probably affecting timing in the regression test itself. One issue with the XORP EventLoop is that the timers it uses to invoke periodic events are subject to jitter introduced by the operating system's scheduler, as well as the EventLoop code itself. Normally in operational practice this jitter doesn't affect timer operation in a way which would cause any catastrophic failures of the system. Assuming that the tests pass OK when you run 'gmake check' in a non-virtualized environment, there may be no cause for concern here. thanks, BMS From bms at incunabulum.net Sun Jun 7 21:17:33 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 08 Jun 2009 05:17:33 +0100 Subject: [Xorp-users] xorp connecting mrouted In-Reply-To: <289966.81724.qm@web76513.mail.sg1.yahoo.com> References: <289966.81724.qm@web76513.mail.sg1.yahoo.com> Message-ID: <4A2C90DD.5060500@incunabulum.net> irfan irfan wrote: > Any one can connecting xorp and mrouted for multicast routing ? Xorp > use PIM-SM protocol and mrouted use DVMRP protocol.... > thanks I'm afraid that isn't possible; XORP has no DVMRP support. If you wanted to port DVMRP to XORP, I'm sure that's a code contribution that would be gladly considered for the project, but only the basis of enabling interoperability with legacy systems. The MBONE does not exist now as such, and it was one of the last networks to use DVMRP for operational deployments. DVMRP should be considered an obsolete protocol which is not recommended for new multicast deployments. There are certain instances in which it may still be useful, but generally, PIM-SM is more desirable for many different reasons which I will not describe here for brevity. thanks, BMS From bms at incunabulum.net Sun Jun 7 21:19:54 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 08 Jun 2009 05:19:54 +0100 Subject: [Xorp-users] Querry regarding domain wide address and primary address In-Reply-To: <36cdf71c38edc0a58d8044998ee2b860.squirrel@gpo.iitb.ac.in> References: <36cdf71c38edc0a58d8044998ee2b860.squirrel@gpo.iitb.ac.in> Message-ID: <4A2C916A.2090608@incunabulum.net> Hi, Thanks for your question about PIM. I looked at RFC 4601 briefly to answer your question. This paragraph in the RFC should clarify the difference: "The primary address of a PIM neighbor is obtained from the source IP address used in its PIM Hello messages." bhavin81 at iitb.ac.in wrote: > Hello Friends, > > > I have got querry related with Primary address and domain > wide address? What is the difference between those two addresses with > any example if possible. Are those two addresse are related with the > primary addresses and secondary addresses mentioned in RFC 4601? > If not then what is the difference between primary and secondary addresses > of router? > In general, IPv4 addresses identify interfaces on-link, not nodes. There are special situations where this is not the case, i.e. BGPv4 Anycasting, HSRP etc. PIM, like many IETF protocols, uses one IPv4 address configured on an IPv4 PIM node to consistently refer to that node within the PIM protocol. The definition of a secondary address is covered elsewhere in that RFC; they may either come from other interfaces, or be other addresses on the interface where the primary address is configured. thanks, BMS P.S. It would be more useful if, when asking questions about PIM implementation, you could mention PIM in the subject line of your message. P.P.S. You might want to direct non-XORP specific questions about protocol implementation to a more appropriate list, e.g. an IETF WG mailing list or perhaps end2end, as we need to keep xorp-users on topic. Thanks. From bms at incunabulum.net Sun Jun 7 21:22:58 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 08 Jun 2009 05:22:58 +0100 Subject: [Xorp-users] XORP 1.6 support Click 1.6.0 ? In-Reply-To: References: Message-ID: <4A2C9222.2020704@incunabulum.net> Tom Gibson wrote: > I don't think I ever got Xorp 1.6 working with Click in Linux, though > I did get a version out of source control at one point that worked. > I'm trying now with the latest code and having trouble. If anyone has > advice on this please let me know. > > I've had minimal experience using cvs and have only so far used it to > do a checkout of latest code. I should still have my code directory > on my other computer with the version of Xorp that worked though. I'm > guessing it shouldn't be too hard to figure out a cvs command to do a > "get" of code current as of that date. > > If I can figure out a small window of time in which the Click support > was fixed, what ways would be best to figure out what fixed it? Short answer is: nobody is officially supporting Click with XORP at the moment, and we rely on user contributions in order to do so. If you can find the CVS checkout dates which work for you, please notify us upstream of any regression(s) introduced into the Click support against what's at the top of the tree, using Bugzilla to report the regressions -- then hopefully someone can come along and integrate the fixes upstream. thanks, BMS From bms at incunabulum.net Sun Jun 7 21:39:37 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 08 Jun 2009 05:39:37 +0100 Subject: [Xorp-users] Error tryng to launch Net-SNMP via the router manager In-Reply-To: References: Message-ID: <4A2C9609.8040303@incunabulum.net> David Santiago Santos wrote: > Hello, > > I installed the XORP 1.6 and Net-SNMP 5.4.1. Therefore, both of them > were compiled without errors. > > Although I did the configurations according to the XORP manual, I got > an erro tryng to launch it. Do you specifically need the XORP SNMP functionality? The only things it actually provides are the IfMib counters and some access to the BGP protocol MIB, which isn't memory efficient for large routing tables. Is this a requirement for your deployment of XORP? > > Below is the output when I run the command shell "sudo xorp_rtrmgr": > > [ 2009/06/04 14:18:49 INFO xorp_rtrmgr:8376 RTRMGR +239 master_conf_tree.cc execute ] Changed modules: interfaces, xorp_if_mib, fea, rib, fib2mrib, policy, static_routes > > [ 2009/06/04 14:18:49 INFO xorp_rtrmgr:8376 RTRMGR +96 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) > [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] MFEA enabled > [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] CLI enabled > > [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] CLI started > [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] MFEA enabled > [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] CLI enabled > [ 2009/06/04 14:18:50 INFO xorp_fea MFEA ] CLI started > > [ 2009/06/04 14:18:51 INFO xorp_rtrmgr:8376 RTRMGR +96 module_manager.cc execute ] Executing module: xorp_if_mib (mibs/snmpdscripts/startsnmp) > No log handling enabled - turning on stderr logging > registered debug token xorp_if_mib_module, 1 > > registered debug token dlmod, 1 > registered debug token usmUser, 1 > netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load() > netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load() > > netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load() These are probably benign warnings. > dlmod: register mib > dlmod: dlmod_path: /usr/local/lib/snmp/dlmod > dlmod: dlmod_create_module > dlmod: dlmod_load_module xorp_if_mib_module: /usr/local/xorp/mibs/xorp_if_mib_module.so > > xorp_if_mib_module: XorpIfMib created > xorp_if_mib_module: Initialized... > Error opening specified endpoint "" > Server Exiting with code 1 > xorp_if_mib_module: XorpIfMib destroyed This sounds like it may be an issue with the net-snmp library configuration, or possibly the agent itself. > [ 2009/06/04 14:18:51 ERROR xorp_rtrmgr:8376 RTRMGR +747 module_manager.cc done_cb ] Command "/usr/lib/xorp/mibs/snmpdscripts/startsnmp": exited with exit status 1. > This is the real indication of the failure. > [ 2009/06/04 14:18:51 INFO xorp_rtrmgr:8376 RTRMGR +318 module_manager.cc module_exited ] Module abnormal exit: xorp_if_mib > [ 2009/06/04 14:18:53 WARNING xorp_rtrmgr:8376 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does not exist or is not enabled. > > [ 2009/06/04 14:18:54 WARNING xorp_rtrmgr:8376 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does not exist or is not enabled. > > [ 2009/06/04 14:18:55 WARNING xorp_rtrmgr:8376 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does not exist or is not enabled. > > [ 2009/06/04 14:18:56 WARNING xorp_rtrmgr:8376 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does not exist or is not enabled. > > [ 2009/06/04 14:18:57 INFO xorp_rtrmgr:8376 RTRMGR +2228 task.cc run_task ] No more tasks to run > [ 2009/06/04 14:18:57 INFO xorp_rtrmgr:8376 RTRMGR +171 module_manager.cc terminate ] Terminating module: interfaces > > [ 2009/06/04 14:18:57 INFO xorp_rtrmgr:8376 RTRMGR +194 module_manager.cc terminate ] Killing module: interfaces > [ 2009/06/04 14:18:57 ERROR xorp_rtrmgr:8376 RTRMGR +747 module_manager.cc done_cb ] Command "/usr/lib/xorp/fea/xorp_fea": terminated with signal 15. > > [ 2009/06/04 14:18:57 INFO xorp_rtrmgr:8376 RTRMGR +282 module_manager.cc module_exited ] Module killed during shutdown: interfaces > > This is just fallout from the IfMib registration failure and can be ignored. XORP's SNMP MIB support, as it currently stands is quite minimal, and probably not that useful for real deployments. However it does have a hard dependency on the ability to load MIB extension modules into the main net-snmp agent, snmpd. This is a net-snmp and platform specific mechanism. Are you able to load other, non-XORP, MIB extension modules into snmpd? Is this system exclusively using IPv6? Does the host have any network configuration at all before net-snmp runs? See here for more hints which may help you to debug your net-snmp installation: http://www.net-snmp.org/docs/man/snmpd.html Do remember that the community version of XORP is offered on a best effort open-source basis, and contributions are very welcome. thanks, BMS From bms at incunabulum.net Sun Jun 7 21:42:11 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 08 Jun 2009 05:42:11 +0100 Subject: [Xorp-users] How do class SnmpEventLoop export events to the snmp agent In-Reply-To: <4A22AAED.8070102@incunabulum.net> References: <4A214732.7090502@incunabulum.net> <25480751.317311243676078263.JavaMail.coremail@bj126app55.126.com> <28742318.186831243751501992.JavaMail.coremail@bj126app33.126.com> <4A22AAED.8070102@incunabulum.net> Message-ID: <4A2C96A3.5080104@incunabulum.net> A bit more detail as there have been ongoing questions about SNMP on this list. Bruce Simpson wrote: > > Last August I did a feasibility study / technical report for XORP, > Inc. to look at the problem in detail. I've been of the opinion that > AgentX should be used, as it side-steps the need to depend on the > loader mechanism. ... > > > These problems are not XORP-specific, or even Net-SNMP-specific, by > any means. It's just something which needs to be revisited carefully. P.S. One of the other things I pointed out in that technical memo, was that current commercial SNMP toolkit offerings didn't actually add any value for the XORP code base. I looked at Agent++ in particular as it seemed the most mature and refined commercial option. The Net-SNMP developers were very helpful and responsive to technical questions, and understood the technical limitations involved in trying to propagate large structures across address spaces, having had to tackle this engineering problem themselves in commercial deployments. Using it, of course, requires exposure to the Net-SNMP code base, as there is no definitive textbook on how to do it. If there is, I'm all ears and would wish someone had pointed me at that book many years ago. Again, SNMP support is one of many things which were not as mature in XORP, during its time as a research project, as we would like. The important thing to remember is that XORP is an open source software project, and outside contributions to fix community issues are very welcome. cheers, BMS From bms at incunabulum.net Wed Jun 10 00:35:05 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Wed, 10 Jun 2009 08:35:05 +0100 Subject: [Xorp-users] XORP problems at boot In-Reply-To: <36243D984F88BA4ABD1E0EFC1E61B989796BBE@fudd.ad.maine.edu> References: <36243D984F88BA4ABD1E0EFC1E61B989796B8F@fudd.ad.maine.edu> <4A27F7D1.9080008@incunabulum.net> <36243D984F88BA4ABD1E0EFC1E61B989796BBE@fudd.ad.maine.edu> Message-ID: <4A2F6229.1030005@incunabulum.net> Hi, Sorry for the delay in my response -- it looks like you sent this followup to me personally... mailing list is the preferred venue for XORP questions, thanks! Soucy, Ray wrote: > Pentium(R) Dual-Core CPU E5200 2.50GHz, rev. 6 (2494.116 MHz) > Linux 2.6.29.1 > XORP 1.6 > > Clock in BIOS and clock on OS after boot are both correct and in sync w/ > RIP router (which is actually the NTP source) > Clock doesn't seem to change during the boot process... > It is a pretty customized Linux setup, loads everything into a ram disk > then unmounts the physical disk after boot (to avoid disk damage due to > power loss, or service disruption from disk failure). > Hmm. Something is definitely amiss with timing, then. > Very odd that it works fine if run manually post-boot (making me think > its not a XORP issue) just figured I'd ask if anyone else has > experienced it. > When you compiled XORP, did the config.log file say that support for CLOCK_MONOTONIC was there? %%% configure:30741: checking whether the build environment has CLOCK_MONOTONIC configure:30771: gcc -c -g -O2 conftest.c >&5 configure:30777: $? = 0 configure:30787: result: yes %%% If you're cross compiling this can also be an issue. > The crash on boot if interfaces aren't connected is a bit of an > annoyance though. Is there a way to prevent this (perhaps running some > ifconfig commands before XORP is started?) > > ... > We are using PIM-SM pretty extensively. > That'll be why -- there is a patch for this issue but it isn't integrated yet. Search xorp-users@ archives for 'Heiko'. thanks, BMS From info at cmd.nu Thu Jun 11 03:18:39 2009 From: info at cmd.nu (Christian Svensson) Date: Thu, 11 Jun 2009 12:18:39 +0200 Subject: [Xorp-users] Progress in Xorp development? Message-ID: Hello. I was browsing the CVS code to look at what work is being done for 1.7 / 2.0. I was very surprised to see that no real code has been committed to CVS since 2008. Why is that? Greetings, Christian "BC" Svensson Command Systems -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090611/5335a2fa/attachment.html From john.tavs at xorp.net Thu Jun 11 10:57:03 2009 From: john.tavs at xorp.net (John Tavs) Date: Thu, 11 Jun 2009 13:57:03 -0400 Subject: [Xorp-users] Progress in Xorp development? In-Reply-To: References: Message-ID: <1F29BD8FD2CAE147B35C21D7C69AB6321FE46005F0@VMBX111.ihostexchange.net> Two things have happened that prevent people from seeing the checkins. 1) We had to move the code from ICSI Server to a new server and we were planning to covert to SVN that we were already internally using. 2) We discovered problems in making SVN server public that has resulted in us now looking at non-SVN options. Having said this, we do expect this to be resolved soon and if anyone is interesting being a committer to XORP, please send an mail to info at xorp.net with your contact information and we tell you how to get set up on the new system when we bring it up. From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Christian Svensson Sent: Thursday, June 11, 2009 3:19 AM To: xorp-users at xorp.org Subject: [Xorp-users] Progress in Xorp development? Hello. I was browsing the CVS code to look at what work is being done for 1.7 / 2.0. I was very surprised to see that no real code has been committed to CVS since 2008. Why is that? Greetings, Christian "BC" Svensson Command Systems -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090611/085668b6/attachment.html From greearb at candelatech.com Thu Jun 11 11:15:59 2009 From: greearb at candelatech.com (Ben Greear) Date: Thu, 11 Jun 2009 11:15:59 -0700 Subject: [Xorp-users] Progress in Xorp development? In-Reply-To: <1F29BD8FD2CAE147B35C21D7C69AB6321FE46005F0@VMBX111.ihostexchange.net> References: <1F29BD8FD2CAE147B35C21D7C69AB6321FE46005F0@VMBX111.ihostexchange.net> Message-ID: <4A3149DF.8050100@candelatech.com> John Tavs wrote: > Two things have happened that prevent people from seeing the checkins. > > > > 1) We had to move the code from ICSI Server to a new server and we > were planning to covert to SVN that we were already internally using. > > 2) We discovered problems in making SVN server public that has > resulted in us now looking at non-SVN options. Here's hoping you choose 'git'! I've already imported from your CVS tree into my own xorp git repo and that went smoothly... > Having said this, we do expect this to be resolved soon and if anyone is > interesting being a committer to XORP, please send an mail to > info at xorp.net with your contact information and > we tell you how to get set up on the new system when we bring it up. Please post to this list when you have the repo set up. I don't know if I actually want submit access, but I would like to merge with your latest efforts when they are somewhat stable.. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From murad03_khan at yahoo.com Fri Jun 12 03:49:49 2009 From: murad03_khan at yahoo.com (Murad) Date: Fri, 12 Jun 2009 03:49:49 -0700 (PDT) Subject: [Xorp-users] QoS in XORP routers Message-ID: <596957.22463.qm@web52401.mail.re2.yahoo.com> Hi, Can anyone please tell me how to configure QoS like Diffserv in XORP routers. I have two XORP routers. router A connected to router B and router B connected to Cisco router. Both the routers has two NICs installed.I am doing multicasting for IPTV. i want if i can configure these routers to sent different traffic classses for IPTV streams and internet traffic as well as VOIP traffic. Thanks in advance, /Murad -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090612/ad2b9715/attachment.html From bms at incunabulum.net Fri Jun 12 11:19:42 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Fri, 12 Jun 2009 19:19:42 +0100 Subject: [Xorp-users] QoS in XORP routers In-Reply-To: <596957.22463.qm@web52401.mail.re2.yahoo.com> References: <596957.22463.qm@web52401.mail.re2.yahoo.com> Message-ID: <4A329C3E.8070904@incunabulum.net> Murad wrote: > Hi, > > Can anyone please tell me how to configure QoS like Diffserv in XORP > routers. I have two XORP routers. router A connected to router B and > router B connected to Cisco router. Both the routers has two NICs > installed.I am doing multicasting for IPTV. i want if i can configure > these routers to sent different traffic classses for IPTV streams and > internet traffic as well as VOIP traffic. > End-to-end Internet QoS is still an ongoing research topic. In-depth support for IP ToS (i.e. DiffServ) is not part of XORP, it requires tight coupling to the forwarding plane. There is basic support for protocols to request that they have Internetwork Control precedence and that's about it. Typically the model boils down to using a firewall/packet filter module as a traffic classifier -- then implementing QoS according to some form of output queueing. Linux and the BSDs support this model -- unfortunately, there is no real standard for the API coupling involved, and glue code as found in the FEA would be needed. cheers, BMS From dongwx134398 at huawei.com Wed Jun 17 01:36:56 2009 From: dongwx134398 at huawei.com (=?gb2312?B?tq32qc+8?=) Date: Wed, 17 Jun 2009 16:36:56 +0800 Subject: [Xorp-users] How to run XORP+Click(Linuxmodel) on the same PC Message-ID: <010101c9ef26$c669ada0$960c6f0a@china.huawei.com> Hi All: I want to run XORP + Click(Linuxmodel) on the same PC(Fedora 6.0 2.6.19.2kernel), and write the XORP configuration as follows. Do I need write click configuration ? How to write Click configration? If you have done this work ,could you share your configuration file and experience with me. Please help me.Thanks a lot. /////////////////////////////////////// My XORP config file as follows: ////////////////////////////////////// /* interface configure */ interfaces { interface eth1 { vif eth1 { address 20.1.1.2 { prefix-length: 24 } } } interface eth2 { vif eth2 { address 30.1.1.2 { prefix-length: 24 } } } } /* end interface configure*/ /* forwarding engine abstraction*/ fea{ unicast-forwarding4{ disable:true } click { disable: false /* duplicate-routes-to-kernel: false*/ kernel-click { disable: false install-on-startup: true kernel-click-modules: "/home/dwx/click/click-1.7.0rc1/linuxmodule/proclikefs.o:/home/dwx/click/click-1.7.0rc1/linuxmodule/click.o" /* XXX: On FreeBSD we need only module click.ko */ /*kernel-click-modules: "/home/dwx/click/click-1.7.0rc1/linuxmodule/click.ko" */ mount-directory: "/click" kernel-click-config-generator-file: "/home/dwx/xorp-1.6/fea/xorp_fea_click_config_generator" } user-click { disable: true command-file: "/usr/local/bin/click" command-extra-arguments: "-R" command-execute-on-startup: true control-address: 20.1.1.2 control-socket-port: 50006 startup-config-file: "/dev/null" user-click-config-generator-file: "/home/dwx/xorp-1.6/fea/xorp_fea_click_config_generator" }/*end of user-click*/ }/*end of Click*/ }/*end of fea*/ /*static route configure */ protocols { static { route 20.1.1.0/24 { next-hop: 20.1.1.2 } route 30.1.1.0/24 { next-hop: 30.1.1.2 } } }/*end of static route configure*/ /////////////////////////////////////// the error as follows: ////////////////////////////////////// [2009/06/17 14:25:08 INFO xorp_rtrmgr:6906 RTRMGR +101 module_manager.cc execute] Executing module: fea(fea/xorp_fea)insmod: error inserting '/home/dwx/click/click-1.7.0rc1/linuxmodule/proclikefs.o':-1 Invalid module format [2009/06/17 14:25:08 INFO xorp_rtrmgr:6906 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command faild Executing system commad '/sbin/insmod /home/dwx/click/click-1.7.0rc1/linuxmodule/proclikefs.o' returned value '256' Best regards. Wenxia Dong -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090617/0cf5a477/attachment.html From david at utopia.cable.nu Wed Jun 17 07:32:00 2009 From: david at utopia.cable.nu (David Balnaves) Date: Thu, 18 Jun 2009 00:32:00 +1000 Subject: [Xorp-users] Questions about Xorp. Message-ID: Hi Xorp Users, I've just discovered xorp after trying bird and quagga. I really like quagga but it seems that there were some bugs I couldn't figure a way around and as such I have decided to look into xorp. There was also a clear lack of support for IGMP & PIM under these routing daemons (while this is not the place, please correct me if I'm wrong!). So far the XORP work seems really impressive, but I have a few things I would like to clarify: * Is there any prerequisite configuration needed on the router before XORP is started (including IPv6)? For example, should I need to configure anything under the debian network scheme of /etc/network/interfaces? * To my understanding Xorp doesn't appear to support IPv6 router advertisements for auto address configuration, is this correct? Is there plans to implement this functionality? * I'm using OSPFv3 for IPv6. I see some IPv6 interfaces on my Xorp router that return "destination host unreachable". When I query the route I see: 2002:XXXX:XXXX:4::1 via 2002:XXXX:XXXX:4::1 dev eth1 src 2002:XXXX:XXXX::2 metric 0 cache mtu 1500 advmss 1440 hoplimit 4294967295 I also see that the the interface has "scope global tenative", what does this mean? Is there a way to resolve this issue? 3: eth1: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:40:48:b1:23:36 brd ff:ff:ff:ff:ff:ff inet 192.168.4.1/24 brd 192.168.4.255 scope global eth1 inet6 2002:XXXX:XXXX:4::1/64 scope global tentative valid_lft forever preferred_lft forever inet6 fe80::240:48ff:feb1:2336/64 scope link tentative valid_lft forever preferred_lft forever Also, I understand that in OSPFv3 the link local is used for next hop routing. Is there a reason why you need to declared the link local address (ie: fe80:) on the interface under OSPFv3 protocol? Why isn't this inherited from the interface? * Xorp seems to do mostly everything from within the CLI. Is there syntax to declare if I an address should be gained from DHCP, or RA in the case of IPv6? Either way, I think XORP is awesome. I'd love to get the chance to use this in a production environment! -- David Balnaves From tom.gibson at ipvidnet.com Wed Jun 17 10:48:36 2009 From: tom.gibson at ipvidnet.com (Tom Gibson) Date: Wed, 17 Jun 2009 10:48:36 -0700 Subject: [Xorp-users] How to debug xorp_fea ? Message-ID: <4a392c7d.1ed6720a.26a7.fffffbc8@mx.google.com> Hi all, I was hoping someone could lend advice on how to go about figuring out what's going wrong inside xorp_fea. I'm getting pretty tired trying to hack my way through a setup to debug it. For some reason when I try to use Click, things hang somewhere, but I don't know where. If I try and use ddd / gdb on xorp_fea, xorp_rtrmgr kills it before I can figure things out. Any help is appreciated. Thanks, Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090617/4ef22433/attachment.html From greearb at candelatech.com Wed Jun 17 11:03:00 2009 From: greearb at candelatech.com (Ben Greear) Date: Wed, 17 Jun 2009 11:03:00 -0700 Subject: [Xorp-users] How to debug xorp_fea ? In-Reply-To: <4a392c7d.1ed6720a.26a7.fffffbc8@mx.google.com> References: <4a392c7d.1ed6720a.26a7.fffffbc8@mx.google.com> Message-ID: <4A392FD4.8050705@candelatech.com> Tom Gibson wrote: > Hi all, > > > > I was hoping someone could lend advice on how to go about figuring out > what?s going wrong inside xorp_fea. I?m getting pretty tired trying to > hack my way through a setup to debug it. For some reason when I try to > use Click, things hang somewhere, but I don?t know where. If I try and > use ddd / gdb on xorp_fea, xorp_rtrmgr kills it before I can figure > things out. strace -p might help if it's hung on a system call. Otherwise, probably adding logging is the only help since as you found, stopping the process with gdb adversely affects other things... Ben > > > > Any help is appreciated. > > > > Thanks, > > > > Tom > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Ben Greear Candela Technologies Inc http://www.candelatech.com From vommwa at yahoo.com Thu Jun 18 00:33:24 2009 From: vommwa at yahoo.com (victor omwando) Date: Thu, 18 Jun 2009 00:33:24 -0700 (PDT) Subject: [Xorp-users] Error loading xorp config file Message-ID: <955902.35684.qm@web56604.mail.re3.yahoo.com> Hi, I'm getting the following error when I try to load the attached xorp config file using xorp_rtrmgr's -b command line switch. The error occurs somewhere in my policy statements, but I can't for the life of me see what is wrong. Any quick help will be greatly appreciated. I'm running xorp 1.6. This happens on both an Ubuntu and Debian installation of xorp. [ 2009/06/18 07:31:52? ERROR xorp_rtrmgr:520 RTRMGR +349 main_rtrmgr.cc run ] rtrmgr shutting down due to an init error: PARSE ERROR [Config File /hosthome/r1.config.boot, line 84]: syntax error; Last symbol parsed was "network4-list" -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090618/263b9a1f/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: r1.config.boot Type: application/octet-stream Size: 6499 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090618/263b9a1f/attachment.obj From vommwa at yahoo.com Thu Jun 18 08:57:52 2009 From: vommwa at yahoo.com (victor omwando) Date: Thu, 18 Jun 2009 08:57:52 -0700 (PDT) Subject: [Xorp-users] Error loading xorp config file Message-ID: <6986.48436.qm@web56603.mail.re3.yahoo.com> Never mind, I found the problem. I'm testing this Haskell-based DSL that generates xorp config files and it appears it is buggy (duh). It had failed to put quotation marks around text arguments in the policy-statement sections. --- On Thu, 6/18/09, victor omwando wrote: From: victor omwando Subject: [Xorp-users] Error loading xorp config file To: xorp-users at xorp.org Date: Thursday, June 18, 2009, 12:33 AM Hi, I'm getting the following error when I try to load the attached xorp config file using xorp_rtrmgr's -b command line switch. The error occurs somewhere in my policy statements, but I can't for the life of me see what is wrong. Any quick help will be greatly appreciated. I'm running xorp 1.6. This happens on both an Ubuntu and Debian installation of xorp. [ 2009/06/18 07:31:52? ERROR xorp_rtrmgr:520 RTRMGR +349 main_rtrmgr.cc run ] rtrmgr shutting down due to an init error: PARSE ERROR [Config File /hosthome/r1.config.boot, line 84]: syntax error; Last symbol parsed was "network4-list" -----Inline Attachment Follows----- _______________________________________________ Xorp-users mailing list Xorp-users at xorp.org http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090618/a89e47ff/attachment.html From vommwa at yahoo.com Thu Jun 18 06:54:10 2009 From: vommwa at yahoo.com (victor omwando) Date: Thu, 18 Jun 2009 06:54:10 -0700 (PDT) Subject: [Xorp-users] Fw: Error loading xorp config file Message-ID: <326742.47014.qm@web56605.mail.re3.yahoo.com> Hi, I'm getting the following error when I try to load the attached xorp config file using xorp_rtrmgr's -b command line switch. The error occurs somewhere in my policy statements, but I can't for the life of me see what is wrong. Any quick help will be greatly appreciated. I'm running xorp 1.6. This happens on both an Ubuntu and Debian installation of xorp. Note that this is a repost, but I have just included the config.boot file in the email text rather than as an attachment. [ 2009/06/18 07:31:52? ERROR xorp_rtrmgr:520 RTRMGR +349 main_rtrmgr.cc run ] rtrmgr shutting down due to an init error: PARSE ERROR [Config File /hosthome/r1.config.boot, line 84]: syntax error; Last symbol parsed was "network4-list" interfaces { ??????????? interface "eth0" { ????????????????????????????? description: "data" ????????????????????????????? disable: false ????????????????????????????? vif?? "eth0" { ??????????????????????????????????????????? disable: false ??????????????????????????????????????????? address?? 100.100.100.2 { ???????????????????????????????????????????????????????????????????? prefix-length: 30 ???????????????????????????????????????????????????????????????????? broadcast: 100.100.100.2 ???????????????????????????????????????????????????????????????????? disable: false ????????????????????????????????????????????????????????????????????? } ???????????????????????????????????????????? } ????????????????????????????? vif?? "loopback" { ??????????????????????????????????????????????? disable: false ??????????????????????????????????????????????? address?? 172.160.1.1 { ?????????????????????????????????????????????????????????????????????? prefix-length: 32 ?????????????????????????????????????????????????????????????????????? broadcast: 172.160.1.1 ?????????????????????????????????????????????????????????????????????? disable: false ??????????????????????????????????????????????????????????????????????? } ???????????????????????????????????????????????? } ?????????????????????????????? } ???????????? } fea { ???? unicast-forwarding4 { ????????????????????????? disable: false ?????????????????????????? } ????? } protocols { ?????????? bgp { ??????????????? bgp-id: 172.160.1.1 ??????????????? local-as: 300 ??????????????? peer 130.0.2.5 { ??????????????????????????????? local-ip: 130.0.1.4 ??????????????????????????????? as: 300 ??????????????????????????????? next-hop: 130.0.1.4 ???????????????????????????????? } ??????????????? peer 130.0.3.4 { ??????????????????????????????? local-ip: 130.0.1.4 ??????????????????????????????? as: 300 ??????????????????????????????? next-hop: 130.0.1.4 ???????????????????????????????? } ??????????????? peer 100.100.100.1 { ??????????????????????????????????? local-ip: 100.100.100.0 ??????????????????????????????????? as: 100 ??????????????????????????????????? next-hop: 100.100.100.0 ???????????????????????????????????? } ??????????????? export: "redistpolicy1,exportpolicies" ??????????????? import: "importpolicies" ???????????????? } ?????????? static { ?????????????????? disable: false ?????????????????? route 172.160.0.0/16 { ???????????????????????????????????????? next-hop: 200.200.200.0 ????????????????????????????????????????? } ??????????????????? } ??????????? } policy { ??????? network4-list netlist1 { ??????????????????????????????? network?? 0.0.0.0/8 ??????????????????????????????? network?? 10.0.0.0/8 ??????????????????????????????? network?? 127.0.0.0/8 ??????????????????????????????? network?? 169.254.0.0/16 ??????????????????????????????? network?? 172.0.0.0/12 ??????????????????????????????? network?? 172.160.0.0/16 ??????????????????????????????? network?? 192.0.2.0/24 ??????????????????????????????? network?? 192.168.0.0/16 ??????????????????????????????? network?? 224.0.0.0/3 ?????????????????????????????? } ??????? policy-statement redistpolicy1 { ??????????????????????????????????????? term redist1 { ????????????????????????????????????????????????????? from { ??????????????????????????????????????????????????????????? protocol: "static" ??????????????????????????????????????????????????????????? network4: 100.200.0.0/16 ???????????????????????????????????????????????????????????? } ?????????????????????????????????????????????????????? } ???????????????????????????????????????? } ???????? ??????? policy-statement importpolicies { ???????????????????????????????????????? term impterm1 { ??????????????????????????????????????????????????????? from { ????????????????????????????????????????????????????????????? neighbor: 100.100.100.1 ????????????????????????????????????????????????????????????? network4-list: netlist1 ?????????????????????????????????????????????????????????????? } ??????????????????????????????????????????????????????? then { ????????????????????????????????????????????????????????????? reject ?????????????????????????????????????????????????????????????? } ???????????????????????????????????????????????????????? } ????????????????????????????????????????? ???????????????????????????????????????? term impterm2 { ??????????????????????????????????????????????????????? from { ????????????????????????????????????????????????????????????? nexthop4: 100.100.100.1 ?????????????????????????????????????????????????????????????? } ??????????????????????????????????????????????????????? then { ????????????????????????????????????????????????????????????? localpref: 120 ????????????????????????????????????????????????????????????? accept ?????????????????????????????????????????????????????????????? } ???????????????????????????????????????????????????????? } ????????????????????????????????????????? ???????????????????????????????????????? term impterm3 { ??????????????????????????????????????????????????????? then { ????????????????????????????????????????????????????????????? localpref: 100 ????????????????????????????????????????????????????????????? accept ?????????????????????????????????????????????????????????????? } ???????????????????????????????????????????????????????? } ????????????????????????????????????????? } ???????? ??????? policy-statement exportpolicies { ???????????????????????????????????????? term expterm1 { ??????????????????????????????????????????????????????? to { ??????????????????????????????????????????????????????????? neighbor: 100.100.100.1 ??????????????????????????????????????????????????????????? network4 != 172.160.0.0/16 ???????????????????????????????????????????????????????????? } ??????????????????????????????????????????????????????? then { ????????????????????????????????????????????????????????????? reject ?????????????????????????????????????????????????????????????? } ???????????????????????????????????????????????????????? } ????????????????????????????????????????? ???????????????????????????????????????? term expterm2 { ??????????????????????????????????????????????????????? then { ????????????????????????????????????????????????????????????? accept ?????????????????????????????????????????????????????????????? } ???????????????????????????????????????????????????????? } ????????????????????????????????????????? } ???????? } -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090618/c48a4d1f/attachment-0001.html From bms at incunabulum.net Fri Jun 19 14:18:32 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Fri, 19 Jun 2009 22:18:32 +0100 Subject: [Xorp-users] How to debug xorp_fea ? In-Reply-To: <4a392c7d.1ed6720a.26a7.fffffbc8@mx.google.com> References: <4a392c7d.1ed6720a.26a7.fffffbc8@mx.google.com> Message-ID: <4A3C00A8.8010701@incunabulum.net> Hi, I posted a script on this list a few weeks ago which should help, should be in the archives. Tom Gibson wrote: > > Hi all, > > I was hoping someone could lend advice on how to go about figuring out > what?s going wrong inside xorp_fea. I?m getting pretty tired trying to > hack my way through a setup to debug it. For some reason when I try to > use Click, things hang somewhere, but I don?t know where. If I try and > use ddd / gdb on xorp_fea, xorp_rtrmgr kills it before I can figure > things out. > The key thing is to attach GDB on the FEA, set the breakpoint/catchpoint you need, and immediately continue, as there are keepalive timers which the Router Manager will use to determine if the FEA has died or not. cheers BMS From bms at incunabulum.net Fri Jun 19 14:30:23 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Fri, 19 Jun 2009 22:30:23 +0100 Subject: [Xorp-users] Questions about Xorp. In-Reply-To: References: Message-ID: <4A3C036F.1040801@incunabulum.net> Welcome. David Balnaves wrote: > Hi Xorp Users, > > I've just discovered xorp after trying bird and quagga. > > I really like quagga but it seems that there were some bugs I couldn't > figure a way around and as such I have decided to look into xorp. There was > also a clear lack of support for IGMP & PIM under these routing daemons > (while this is not the place, please correct me if I'm wrong!). > That's correct, XORP is the only cohesive multicast routing story in open source at the moment. PIM-SM can have significant complexity, and needs to be low latency, which is one reason that a C++ implementation of that protocol is justified. > So far the XORP work seems really impressive, but I have a few things I > would like to clarify: > > * Is there any prerequisite configuration needed on the router before XORP > is started (including IPv6)? For example, should I need to configure > anything under the debian network scheme of /etc/network/interfaces? > You shouldn't need to configure this further than ensuring essential network drivers are loaded -- the XORP configuration file should be able to take care of it, unless you have a compelling reason to do otherwise (i.e. configure up management interface port on boot -- and use default-system-config directive for that interface in the XORP config). > * To my understanding Xorp doesn't appear to support IPv6 router > advertisements for auto address configuration, is this correct? Is there > plans to implement this functionality? > That's correct. People have requested this feature before. I don't believe there is a Bugzilla entry for this feature request. Adding it would require code modification. > * I'm using OSPFv3 for IPv6. I see some IPv6 interfaces on my Xorp router > that return "destination host unreachable". When I query the route I see: > 2002:XXXX:XXXX:4::1 via 2002:XXXX:XXXX:4::1 dev eth1 src 2002:XXXX:XXXX::2 > metric 0 > cache mtu 1500 advmss 1440 hoplimit 4294967295 > > I also see that the the interface has "scope global tenative", what does > this mean? Is there a way to resolve this issue? > A tentative address in IPv6 is usually one for which the Duplicate Address Detection (DAD) mechanism may have failed. Are you using stateless address autoconfiguration on these interfaces? > 3: eth1: mtu 1500 qdisc pfifo_fast state > UNKNOWN qlen 1000 > link/ether 00:40:48:b1:23:36 brd ff:ff:ff:ff:ff:ff > inet 192.168.4.1/24 brd 192.168.4.255 scope global eth1 > inet6 2002:XXXX:XXXX:4::1/64 scope global tentative > valid_lft forever preferred_lft forever > inet6 fe80::240:48ff:feb1:2336/64 scope link tentative > valid_lft forever preferred_lft forever > > Also, I understand that in OSPFv3 the link local is used for next hop > routing. Is there a reason why you need to declared the link local address > (ie: fe80:) on the interface under OSPFv3 protocol? Why isn't this > inherited from the interface? > Yes, in OSPFv3 the link-local addresses normally need to be used, although I believe that was only a requirement for XORP release 1.4. The user manual says: %%% OSPFv3 does not require any addresses to be configured in which case it will advertise all global addresses configured on the interface/vif. If any addresses are configured in OSPFv3 then only those addresses will be advertised. If it is required that no addresses should be advertised then configuring an address and disabling it, will stop any global addresses being advertised. %%% Are you trying to configure only specific interfaces for OSPFv3 use? If so, it sounds like perhaps there should be a configuration switch to request the link-local address be bound for OSPFv3 without actually specifying it, for convenience. > * Xorp seems to do mostly everything from within the CLI. Is there syntax > to declare if I an address should be gained from DHCP, or RA in the case of > IPv6? > No, there is currently no DHCP client support in XORP itself. Normally we rely on the host platform's mechanisms for doing this. This could potentially be added at a later date, user contributions are welcome -- discussions are in progress about how to improve the software component model in XORP to facilitate such additions. > Either way, I think XORP is awesome. I'd love to get the chance to use this > in a production environment! > > Thanks! BMS From appletrp at gmail.com Tue Jun 23 07:40:47 2009 From: appletrp at gmail.com (Robert Appleton) Date: Tue, 23 Jun 2009 10:40:47 -0400 Subject: [Xorp-users] xorpsh problem Message-ID: I can't seem to get xorpsh to run so that I can start configuring. I am running fedora 10, and have already compiled the code using configure and make. Any help is appreciated. - Bob Appleton appletrp at gmail.com From bms at incunabulum.net Tue Jun 23 08:55:30 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Tue, 23 Jun 2009 16:55:30 +0100 Subject: [Xorp-users] xorpsh problem In-Reply-To: References: Message-ID: <4A40FAF2.7080603@incunabulum.net> Hi Robert, You have to write at least a skeleton configuration file in order for the Router Manager to run, as xorpsh cannot run without the Router Manager. There is a skeleton config generator in the setup for the XORP LiveCD/LiveUSB, however, it's probably easiest just to do this with your favorite text editor. Robert Appleton wrote: > I can't seem to get xorpsh to run so that I can start configuring. > I am running fedora 10, and have already compiled the code using > configure and make. Any help is appreciated. > thanks, BMS From timothyc at ucla.edu Thu Jun 25 01:58:21 2009 From: timothyc at ucla.edu (Timothy Chow) Date: Thu, 25 Jun 2009 01:58:21 -0700 Subject: [Xorp-users] Empty routing table Message-ID: <20090625015821.84505gugcw8eg8g8@mail.ucla.edu> Hello all, I am porting XORP to an embedded target which has a ARM processor. Everything got cross-compiled OK. xorp_rtrmgr and xorpsh also runs OK under the target platform. I tried static and OSPF routing protocols, and looks like both protocols do not populate the routing table at all. The "show routing table" commands in xorpsh for both protocols gave me empty routing tables. I have tested XORP under VM so I do have a set of working configuration files for a scenario I am testing with either static routes or OSPF. I just wonder if there is anything or anywhere I can check if XORP is working correctly on my target platform. Maybe something I missed during the whole cross-compilation process? Any thoughts? Thanks in advance, Tim From bms at incunabulum.net Thu Jun 25 03:20:37 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 25 Jun 2009 11:20:37 +0100 Subject: [Xorp-users] Empty routing table In-Reply-To: <20090625015821.84505gugcw8eg8g8@mail.ucla.edu> References: <20090625015821.84505gugcw8eg8g8@mail.ucla.edu> Message-ID: <4A434F75.5060108@incunabulum.net> Timothy Chow wrote: > Hello all, > > I am porting XORP to an embedded target which has a ARM processor. > Everything got cross-compiled OK. xorp_rtrmgr and xorpsh also runs OK > under the target platform. > > I tried static and OSPF routing protocols, and looks like both > protocols do not populate the routing table at all. The "show routing > table" commands in xorpsh for both protocols gave me empty routing > tables. > Did they give you empty routing tables or empty *output* ? If there were empty tables you would have seen headers. Can you double confirm? Do the protocols involved see their own routes? Are you working from CVS sources, or a release tarball? We are currently waiting for clearance to move these sources to SourceForge so there isn't actually any point in committing bug fixes until that happens, sorry, this is a major hold-up. > I just wonder if there is anything or anywhere I can check if XORP is > working correctly on my target platform. Maybe something I missed > during the whole cross-compilation process? Any thoughts? > ARM is a strong alignment architecture. Whilst warnings have been fixed there are places in the code where strong alignment may be broken. thanks BMS From seb at anet.fr Thu Jun 25 08:19:17 2009 From: seb at anet.fr (=?ISO-8859-1?Q?S=E9bastien_Nam=E8che?=) Date: Thu, 25 Jun 2009 17:19:17 +0200 Subject: [Xorp-users] How to AS prepend ? Message-ID: Hi everybody, I am new to Xorp (say 3 days). I'm doing some tests and comparisons between Quagga, OpenBGP and Xorp. And Xorp is nice. We want to redistribute some (carefully selected) OSPF routes to BGP. This works. However, there is still something I can't do : AS prepending. My configuration is : .../... bgp { bgp-id: A.B.C.34 local-as: "64512" peer "A.B.C.33" { local-ip: "A.B.C.34" as: "65042" next-hop: A.B.C.34 import: "filter_bgp_std" } export: "ospf_to_bgp" } .../... policy-statement "ospf_to_bgp" { term ip1 { from { protocol: "ospf4" network4: X.Y.Z.0/23 } then { as-path-prepend: 64512 } } } .../... The prefix "X.Y.Z.0/23" is announced to my peer since I know it from my OSPF neighbor. But the AS path seen by my BGP peer is (only) "64512". I have carefully read the doc, crawled other Google and made several tests with several configurations (and also played with "as-path- expand"). But still can't find how to do it. Now, I have a terrible headache ;o) What am I doing wrong ? Thanks, -- Seb ?Un peuple pr?t ? sacrifier un peu de libert? pour un peu de s?curit? ne m?rite ni l?une ni l?autre, et finit par perdre les deux.? -- Thomas Jefferson. From bms at incunabulum.net Thu Jun 25 09:32:45 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 25 Jun 2009 17:32:45 +0100 Subject: [Xorp-users] How to AS prepend ? In-Reply-To: References: Message-ID: <4A43A6AD.5000005@incunabulum.net> Hi, The routes redistributed from OSPF into BGP are not going to have an AS-attribute to begin with, so prepend will be prepending to what is essentially an empty list. S?bastien Nam?che wrote: > The prefix "X.Y.Z.0/23" is announced to my peer since I know it from > my OSPF neighbor. But the AS path seen by my BGP peer is (only) "64512". > > I have carefully read the doc, crawled other Google and made several > tests with several configurations (and also played with "as-path- > expand"). But still can't find how to do it. Now, I have a terrible > headache ;o) > > What am I doing wrong ? > I'm surprised 64512 works at all -- as-path-prepend is specified to take a 'txt' value in the configuration, I would have thought the value would have required quotes. Is this not your desired result? Your local-as is clearly set to 64512. thanks BMS From appletrp at gmail.com Thu Jun 25 11:48:49 2009 From: appletrp at gmail.com (Robert Appleton) Date: Thu, 25 Jun 2009 14:48:49 -0400 Subject: [Xorp-users] static configuration Message-ID: I just want to set up a basic static configuration so that I can start messing with different things. How do I make the configuration file? I have it set to eth0 but it says it can not add my IP address. How do you know what IP address to put down. I'm running Fedora 10 and I'm new to this. Any help is appreciated, let me know if I need to include more information. Thanks. - Robert Appleton -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090625/196977a4/attachment.html From vommwa at yahoo.com Thu Jun 25 13:35:51 2009 From: vommwa at yahoo.com (victor omwando) Date: Thu, 25 Jun 2009 13:35:51 -0700 (PDT) Subject: [Xorp-users] static configuration In-Reply-To: References: Message-ID: <982372.59912.qm@web56608.mail.re3.yahoo.com> I can't see your config file, can you copy and paste it on the email body and resend the email? I'm assuming it's pretty small. ________________________________ From: Robert Appleton To: xorp-users at xorp.org Sent: Thursday, June 25, 2009 2:48:49 PM Subject: [Xorp-users] static configuration I just want to set up a basic static configuration so that I can start messing with different things. How do I make the configuration file? I have it set to eth0 but it says it can not add my IP address. How do you know what IP address to put down. I'm running Fedora 10 and I'm new to this. Any help is appreciated, let me know if I need to include more information. Thanks. -?Robert Appleton -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090625/869f8023/attachment.html From seb at anet.fr Thu Jun 25 13:43:22 2009 From: seb at anet.fr (=?ISO-8859-1?Q?S=E9bastien_Nam=E8che?=) Date: Thu, 25 Jun 2009 22:43:22 +0200 Subject: [Xorp-users] How to AS prepend ? In-Reply-To: <4A43A6AD.5000005@incunabulum.net> References: <4A43A6AD.5000005@incunabulum.net> Message-ID: <7EA4A6BF-72C7-41FC-BE50-5F861FDB0FBA@anet.fr> Bruce, Le 25 juin 09 ? 18:32, Bruce Simpson a ?crit : > The routes redistributed from OSPF into BGP are not going to have an > AS-attribute to begin with, so prepend will be prepending to what is > essentially an empty list. I understand. > S?bastien Nam?che wrote: >> The prefix "X.Y.Z.0/23" is announced to my peer since I know it >> from my OSPF neighbor. But the AS path seen by my BGP peer is >> (only) "64512". >> >> I have carefully read the doc, crawled other Google and made >> several tests with several configurations (and also played with >> "as-path- expand"). But still can't find how to do it. Now, I have >> a terrible headache ;o) >> >> What am I doing wrong ? >> > > I'm surprised 64512 works at all -- as-path-prepend is specified to > take a 'txt' value in the configuration, I would have thought the > value would have required quotes. Nop, it's a "u32" (at least for 1.6). Seeing in 1.6 source code : ./docs/user_manual/policy.tex 124: as-path-prepend: u32; And "xorpsh" refuses a string. > Is this not your desired result? Your local-as is clearly set to > 64512. Yes, but this is not exactly what we want. We would like to prepend our AS to one of the prefix distributed from OSPF to BGP. Actually, the piece of configuration I sent was simplified in order to isolate the problem. The configuration we want to run will be something like : ----- policy-statement "ospf_to_bgp" { term ip1 { from { protocol: "ospf4" network4: X.Y.Z.0/23 } } term ip2 { from { protocol: "ospf4" network4: X.Y.W.0/23 } then { as-path-prepend: 64512 } } } ----- Our goal is to announce the first prefix to this peer so that the route through this router will be the best. At the same time, we also want to announce another prefix, but this router will act as a "backup" route for "X.Y.W.0/23". This prefix will be announced by another router with a shortest path. So we need to prepend our AS to the path of the second prefix for this router. Regards, -- Seb From bms at incunabulum.net Fri Jun 26 06:10:08 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Fri, 26 Jun 2009 14:10:08 +0100 Subject: [Xorp-users] How to AS prepend ? In-Reply-To: <833E46C9-53EE-4A36-B3E6-EF0B67EA25BF@nameche.fr> References: <4A43A6AD.5000005@incunabulum.net> <833E46C9-53EE-4A36-B3E6-EF0B67EA25BF@nameche.fr> Message-ID: <4A44C8B0.4080603@incunabulum.net> S?bastien Nam?che wrote: > ... > Nop, it's a "u32" (at least for 1.6). Sorry, I was looking at as-path-list. Next... >> Is this not your desired result? Your local-as is clearly set to 64512. > > Yes, but this is not exactly what we want. We would like to prepend > our AS to one of the prefix distributed from OSPF to BGP. What is your desired as-path on the redistributed route(s), in the output you'd expect to see in the BGP routing table ? > ... > Our goal is to announce the first prefix to this peer so that the > route through this router will be the best. That looks fine, subject to AS local-pref. Does this part work for you as expected? > At the same time, we also want to announce another prefix, but this > router will act as a "backup" route for "X.Y.W.0/23". This prefix will > be announced by another router with a shortest path. So we need to > prepend our AS to the path of the second prefix for this router. So your intention is in fact to announce the same prefix X.Y.W.0/23, from the XORP BGP router, but with your AS path prepended to the existing AS path advertised by another BGP router which already announces prefix X.Y.W.0/23? This isn't going to work if you're directly applying the policy to the route redistributed from OSPF, as described earlier; it sounds as though you need to inject this prefix announcement manually, and/or specify the AS of your peer with the shortest path explicitly. thanks, BMS From vommwa at yahoo.com Fri Jun 26 07:35:40 2009 From: vommwa at yahoo.com (victor omwando) Date: Fri, 26 Jun 2009 07:35:40 -0700 (PDT) Subject: [Xorp-users] static configuration In-Reply-To: References: <982372.59912.qm@web56608.mail.re3.yahoo.com> Message-ID: <324162.61820.qm@web56601.mail.re3.yahoo.com> First off, the XORP manual is a very good place to start if you're a beginner like me; it's a relatively light read, and the individual chapters are short and to the point. For your use, I'd recommend chapters 2 and 3, just go get a good feel of how to configure interfaces. First off, if you're configuring the interface that is currently being used by the system, make sure there is no mismatch in the 'address', 'prefix-length' and 'broadcast' segments. The broadcast segment is mandatory when you're configuring an IPv4 address in XORP. Also, at each level in the interface configuration hierachy, (interface, vif and address) it is necessary to include the line 'disable: false', if you want to enable the interface, vif and address respectively. Also, it is not mandatory in some places, but it is good practice to include quotations for arguments that are described as text in the manual , eg 'interface "eth0" '. It's not mandatory here, but trust me, when you get to some policy and protocol sections, it might make you pull hairs forgetting this fact with some fields. Again, consult the manual to get the syntax for various sections, and where text fields are and are not required. So, assuming that your address settings are the same as the computer you are using, the config 'should' look like this: interfaces { interface "eth0" { disable: false vif "eth0" { address 192.168.1.100 { prefix-length: 24 broadcast: 192.168.1.255 disable: false } } } } fea { unicast-forwarding4 { disable: false } } protocols { static { route 192.168.1.101/24 { next-hop: 192.168.1.100 } }} Also, if you have a physical interface that has only one virtual interface, and you want that interface to use the same configuration that the system has assigned to the router, you can use the 'default-system-config' line to specify that the configuration should be obtained form the default system config (again, assuming that the physical interface has already been configured). NOTE that is the 'default-system-config' is used, then the 'vif' and 'address' sections must not be configured. Thus: interfaces { interface "eth0" { default-system-config disable: false } } fea { unicast-forwarding4 { disable: false } } protocols { static { route 192.168.1.101/24 { next-hop: 192.168.1.100 } } } This is just if you have physical interfaces that do not have any virtual interfaces. If you have vifs, then you can't use this. Sorry for being wordy, but I hope this helps. ________________________________ From: Robert Appleton To: victor omwando Sent: Friday, June 26, 2009 7:42:32 AM Subject: Re: [Xorp-users] static configuration Here it is below, any help to get this working is appreciated. interfaces { interface eth0 { vif eth0 { address 192.168.1.100 { prefix-length: 24 } } } } fea { unicast-forwarding4 { disable: false } } protocols { static { route 192.168.1.101/24 { next-hop: 192.168.1.100 } } } On Thu, Jun 25, 2009 at 4:35 PM, victor omwando wrote: I can't see your config file, can you copy and paste it on the email body and resend the email? I'm assuming it's pretty small. ________________________________ From: Robert Appleton To: xorp-users at xorp.org Sent: Thursday, June 25, 2009 2:48:49 PM Subject: [Xorp-users] static configuration I just want to set up a basic static configuration so that I can start messing with different things. How do I make the configuration file? I have it set to eth0 but it says it can not add my IP address. How do you know what IP address to put down. I'm running Fedora 10 and I'm new to this. Any help is appreciated, let me know if I need to include more information. Thanks. - Robert Appleton -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090626/ef01f89a/attachment.html From jnebrera at eneotecnologia.com Sun Jun 28 04:28:59 2009 From: jnebrera at eneotecnologia.com (Jaime Nebrera) Date: Sun, 28 Jun 2009 13:28:59 +0200 Subject: [Xorp-users] Multicore scalability Message-ID: <1246188539.7329.3.camel@blas> Hi all, I'm just wondering on multicore scalability for XORP. I'm aware XORP uses a different process per protocol, so if you have multiple routing protocols active at a given time you can fully exploit this. But what happens if you only use a particular routing protocol, say OSPF or whatever? If I understand it properly, the routing is done at the kernel level (using the standard Linux forwarding mode), and thus should scale with multiple cores. When a control package arrives or there is a route cache miss this "forwarding data plane" asks the user space process on the outcome of the package. This part is essentially mono core, but the forwarding itself should be multi core capable. Am I right? Thanks and regards -- ?Jaime Nebrera - jnebrera at eneotecnologia.com Consultor TI - ENEO Tecnologia SL Pol. PISA - C/ Manufactura 6, P1, 3B Mairena del Aljarafe - 41927 - Sevilla Telf.- 955 60 11 60 / 619 04 55 18 From bms at incunabulum.net Sun Jun 28 05:03:26 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Sun, 28 Jun 2009 13:03:26 +0100 Subject: [Xorp-users] Multicore scalability In-Reply-To: <1246188539.7329.3.camel@blas> References: <1246188539.7329.3.camel@blas> Message-ID: <4A475C0E.2010709@incunabulum.net> Jaime Nebrera wrote: > ... > If I understand it properly, the routing is done at the kernel level > (using the standard Linux forwarding mode), and thus should scale with > multiple cores. When a control package arrives or there is a route cache > miss this "forwarding data plane" asks the user space process on the > outcome of the package. > > This part is essentially mono core, but the forwarding itself should > be multi core capable. > > Am I right? > Yup. The BSD/Linux software forwarding planes will make use of multiple cores -- how scalable it is, though, is down to the implementation. Usually only 1 route at a time can be pushed to the kernel as they generally use some kind of reader-writer lock, even if the routing/netlink sockets use message passing. But the user space "route miss" behaviour you describe doesn't normally exist. There are hooks available in PF_ROUTE and PF_NETLINK to do it, but to my knowledge it is never used for normal IP forwarding. It originally existed to support X.25, it can be used to support on-demand routing protocols for tactical MANET networks (e.g. AODV). If XORP were refactored to use Boost ASIO -- threading the individual processes will get easier. At the end of the day, multicore optimization is largely down to appropriate use of shared data structures/locking/lock-free techniques -- and understanding the system as a whole. cheers, BMS From jnebrera at eneotecnologia.com Sun Jun 28 05:32:12 2009 From: jnebrera at eneotecnologia.com (Jaime Nebrera) Date: Sun, 28 Jun 2009 14:32:12 +0200 Subject: [Xorp-users] Multicore scalability In-Reply-To: <4A475C0E.2010709@incunabulum.net> References: <1246188539.7329.3.camel@blas> <4A475C0E.2010709@incunabulum.net> Message-ID: <1246192332.7329.10.camel@blas> Hi Bruce, Thanks for your prompt reply :) > Yup. The BSD/Linux software forwarding planes will make use of multiple > cores -- how scalable it is, though, is down to the implementation. Great > Usually only 1 route at a time can be pushed to the kernel as they > generally use some kind of reader-writer lock, even if the > routing/netlink sockets use message passing. Understood > But the user space "route miss" behaviour you describe doesn't normally > exist. There are hooks available in PF_ROUTE and PF_NETLINK to do it, > but to my knowledge it is never used for normal IP forwarding. It > originally existed to support X.25, it can be used to support on-demand > routing protocols for tactical MANET networks (e.g. AODV). Well, I'm not that much interested in that part. Surely I didnt explain it fully properly. > If XORP were refactored to use Boost ASIO -- threading the individual > processes will get easier. At the end of the day, multicore optimization > is largely down to appropriate use of shared data > structures/locking/lock-free techniques -- and understanding the system > as a whole. Yep, I'm aware of this. Actually thats why I was making my question. I have been reading quite a lot on forwarding improvements (RSS, lock contention reduction, flow affinity, bottlenecks, ...) but in this docs they dont talk about XORP side by itself. As I'm aware XORP is monothread per routing protocol, I didnt want to invest long time in optimizing the forwarding plane and then discover that doesnt work properly with XORP :( Regards -- ?Jaime Nebrera - jnebrera at eneotecnologia.com Consultor TI - ENEO Tecnologia SL Pol. PISA - C/ Manufactura 6, P1, 3B Mairena del Aljarafe - 41927 - Sevilla Telf.- 955 60 11 60 / 619 04 55 18 From bms at incunabulum.net Sun Jun 28 05:41:25 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Sun, 28 Jun 2009 13:41:25 +0100 Subject: [Xorp-users] Multicore scalability In-Reply-To: <1246192332.7329.10.camel@blas> References: <1246188539.7329.3.camel@blas> <4A475C0E.2010709@incunabulum.net> <1246192332.7329.10.camel@blas> Message-ID: <4A4764F5.3060005@incunabulum.net> Jaime Nebrera wrote: > ... > Yep, I'm aware of this. Actually thats why I was making my question. I > have been reading quite a lot on forwarding improvements (RSS, lock > contention reduction, flow affinity, bottlenecks, ...) but in this docs > they dont talk about XORP side by itself. As I'm aware XORP is > monothread per routing protocol, I didnt want to invest long time in > optimizing the forwarding plane and then discover that doesnt work > properly with XORP :( > Well, XORP is control plane software. Sure, it could benefit from optimization of the FEA->kernel plumb -- what wouldn't -- normally the FEA batch loads this stuff, at the end of the day it's limited by whatever interface is available to the forwarding plane. Most of the time BSD/Linux are not being used in the Default-Free Zone, so the defaults are not optimized for that use case. It entirely depends on what one wishes to achieve. All software forwarding planes have similar limitations, the hardware solution is usually some form of TCAM (ternary content-addressable memory). Various platforms (e.g. in Juniper, Cisco, other vendor space) have more or less TCAM. It is worth bearing in mind which use case of the router you are optimizing for -- routers in the Default-Free Zone have quite different performance requirements from edge routers or MPLS nodes. In fact one could say that was one big motivation behind MPLS... to save money on expensive TCAM boxes. cheers, BMS From jnebrera at eneotecnologia.com Sun Jun 28 22:31:00 2009 From: jnebrera at eneotecnologia.com (Jaime Nebrera) Date: Mon, 29 Jun 2009 07:31:00 +0200 Subject: [Xorp-users] Multicore scalability In-Reply-To: <4A4764F5.3060005@incunabulum.net> References: <1246188539.7329.3.camel@blas> <4A475C0E.2010709@incunabulum.net> <1246192332.7329.10.camel@blas> <4A4764F5.3060005@incunabulum.net> Message-ID: <1246253461.6331.3.camel@blas> Hi, > Well, XORP is control plane software. Those are the magic words I was looking for :) Any improvement we do in the forwarding plane will be exploitable by XORP itself. > All software forwarding planes have similar limitations, the hardware > solution is usually some form of TCAM (ternary content-addressable > memory). Various platforms (e.g. in Juniper, Cisco, other vendor space) > have more or less TCAM. It is worth bearing in mind which use case of > the router you are optimizing for -- routers in the Default-Free Zone > have quite different performance requirements from edge routers or MPLS > nodes. I'm aware of that. In software first comes CPU (now solved with RSS), then RAM latency (seems improved with Nehalem and AMD), next FSB, etc etc I have been reading many articles from academic and Intel and well, at least things are now better than a couple of years back. Still, as you remind, most problems are related to memory management. Kind regards -- ?Jaime Nebrera - jnebrera at eneotecnologia.com Consultor TI - ENEO Tecnologia SL Pol. PISA - C/ Manufactura 6, P1, 3B Mairena del Aljarafe - 41927 - Sevilla Telf.- 955 60 11 60 / 619 04 55 18 From appletrp at gmail.com Mon Jun 29 11:47:25 2009 From: appletrp at gmail.com (Robert Appleton) Date: Mon, 29 Jun 2009 14:47:25 -0400 Subject: [Xorp-users] Basic questions for static routing Message-ID: Hi All, I just got xorp running today, but now am trying to figure out how to configure a simple static route between 2 computers (3 including the one xorp is on) on different subnets. I have them set on different subnets through a switch (for testing purposes at the moment. I just want them to be able to ping each other. How do I need to configure the computer with xorp on it? (I'm running fedora). Do I need to alter anything in my boot file pasted below? Thanks for the help. Let me know if more information is needed. - Robert Appleton interfaces { interface "eth0" { disable: false vif "eth0" { address 192.168.1.0 { prefix-length: 24 broadcast: 192.168.1.255 disable: false } } vif "eth0" { address 192.168.2.0 { prefix-length: 24 broadcast: 192.168.2.255 disable: false } } } } fea { unicast-forwarding4 { disable: false } } protocols { static { route 192.168.1.0/24 { next-hop:192.168.2.120 metric: 3 } } static { route 192.168.2.0/24 { next-hop:192.168.1.110 metric: 3 } } } From rae.harbird at gmail.com Tue Jun 30 03:29:19 2009 From: rae.harbird at gmail.com (Rae Harbird) Date: Tue, 30 Jun 2009 11:29:19 +0100 Subject: [Xorp-users] Emulating simple network for testing XORP code Message-ID: Hi Does anyone have recommendations for emulating a small, simple network of XORP routers on a single Linux platform? I want to test my XORP code. Cheers, Rae -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090630/c317111a/attachment.html From bms at incunabulum.net Tue Jun 30 04:02:03 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Tue, 30 Jun 2009 12:02:03 +0100 Subject: [Xorp-users] Emulating simple network for testing XORP code In-Reply-To: References: Message-ID: <4A49F0AB.6010001@incunabulum.net> Rae Harbird wrote: > > Hi > > > Does anyone have recommendations for emulating a small, simple network > of XORP routers on a single Linux platform? I want to test my XORP code. There is something out there that might wrap XORP in some kind of virtualization environment, although I can't remember what the name of this thing is -- it was mentioned on this list in the last 12 months, a trawl through the list archives may help. Sorry, it's just a vague memory at the moment. thanks, BMS From bms at incunabulum.net Tue Jun 30 04:11:13 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Tue, 30 Jun 2009 12:11:13 +0100 Subject: [Xorp-users] Basic questions for static routing In-Reply-To: References: Message-ID: <4A49F2D1.7010801@incunabulum.net> Hello, Robert Appleton wrote: > Hi All, > > I just got xorp running today, but now am trying to figure out how to > configure a simple static route between 2 computers (3 including the > one xorp is on) on different subnets. I have them set on different > subnets through a switch (for testing purposes at the moment. I just > want them to be able to ping each other. How do I need to configure > the computer with xorp on it? (I'm running fedora). Do I need to alter > anything in my boot file pasted below? Thanks for the help. Let me > know if more information is needed. > You might want to fold the vif {} and static {} blocks together as they should actually get parsed as same block, however this may just be stylistic. Not knowing your network topology, I couldn't say further, apart from the above issue your config looks fine. Do remember that in order for ICMP echo packets to be transmitted and received, all of the machines involved must have valid routes pointing to each other's network prefix, or otherwise be reachable i.e. in both directions. You need at least one way of reaching the XORP box i.e. a management interface, normally this must be configured at boot in your distribution using its normal procedures. Different subnets on same physical switch is fine for testing, but it's usually discouraged for operational reasons. You will of course need to have the appropriate configuration in place on the other machines for this. I'm not familiar with Fedora, so can't advise on how you might do that, hopefully others can help. hope this helps BMS From r.harbird at cs.ucl.ac.uk Tue Jun 30 04:33:03 2009 From: r.harbird at cs.ucl.ac.uk (Rae Harbird) Date: Tue, 30 Jun 2009 12:33:03 +0100 Subject: [Xorp-users] Emulating simple network for testing XORP code In-Reply-To: <4A49F0AB.6010001@incunabulum.net> References: <4A49F0AB.6010001@incunabulum.net> Message-ID: Hi This was probably IMUNES. Since I last touched IMUNES, I believe it is being ported rewritten for the FreeBSD Network Stack Virtualization Project: http://wiki.FreeBSD.org/Image >From the wiki: "The network stack virtualization project aims at extending the FreeBSD kernel to maintain multiple independent instances of networking state" I don't think it's ready for use in this incarnation yet and I'm not sure that the previous instantiation (imunes) is supported. I have cc'd Marco Zec, the principle developer, as this information may not be up-to-date. Any other options? Rae === 2009/6/30 Bruce Simpson > Rae Harbird wrote: > >> >> Hi >> >> >> Does anyone have recommendations for emulating a small, simple network of >> XORP routers on a single Linux platform? I want to test my XORP code. >> > > There is something out there that might wrap XORP in some kind of > virtualization environment, although I can't remember what the name of this > thing is -- it was mentioned on this list in the last 12 months, a trawl > through the list archives may help. Sorry, it's just a vague memory at the > moment. > > thanks, > BMS > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090630/4e256ca0/attachment.html From bms at incunabulum.net Tue Jun 30 04:52:20 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Tue, 30 Jun 2009 12:52:20 +0100 Subject: [Xorp-users] Emulating simple network for testing XORP code In-Reply-To: References: <4A49F0AB.6010001@incunabulum.net> Message-ID: <4A49FC74.8000507@incunabulum.net> Rae Harbird wrote: > Hi > > This was probably IMUNES. Since I last touched IMUNES, I believe it is > being ported rewritten for the FreeBSD Network Stack Virtualization > Project: I was actually thinking of a Linux based solution with a somewhat obscure name :-) It had a XORP config generator, I think parts of it were written in Python or possibly Ruby. I believe IMUNES should supported by the upcoming FreeBSD 8.0 release, of course Marko would know more. Not sure if XORP integration is on the radar there, if at all. Major code surgery is likely anyway, so if it did, it would probably be locked to an earlier release. cheers, BMS From greearb at candelatech.com Tue Jun 30 08:46:58 2009 From: greearb at candelatech.com (Ben Greear) Date: Tue, 30 Jun 2009 08:46:58 -0700 Subject: [Xorp-users] Emulating simple network for testing XORP code In-Reply-To: References: Message-ID: <4A4A3372.1050404@candelatech.com> Rae Harbird wrote: > > Hi > > > Does anyone have recommendations for emulating a small, simple network > of XORP routers on a single Linux platform? I want to test my XORP code. > Our LANforge product uses a slightly modified xorp (and modified linux kernel) to achieve this. Our main controller code isn't open-source though, and to add support for new Xorp features requires code changes to our product (we do work for hire and general improvement of our products, and may be willing to do work for free, depending on the nature of the work). Our kernel patches (minus the impairment generator) are open-source and freely available, as is my git tree of xorp plus my changes. I can tell you though: It is not trivial to write a virtual router framework. It took us several months and we already had part of the work done, and the general framework in place. I'm still debugging xorp too, it just barely deals with dynamic network re-configuration, for example, but it's pretty solid with a static network emulation (ie, no links between routers coming and going.) We auto-generate perl scripts that do the linux stack configuration, and we auto-generate the xorp config files. If these things don't scare you, I'll be happy to a post simple example. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From yueli.m at gmail.com Tue Jun 30 09:13:23 2009 From: yueli.m at gmail.com (Yue Li) Date: Tue, 30 Jun 2009 12:13:23 -0400 Subject: [Xorp-users] Emulating simple network for testing XORP code In-Reply-To: References: <4A49F0AB.6010001@incunabulum.net> Message-ID: <49567c360906300913w16cc311dkdcbb001d67e1136b@mail.gmail.com> We have done this using OpenVZ and a network emulator PRIME on Linux. Please check out the link below. http://www.primessf.net/pub/Public/WebHome/paper-xorpbgp.pdf On Tue, Jun 30, 2009 at 7:33 AM, Rae Harbird wrote: > Hi > > This was probably IMUNES. Since I last touched IMUNES, I believe it is > being ported rewritten for the FreeBSD Network Stack Virtualization Project: > > http://wiki.FreeBSD.org/Image > > From the wiki: "The network stack virtualization project aims at extending > the FreeBSD kernel to maintain multiple independent instances of networking > state" > > I don't think it's ready for use in this incarnation yet and I'm not sure > that the previous instantiation (imunes) is supported. > > I have cc'd Marco Zec, the principle developer, as this information may not > be up-to-date. > > Any other options? > > > > Rae > === > > 2009/6/30 Bruce Simpson > >> Rae Harbird wrote: >> >>> >>> Hi >>> >>> >>> Does anyone have recommendations for emulating a small, simple network of >>> XORP routers on a single Linux platform? I want to test my XORP code. >>> >> >> There is something out there that might wrap XORP in some kind of >> virtualization environment, although I can't remember what the name of this >> thing is -- it was mentioned on this list in the last 12 months, a trawl >> through the list archives may help. Sorry, it's just a vague memory at the >> moment. >> >> thanks, >> BMS >> > > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090630/e234bf75/attachment.html From vommwa at yahoo.com Tue Jun 30 13:08:43 2009 From: vommwa at yahoo.com (victor omwando) Date: Tue, 30 Jun 2009 13:08:43 -0700 (PDT) Subject: [Xorp-users] Emulating simple network for testing XORP code In-Reply-To: <49567c360906300913w16cc311dkdcbb001d67e1136b@mail.gmail.com> References: <4A49F0AB.6010001@incunabulum.net> <49567c360906300913w16cc311dkdcbb001d67e1136b@mail.gmail.com> Message-ID: <694106.2385.qm@web56602.mail.re3.yahoo.com> You should also probably check out Netkit (wiki.netkit.org). It's based on UML, but does a lot of the uml-switched for you and as a result it is quite easy to use and the learning curve isn't steep at all. Currently, I'm using it to create networks to test a DSL based on Haskell that generated XORP config files from the give nsource code. ________________________________ From: Yue Li To: Rae Harbird Cc: xorp-users at xorp.org; Marko Zec ; zec at fer.hr Sent: Tuesday, June 30, 2009 12:13:23 PM Subject: Re: [Xorp-users] Emulating simple network for testing XORP code We have done this using OpenVZ and a network emulator PRIME on Linux. Please check out the link below. http://www.primessf.net/pub/Public/WebHome/paper-xorpbgp.pdf On Tue, Jun 30, 2009 at 7:33 AM, Rae Harbird wrote: >Hi > >This was probably IMUNES. Since I last touched IMUNES, I believe it is being ported rewritten for the FreeBSD Network Stack Virtualization Project: > >http://wiki.freebsd.org/Image > >From the wiki: "The network stack virtualization project aims at extending the FreeBSD kernel to >maintain multiple independent instances of networking state" > >I don't think it's ready for use in this incarnation yet and I'm not sure that the previous instantiation (imunes) is supported. > >> >I have cc'd Marco Zec, the principle developer, as this information may not be up-to-date. > >Any other options? > > > >Rae >=== > > >2009/6/30 Bruce Simpson > > >Rae Harbird wrote: >> >> >>>>>>Hi >>> >>> >>>>>>Does anyone have recommendations for emulating a small, simple network of XORP routers on a single Linux platform? I want to test my XORP code. >>> >> >>There is something out there that might wrap XORP in some kind of virtualization environment, although I can't remember what the name of this thing is -- it was mentioned on this list in the last 12 months, a trawl through the list archives may help. Sorry, it's just a vague memory at the moment. >> >>>>thanks, >>>>BMS >> > > > >_______________________________________________ >>Xorp-users mailing list >Xorp-users at xorp.org >http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090630/80326e3a/attachment.html From yueli.m at gmail.com Tue Jun 30 19:03:33 2009 From: yueli.m at gmail.com (Yue Li) Date: Tue, 30 Jun 2009 22:03:33 -0400 Subject: [Xorp-users] Emulating simple network for testing XORP code In-Reply-To: <694106.2385.qm@web56602.mail.re3.yahoo.com> References: <4A49F0AB.6010001@incunabulum.net> <49567c360906300913w16cc311dkdcbb001d67e1136b@mail.gmail.com> <694106.2385.qm@web56602.mail.re3.yahoo.com> Message-ID: <49567c360906301903t1dff4699gddc8ba05e5df4860@mail.gmail.com> Thanks, this is cool. One comment is that UML seems not to be an efficient virtual machine. For example we can run hundreds of OpenVZ containers on one physical machine (8GB memory). I guess you can't achieve this on UML :) -Yue Li On Tue, Jun 30, 2009 at 4:08 PM, victor omwando wrote: > You should also probably check out Netkit (wiki.netkit.org). It's based on > UML, but does a lot of the uml-switched for you and as a result it is quite > easy to use and the learning curve isn't steep at all. Currently, I'm using > it to create networks to test a DSL based on Haskell that generated XORP > config files from the give nsource code. > ------------------------------ > *From:* Yue Li > *To:* Rae Harbird > *Cc:* xorp-users at xorp.org; Marko Zec ; zec at fer.hr > *Sent:* Tuesday, June 30, 2009 12:13:23 PM > *Subject:* Re: [Xorp-users] Emulating simple network for testing XORP code > > We have done this using OpenVZ and a network emulator PRIME on Linux. > Please check out the link below. > > http://www.primessf.net/pub/Public/WebHome/paper-xorpbgp.pdf > > > > On Tue, Jun 30, 2009 at 7:33 AM, Rae Harbird wrote: > >> Hi >> >> This was probably IMUNES. Since I last touched IMUNES, I believe it is >> being ported rewritten for the FreeBSD Network Stack Virtualization Project: >> >> http://wiki.freebsd.org/Image >> >> From the wiki: "The network stack virtualization project aims at extending >> the FreeBSD kernel to maintain multiple independent instances of networking >> state" >> >> I don't think it's ready for use in this incarnation yet and I'm not sure >> that the previous instantiation (imunes) is supported. >> >> I have cc'd Marco Zec, the principle developer, as this information may >> not be up-to-date. >> >> Any other options? >> >> >> >> Rae >> === >> >> 2009/6/30 Bruce Simpson >> >>> Rae Harbird wrote: >>> >>>> >>>> Hi >>>> >>>> >>>> Does anyone have recommendations for emulating a small, simple network >>>> of XORP routers on a single Linux platform? I want to test my XORP code. >>>> >>> >>> There is something out there that might wrap XORP in some kind of >>> virtualization environment, although I can't remember what the name of this >>> thing is -- it was mentioned on this list in the last 12 months, a trawl >>> through the list archives may help. Sorry, it's just a vague memory at the >>> moment. >>> >>> thanks, >>> BMS >>> >> >> >> >> >> _______________________________________________ >> Xorp-users mailing list >> Xorp-users at xorp.org >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090630/fe5a8b4f/attachment.html From eruttamkumawat at gmail.com Tue Jun 30 21:37:42 2009 From: eruttamkumawat at gmail.com (*Uttam* *Kumawat*) Date: Wed, 1 Jul 2009 10:07:42 +0530 Subject: [Xorp-users] Emulating simple network for testing XORP code Message-ID: hi, I had tried the emulation of a simple network using XORP router. Brief overview is as follows: Initially, started working with OpenVZ only. Created containers with ostemplate fedoracore- 4-i386-minimal and configured them appropriately i.e. assigned hostname, ipaddress, enabled services such as ssh, web service, etc. It was able to ping any of the configured system in container from anywhere. Then copied the binary of xorp in two container VH101 and VH102. ( You can also compile xorp in a container but it will require gcc to be installed in container.) Configured static route in xorp in VH101 such that it should take packets from hardware and forward it to VH101. Similarly configured static route in xorp in VH102 such that it should forward the received packets to hardware node. In this simple setup, OpenVZ was creating an interface venet0 and all the containers were connected with this interface. Problems faced : ? After configuration of xorp, it was not able to commit the configuration. ? There was only one interface of communication among containers and hardware node. ? There was no MAC address of the venet0 interface. To solve this problem, used the concept of bridge along with OpenVZ. Created a bridge and assigned the eth0 of the hardware node to the bridge. Assigned ip address to this interface. Created the container with an eth0 interface and added it to the bridge and also done the necessary configuration of the container. Installed xorp in it. Configured static route and commited. It is now working fine. Software Requirements: Hardware Node Configuration: Red Hat Enterprise Linux 4 with ovzkernel version 2.6.9-023stab048.4 i686 i686 i386 GNU/Linux OpenVZ Software OS Template Used for Containers : fedora-core-4-i386-minimal OS template Bridge Utility Package: bridge-utils-1.0.4-4.i386.rpm Regards Uttam >Does anyone have recommendations for emulating a small, simple network of >XORP routers on a single Linux platform? I want to test my XORP code. On Wed, Jul 1, 2009 at 12:30 AM, wrote: > Send Xorp-users mailing list submissions to > xorp-users at xorp.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > or, via email, send a message with subject or body 'help' to > xorp-users-request at xorp.org > > You can reach the person managing the list at > xorp-users-owner at xorp.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Xorp-users digest..." > > > Today's Topics: > > 1. Emulating simple network for testing XORP code (Rae Harbird) > 2. Re: Emulating simple network for testing XORP code (Bruce Simpson) > 3. Re: Basic questions for static routing (Bruce Simpson) > 4. Re: Emulating simple network for testing XORP code (Rae Harbird) > 5. Re: Emulating simple network for testing XORP code (Bruce Simpson) > 6. Re: Emulating simple network for testing XORP code (Ben Greear) > 7. Re: Emulating simple network for testing XORP code (Yue Li) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 30 Jun 2009 11:29:19 +0100 > From: Rae Harbird > Subject: [Xorp-users] Emulating simple network for testing XORP code > To: xorp-users at xorp.org > Message-ID: > > Content-Type: text/plain; charset="iso-8859-1" > > Hi > > > Does anyone have recommendations for emulating a small, simple network of > XORP routers on a single Linux platform? I want to test my XORP code. > > > Cheers, > > > > > Rae > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090630/c317111a/attachment-0001.html > > ------------------------------ > > Message: 2 > Date: Tue, 30 Jun 2009 12:02:03 +0100 > From: Bruce Simpson > Subject: Re: [Xorp-users] Emulating simple network for testing XORP > code > To: r.harbird at cs.ucl.ac.uk > Cc: xorp-users at xorp.org > Message-ID: <4A49F0AB.6010001 at incunabulum.net> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Rae Harbird wrote: > > > > Hi > > > > > > Does anyone have recommendations for emulating a small, simple network > > of XORP routers on a single Linux platform? I want to test my XORP code. > > There is something out there that might wrap XORP in some kind of > virtualization environment, although I can't remember what the name of > this thing is -- it was mentioned on this list in the last 12 months, a > trawl through the list archives may help. Sorry, it's just a vague > memory at the moment. > > thanks, > BMS > > > > ------------------------------ > > Message: 3 > Date: Tue, 30 Jun 2009 12:11:13 +0100 > From: Bruce Simpson > Subject: Re: [Xorp-users] Basic questions for static routing > To: Robert Appleton > Cc: xorp-users at xorp.org > Message-ID: <4A49F2D1.7010801 at incunabulum.net> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello, > > Robert Appleton wrote: > > Hi All, > > > > I just got xorp running today, but now am trying to figure out how to > > configure a simple static route between 2 computers (3 including the > > one xorp is on) on different subnets. I have them set on different > > subnets through a switch (for testing purposes at the moment. I just > > want them to be able to ping each other. How do I need to configure > > the computer with xorp on it? (I'm running fedora). Do I need to alter > > anything in my boot file pasted below? Thanks for the help. Let me > > know if more information is needed. > > > > You might want to fold the vif {} and static {} blocks together as > they should actually get parsed as same block, however this may just be > stylistic. Not knowing your network topology, I couldn't say further, > apart from the above issue your config looks fine. > > Do remember that in order for ICMP echo packets to be transmitted > and received, all of the machines involved must have valid routes > pointing to each other's network prefix, or otherwise be reachable i.e. > in both directions. > > You need at least one way of reaching the XORP box i.e. a management > interface, normally this must be configured at boot in your distribution > using its normal procedures. > Different subnets on same physical switch is fine for testing, but > it's usually discouraged for operational reasons. You will of course > need to have the appropriate configuration in place on the other > machines for this. > > I'm not familiar with Fedora, so can't advise on how you might do > that, hopefully others can help. > > hope this helps > BMS > > > > ------------------------------ > > Message: 4 > Date: Tue, 30 Jun 2009 12:33:03 +0100 > From: Rae Harbird > Subject: Re: [Xorp-users] Emulating simple network for testing XORP > code > To: Bruce Simpson > Cc: xorp-users at xorp.org, Marko Zec , zec at fer.hr > Message-ID: > > Content-Type: text/plain; charset="iso-8859-1" > > Hi > > This was probably IMUNES. Since I last touched IMUNES, I believe it is > being > ported rewritten for the FreeBSD Network Stack Virtualization Project: > > http://wiki.FreeBSD.org/Image > > >From the wiki: "The network stack virtualization project aims at extending > the FreeBSD kernel to maintain multiple independent instances of networking > state" > > I don't think it's ready for use in this incarnation yet and I'm not sure > that the previous instantiation (imunes) is supported. > > I have cc'd Marco Zec, the principle developer, as this information may not > be up-to-date. > > Any other options? > > > > Rae > === > > 2009/6/30 Bruce Simpson > > > Rae Harbird wrote: > > > >> > >> Hi > >> > >> > >> Does anyone have recommendations for emulating a small, simple network > of > >> XORP routers on a single Linux platform? I want to test my XORP code. > >> > > > > There is something out there that might wrap XORP in some kind of > > virtualization environment, although I can't remember what the name of > this > > thing is -- it was mentioned on this list in the last 12 months, a trawl > > through the list archives may help. Sorry, it's just a vague memory at > the > > moment. > > > > thanks, > > BMS > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090630/4e256ca0/attachment-0001.html > > ------------------------------ > > Message: 5 > Date: Tue, 30 Jun 2009 12:52:20 +0100 > From: Bruce Simpson > Subject: Re: [Xorp-users] Emulating simple network for testing XORP > code > To: Rae Harbird > Cc: xorp users > Message-ID: <4A49FC74.8000507 at incunabulum.net> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Rae Harbird wrote: > > Hi > > > > This was probably IMUNES. Since I last touched IMUNES, I believe it is > > being ported rewritten for the FreeBSD Network Stack Virtualization > > Project: > > I was actually thinking of a Linux based solution with a somewhat > obscure name :-) It had a XORP config generator, I think parts of it > were written in Python or possibly Ruby. > > I believe IMUNES should supported by the upcoming FreeBSD 8.0 release, > of course Marko would know more. > > Not sure if XORP integration is on the radar there, if at all. Major > code surgery is likely anyway, so if it did, it would probably be locked > to an earlier release. > > cheers, > BMS > > > > ------------------------------ > > Message: 6 > Date: Tue, 30 Jun 2009 08:46:58 -0700 > From: Ben Greear > Subject: Re: [Xorp-users] Emulating simple network for testing XORP > code > To: r.harbird at cs.ucl.ac.uk > Cc: xorp-users at xorp.org > Message-ID: <4A4A3372.1050404 at candelatech.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Rae Harbird wrote: > > > > Hi > > > > > > Does anyone have recommendations for emulating a small, simple network > > of XORP routers on a single Linux platform? I want to test my XORP code. > > > Our LANforge product uses a slightly modified xorp (and modified linux > kernel) to achieve this. Our main controller > code isn't open-source though, and to add support for new Xorp features > requires code changes to our product > (we do work for hire and general improvement of our products, and may be > willing to do work for free, > depending on the nature of the work). > > Our kernel patches (minus the impairment generator) are open-source and > freely available, as is my git tree of > xorp plus my changes. > > I can tell you though: It is not trivial to write a virtual router > framework. It took us several months and we already > had part of the work done, and the general framework in place. I'm > still debugging xorp too, it just barely deals with > dynamic network re-configuration, for example, but it's pretty solid > with a static network emulation (ie, no links between > routers coming and going.) > > We auto-generate perl scripts that do the linux stack configuration, and > we auto-generate the xorp config files. > If these things don't scare you, I'll be happy to a post simple example. > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > > > > ------------------------------ > > Message: 7 > Date: Tue, 30 Jun 2009 12:13:23 -0400 > From: Yue Li > Subject: Re: [Xorp-users] Emulating simple network for testing XORP > code > To: Rae Harbird > Cc: xorp-users at xorp.org, Marko Zec , zec at fer.hr > Message-ID: > <49567c360906300913w16cc311dkdcbb001d67e1136b at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > We have done this using OpenVZ and a network emulator PRIME on Linux. > Please check out the link below. > > http://www.primessf.net/pub/Public/WebHome/paper-xorpbgp.pdf > > > > On Tue, Jun 30, 2009 at 7:33 AM, Rae Harbird > wrote: > > > Hi > > > > This was probably IMUNES. Since I last touched IMUNES, I believe it is > > being ported rewritten for the FreeBSD Network Stack Virtualization > Project: > > > > http://wiki.FreeBSD.org/Image > > > > From the wiki: "The network stack virtualization project aims at > extending > > the FreeBSD kernel to maintain multiple independent instances of > networking > > state" > > > > I don't think it's ready for use in this incarnation yet and I'm not sure > > that the previous instantiation (imunes) is supported. > > > > I have cc'd Marco Zec, the principle developer, as this information may > not > > be up-to-date. > > > > Any other options? > > > > > > > > Rae > > === > > > > 2009/6/30 Bruce Simpson > > > >> Rae Harbird wrote: > >> > >>> > >>> Hi > >>> > >>> > >>> Does anyone have recommendations for emulating a small, simple network > of > >>> XORP routers on a single Linux platform? I want to test my XORP code. > >>> > >> > >> There is something out there that might wrap XORP in some kind of > >> virtualization environment, although I can't remember what the name of > this > >> thing is -- it was mentioned on this list in the last 12 months, a trawl > >> through the list archives may help. Sorry, it's just a vague memory at > the > >> moment. > >> > >> thanks, > >> BMS > >> > > > > > > > > > > _______________________________________________ > > Xorp-users mailing list > > Xorp-users at xorp.org > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090630/e234bf75/attachment-0001.html > > ------------------------------ > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > End of Xorp-users Digest, Vol 39, Issue 19 > ****************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090701/0f91f97f/attachment-0001.html From greearb at candelatech.com Mon Jun 29 16:51:28 2009 From: greearb at candelatech.com (Ben Greear) Date: Mon, 29 Jun 2009 16:51:28 -0700 Subject: [Xorp-users] Questions on multicast routing Message-ID: <4A495380.8040604@candelatech.com> I am trying to figure out why multicast is taking the 'long' way through the network. My network diagram is attached. The xorp output below is from router 2 (the top one). I am generating mcast traffic from Node2 interface to Node3. I would expect it to go through the link between R2 and R3, but instead it goes R2 -> R1 -> R3. My traffic flow is 64k, so I think it's using xorp user-space routing instead of setting up a kernel cache. I have hacked on multicast to support multiple routing tables, so it could be my bug, but I'd still appreciate any pointers to what might be going wrong if anyone has any ideas! I'll be happy to send any other information, just ask. root at nehalem> show pim `pim' is ambiguous. Possible completions: bootstrap Display information about PIM IPv4 bootstrap routers interface Display information about PIM IPv4 interfaces join Display information about PIM IPv4 groups mfc Display information about PIM Multicast Forwarding Cache mrib Display MRIB IPv4 information inside PIM neighbors Display information about PIM IPv4 neighbors rps Display information about PIM IPv4 RPs scope Display information about PIM IPv4 scope zones root at nehalem> show pim interface Interface State Mode V PIMstate Priority DRaddr Neighbors 1.2.2 UP Sparse 2 DR 125 10.1.2.2 1 2.3.2 UP Sparse 2 NotDR 125 10.2.3.3 1 br2 UP Sparse 2 DR 125 10.2.2.2 0 my_discard DISABLED Sparse 2 NotDR 1 0.0.0.0 0 register_vif UP Sparse 2 DR 1 10.2.2.2 0 root at nehalem> show pim mrib DestPrefix NextHopRouter VifName VifIndex MetricPref Metric 10.1.1.0/24 10.1.2.1 1.2.2 0 254 3 10.1.2.0/24 10.1.2.2 1.2.2 0 0 0 10.1.3.0/24 10.1.2.1 1.2.2 0 254 4 10.2.2.0/24 10.2.2.2 br2 2 0 0 10.2.3.0/24 10.2.3.2 2.3.2 1 0 0 root at nehalem> show pim rps RP Type Pri Holdtime Timeout ActiveGroups GroupPrefix root at nehalem> show pim rps RP Type Pri Holdtime Timeout ActiveGroups GroupPrefix 10.1.1.1 bootstrap 101 150 145 0 224.0.0.0/4 10.3.3.3 bootstrap 103 150 145 0 224.0.0.0/4 10.2.2.2 bootstrap 102 150 145 0 224.0.0.0/4 root at nehalem> show pim mrib DestPrefix NextHopRouter VifName VifIndex MetricPref Metric 10.1.1.0/24 10.1.2.1 1.2.2 0 254 3 10.1.2.0/24 10.1.2.2 1.2.2 0 0 0 10.1.3.0/24 10.2.3.3 2.3.2 1 254 3 10.2.2.0/24 10.2.2.2 br2 2 0 0 10.2.3.0/24 10.2.3.2 2.3.2 1 0 0 10.3.3.0/24 10.2.3.3 2.3.2 1 254 2 root at nehalem> show pim mfc Group Source RP 224.10.10.1 10.2.2.253 10.1.1.1 Incoming interface : br2 Outgoing interfaces: ....O root at nehalem> show pim neighbors Interface DRpriority NeighborAddr V Mode Holdtime Timeout 1.2.2 125 10.1.2.1 2 Sparse 105 99 2.3.2 125 10.2.3.3 2 Sparse 105 77 root at nehalem> show pim mrib DestPrefix NextHopRouter VifName VifIndex MetricPref Metric 10.1.1.0/24 10.1.2.1 1.2.2 0 254 3 10.1.2.0/24 10.1.2.2 1.2.2 0 0 0 10.1.3.0/24 10.2.3.3 2.3.2 1 254 3 10.2.2.0/24 10.2.2.2 br2 2 0 0 10.2.3.0/24 10.2.3.2 2.3.2 1 0 0 10.3.3.0/24 10.2.3.3 2.3.2 1 254 2 root at nehalem> [root at nehalem lanforge]# tshark -n -i 1.2.2 Running as user "root" and group "root". This could be dangerous. Capturing on 1.2.2 0.000000 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.145744 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.292327 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.441116 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.585402 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.730664 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.877894 10.1.2.2 -> 10.1.1.1 PIMv2 Register [root at nehalem lanforge]# tshark -n -i 1.2.1 Running as user "root" and group "root". This could be dangerous. Capturing on 1.2.1 0.000000 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.000001 00:f3:9d:ac:a5:fb -> 00:22:c0:12:1d:44 ARP Who has 10.1.2.1? Tell 10.1.2.2 0.000092 00:22:c0:12:1d:44 -> 00:f3:9d:ac:a5:fb ARP 10.1.2.1 is at 00:22:c0:12:1d:44 0.184021 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.361942 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.361944 10.1.2.2 -> 224.0.0.5 OSPF Hello Packet 0.361945 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.542985 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.723988 10.1.2.2 -> 10.1.1.1 PIMv2 Register 0.905965 10.1.2.2 -> 10.1.1.1 PIMv2 Register 1.089988 10.1.2.2 -> 10.1.1.1 PIMv2 Register 1.089990 10.1.2.2 -> 10.1.1.1 PIMv2 Register [root at nehalem lanforge]# tshark -n -i 2.3.2 Running as user "root" and group "root". This could be dangerous. Capturing on 2.3.2 0.000000 10.2.3.3 -> 224.0.0.5 OSPF Hello Packet 3.868836 10.2.3.2 -> 224.0.0.5 OSPF Hello Packet 10.033968 10.2.3.3 -> 224.0.0.5 OSPF Hello Packet 13.868846 10.2.3.2 -> 224.0.0.5 OSPF Hello Packet root at nehalem> configure Entering configuration mode. There are no other users in configuration mode. [edit] root at nehalem# show protocols { fib2mrib { } igmp { interface br2 { vif br2 { } } interface "1.2.2" { vif "1.2.2" { } } interface "2.3.2" { vif "2.3.2" { } } traceoptions { flag { all { } } } } ospf4 { router-id: 127.1.0.2 area 0.0.0.0 { interface br2 { vif br2 { address 10.2.2.2 { } } } interface "1.2.2" { vif "1.2.2" { address 10.1.2.2 { interface-cost: 2 } } } interface "2.3.2" { vif "2.3.2" { address 10.2.3.2 { } } } } } pimsm4 { interface br2 { vif br2 { dr-priority: 125 } } interface "1.2.2" { vif "1.2.2" { dr-priority: 125 } } interface "2.3.2" { vif "2.3.2" { dr-priority: 125 } } interface "register_vif" { vif "register_vif" { } } bootstrap { cand-bsr { scope-zone 224.0.0.0/4 { cand-bsr-by-vif-name: "br2" bsr-priority: 198 } } cand-rp { group-prefix 224.0.0.0/4 { cand-rp-by-vif-name: "br2" rp-priority: 102 } } } switch-to-spt-threshold { bytes: 1024000 } } static { interface-route 0.0.0.0/0 { next-hop-interface: "my_discard" next-hop-vif: "my_discard" } } } fea { unicast-forwarding4 { table-id: 10002 } } interfaces { interface "my_discard" { unreachable: true vif "my_discard" { } } interface br2 { vif br2 { address 10.2.2.2 { prefix-length: 24 } } } interface "1.2.2" { vif "1.2.2" { address 10.1.2.2 { prefix-length: 24 } } } interface "2.3.2" { vif "2.3.2" { address 10.2.3.2 { prefix-length: 24 } } } } plumbing { mfea4 { interface br2 { vif br2 { } } interface "1.2.2" { vif "1.2.2" { } } interface "2.3.2" { vif "2.3.2" { } } interface "register_vif" { vif "register_vif" { } } } } Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com -------------- next part -------------- A non-text attachment was scrubbed... Name: out.pdf Type: application/pdf Size: 114821 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090629/6675ad1f/attachment-0001.pdf