PA not be able to access internet

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

PA not be able to access internet

L1 Bithead

Dear All, 

 

            I have a PA-1410 and the box do not have internet connectivity and below are the configuration, when i do trace route i see the next hop is showing 192.168.1.1 (mgmt interface) instead of 192.168.1.100  (ethernet1/1) and under monitor - taffic tab i do not see any traffic coming from trust to untrust, is it true that the PA rely on mgmt interface for internet access ? if i dont use mgmt interface any other method i could allow the PA access to internet ? any help would be appreicated 

 

ethernet1/1 - 192.168.6.1/24           untrust zone 

ethernet1/2 - 192.168.1.100/24           trust zone 

management interface - 192.168.1.1    <-- did not connect to any network switch 

 

static route - 0.0.0.0/0   ethernet1/1   next hop - 192.168.6.254 

 

 

security policy

piaakit_0-1721201899741.png

 

 

 

 

ping result to 8.8.8.8

admin@PA-1410> ping host 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 18ms

 

 

trace route to 8.8.8.8

admin@PA-1410> traceroute host 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 3088.883 ms !H 3088.848 ms !H 3088.847 ms !H

 

1 accepted solution

Accepted Solutions

Community Team Member

Hi @piaakit ,

 

@OtakarKlier means that your screenshot is showing 192.168.4.1 as the source address instead of 192.168.6.1 which is confusing.

 

The article you're referring to is a way to get your updates in case your management interface is out-of-band and has no route to the internet.  In that case you can use one of the other DP interfaces by configuring a service route.  So yes, that can work too.

 

The article also explains that you can download the updates using another connection and then upload the updates manually using the 'upload' feature.

 

Kind regards,

-Kim.

LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

View solution in original post

6 REPLIES 6

Community Team Member

Hi @piaakit ,

 

If you don't specify a source address then the ping will originate from your mgmt interface by default.

You'll have to specify the source address in your ping command.

 

For example:

 

> ping source 192.168.6.1 host 8.8.8.8

 

How to Designate Source Interface for the Ping Host Command 

 

Kind regards,

-Kim.

LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

Cyber Elite
Cyber Elite

Hello,

Also check the rouse address on your policy as I cannot tell if the IP Object is correct since it has a 4 instead of a 6.

 

Regards,

L1 Bithead

yes its could ping to 8.8.8.8 if i use the source interface, may i ask what means by IP Object 4 instead of 6 ? or is below article also work ? 

https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-get-updates-from-the-int...

 

piaakit

Community Team Member

Hi @piaakit ,

 

@OtakarKlier means that your screenshot is showing 192.168.4.1 as the source address instead of 192.168.6.1 which is confusing.

 

The article you're referring to is a way to get your updates in case your management interface is out-of-band and has no route to the internet.  In that case you can use one of the other DP interfaces by configuring a service route.  So yes, that can work too.

 

The article also explains that you can download the updates using another connection and then upload the updates manually using the 'upload' feature.

 

Kind regards,

-Kim.

LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

L4 Transporter

IP Object 4 instead of 6 it's referring that in your security policy it's mentioned source IP address the object called PA_192.168.4.1.

You should check the value of that PA_192.168.4.1 is 192.168.6.1 and maybe to rename that IP address object to help you see faster the value.

Cheers,
Cosmin

Don't forget to Like items if a post is helpful to you!
Please help out other users and “Accept as Solution” if a post helps solve your problem!

Read more about how and why to accept solutions.

Disclaimer: All messages are my personal ones and do not represent my company's view in any way.

L1 Bithead

sorry for my typo should be 192.168.4.1 instead of 6, and its works now after i configured server route configuration by enabling DNS and palo alto network services with untrust interface, thanks all of your help 

  • 1 accepted solution
  • 2097 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!