el 11-13-2024 11:45 AM
I have a host (eg 33.33.33.254) unable to reach HTTP server 192.168.0.3 (PUBLIC), but they are pinged.
¡Resuelto! Ir a solución.
el 11-13-2024 01:57 PM
el 11-13-2024 11:53 AM
Ping is very helpful but limited to connectivity. If you are trying to reach a HTTP server you need to check if the service is enabled on the target server, if there is no firewall or ACL in the path preventing you from get to the HTTP port on the server.
el 11-13-2024 12:03 PM
I don't know how to do it. I tried using ACL (on another project) to configure access to port 80, but nothing ever started working. Please help me with this
11-13-2024 12:07 PM - editado 11-13-2024 12:07 PM
what is it? PacketTracer? Or real device?
el 11-13-2024 12:14 PM
el 11-13-2024 12:34 PM
The problem is that you have two networks 192.168.0.0/24 on the topology. when you try to access the 192.168.0.3, HTTP server, the traffic is going to FILIA_1 and not to MAIN BULDING
You need to change the IP address in one of those segment.
el 11-13-2024 12:51 PM
11-13-2024 01:20 PM - editado 11-13-2024 01:21 PM
This one was interesting. Let me explain exactly what I have done.
First there was a connectivity problem. You have a default route on Rmb sending everything to 11.11.11.14 but you dont have dynamic routing protocol running between ISP1 and Rmb, so, the ISP1 router 5 does not know how to get to 192.168.0.0/24.
What I had to do is add a static route on ISP1 R5 sending the 192.168.0.0/24 to Rmb.
ip route 192.168.0.0 255.255.255.0 11.11.11.13
But now, you need to tell the rest of your router that the network 192.168.0.0/24 is on Rmb. So far, I only told to ISP1 router 5 about that.
For that, I did a redistribute static on OSPF in ISP1
router ospf 1
redistribute static subnets
This way, ISP1 advertized to the other routers where is the network 192.168.0.0/24.
Connectivity problem solved. But, it will not work yet. It turns out that you have NAT on the Rmb Router for exit traffic.
By doing the NAT, the routing does not work as expected. So, I remove the network 33.33.33.0 from NAT by denying the network on the NAT Access List. Bingo!! it works now.
ip access-list extended FOR-NAT
deny ip 192.168.0.0 0.0.0.255 192.168.1.0 0.0.0.255
deny ip 192.168.0.0 0.0.0.255 33.33.33.0 0.0.0.255
permit ip 192.168.0.0 0.0.0.255 any
!
!
el 11-13-2024 01:31 PM
Still doesnt work.
el 11-13-2024 01:34 PM
el 11-13-2024 01:42 PM
Please write "Write memory" on router and send me it again. Cuz i tried to write it in and it doesnt work
el 11-13-2024 01:57 PM
el 11-13-2024 02:12 PM
Thank you very much!
el 11-13-2024 01:00 PM
Descubra y salve sus notas favoritas. Vuelva a encontrar las respuestas de los expertos, guías paso a paso, temas recientes y mucho más.
¿Es nuevo por aquí? Empiece con estos tips. Cómo usar la comunidad Guía para nuevos miembros
Navegue y encuentre contenido personalizado de la comunidad