*** From dhcp-server -- To unsubscribe, see the end of this message. ***
> What you're asking for sounds awfully like what SPINACH does; see
> http://spinach.stanford.edu/spinach_info/
We implemented almost the exact same idea over 4 years ago for our public
labs. The router is a bridge though (KarlBridge) modified to do IP
filtering. The implementation is a bit dated (telnet interface to auth server,
SNMP V1 is used to get the src/dst/mask IP into the bridge, not enough logging...)
but still in use.
There have been a number of references on this list to a registration
process using DHCP which binds a hardware address to a user. We keep
logs of
IP to MAC address bindings from the router ARP tables and DHCP logs
MAC address to interface bindings from switch ports
Interface to physical location (where possible)
Minimally a few weeks of IP conversations from netflow exports
In most public areas IP to username using a filtering bridge --
user authenticates, dynamic filter times out after 15 minutes of
inactivity or logout.
Given that the user -> ethernet address mapping can be done without
forcing people to register, is it really worth the effort? Does
creating a long term binding from user to MAC address really make sense?
--
mark
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
