I have don't extensive testing and discovered that if a GlobalProtect Portal interface is addressed via DHCP it does not respond to HTTPS requests. It only responds if the Portal interface has a Static IP Address.
Can someone please help with why?
My device is working well.
This is what I configured on my PA-200 v4.1.8
ethernet1/1 is configured as DHCP client.
In GP Portal settings, I only select Interface and leave IP address as 'none'.
In GP Gateway settings, I configured same as above on Tunnel Gateway Address.
Just be careful, you have to enter exact IP address that eth1/1 will be assigned in external gateway list.
If you use dynamic IP address, you might need FQDN instead.
I apologize, I wasn't very clear in my previous post. I was so frustrated that I forgot a few items. You're correct, with the configuration you describe, yes, it does work however, only from the outside. Internal users still cannot connect to the GP Portal address when it is a DHCP IP address on the Portal interface. The other configuration I was trying was NATting GP Portal & Gateway connections to a Loopback interface. It works perfectly if the Public interface is a static IP address. Once I change it to a DHCP address, it will not respond to Portal or Gateway connections.
I tested on my unit.
As you say, I can't access to outside I/F from inside even I configure no NAT rule.
Hence if enable ssl management on outside I/F, I could access to https://outside IP address:4443/.
This means it might be a bug.
I think we need to open a case for further investigation.
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!