- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
01-30-2023 05:22 PM - edited 01-30-2023 05:26 PM
Hey All looking for some help on a VM Palo that lives on a dedicated ESX box
See attached diagram sorry if its confusing
ISP modem(192.168.10.1) --Palo WAN port ether1/1 using sub interface ether 1/1.10 (192.168.10.3)
Switch (VLAN1 192.168.10.2) --> Palo LAN Port on eth1/2 using sub interface eth 1/2.10 (192.168.10.4)
A machine on 192.168.10.X can ping 192.168.10.4 fine
I can log into the Palo fine at 192.168.10.4
Cannot ping the WAN interface at 192.168.10.3
Cannot get out to the internet
I think I have a routing issue but not sure where.
What static routes would I need on the virtual routers? I do no need 2 VRs since they are on the same subnet
VR 1 - default and contains the WAN interface
VR 2 - contains LAN interface
I realize I should move the Modem to a separate network, which I will do and the WAN interface. For now I am trying to get this working without having internet downtime. Any help is appreciated
Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.
01-31-2023 11:01 AM
Hi @ryansoto12 ,
Can you create a default route on the VR that has the internal and as the next hop, specify the other VR.
01-31-2023 02:31 PM - edited 01-31-2023 02:44 PM
Hey @JayGolf I have cleaned the mess up
Its as attached
From 192.168.10.X I cannot ping 192.168.10.1 (LAN interface on Palo) or 192.168.9.3 (WAN Interface on Palo)
Also why is the Palo picking up traffic at this point? I have nothing on the network with a Default Gateway as the Palo. Everything is still has a default gateway of 192.168.10.2 or 192.168.50.2 (Switch vlan IPs ) with a static route to the ISP at 192.168.9.1
Appreciate the time!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!