Hello Fabrice,
in fact the device try to detect internet access by fetching the gif, so
it´s more from the production vlan are you able to reach the gif ?
By the way when something like that happen, i use wireshark to see what
happen exactly on the device and to check if the http on the gif is working.
Regards
Fabrice
Le 2014-04-01 06:54, Monnier Fabrice a écrit :
Hi
I've check with my firewall admins, http and https are ok to reach PF.
In fact it's seem that is PF that is not responding.
Do you in which log file I can look to find more information.
I also tried to change in pf.js the url from http to https but with no
success.
Regards
Fabrice Monnier
Le 28/03/2014 16:00, Monnier Fabrice a écrit :
I'll ask my firewall administrators what is the current configuration
on monday now
Thank you very much for your answers
Le 28/03/2014 15:44, Fabrice DURAND a écrit :
If you can reach the gif only in https and not in http with on the
normal vlan then it´s a network issue on your side (like a proxy).
Regards
Fabrice
Le 2014-03-28 10:39, Monnier Fabrice a écrit :
I've made the correction on one of my captives portals.
Now I have the correct number of parameters in the source of the
HTML page but it's still doesn't work.
During the tests I've made a new constatation : I can reach the
image @-PF/common/networt-access-detection.gif with https not with
http.
Thank you for your attention
Fabrice
Le 28/03/2014 13:56, Fabrice DURAND a écrit :
Ok so change the call of the function detectNetworkAccess in all
your template page. (/usr/local/pf/html/captive-portal)
Regards
Fabrice
Le 2014-03-28 08:52, Monnier Fabrice a écrit :
Ok I edit the source of the html page and found :
detectNetworkAccess.delay(12,
2,"http://www.ac-rennes.fr";, "", "PF-ip"
);
It seem that I have a problem with the number of parameters (5
instead of 4) with one empty .
I've checked if the redirection url http://www.ac-rennes.fr have
some double-quotes in the GUI -> no. Same for PF ip.
I don't know from where comes my "" parameter.
Le 28/03/2014 13:25, Fabrice DURAND a écrit :
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
------------------------------------------------------------------------------
_______________________________________________
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
------------------------------------------------------------------------------
_______________________________________________
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
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
_______________________________________________
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
