- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
10-31-2024 12:12 PM
man now its pinging remote IP once i define source IP in PA fw.. 😞 feeling embarrassing
10-31-2024 11:39 AM
Hello,
According to the traffic logs, which policy is blocking the traffic? Are both interfaces, R1 and the Palo 192.168.1.2 in the same zone?
Regards,
10-31-2024 11:56 AM - edited 10-31-2024 11:56 AM
i need to enable logging first and will check there in traffic logs.
yes 1.1 and 1.2 are in INSIDE zone.
i just applied mgmt profile called ping now, I can ping from R1 to PA FW IP but from PA FW, i cannot ping R1 IP. its failing from fw
attached snapshots
10-31-2024 12:01 PM
Hello,
Add a security policy above the deny all one that allows traffic from internal zone to internal zone.
Regards,
10-31-2024 12:12 PM
man now its pinging remote IP once i define source IP in PA fw.. 😞 feeling embarrassing
10-31-2024 12:20 PM
Hello,
Please dont. Asking questions should never make you feel this way. Happy you got it working!
Regards,
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!