07-06-2010 09:04 AM
Hi , I have a Palo Alto 4020 . I have configured one of the interfaces as Layer 3 and also allowed Ping and telent on this interface . The IP given to this Layer 3 interface is 192.168.90.17 and its default gateway is the VLAN interface 192.168.90.1. Even when I connect a Laptop directly to the interface by giving the Laptop an IP of 192.168.90.18 I am unable to ping the Layer interface. I also dont see any Traffic hitting the firewall when viewing the monitor TAB .
07-07-2010 07:56 AM
Do you have a deny all rule towards to bottom of your rule set?
Basically this would be a rule that denys all traffic to any zones. The primary purpose of this rule is typically to log even the traffic that is being denied. Having this "deny all" rule also blocks intra zone traffic that is normally allowed by default.
By "intra zone" traffic, I mean traffic from zone A to zone A, traffic from zone B to zone B, etc....
The traffic that you are describing from the PC to the interface would be "intra zone traffic".
Also verify that your interface managment profile includes the IP of the pc in the "permitted ip addresses".....if you have "permitted ip addresses".
07-08-2010 03:51 AM
I have done all the thinngs you have asked for and the problem remains unresolved . Can you please help think of other alternatives / solutions
07-13-2010 07:47 AM
can you call into support when you have remote access? We will be able to isolate this issue rather quickly if we are able to troubleshoot live.
11-19-2010 07:32 PM
I also encoutered exactly the same problem and I am using Palo Alto 500, OS version 3.1.6.
Policy already allowed both direction on the same zone. Ping to L3 interface at palo alto request time out.
Any way out?
11-20-2010 10:41 AM
Have you created an Interface Management Profile that allows Ping and configured it on the L3 interface?
11-21-2010 05:51 AM
Thank you very much for the advice and it solved my problem.
I did not aware that management interface need to be created in order to be use.
12-02-2010 07:08 AM
I actually have the exact same problem (using 3.1.6), however what I found is that ping does work to a regular Layer 3 interface, it does not work on any of my logical interfaces (sub-interface). I do have an interface management profile for 'ping only' applied to all regular and logical Layer 3 interfaces.
12-07-2010 11:10 AM
if you are still having an issue with pinging the logical interfaces please create a support case and we'll set up a remote session to further debug.
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!