I understand that but he was looking for a way to track who was connecting to his network and pulling from the DHCP without knowing the MAC ID of the client. He wants to put a name to the client device, so to speak. Plain DHCP is fine but it's pretty faceless as you said, but with the client not passing any identifying information to him he has no way of knowing who is who.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of David E. Smith Sent: Thursday, October 08, 2009 5:12 PM To: WISPA General List Subject: Re: [WISPA] DHCP options Robert West wrote: > But it sounds like this has PPPoE written all over it. What is the barrier > to PPPoE? Maybe we can look at that end of it as well to see if the > objections to it can be weeded out. Not to push that but I think some would > at least like to know why things have been rejected. PPPoE requires the customer to do extra work, whereas DHCP (if implemented well) is basically zero-configuration to the end-user. They can buy a new PC, a new router, a new whatever, plug it in, and magic happens. Magic means they're not calling for support configuring a PPPoE client, which makes us happy. David Smith MVN.net ---------------------------------------------------------------------------- ---- WISPA Wants You! Join today! http://signup.wispa.org/ ---------------------------------------------------------------------------- ---- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
