Geir Holmavatn wrote:
> "prg" <(E-Mail Removed)> wrote
>
> > http://www.southwestern.edu/pipermail/netreg/
> > http://www.southwestern.edu/pipermai...er/001071.html
> > << help?
> >
> > If you allow something like this, then this may be the best way to go
> > as the MAC address is included as the clientID in the dhcp request.
> >
> > If you provide the computers just set up dhcp using the MACs. This
> > will provide a MAC/IP mapping. The registration of Netreg collects the
> > MAC in a similar fashion and does/can provide additional
> > authentication/authorization processes. I'm pretty sure that at least
> > some sites have added this capabilty.
> >
> > Once you have MAC/IP maps you can use Squid and Netfilter as you
> > require. You could further refine authentication and/or authorization
> > via ldap or radius. Then you could ... well, make this more
> > complicated than needed ;-)
> >
> > At the very least it should give you some ideas and maybe some
> > additional google terms to search for. It's been a year since I looked
> > at it.
> >
> > Let us know if this works for your situation.
>
> Hi again,
>
> Thanks a lot for your suggestion. NetReg looked interesting, albeit it has
> its shortcomings, not being very bulletproof.
>
> Before I test it further I just wonder if it exist commercial solutions of
> such software?
>
> I plan to use this with a Ubuntu server.
Well, I'm still not clear just what your primary, secondary, etc.
requirements are and at which points you need to "enforce" security
policy. Eg., are these student machines or do you own them? This
point is critical. Do you need now or maybe in the future to provide
for campus wireless access? Is controlling/monitoring web access your
_main_ concern along with ... what?
Problem you face is that educational institutions are viewed at two
levels: those with $ to spend like corporate and government profit
makers or those without that serve PR "community service" efforts.
Which are you? Do have a local LUG that can help you review your needs
and possible solutions?
Another question is _where_ you need the bullet proofing and what kind
are you willing to spend $ for and/or in house effort on. Personally,
I don't believe in "bullet proof" security as an achievement one
actually ever attains :-) Is your available expertise to setup and
maintain a solution "limited"? Do you _need_ a shrink-wrap, commercial
solution due to practical constraints?
Afaik, any of the "portal" registration/login schemes rely on a backend
authentication and authorization service, similar to wireless WAP (ie.,
something similar to EAP). Eg., a radius server together with an ldap
server or, joy-oh-joy, Kerberos. Probably just an ldap server like
OpenLdap would be enough to start.
The restriction of Ubuntu leaves me in the dark beyond OSS software.
Not aware of any commercial solutions down that road. If you could
consider Suse, I would tell you to look in that direction for a $
solution from Novell via eDirectory, etc.
Sorry not to be able to point you any further than these generalities
without more info.
regards,
prg