Skip to main content
mumbles202
New Member
February 6, 2022
Question

Captive Portal

  • February 6, 2022
  • 1 reply
  • 2156 views

Is there a way to create a captive portal on my inside interface, then create an exception for the entire network and then allow people to redirect themselves to the portal? As in inside interface is 192.168.0.1/22 so enable the captive portal on the interface. Then create a bypass for the enitre /22 so users aren't redirected by default and just get  matched to the existing policies.

 But if a user needs to get authentication allow them to type in a URL that lands them on the FGT so they can authenticate. This is so they can authenticate against a backend LDAP server if they're using a device that doesn't allow them to sign in with domain creds.

1 reply

Debbie_FTNT
Staff & Editor
Staff & Editor
February 7, 2022

Hey mumbles,

if I remember correctly, your users could technically go directly to http://192.168.0.1:1000/fgtauth or https://192.168.0.1:1003/fgtauth to log in.

mumbles202
New Member
February 10, 2022

Thanks for this. I did some testing today with using it but had inconsistent results. I'll try it again tomorrow and post back.