netreg Revisited

[sscdvp at gmail.com]

In 2011 I've opened ISC-Bug #23069 (Memory leak in handling OMAPI messages
OMAPI_OP_STATUS) and posted patch which solves OMAPI memory leak problem.
Patch is attached.

Serghei Samsi

2012/4/4 Randall C Grimshaw <rgrimsha at syr.edu>

> Ditto, with the exception that we did use omapi in a captive portal
> implementation which required custom coded middleware to work around a
> memory leak in omapi.... thus I feel justified in avoiding omapi when
> possible.
>
> Randall Grimshaw rgrimsha at syr.edu
> ________________________________________
> From: dhcp-users-bounces+rgrimsha=syr.edu at lists.isc.org[dhcp-users-bounces+rgrimsha=
> syr.edu at lists.isc.org] on behalf of John Wobus [jw354 at cornell.edu]
> Sent: Friday, March 25, 2011 10:34 AM
> To: Users of ISC DHCP
> Subject: Re: netreg Revisited
>
> We rolled our own system years ago that's pretty
> much as you describe netreg and we have never
> changed from restarting dhcpd to using OMAPI.  I was
> influenced by an on-list dhcpd developer comment that
> they'd like to replace OMAPI, and also I was
> uncomfortable with host configs in the lease file
> rather than the config file.  Also, by regenerating
> the entire config file, we easily eliminate the
> possibility of dhcpd and our database getting out
> of synch.  But obviously OMAPI's worked very
> well for many sites, who probably laugh at the
> hoops we jump through to avoid using it.
>
> We run a redundant pair and we restart dhcpd every 2
> minutes when there are config changes awaiting
> deployment.  I think we assist ISC by exercising
> dhcpd in a somewhat-extreme manner.
>
> John Wobus
> Cornell
>
>
> On Mar 22, 2011, at 12:27 PM, Martin McCormick wrote:
>
> >       Some years ago, Carnegie Mellon University built a
> > clever use of dhcp and DNS called netreg to authenticate clients
> > who wanted to connect to their networks. It looks like nobody
> > has done much to it since about 2005 and there is no mention of
> > failover or omapi. All updates are done the old fashioned-way.
> > Modify dhcpd.conf. Stop the server. Say a prayer and restart
> > dhcpd.
> >
> >       We've been asked to investigate netreg so I am asking
> > whether there is a modernized version that exists and makes use
> > of omapi for dynamic updates.
> >
> >       The original idea was that each network had a small pool
> > of dynamic leases with very short lifetimes. A client is sent to
> > the authentication server and, if approved, he gets put in to
> > the known pool. By using omapi, he could also be given a bootP
> > entry if the magic between authentication and approval can do
> > that.
> >       We are basically looking to make sure we don't re-envent
> > any good wheels that have already been proven to roll.
> >
> >       Thanks for all constructive ideas.
> >
> > Martin McCormick WB5AGZ  Stillwater, OK
> > Systems Engineer
> > OSU Information Technology Department Telecommunications Services
> > Group
> > _______________________________________________
> > dhcp-users mailing list
> > dhcp-users at lists.isc.org
> > https://lists.isc.org/mailman/listinfo/dhcp-users
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20120404/fc162cb8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dhcp-4.2.0-P2-omapi-messages-memleaks.patch
Type: application/octet-stream
Size: 1481 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20120404/fc162cb8/attachment.obj>