[Xorp-users] problem when ppp interface down

Ben Greear greearb at candelatech.com
Tue Dec 8 23:54:32 PST 2009


On 12/08/2009 11:31 PM, LE Hong Boi wrote:

> [ 2009/12/08 13:17:24 INFO xorp_pimsm4 PIM ] Interface stopped: Vif[ppp0] pif_index: 12 vif_index: 2 Flags: P2P MULTICAST MTU: 1492 DOWN IPv4 ENABLED
> [ 2009/12/08 13:17:24 WARNING xorp_igmp XrlMld6igmpTarget ] Handling method for mld6igmp/0.1/delete_protocol4 failed: XrlCmdError 102 Command failed Cannot delete protocol instance 'PIMSM_4' on vif ppp0 with vif_index 2
> [ 2009/12/08 13:17:24  FATAL xorp_pimsm4:5913 PIM +2217 xrl_pim_node.cc mld6igmp_client_send_add_delete_protocol_mld6igmp_cb ] Cannot deregister with the MLD6IGMP: 102 Command failed Cannot delete protocol instance 'PIMSM_4' on vif ppp0 with vif_index 2
> [ 2009/12/08 13:17:24 WARNING xorp_fea XrlFeaTarget ] Handling method for raw_packet4/0.1/send failed: XrlCmdError 102 Command failed Interface ppp0 is down
> [ 2009/12/08 13:17:24  ERROR xorp_rtrmgr:5888 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/pim/xorp_pimsm4": terminated with signal 6.
> [ 2009/12/08 13:17:24  INFO xorp_rtrmgr:5888 RTRMGR +299 module_manager.cc module_exited ] Module abnormally killed: pimsm4
> [ 2009/12/08 13:17:24  ERROR xorp_fea:5889 LIBXORP +226 buffered_asyncio.cc io_event ] read error 104
> [ 2009/12/08 13:17:24  ERROR xorp_fea:5889 XRL +169 xrl_pf_stcp.cc read_event ] Read failed (error = 104)
> [ 2009/12/08 13:17:24  ERROR xorp_fea:5889 XRL +378 xrl_pf_stcp.cc die ] STCPRequestHandler died: read error
> [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 192.168.24.1 to 224.0.0.2 on vif vmnet1
> [ 2009/12/08 13:17:24 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.24.1 to 224.0.0.13
> [ 2009/12/08 13:17:25 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.24.1 to 224.0.0.13
> [ 2009/12/08 13:17:26 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (0.0.0.0, 224.0.0.13) on vif vmnet1
> [ 2009/12/08 13:17:26  WARNING xorp_rtrmgr:5888 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/12/08 13:17:26  ERROR xorp_igmp:5912 MLD6IGMP +1106 xrl_mld6igmp_node.cc mld6igmp_client_send_add_delete_membership_cb ] XRL communication error: 201 Resolve failed
> [ 2009/12/08 13:17:27 INFO xorp_fea MFEA ] Interface deleted: ppp0
> [ 2009/12/08 13:17:27  WARNING xorp_rtrmgr:5888 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 "ifmgr_mirror-f81d1286737407c92dea75aaab3c6eed at 127.0.0.1" does not exist or is not enabled.
> [ 2009/12/08 13:17:27 INFO xorp_fea LIBFEACLIENT ] An error occurred sending an Xrl to "ifmgr_mirror-f81d1286737407c92dea75aaab3c6eed at 127.0.0.1".  Target is being removed from list of interface update receivers.
>
> Then pim stops working.
>
> The problem is similar when I replace ppp0 with eth0 (instead of disconnect PPPoE, I ifdown eth0): pim stops working.
> How to fix this problem?
> Thanks in advance.

I've fixed a bunch of similar issues in my xorp tree.  If you can compile your own
xorp, you might want to give it a try.  If it still fails, please send me a trace from
that and I'll see if I can fix it:

http://www.candelatech.com/oss/xorp-ct.html

Please note, this is based off of the upstream development tree, and I haven't done any solid
testing since the last merge, so it may be a bit touchy.  Let me know if you run into any troubles.

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com



More information about the Xorp-users mailing list