Auth via MAC before login

[cdavis]

If a user exists in radius and I have auth via MAC before login set, does it require the user attempt any http traffic, or any traffic at all?

[tony]

The user requires http traffic first. If you use DHCP Auto-Auth (with radius option enabled), it will authenticate the session automatically without user intervention.

[cdavis]

And if I am seeing things correctly, dhcp auto auth will give the IP listed in the radius file if the IP exists, and an IP from the configuration otherwise. If the MAC is not listed it will still give an IP but only allow white list servers?

What will turning on ez client do to the users that are already setup with dhcp clients?

[tony]

eezee client will not interfere with users using dhcp, so if you assign an IP to them, they will continue to use it if you have eezee client enabled.

[cdavis]

Do I have something setup wrong or am I reading this wrong? It looks like it is changing my dhcp static IPs to ez client ip's

kernel: eth0: new eeZee client 00:04:5a:a3:a2:a7 10.0.0.18 -> 10.0.0.88
kernel: eth0: new eeZee client 00:e0:98:7f:b8:cf 10.0.0.28 -> 10.0.0.88
kernel: eth0: new eeZee client 00:00:39:1a:d8:9f 10.0.0.38 -> 10.0.0.88
kernel: eth0: new eeZee client 00:20:e0:69:46:b5 10.0.0.49 -> 10.0.0.82

[tony]

You may get these messages until the user successfuly gets a DHCP-based IP.

This would explain why it looks like many users are using 10.0.0.88 (which is released for re-use once the DHCP IP is assigned).

You can verify who is, and is not being handled by the eezee client, by looking at the eezee client lease list.

Note: If the eezee-based AP is reset, and the user is on DHCP, the eezee client may remap the user until such time as they renew their IP.

Thanks!