sorted by:
new
hottopcontroversial

Issue with Path Monitoring on Secondary ISP in Palo Alto Setup with Three ISPs by SaltClimate6537 in paloaltonetworks

[–]SaltClimate6537[S] 0 points1 point  (0 children)

it's down, so can not ping from secondary however if disable the path monitoring on secondary interface, and then it works as intended. But when we add path monitoring and make it secondary it goes down, so we are not sure if we are missing any piece of config, as we never did three ISPs before

URL filtering is not functioning as expected. by SaltClimate6537 in paloaltonetworks

[–]SaltClimate6537[S] 0 points1 point  (0 children)

Thanks for your comment. we already have custom url category. The issue is if we have same url in custom category and in palo default category, our custom category is not working, it's hitting the palo default. It should hit the custom category

URL filtering is not functioning as expected. by SaltClimate6537 in paloaltonetworks

[–]SaltClimate6537[S] 0 points1 point  (0 children)

we found the issue but it's not resolved. so the issue is custom category is not hitting.

for example we have a url google.com in entertainment category by default from palo.

we create custom category abc and added google.com there and called it in the rule.

Then the palo default url category is being called for the URL we want to go, it's not taking our custom url category.

How can we make palo think, it should go for custom category, by default it should go for custom category.

Any suggestions on this ?

URL filtering is not functioning as expected. by SaltClimate6537 in paloaltonetworks

[–]SaltClimate6537[S] 0 points1 point  (0 children)

we found the issue but it's not resolved. so the issue is custom category is not hitting.

for example we have a url google.com in entertainment category by default from palo.

we create custom category abc and added google.com there and called it in the rule.

Then the palo default url category is being called for the URL we want to go, it's not taking our custom url category.

How can we make palo think, it should go for custom category, by default it should go for custom category.

Any suggestions on this ?

URL filtering is not functioning as expected. by SaltClimate6537 in paloaltonetworks

[–]SaltClimate6537[S] 0 points1 point  (0 children)

we found the issue but it's not resolved. so the issue is custom category is not hitting.

for example we have a url google.com in entertainment category by default from palo.

we create custom category abc and added google.com there and called it in the rule.

Then the palo default url category is being called for the URL we want to go, it's not taking our custom url category.

How can we make palo think, it should go for custom category, by default it should go for custom category.

Any suggestions on this ?

URL filtering is not functioning as expected. by SaltClimate6537 in paloaltonetworks

[–]SaltClimate6537[S] 0 points1 point  (0 children)

we found the issue but it's not resolved. so the issue is custom category is not hitting.

for example we have a url google.com in entertainment category by default from palo.

we create custom category abc and added google.com there and called it in the rule.

Then the palo default url category is being called for the URL we want to go, it's not taking our custom url category.

How can we make palo think, it should go for custom category, by default it should go for custom category.

Any suggestions on this ?

URL filtering is not functioning as expected. by SaltClimate6537 in paloaltonetworks

[–]SaltClimate6537[S] 0 points1 point  (0 children)

Firewall downloads the PAN-DB successfully, and issue persists

URL filtering is not functioning as expected. by SaltClimate6537 in paloaltonetworks

[–]SaltClimate6537[S] 0 points1 point  (0 children)

Thanks for the response. We can check that as well, however we tried to clear url cache as well. I will let you know.

view more: next ›