change block page

Question

Hi, 
 
 In XG v15, the block page was set to http://172.16.16.16:8090/httpclient.html(network authentication) but in version v16 it was change to a block page (with link to network authentication) 
 
 Is there a way to use http://172.16.16.16:8090/httpclient.html again as block page, and use it as a captive portal. currently using v16. 
 
 TIA 
 
 Leo,

varunparikh · Accepted Answer

You got it correctly. 
 Upon the first time, a block page will be shown with link to captive portal. 
 From there onwards, the block page will be without a link to captive portal. That is the reason I insisted on behaviour change in XGv16 :) 
 You could post this in a separate thread as a feature request, for now, this is what we have. 
 Regards,

lferrara · Answer

Leo, 
 You can change this behavior under Authentication > services and look at the last part "captive portal" and change from block page to redirect. 
 Thanks

varunparikh · Answer

hi Leo 
 Please see the release notes for XG v16 here. XG Release 16.01.1.zip 
 In the PDF, Page 17 you can find this under known behaviour. 
 
 Hope this helps. 
 EDIT: Sorry that is page 18.

varunparikh · Answer

hi Luk 
 AFAIK when you enable match known users on a rule, the network rule would change to user based rule. 
 I tested this in my lab, it still shows me the block page with a link to login to captive portal. 
 Here's the advantage of enabling "Show captive portal to unknown users" on the firewall rule. 
 1. You do not need to create a seperate drop rule to show captive portal 
 2. You have selectively enabled captive portal. For an example, if I create a firewall rule from LAN (particular subnet) to WAN with match known users and show captive portal enabled, only those users of the particular subnet would get the captive portal. 
 Hope that helps.