weird ping problem + can't ping from within router.

[paublo]

Ok this is weird problem at least to me. I have some PPPOE users terminating on a cisco 7200, on the same interface, that also does route-bridged on other sub interfaces.

the problem is from my desktop i can ping the PPPOE user's ip address with out any issues, same goes from outside my network.

However if i login to the router and i try to ping that ip address i get a request time out even though sh ip route shows this as a connected ip. In theory once im telnetted to the 7200 i should be able to ping the connected ip bypassing all ACL's NAT etc, correct?


any ideas what is going on here, i mean all is working but i cant figure out why i cant ping within the router.

thanks P

 

[paublo]

here more info is someone can take the time to help.

I have a 7200 terminating some pppoe customers using BBA-GROUP.
Everything is working and has been working without any issues. However digging around I came across a weird problem. It seems that from the 7200 terminating router I can't ping any of the pppoe user's ip addresses but I can from outside the 7200.

I'm using a BBA-GROUP that references Virtual-Template 1, the weird part is everything is working but my virtual-template shows that its down.

stingray-capedsl-gw#sh int virtual-template 1
Virtual-Template1 is down, line protocol is down

Should this interface not be showing as up/up? And is this the reason my I can't seem to ping from within the 7200.

Thanks P.


bba-group pppoe pppoeusers
virtual-template 1
service profile pppoeusers
sessions per-mac limit 1
sessions auto cleanup


interface Virtual-Template1
description xxxx
mtu 1492
ip unnumbered Loopback0
no ip redirects
no ip unreachables
peer default ip address pool pppoeuserspool
ppp authentication pap pppoeusers
ppp authorization pppoeusers
ppp ipcp dns xxxx
ppp ipcp address required
ppp ipcp address unique

interface Loopback0
no ip address
no ip redirects
no ip unreachables

ip local pool pppoeuserspool xxxx.2 xxxx.254

 

[paublo]

turns out that the virtual-template is going to show down/down because its not associated with a real interface. The problem with the pings was the loop0 which was being used by virtual-template didnt have an ip. once i put an ip it worked.