Traffic can only take blue path.
There is no interconnection or routing between management module and dataplane (LAN on your diagram) inside Palo.
Packets from sourcing from management interface physically leave management interface to get to the destination.
Hi @young19918 ,
Using the command ping host <IP address> and you will automatically ping from your mgmt interface:
Hi @kiwi ,
Thanks for your reply.
I've tried this before, but had some problems ...... (as shown in the picture below)
These two red boxes show the source should be the same (mgmt), but one works and the other doesn't ......
And it can also ping the LAN port of the PA, why can't ping a server with port docking? (192.168.30.1)
Any help is appreciated.
In addition to what @OtakarKlier suggested, do you have ping enabled on the Data interface? Every interface has a Management Profile which lists the services that are allowed to run on that interface (except the Management interface which is handled a little bit differently). The interface Management Profile can be found under: Network-Interfaces->[interface_config]->Advanced->Other Info-Management Profile.
The Management Profiles define which services (ping, HTTP/HTTPS, SSH, etc.) can run on an interface and are configured from: Network->Network Profiles->Interface Mgmt
Is 10.2.100.54 your firewall management interface or have you enabled Interface Management profile on dataplane interface with IP 10.2.100.54?
ping host 220.127.116.11 (ping request goes out from mgmt interface)
ping source x.x.x.x host 18.104.22.168 (ping goes out from dataplane interface with IP x.x.x.x)
Well command "ping host 192.168.30.1" sends ping out from management interface.
Something needs to route from 10.2.100.x network to 192.168.30.x network.
Packet don't jump from management plane to dataplane inside firewall. Those packets will actually exit from management interface and need to be routed to different subnet to reach 192.168.30.1
In "Monitor > Traffic" you should see traffic from 10.2.100.54 to 192.168.30.1
If you don't then check that you have overridden interzone-default rule at the bottom of the ruleset and chosen "Log at session end".
If you see sessions but no return packets then OS firewall is blocking incoming ping.
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!