Hello,
we change the javascript code for the portal detection.
If you create your custom portal page then it can be the issue.
Check that in your html page the call to detectNetworkAccess look like
that:
detectNetworkAccess.delay([% initial_delay %],
[% retry_delay %], "[% destination_url %]", "[% external_ip %]"
);
Regards
Fabrice
Le 2014-03-28 06:10, Monnier Fabrice a écrit :
Hello
I have a strange phenomenon with the network access detection.
Before I upgrade to 4.1.0 , I have used the public IP address of our
Web server for the parameter IP in the Captive Portal section (our
firewall don't let wifi's users to reach the packetfence server
sub-network).
The network detection was OK.
After the upgrade I have no detection (but the network is well
activated).
I have asked my firewall managers to temporaly authorize the IP
address of my PacketFence server as preconize in the configuration
section.
The detection is still failed, but I'm able to reach with my browser
the network-access-detection.gif image.
Is somebody have any clue to solve my problem ?
Or do you know in which packetfence file it's possible to change the
destination of that test ?
Thank you for your attention.
F Monnier
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
--
Fabrice Durand
[email protected] :: +1.514.447.4918 (x135) :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence
(http://packetfence.org)
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
