Hi Alex, Yes, I did extended ping, but the result was the same.
The local MLPPP IP is on the same subnet as the remote IP, and the route is in the routing table. So it's <supposed to> work. This behavior is not observed in a Juniper router with similar configuration. So I thought it's something specific to Cisco. Regards, Sarah Zhao http://www.geocities.com/redoakland/ -----Original Message----- From: Alex Balashov [mailto:[EMAIL PROTECTED] Sent: Friday, August 24, 2007 4:02 PM To: Zhao, Wenmei (Sarah) Cc: [email protected] Subject: Re: [c-nsp] cannot ping MLPPP local IP address Are you inadvertently pinging it from a default source interface that cannot route to that IP address due to access lists, route maps, etc? Try "extended ping" options and specify your source address explicitly. On Fri, 24 Aug 2007, Zhao, Wenmei (Sarah) wrote: > Hi All, > > I have a MultiLinkPPP session up. Everything is working, > traffic is flowing and I am able to ping the remote side of the link, > but I can not ping the local MLPPP IP address. Is that intentional? > Or is there some other configuration prohibiting the ping? > > Regards, > Sarah Zhao > > http://www.geocities.com/redoakland/ > <http://www.geocities.com/redoakland/> > > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > -- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : +1-678-954-0670 Direct : +1-678-954-0671 _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
