Hello Dominic,
You are right for the test for internet connectivity, all we do is
requesting a small gif from inverse.ca, it could be an issue with MacOS
which does not manage to renew it's IP in time, could also be a browser
cache issue.
You could try to raise up the redirection_timer for instance
(progression bar while getting redirected on the portal), under the
section trapping in configuration.
To be sure of the issue you should do a packet capture on one of the Mac
which have issue, and from there you should be able to see, if the issue
come from the address which is taking time to get renew or a browser
cache issue for instance.
Thanks
On 08/24/2016 08:26 AM, Dominic Kilbride wrote:
Hi Antoine,
Thank you for answering.
YES the CoA is properly applied and the client ends up in the production VLAN.
Im using VLAN enforcement.
It seems to be only the test that fails, despite the client being moved to the
correct Vlan with CoA. The Clint then displays the error text even though it is
connected to the internet as configured.
Im wondering how the connectivity test is run? I understand that if you are
using the default ip address then the clients web browser will try to fetch a
small img file from the inverse web server … But how is this done? Is this
compatible with all browser and client versions? Windows 10 is working great
for me but I’m having problems with MacOS.
Could it be a timeout problem? Like the client trys too early to get the image?
And the change to production Vlan occures later?
Any suggestions?
Best regards
Dominic
-----------------------------------------------------
Hellp Dominic
Is your CoA properly applied? Do you obtain an IP in your new VLAN
(production)?
Are you using VLAN or WebAuth enforcement type?
If VLAN enforcement, you could try to lower the DHCP lease in the
registration VLAN, to force an earlier re-auth.
Also make sure the configuration 'Allow AAA override' in the SSID
configuration on the WLC.
Thanks
On 08/23/2016 07:42 AM, Dominic Kilbride wrote:
> Hi all,
> Im running 6.2 on CentOS and am having the following problems.
>
> After successful registration and CoA on my Cisco WLC the client ends up at
> the …
> ‘Unable to detect network connectivity. Try to restarting your web browser or
> opening a new tab to see if your access has been successfully enabled.’
>
> Im an using the default method using the address of the inverse web server
> for the control. The test seems to be failing despite a working connection!
>
> Is there som time-out that can be adjusted? Can the detection method be
> bypassed as a workaround?
>
> Thanks in advance
>
> Dominic Kilbride
> ------------------------------------------------------------------------------
> _______________________________________________
> PacketFence-users mailing list
>[email protected]
<mailto:[email protected]>
>https://lists.sourceforge.net/lists/listinfo/packetfence-users
--
Antoine Amacher
[email protected] <http://inverse.ca> ::www.inverse.ca
<http://www.inverse.ca>
+1.514.447.4918 x130 :: +1 (866) 353-6153 x130
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu>) and
PacketFence
(www.packetfence.org <http://www.packetfence.org>)
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
--
Antoine Amacher
[email protected] :: www.inverse.ca
+1.514.447.4918 x130 :: +1 (866) 353-6153 x130
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
