Ticket #76 (new Feature Request)

Opened 3 years ago

Last modified 5 months ago

TrustedMACList on auth server

Reported by: ray@gwinn.com Assigned to:
Priority: high Milestone: WifiDog Auth Server 1.1
Component: Gateway and Auth server Keywords:
Cc:

Description

Is it possible to consider moving the TrustedMACList to the wifidog server, or possibly having it on both server and client?

Logically, the server is the authenticater, and should it not authenticate mac and/or user name and password?

I have coded scripts to configure our nodes before they go into the field. As I add the code to implement wifidog into our remote nodes, I see/believe the TrustedMACList is going to be very long. In addition we have to update the TrustedMACList in an existing node before we can add a new node that routes through the existing node.

I suspect in all cases, the wifidog server is a computer that is much more capable of dealing with a long list of mac addresses. The server is also much more likely to be physically accessible if something goes wrong.

Ray

Attachments

Change History

02/22/06 11:19:52 changed by max-horvath

  • priority changed from low to high.
  • version set to Auth Server SVN.
  • milestone set to WifiDog Auth Server 1.1.

01/22/07 15:48:57 changed by benoitg

  • component changed from Auth server: Authentication to Gateway and Auth server.

05/18/08 05:27:35 changed by anonymous

We are working to nodes trust other first nodes (non-internet) will become trusted automaticly.

05/18/08 05:28:13 changed by anonymous

anonymous=ikerc wireless-fr.org

Add/Change #76 (TrustedMACList on auth server)