• January 23, 2021, 10:01:15 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Capative Portal  (Read 2930 times)

0 Members and 1 Guest are viewing this topic.

Offline newdud

  • Jr. Member
  • **
  • Posts: 30
Capative Portal
« on: March 03, 2014, 04:35:04 PM »

I have a RFS6010 and AP650 and Wings 5.4
We have a SSID for guest use with captive portal authentication.

We have a constant problem where by Apple users complain that they have to re-authenticate frequently :(.

The problem is worse with iPhone 5. I have seen connection where by after authentication the session time is set for 8hr but after a while it goes down to zero and on the captive portal user cache the authentication status is set to redirect i.e. after the device tries to connect it is sent to the portal for re-authentication  ???.

This problem only happens with only apple device, Android and PC are fine !

Below is part of the config, can any one shed any light on this ?

captive-portal CaptivePortal
 access-type logging
 access-time 480
 connection-mode https
 inactivity-timeout 28800
 server host wifi.xxx.org.uk
 server mode centralized
 simultaneous-users 200
 webpage-location advanced
 use aaa-policy VM-NAP
 use dns-whitelist DNS\ Whitelist
 wlan GUESTWifi
 description Guest User
 ssid GUESTWifi
 vlan 29
 bridging-mode tunnel
 encryption-type none
 authentication-type none
 wireless-client hold-time 28800
 wireless-client inactivity-timeout 28800
 wireless-client cred-cache-ageout 28800
 wpa-wpa2 psk 0 Jup1ter123456
 use aaa-policy AAA\ Internal\ Policy
 use captive-portal CaptivePortal

Offline TankII

  • Hero Member
  • *****
  • Posts: 556
Re: Capative Portal
« Reply #1 on: March 04, 2014, 10:44:26 AM »
Just a general comment:  Apple devices perform badly on the network.
We had to dedicate a separate router to handle DHCP requests on our Visitor network due to the way Apple requests DHCP leases.  I was seeing 14 request/second per device on average - on devices already connected and communicating through our Proxy server!  Since the gateway router was also handling DNS with DHCP, the box wound up with memory errors and rebooted a few times until we moved DHCP over to the separate router on the same network (Console access only).