ILIA_93 wroteThe current problems that I found were:
1) Wrong subnet mask on beirut server (no nat translation for 0.0.255.255 "check access list entry")
2) beirut server connected to wrong port (Fa0/1 doesn't support VLANs)
3) rip on a stick doesn't advertise private lans: Basically this is how RIP protocol works: the router will advertise the network it has to the neighbor routers. Those neighbor routers will advertise their networks and "the networks they learned through all ports except the one they received the learned network on", so although router0 receives 192.168.2.0/24 and 192.168.0.0/24 on fa0/0, it won't rebroadcast these network out of this interface, hence beirut and saida routers won't learn about each other. A simple hack is to use a switch between the internet cloud and the router, and install one more ethernet port on the cloud. connect each port on the cloud to a port on the switch and configure DSL. Now when beirut broadcast its networks, it will reach both router0 and saida router and vice versa.
4) beirut and saida routers wouldn't translate the 71.0.0.0/8 to internal IPs :@ These motherf***ing routers won't translate the outside IP to internal IP although I can clearly see the entry in the nat translate table. Packet tracer just says that it doesn't have a translation entry for 71.0.0.x:xx in the nat table, but it's right there :@ I QUIT!!!!!!!!!!!!!!!
RAGE QUIT TROUBLESHOOTING! THANK YOU FOR HELPING ME PROCRASTINATE ALI :@ NOW I HAVE TO STAY UP UNTIL 5AM TO FINISH MY WORK
Thank you @ILIA_93 for taking the time to look at my network this was my first try and searching online has been a pain in the ass since there's nothing what so ever about troubleshooting packet tracer or even decent tutorials.
I will look into it more with your hints hope it works out.