Azure - no traffic to untrust public ip

[dmarlow]

I've followed the instructions here and can't get traffic to my untrust public IP: https://www.paloaltonetworks.com/documentation/71/virtualization/virtualization/set-up-the-vm-series...

I'm using the Azure BYOL template (version 8.1) and can see my PA interfaces getting the proper azure NIC IPs as the document describes. I then setup a public IP for that untrust NIC and tried creating a GlobalProtect gateway and portal, but cannot get any traffic to the public IP to view the GP portal. I've tried just about everything I can think of, even making sure "firewalls" are all basically wide open. 

Basically, I'm just trying to setup a basic VPN from internet to an existing VNET, I don't understand the need for trust and untrust. I basically just want one external IP to allow users to connect to that then assigns an IP and routes into my Azure VNET. Any help appreciated.

[nicholajacobi]

I’m heading home very excited for what we’ve done for hockey, the NHL, the IIHF, Hockey Canada and all those junior players who would have missed out on a chance to play in a World Juniors Live Ice Hockey Championship.

[iam_2021]

@dmarlow @jperry1 

I am facing same issue on AWS, should I add a static route ? 

both untrust and trust interfaces are set for dhcp and an EIP is attached to the untrust interface

should I do any configuration on AWS side apart from adding route for private and public subnets 

[tostern]

@iam_2021 

Yes, you have to do may more configurations on the AWS side to make traffic flowing.

Please follow those guides:

https://docs.paloaltonetworks.com/vm-series/10-0/vm-series-deployment/set-up-the-vm-series-firewall-...

https://docs.paloaltonetworks.com/vm-series/10-0/vm-series-deployment/set-up-the-vm-series-firewall-...