Optimize Routing Table

[davidex95]

Hi, i'm writing becuase i have one problem to optimize the routers's routing table in this exercise, i already give at each subnet the correct ip and mask, now i have just to complete this task. Is important allow a full connetivity inside the network and with the web server. R0 and R1 seems work correctly but i'm not sure about the table aniway, and honestly i dont know what i should do with R3 and R4. Someone can help me and if is possible explain how do that for the future. 

I'm adding  a zip with the exercise.

[toj12]

Hey David, I wasn't able to ping the server from the hosts in this network (such as H1 and H2 > Server). Here are some ideas to optimize this network:

1.

Based on your topology, you're using Classless IP Addressing or VLSM (Variable Length Subnet Masking). In the real world you will need to be mindful of network expansion when using VLSM. Also to note, the IPv4 network in your topology is for a public network not private. But for this lab/experiment create a breakdown of subnets and usable addresses then setup the interfaces as you would for a private network

Excellent Practice based on your topology
Class C Network 200.0.62.0/24 (Public Network)
CIDR   Network Addr    Usable IP Address                        Broadcast Address    LAN
/26     200.0.62.0     >  200.0.62.1    - 200.0.62.62     <  200.0.62.63              Setup on R4
/27     200.0.62.64   > 200.0.62.65   - 200.0.62.94     <  200.0.62.95              Setup on R2
/27     200.0.62.96   > 200.0.62.97   - 200.0.62.126   <  200.0.62.127            etc...
/27     200.0.62.128 > 200.0.62.129 - 200.0.62.158   <  200.0.62.159
/27     200.0.62.160 > 200.0.62.161 - 200.0.62.190   <  200.0.62.191
/28     200.0.62.192 > 200.0.62.193 - 200.0.62.206   <  200.0.62.207
/28     200.0.62.208 > 200.0.62.209 - 200.0.62.222   <  200.0.62.223
/28     200.0.62.224 > 200.0.62.225 - 200.0.62.238   <  200.0.62.239
/28     200.0.62.240 > 200.0.62.241 - 200.0.62.254   <  200.0.62.255

2.
You're using static routing instead of routing protocols such as OSPF, EIGRP, or RIP. This ok but using one of the mentioned protocols is more manageable and time effective. For this lab this is good repetition for IP addressing and static routing

3.
The network topology you have is a Bus like network. If a connection fail between routers (such as R2 and R0), all hosts from SW-D, going left, will lose connection to the internet. A Mesh topology is best suited for optimization and redundancy.
As a guide when designing networks keep this in mind: OSI Northbound and Southbound Hierarchy Model (Core <> Distribution <> Access). As you get deeper into networks, you will notice the granularity within this model and more advanced areas when overseeing Multiple WANs (Management Plane <> Control Plane <> Data Plane)

4. LAN to WAN (Internet) - Private to Public IP addressing
Network Translation is necessary in the real world (also good practice in lab world) when connecting internal to external networks. On the Internet Router you can use:
PAT (Port Address Translation) or NAT (Network Address Translation)
PAT is more manageable, better network optimization

stay safe

[davidex95]

For first thanks for the answer, i didnt understnd everything cause i didnt study some of protocolos quoted by you yet. anyway i cant do any change at this network, is a project where the request is only set each subnet with ip and mask minimized and optimize the static routing table for each router. Anyway thanks for the help.

[toj12]

oh I was thinking that at first but my design thought kicked in when you  asked about optimization. 

I'll take another look at it again but the IPs look like they will overlap in one of the areas 

By the way, I mentioned 200.x.x.x, I should have said 220.x.x.x 

[davidex95]

About the ip on H subnets, honestly i was sure than were wrongs, but when i asked at my teacher him said than were correct. Seems strange because that subnet is really small so i was sure to did a mistake on the mask. I dont know what say.