1

I have a project that includes a firewall and two routers. I have created two subnetworks with VLSM for both routers and I have a cable that represents a serial connection between them. The firewall should be between the internet and the first router that I have used. I have no trouble about pinging routers' ethernet interfaces and serial connections, I think my network is working well. However, I can connect to the Internet from firewall but cannot access it from the other routers. Here is my firewall and network configuration:

Firewall:

-Ethernet 0/1 is connected to the router-1 with a cat5 cable. This port's IP address is 10.1.1.30(You'll see it is a part of the network that is created for router-1) -Ethernet 0/0 is connected to the Internet.

Router-1:

-Ethernet 0/0 port has the IP 10.1.1.1/27 -Serial 0/0 port has the IP 10.1.1.81/30

Router-2:

-Ethernet 0/0 port has the IP 10.1.1.65/28 -Serial 0/0 port has the IP 10.1.1.82/30

PS:I have used RIPv2 on all devices.

Like I said, I can connect to the Internet from the fw but cannot from the routers. Thanks ^_^.

1
  • Did any answer help you? If so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you could provide and accept your own answer. – Ron Maupin Aug 11 '17 at 17:36
1

Just for clarity I am assuming your layout is:

Internet - FW - 10.1.1.0/27 - r1 - 10.1.1.80/30 - r2 - 10.1.1.64/28

You mention that you are running a routing protocol (RIPv2) on all devices. Assuming that includes the firewall and all things are configured correctly the firewall should have a route back to the other 2 networks (10.1.1.80 & 10.1.1.64). Can you confirm that you can ping these from the firewall?

You state that you can ping all interfaces on both routers but you don't specify the source you are pinging from.

You don't mention a default route in your routers so I will guess that is where the problem lies. If your routing protocol is operating properly your firewall is going to be a node hanging off of the 10.1.1.0 network. If you don't specifically tell R1 and R2 to utilize it as the default they won't. Here is a document on the Cisco website on the subject:

Gateway of last resort.

2
  • Gateway of last resort is 10.1.1.30 to network 0.0.0.0 10.0.0.0/8 is variably subnetted, 3 subnets, 3 masks C 10.1.1.0/27 is directly connected, Ethernet0/0 R 10.1.1.64/28 [120/1] via 10.1.1.82, 00:00:16, Serial0/0 C 10.1.1.80/30 is directly connected, Serial0/0 S* 0.0.0.0/0 [1/0] via 10.1.1.30 Ankara#ping 8.8.8.8 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) This is I see when I try to ping. – Fake Hesap Jun 25 '15 at 7:29
  • So that looks like route table and ping results from R1. If you can ping from FW to R2 then I think the problem must exist in your firewall. Does it have any capabilites to packet trace? I would start a packet trace on the inside interface and watch the packets arrive and then jump over to the outside interface to verify that the are arriving at the firewall but not being forwarded/routed/NATed. More than likely you will have a problem in one of those areas. – stephen muth Jun 25 '15 at 17:01
1

Firt of all. You need to review your policies on the way to permit the traffic from inside to outside, and on the contrary way.

If that is OK, then you can check if your firewall know your LAN networks. I think your firewall do not know how to reach your networks, you need to check if it is also running RIPv2, the same that routers.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.