DHCP auto-auth

[bketelsen]

I was setting up my router for the 100th time and it dawned on me that the dhcp-auto-auth is limited to a Class C for auto-auth. Is there any way around this limitation? I need to do a captive portal, but don't want to force web authentication for customers that already exist. Without the dhcp-auto-auth, they'd have to open a web browser before they could check their POP3 email, correct?

Please let me know if I'm headed in the wrong direction or have made incorrect assumptions.

thanks,
Brian

[tony]

Unfortunately the dhcp auto-auth by design is limited to a single class-c.

[lonnie]

You can have the auto-auth and hotspot do a MAC based radius lookup and they are not required to have the web login. You can also put them in the whitelist file.

[bketelsen]

OK, I'm slightly confused now. Can I do DHCP auto-auth (what I really want is the radius lookup on the mac address) without being restricted to the single class C? Is the DHCP server part separate from the auto-auth part?

Please forgive my density. I'm trying to find a way to restrict ethernet traffic to authorized users only, and the auto-auth looked like the way to go, but I will likely have more than 253 users.

Am I on the right track or is there another way to skin this cat?

[lonnie]

Sure, you might have more than 253 users but not behind each and every interface. That is 253 IP addresses per interface. It would be poor network design to have that many users sharing an Ethernet port or Wireless card.

Auto-Auth was designed for distributed use and not central use.