With functional DHCP option 82 all you need to know is the MAC Address of the Client's CPE, which is good practice to keep anyhow. :)
On Tue, Oct 31, 2017 at 6:12 PM, Charles Boening <charl...@calore.net> wrote: > These guys are worth checking out. > > http://www.network1.net/products/dhcpatriot/ > > > It's essentially the same thing Jesse mentioned just in a commercial > product with some management wrapped around it. Linux underneath the hood > and a basic yet functional web UI. RADIUS integration, RADIUS forwarding, > local users, etc. It has captive portal functionality so you can identify > what username has what IP and MAC address. You can pre-auth users > (xbox/playstation only types out there) as well as suspend users with a > custom message. You can do static IP as well. They also have a basic API > so you can do some integrations. We supply routers so when we know the MAC > we pre-auth the customer. Makes a more seamless experience for the > customer. > > They support IPv6 as well. > > Happy to answer any questions. 😊 > > > Charlie > > > > > > > -----Original Message----- > From: Af [mailto:af-boun...@afmug.com] On Behalf Of Sterling Jacobson > Sent: Tuesday, October 31, 2017 1:00 PM > To: 'af@afmug.com' <af@afmug.com> > Subject: [AFMUG] DHCP Server Redundancy Survey > > I want to do a more flexible/standard setup for my DHCP handouts. > > I hand out public IPv4 and IPv6 dual stack to each customer router from > two main routers on my network. > > Is it best to create two redundant DHCP servers instead and use DHCP Relay > on-net to them? > > And how is everyone doing that? > > I'm guessing it's probably best to have those two redundant DHCP servers > be RADIUS controlled so billing systems can easily integrate with them. >
