• September 21, 2020, 08:05:14 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Mac Address Registration  (Read 6091 times)

0 Members and 1 Guest are viewing this topic.

Offline newdud

  • Jr. Member
  • **
  • Posts: 30
Mac Address Registration
« on: July 17, 2013, 07:04:38 PM »
Hi

I am running WINGS 5.4.1 on RFS6010. I updated to this version of the firmware from v5.3 mac address registration

The only doc that I can find on how to enable and use this feature is this PDF (WiNG_5.4_Feature_Guide_Analytics.pdf).

I am struggling to make this work in my setup  >:(

Has any one done this or can any one point in the right direction

Thanks in Advance


Offline Fido

  • Rookie
  • **
  • Posts: 20
Re: Mac Address Registration
« Reply #1 on: July 18, 2013, 05:29:18 AM »
Could you please explain in more detail what you want to do?
MAC registration of what? to where?

Offline newdud

  • Jr. Member
  • **
  • Posts: 30
Re: Mac Address Registration
« Reply #2 on: July 18, 2013, 06:36:57 AM »
We have a SSID for Guest use with no encryption. A user connects to the SSID opens a browser gets re-directed to a Captive Portal (CP) and has to authenticate (which is against our AD) and they are on.  This works well for PCs etc.

The issues is that for Smart Phones and Tables when the WiFi switches off due to inactivity it disconnects from the authenticated session and the user tries to re-connect, they are pointed to the CP again and go through the whole authentication process, which irritates them  >:(

I wanted to change the behavior of the the CP so that after successful authenticate the MAC address of the device and stored on the local RADIUS server for a set period of time, so when the user comes back with the same device they do not have to go via the CP authentication again since their MAC address is known  :).

This feature is described in various CLI and system Ref manuals

This process is also described in here (WiNG_5.4_Feature_Guide_Analytics.pdf  but for a different purpose.


Thanks




Offline noobie

  • Full Member
  • ***
  • Posts: 92
Re: Mac Address Registration
« Reply #3 on: July 22, 2013, 12:38:42 PM »
do you see this behavior with iOS devices? If so, then increase the "wireless client hold-time" in the WLAN settings to e.g. match the inactivity-timeout of your Captive Portal policy. By default it is 30 seconds and after any iOS device will suspend + this hold timer, CP session will be dropped and client will need to be reauthenticated.


Offline hchen01

  • Full Member
  • ***
  • Posts: 73
Re: Mac Address Registration
« Reply #4 on: July 23, 2013, 03:19:05 AM »
I wanted to change the behavior of the the CP so that after successful authenticate the MAC address of the device and stored on the local RADIUS server for a set period of time, so when the user comes back with the same device they do not have to go via the CP authentication again since their MAC address is known  :).

MAC-Registration need MAC authentication enable, if you are using radius, which means that you are using EAP authentication mode, so you can't enable MAC-Registration.

If you want to achieve your goal, you can set the the value of "inactivity timeout" suggested by "noobie" to the same value as "client access time":
configuration-->Services-->Captive Portals-->"name"-->client setting

Offline newdud

  • Jr. Member
  • **
  • Posts: 30
Re: Mac Address Registration
« Reply #5 on: July 23, 2013, 04:23:05 AM »
[quote
If you want to achieve your goal, you can set the the value of "inactivity timeout" suggested by "noobie" to the same value as "client access time":
configuration-->Services-->Captive Portals-->"name"-->client setting
[/quote]

This does not achieve my objective, as when a devices Wifi switches off or the user leaves the area covered by wifi, they leave authenticated session.
As such when the same devices comes back on it is forced to re-authenticate via the CP again. I am using simple RADIUS authentication with no accounting etc.

Offline noobie

  • Full Member
  • ***
  • Posts: 92
Re: Mac Address Registration
« Reply #6 on: July 23, 2013, 04:32:18 AM »
I am talking about wireless client hold-time, not inactivity timeout. Increase the hold-time under wlan settings to match inactivity timeout of the CP. This will solve your problem.

Offline newdud

  • Jr. Member
  • **
  • Posts: 30
Re: Mac Address Registration
« Reply #7 on: July 23, 2013, 05:03:55 AM »
I am talking about wireless client hold-time, not inactivity timeout. Increase the hold-time under wlan settings to match inactivity timeout of the CP. This will solve your problem.

This issue is not isolated to just iOS Devices, Android and Blackberry also exhibit this symptom as well.
This SSID is for guests, I would like them to be able to come into the building, connect to the WiFi and not have to alter the default setting on the device.

Offline noobie

  • Full Member
  • ***
  • Posts: 92
Re: Mac Address Registration
« Reply #8 on: July 23, 2013, 06:34:05 AM »
You don't have to do anything on the side of the client device itself. Please post config of your guest WLAN and Captive portal policy, would be easier to advise.

Offline newdud

  • Jr. Member
  • **
  • Posts: 30
Re: Mac Address Registration
« Reply #9 on: July 23, 2013, 08:11:41 AM »
You don't have to do anything on the side of the client device itself. Please post config of your guest WLAN and Captive portal policy, would be easier to advise.

My Apologies noobie  :(, I miss understood you suggestion. You meant, to change the 'wireless client hold time' on the WLAN SSID on the controller and not on the individual devices. This setting only appears to be available from the CLI and not on the GUI.

I have made the change and  indeed it does have the desired effect.  ;D

One question, I take it this change takes effect on the WLAN SSID only and not global ?

Offline noobie

  • Full Member
  • ***
  • Posts: 92
Re: Mac Address Registration
« Reply #10 on: July 24, 2013, 04:13:07 PM »
Glad it all worked:) Yes, correct, this is WLAN parameter which would apply only to a single WLAN/SSID, not globally, default value on newly created WLAN is 30 seconds.