Error when pinging from one PC to another

[Yozhz]

I have this assignment where I need to make this work. I am new, and I've spent 5 days without understanding what I'm doing wrong and why it doesn't work. The topology must not be altered. I must use OSPF and change the addresses shown in the picture for the following:

Area 2 (Left)

Internal LAN: 192.168.100.0/24

Wireless Router WRT0 (LAN: 192.168.100.1 / WAN: 10.60.1.2)

Router R1 (Fa0/0: 10.60.1.1) → towards Area 0

Loopback R1: 10.10.10.1/30

Area 0 (Backbone)

Serial link R1-R0: 10.60.3.0/30

R1: 10.60.3.1

R0: 10.60.3.2

Area 1 (Right)

Internal LAN: 192.168.200.0/24

Wireless Router WRT1 (LAN: 192.168.200.1 / WAN: 10.60.2.2)

Router R0 (Fa0/0: 10.60.2.1)

Loopback R0: 10.10.10.2/30

I don't know what else it could be. My professor says it's the configuration, but I'm completely stuck.

Routing method used: OSPF All networks must be known and reachable via ICMP (Ping)

These are the default IPs that need to be changed

Additional Required Configurations

Interface loopback 0 - RouterID: 10.10.10.0/30

Wireless Router 0

LAN: 192.168.100.1/24

Internet (WAN): 167.78.80.5/25

Wireless Router 1

LAN: 192.168.100.1/24

Internet (WAN): 200.20.40.5/25

And I can only use the 192.168.x.x network for the LAN network specified in the file.

I am new and would like to understand better without overwhelming myself.

I can ping from right to left, but when it reaches WRT0 to enter, it doesn't pass, and viceversa

im new i this page sorry

[Joseph W. Doherty]

@Yozhz an excellent analysis summarization!

As the capabilities of the WRT300N, or lack there of (at least in the PT variant), appears to be the major issue, if that device were replaced with an "ordinary" router or L3 switch, you would have your 5 subnets, without blocking any traffic.  (NB: as the WRT300N supports L2 LAN ports, you would also need either wireless host end L2 switches [see next paragraph] or routers that also can provide L2 LAN ports [or a L3 switch].)  L3 replacements for the WRT300Ns, even in PT, likely could also run OSPF.

BTW, in the existing topologies, Switches 0 and 1 are unnecessary.  I.e. a direct Ethernet connection can be used between Routers 0 and 1 and their WRT300N counterparts (or their replacements).

Also BTW, I would love to see the instructors working version.

[DRC]

It's just a security measure for this computer I would have to switch PC to view file. However, I understand the NAT and filter statement on the WRT but cannot confirm with a simulation on my end.

When you see the packets leave from an source LAN to external device such as R1/R0. When walking the the trace does the source address pack of 192.168.X.X change at all to a 10.60.X.X?

I see you local R0/R1 interface are in OSPF process successfully but that does not explain how they know how to route to the other side of the serial link to reach those LAN networks. There is no gateway not is there a inter area route publishing the 192.168.X.X network. 

I could be missing something so I will look more into the routing path. 

[DRC]

Also, I noticed your topology has a internet address. The port you are currently plugged into for the WRT300N to the R1/RO router is an internet port. It does make sense that a implicit rule to block ICMP exist on that physical port since it is untrusted. However, I still think the fact you cannot remove is a problem with the app. 

I updated your topology and the pings work across the network. 

The first change is physical: Cross over cable between the WRT300N and R1/R0 using one of the ethernet 1-4 ports on the WRT. 

This allows the 192.168.X.X network to expand to the R1/R0. 

I made the fa0/0 interface on the routers 192.168.100.1 or 192.168.200.1 and added network statement to the OSPF config for each. 

Removed the 192.168.100.1 and 192.168.200.1 from the WRT and assigned a new address, as the PCs have Default GW as.1, so now they will send those external network ICMP packets in which the R1/R0 have those in the OSPF table . 

[Joseph W. Doherty]

Unable to view jpg attachment, but from what's described, yup that should work as you've changed the WRT300Ns into L2 switches that act as DHCP servers.  However, it's unclear to me what all the network requirements are, as I've only been able to download the one off Cisco attachment.

[Yozhz]

I was just watching, or rather trying to do, what he did, but I got lost. It looks like something I tried before, but it didn't work for me.

If he could send over the procedure he followed or the file so I can see what he did, that would be great, because I can't see the image either.

And regarding the versions, the Google Drive one is the exact same as the Mega one; I just switched download managers.

[DRC]

OK I will attach a screen shot for the ACL error if it works, I changed image file to .png. However, to see the issue with the ACL, you put pack tracer in Simulation. Send a ICMP request from Laptop 1 (192.168.100.x) to the 10.60.2.2 WRT300N.  You can see it when you click on the envelope as it traverses from one side to the other. Once it makes it to the WRT300N click on the envelope and look you in the "In Layers" Column you can see the below text. 

1. The receiving port has an inbound traffic access-list with an ID of 100. The device checks the packet against the access-list

2. The packet matches the criteria of the following statement: deny icmp any any. The packet is denied and dropped.

For the update I will break it down and attach my lab file. 

First issue is physical connection between the WRT300N and the Switch-PT should be a crossover cable not straight through. It is the cable has dashed line. When connecting the cable back to the WRT300N use the "ethernet ports" not the internet. In your current lab, there is no internet devices or active network that matches your original post ie. Internet (WAN): 167.78.80.5/25

Instead, what your network has connected is the LAN 192.168.X.0/24 and a trusted network 10.60.x.0/24 path to your next hop router over serial.

Second for the R1/R0 routers they would be assigned the the 192.168.100.1 or 192.168.200.1 IP address depending on which side to be the default GW for the LAN. I only did this to then have OSPF from each routers attach the 192.168.x.0/24 network to Area 1 or Area 2 go and redistribute the LAN across the Serial link Area 0. If not you need static routes in place, I mentioned before there is no current route in place for the LANs to reach one another. 

At this point you have your LAN network attached to the Access Points and to the respective R0/R1 fa0/0 interfaces all within their own 192.168.x.0/24 range. 

Third you would then update the OSPF network statement on each Router cause at this point we eliminated the 10.60.1.X and 10.60.2.X from the R1 and R0 router.

Lastly, that Internet interface being used on the WRT300N will not accept a ICMP request. Will it accept other traffic, yes I believe so. I assume that since ICMP is like a network monitor and query tool it could be deemed suspicious across the internet compared to a 443 request. If you want, try and setup a web server on a LAN PC and from the other LAN PC try to connect. This would be after proper routing is in place though since the LANs need to be setup above on the R0/R1 routers with OSPF or a static route like ip route 192.168.100.0 255.255.255.0 10.60.1.2 on R1 and 192.168.100.0 255.255.255.0 10.60.3.1 on R0

https://drive.google.com/file/d/18kKGWVvHSmFdLRbgWd_wUybZLZWBcNZv/view?usp=sharing

https://drive.google.com/file/d/1o6kmIsg9JjtsWaocSBBEWWs99434jES3/view?usp=sharing

[DRC]

I only changed the connected interface from the switch-PT and WRT300n to a crossover cable. Also, you can't see from screenshot but the WRT300N to the Switch-PT is using it's internet port, so since the WRT300N has four physical ethernet ports I used one of those instead. That is the issue with the ICMP is only outbound works on that internet interface and blocks inbound.

https://drive.google.com/file/d/18kKGWVvHSmFdLRbgWd_wUybZLZWBcNZv/view?usp=sharing