problems with a stub network on Frame Relay network - TechRepublic
Question
September 10, 2009 at 12:14 PM
cg it

problems with a stub network on Frame Relay network

by cg it . Updated 16 years, 10 months ago

Working with a client that has a private frame-relay network. While there are no issues with the frame-relay network, they are trying to connect the frame-relay network to the Internet via a stub network. The stub is off a 3640 at one of the sites using an ethernet connection from the 3640 to the perimeter router, then off to the internet. Everyone on the frame-relay network [all subnets] can ping the ethernet interface on the 3640, but they can not ping the DSL perimeter router. eg packets are dropped at the 3640 ethernet interface that connects to their DSL router [the stub network].

Here’s a ip route table [RIP] from the 3640: Router#sh ip route
Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP
D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area
N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2
E1 – OSPF external type 1, E2 – OSPF external type 2
i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2
ia – IS-IS inter area, * – candidate default, U – per-user static route
o – ODR, P – periodic downloaded static route

Gateway of last resort is 192.168.X.X to network 0.0.0.0

172.16.0.0/24 is subnetted, 3 subnets
R 172.16.40.0 [120/1] via 172.16.20.2, 00:00:08, Serial0/0
R 172.16.30.0 [120/1] via 172.16.20.1, 00:00:09, Serial0/0
C 172.16.20.0 is directly connected, Serial0/0
173.55.0.0/16 is variably subnetted, 2 subnets, 2 masks
R 173.55.0.0/16 [120/3] via 172.16.20.2, 00:00:08, Serial0/0
R 173.55.107.0/24 [120/1] via 192.168.X.X, 00:00:16, Ethernet0/0
C 192.168.X.X/24 is directly connected, Ethernet0/0
S* 0.0.0.0/0 [1/0] via 192.168.X.X
is directly connected, Ethernet0/0

The 192.168.X.X directly connected to ethernet 0/0 is the stub network off to the DSL router. The DSL router has the 192.168.X.X subnet.

Note: you can ping yahoo from the 3640 …

Here’s the ip route table [RIP] from one of the sites :
Gateway of last resort is not set

172.16.0.0/24 is subnetted, 3 subnets
R 172.16.40.0 [120/1] via 172.16.20.2, 00:00:03, Serial0/0
C 172.16.30.0 is directly connected, FastEthernet0/0
C 172.16.20.0 is directly connected, Serial0/0
R 173.55.0.0/16 [120/3] via 172.16.20.2, 00:00:03, Serial0/0
R 192.168.X.X/24 [120/1] via 172.16.20.2, 00:00:03, Serial0/0
Router#

While the gateway hasn’t been set at the site they can ping the 3640 ethernet interface via the frame-relay network.

They advised me they set the gateway to the DSL perimeter router 192.168.x.x [1 hop away] eg o.o.o.o = 192.168.x.x and that didn’t work.

IP classless is running on all routers.

Any ideas why the stub network will not allow icmp ping from frame-relay sites to the perimeter router ?

note no ACLs on any router and no firewalls block icmp traffic. any host on any of the frame-relay sites can ping the ethernet interface on the 3640 which is the stub network and where the DSL perimeter router connect to. It appears that when icmp ping gets to the 3640 ethernet interface, it doesn’t forward them to the DSL router rather drops the packets.

This discussion is locked

All Comments