Captive Portal with Vwire.

[clyde.franklin]

Why does below document advise we need a L3 interface  for captive portal? We are running solely vwire and I still get on form when testing. I do have repsonse pages setup as well

https://live.paloaltonetworks.com/t5/Configuration-Articles/Configuring-Captive-Portal-in-V-Wire-wit...

[kiwi]

Hi,

You are likely using Tranparent mode.

The document indicates it is using Redirect mode.

Cheers,

-Kim.

[clyde.franklin]

Thanks Kim I will change mode and retry

[clyde.franklin]

Just FYI changing mode did not work eiter I will spend some more time playing with it

[rmonvon · Accepted solution]

Hi...Captive Portal (CP) is typically implemented by redirecting the users to the CP page which is tied to an L3 interface.  The L3 interface will allow us to assign an SSL certificate to that interface IP because CP is encrypted in SSL to secure the user's credentials.   Make sure the L3 interface has a mgmt profile that allows response page & userID.

[clyde.franklin · Accepted solution]

Just to close loop in case anyone else runs into Issue. What can be done to rule out that a issue isnt related to Blue Coat Proxy (or any other proxy for that matter) Would be to view traffic logs and sort by destination country which will show you if you are hitting external website directy. In the event you never see external IP adress then you are  hitting a proxy. Equally modifying the URL filter and check x-forwarded-for will not change behavior either as the proxy may not have it enabled or blocking untrusted certs. So to my knowledge no way to bypass inline Blue Coat with Palo Alto ----Unless someone has tried.  This my reason for not getting CP page. I confirmed with TAC as well