Unable to ping local (an remote) subinterface

[misa2]

Hello,
I presume that this is an old problem, but it already took a whole week out of my work.
Anyway, I can't ping both local FR subinterface and remote (ISP's). I can however ping local e0. There are no routing protocols at all. And there is another DLCI which is currently unused.
When i switch on packet debugging, i get packets from other networks, but they don't see my router's packets.
When i ping other hosts, it apperas that router sends them correctly, but they don't get any.
What am i missing?

Thanks


interface Serial0
no ip address
no ip directed-broadcast
encapsulation frame-relay IETF
frame-relay lmi-type ansi
!
interface Serial0.1 point-to-point
ip address 195.178.33.74 255.255.255.252
no ip directed-broadcast
frame-relay interface-dlci 101
--------------------------------------------------------
Serial0.1 (up): point-to-point dlci, dlci 101(0x65,0x1850), broadcast
status defined, active
--------------------------------------------------
DLCI = 101, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.1
--------------------------------------------------------
sh ip route: - got to be somewhere in here

Gateway of last resort is not set
195.178.63.0/29 is subnetted, 1 subnets
C 195.178.63.8 is directly connected, Ethernet0
195.178.33.0/30 is subnetted, 1 subnets
C 195.178.33.72 is directly connected, Serial0.1
--------------------------------------------------------
Router#ping 195.178.33.73
01:46:42: IP: s=195.178.33.74 (local), d=195.178.33.73 (Serial0.1), len 100, sending
01:46:42: ICMP type=8, code=0.
...
Success rate is 0 percent (0/5)
--------------------------------------------------------
Traceroute from

http://www.all-nettools.com:

I got these:

01:50:06: IP: s=216.92.131.153 (Serial0.1), d=195.178.33.74 (Serial0.1), len 40, rcvd 3
01:50:06: UDP src=46373, dst=33480
01:50:06: ICMP: dst (195.178.33.74) port unreachable sent to 216.92.131.153
01:50:06: IP: s=195.178.33.74 (local), d=216.92.131.153 (Serial0.1), len 56, sending
01:50:06: ICMP type=3, code=3

 

[jeter]

whats the ip address of the other end I assume its 195.178.33.73 or .74

What ever it is put in this route.

0.0.0.0 0.0.0.0 195.178.33.73
ip's subnet next hop

and do the same for the other router

0.0.0.0 0.0.0.0 195.178.33.74

this will give you a route between the routers.
you can also use rip, igrp, and eigrp. I would go with the
static route. Let me know if this works.
Jeter@LasVegas.com
J.Fisher CCNA

 

[misa2]

I already tried something like that. You see, .74 is my router and .73 is port on ISP's router. They can't put default network route to my network. Instead they should have route to my LAN via .74 router:
ip route 195.178.63.8 255.255.255.248 195.178.33.74
and .72/30 should be seen on their side as directly connected.
I, of course, have no authority over ISP's routing table. However, i am getting packets from other networks (thanks to "Code Red's" random scanning, so i am guessing that there must be a route in place to my network.
But i am trying to work on this one step-by-step. I would like to ping my local interface, then other router interface (on directly connected network).

 

[jeter]

thats correct now that you set me in the right direction.

show me a print of your interfaces.

C 195.178.33.72 is directly connected, Serial0.1

I really think that your isp has something setup incorrectly

Jeter@LasVegas.com
J.Fisher CCNA

 

[misa2]

yeah, I am thinking the same (blame ISP). My ISP runs Ahtena switch.

One more thing. I have another dlci (100) for currently inactive pvc. When that pvc were active (before they activated dlci 101) i haven't had any problems like pingig local and remote interface etc.
I will activate that pvc on tuesday, and we'll se if it is ISP's problem or mine.

Thanks again
Misa

 

[misa2]

Problem solved! It was bad encapsulation (should of been IETF). This stupid athena switch in combinaton with the router can not detect encapsulation change "on-the-fly". Therefore, when PVC was initialized, it used default encap (cisco), and router didn't recognize that. Any changes afterwards were futile.

It worked after complete reload of system software at telco's switch AND telco's router.

Thanks everybody, and jeter especially.

Misa