HI Andy,
Seems like you have set the network detection IP to your own server.
That’s fine, but make sure these requests succeed.
If they fail you will see exactly the behaviour you described (timeout on
authentication).
When you register on the portal, that triggers a browser side javascript that
tries repeatedly to fetch a file from the network detection IP.
If it does not succeed before the timeout (5 seconds in your case) you will see
the issue you mentioned.
Check in the portal access logs to see if you get requests for
'network-access-detection.gif’ and what is the status of the reply (e.g. http
200 or other).
Regards,
--
Louis Munro
[email protected] :: www.inverse.ca
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
On Jun 23, 2015, at 11:41 , Andy A <[email protected]> wrote:
>
> [captive_portal]
> #
> # captive_portal.network_detection_ip
> #
> # This IP is used as the webserver who hosts the
> common/network-access-detection.gif which is used to detect if network
> # access was enabled.
> # It cannot be a domain name since it is used in registration or quarantine
> where DNS is blackholed.
> # It is recommended that you allow your users to reach your packetfence
> server and put your LAN's PacketFence IP.
> # By default we will make this reach PacketFence's website as an easy
> solution.
> #
> network_detection_ip=172.31.30.10
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
