Ticket #19 (new Feature Request: None)

Opened 17 years ago

Last modified 12 years ago

Per user MAC address whitelisting

Reported by: benoitg Owned by:
Priority: normal Milestone: WifiDog Auth Server 2.0
Component: Auth server, Authentication, permissions and access control Version: Auth Server SVN
Keywords: Cc:

Description (last modified by max-horvath) (diff)

If enabled by the network, will allow a device with a specific MAC adress to be considered "logged-in" without a login page, probably under a different bandwidth policy than full token authentication. This may require some changes on the gateway.

Change History

Changed 17 years ago by max-horvath

Logged In: YES 

This feature has been implemented in the gateway, hasn't it?

So this feature request might be closed ...

Changed 17 years ago by benoitg

Logged In: YES 

No, the feature implemented in the gateway does not serve the 
same purpose.  This is meant, for example, for someone who 
has a WiFi phone and whant it whitelisted throughout the 

Changed 16 years ago by benoitg

  • version Long term deleted
  • component changed from Auth server: Features to Auth server: Features
  • description modified (diff)

Changed 16 years ago by max-horvath

Well, I like the idea as is ...

The most comfortable way would be if a registered user could enter say 2 or 3 MAC ids in his profile.

If whitelisting would be possible for the network administrator this could result too much work the more nodes and users a network gets ...

The only problem we have is, how to detect, if a user cheats. He could just enter the MAC id of his notebook and voila - he'd never see the login screen again ...

This is kinda though ...

Changed 16 years ago by max-horvath

  • owner nobody deleted
  • status changed from assigned to new
  • version set to Auth Server SVN
  • component changed from Auth server: Features to Auth server: Authentication
  • milestone set to WifiDog Auth Server 2.0

Changed 16 years ago by max-horvath

  • description modified (diff)

Changed 15 years ago by benoitg

  • component changed from Auth server: Authentication to Auth server, Authentication

Changed 14 years ago by anonymous

One way around this would be to add device classes. A user for instance wouldn't just add a mac address but "a sip device mac address". Sip devices will only be allowed to use ports used by the sip protocol. And other devices their respective protocol ports.

Note: See TracTickets for help on using tickets.